Skip to main content
Access Audit

Remediation

Developer fix assistant

Each item explains the issue, affected users, implementation guidance, and tests to confirm the fix before rescanning.

CriticalOpen

Coupon dialog can trap keyboard focus

CouponDialog | 2.1.2, 2.4.3, 4.1.2

Plain English

When the dialog closes, send focus back to the button that opened it and remove hidden focusable content.

Accessibility impact

Users who cannot use a mouse need a predictable way to leave dialogs and continue checkout.

Framework-agnostic fix

Use a tested dialog primitive, hide inactive content with inert, close on Escape, and restore focus to the trigger.

const trigger = document.activeElement;
closeDialog();
if (trigger instanceof HTMLElement) trigger.focus();

Suggested tests

  • Open the dialog with Enter.
  • Press Escape and confirm focus returns to Apply coupon.
  • Tab through checkout and confirm focus does not loop.
Open FindingSchedule Re-scan
SeriousIn Progress

Low contrast promotional text

PromoBanner | 1.4.3

Plain English

Increase contrast between the banner text and its background.

Accessibility impact

The message becomes readable for people with low vision and many situational impairments.

Framework-agnostic fix

Use foreground and background tokens that meet at least 4.5:1 for normal text.

.promo-banner .muted { color: #0b2c4f; background: #e8f4f3; }

Suggested tests

  • Run axe color-contrast.
  • Verify computed contrast is at least 4.5:1.
Open FindingSchedule Re-scan
SeriousOpen

Email input missing accessible label

NewsletterForm | 1.3.1, 3.3.2, 4.1.2

Plain English

Add a real label that stays available to assistive technology.

Accessibility impact

Users can identify the control and complete the form with screen readers or voice commands.

Framework-agnostic fix

Associate a visible label with the input using htmlFor/id, or use aria-label only when a visible label cannot fit.

<label for="newsletter-email">Email address</label>
<input id="newsletter-email" name="email" type="email" />

Suggested tests

  • Inspect the accessibility tree.
  • Run axe label checks.
  • Submit with an empty value and confirm error is announced.
Open FindingSchedule Re-scan
Needs ReviewNeeds Review

Linked PDF requires manual accessibility verification

DocumentLink | 1.3.1, 2.4.2, 3.1.1

Plain English

Audit the PDF with a document accessibility workflow.

Accessibility impact

Users need the PDF content to preserve structure, reading order, and equivalent access.

Framework-agnostic fix

Check tags, headings, language, alt text, table headers, form fields, reading order, and metadata.

Suggested tests

  • Run PAC or Acrobat accessibility checks.
  • Test reading order with a screen reader.
  • Confirm a tagged PDF is available.
Open FindingSchedule Re-scan
ModerateOpen

Mobile filter chips have small touch targets

FilterChip | 2.5.8

Plain English

Increase the tappable area for compact filter controls.

Accessibility impact

Controls become easier to activate accurately on touch devices.

Framework-agnostic fix

Use min-height/min-width of 24 CSS pixels for WCAG 2.2 AA and larger spacing where possible.

.filter-chip { min-width: 2rem; min-height: 2rem; padding-inline: .75rem; }

Suggested tests

  • Run mobile viewport scan.
  • Measure target bounding boxes.
  • Test with browser zoom at 200%.
Open FindingSchedule Re-scan