Sample Accessibility Audit Report

User impact

Keyboard and screen-reader users can move into content behind the open dialog and lose the relationship between the review task and available actions.

Reproduction evidence

1. Open the order review dialog from the payment step.
2. Press Tab repeatedly after focus reaches the final dialog action.
3. Focus moves to the page navigation behind the modal while the modal remains visible.

Remediation guidance

Use a native dialog implementation or a tested modal pattern. Move focus to a meaningful element when the dialog opens, constrain sequential focus while it is modal, support Escape where appropriate, and restore focus to the invoking control when it closes.

Verification requires retesting the corrected behavior in the agreed environment. A code change alone does not close the finding.

User impact

A screen-reader user receives no programmatic notification that submission failed or which fields need correction.

Reproduction evidence

1. Leave the postal code and city fields empty.
2. Activate Continue.
3. Visual error text appears, but focus remains on Continue and no status or error summary is announced.

Remediation guidance

Provide an error summary with links to invalid fields, move focus to the summary after unsuccessful submission, associate each field error using aria-describedby, and maintain aria-invalid until the value is corrected.

Verification requires retesting the corrected behavior in the agreed environment. A code change alone does not close the finding.

User impact

Speech-input users cannot reliably activate the option by saying the visible label, and screen-reader output differs from the text presented visually.

Reproduction evidence

1. Inspect the option labelled Pay by bank transfer.
2. Its accessible name is Transfer payment method.
3. The visible words Pay by bank transfer are not contained in the computed name.

Remediation guidance

Use the visible text as the control's accessible name. Prefer an associated native label and remove the conflicting aria-label unless additional context is genuinely required.

Verification requires retesting the corrected behavior in the agreed environment. A code change alone does not close the finding.

User impact

People using browser zoom must repeatedly scroll in two dimensions to compare item names, quantities, and totals.

Reproduction evidence

1. Set a 1280 CSS pixel viewport and zoom the browser to 400 percent.
2. Navigate to the order review step.
3. The summary table retains a fixed minimum width and creates horizontal page scrolling.

Remediation guidance

Replace the fixed-width layout with a responsive summary pattern. Allow labels and values to wrap, move secondary metadata below the item name, and test at an effective viewport width of 320 CSS pixels.

Verification requires retesting the corrected behavior in the agreed environment. A code change alone does not close the finding.