GatekeeperQA
GATEKEEPERQA

Accessibility assessment

Clear findings.
Practical next steps.

GatekeeperQA: FAIL

Prepared 2026-09-25 20:18:11 UTC

Executive summary

1 page(s) requested. 0 scan error(s). 1 confirmed rule violation(s), affecting 1 element occurrence(s). 0 rule check(s) need manual review (0 listed element occurrence(s)).

1 confirmed rule violation(s) affect 1 element occurrence(s). Start with critical and serious findings, then retest.

What to do next

  1. Fix the button name. Give the flagged button an accessible name that describes its action.
  2. Complete manual checks. Test keyboard, focus and screen-reader behavior, even when no checks are flagged.
  3. Rescan and compare. Retest the same page and state after changes, and keep manual test evidence alongside the reports.

Read the detailed testing checklist. An automated pass does not prove accessibility.

Confirmed findings by severity

Counts represent affected elements per rule; an element may appear under more than one rule. Manual-review items are counted separately.

1critical
0serious
0moderate
0minor
0unknown

Scope and method

Playwright and axe-core evaluated the initially loaded pages using WCAG 2.1/2.2 A/AA rule tags. Linked pages, authenticated journeys and interactions were not tested.

Automated checks cover only part of accessibility. PASS is a configured gate result, not WCAG or Section 508 certification. Manual review is required.

Tester overview

What to fix first

Start with scan errors, then critical and serious findings. Counts below are element occurrences, not unique elements. Review shared components before fixing each page separately.

  1. CRITICAL: A button needs an accessible name

    1 occurrence(s) across 1 page(s). Page 1

    Give the button clear visible text. For an icon-only button, provide an accessible name describing its action. Check it with a screen reader and rescan.

Why this gate result?

Quality gate: FAIL on serious, critical; WARN on minor, moderate, unknown. Unresolved checks cause WARN; scan errors or missing pages cause FAIL. Failed policy: 0 critical occurrences allowed (1 found). 0 scan error(s). Expected 1 pages; received 1.

Page-by-page coverage

Scanned pageRunConfirmed occurrencesReview checks
Page 1: http://127.0.0.1:62243/Completed10

Completed describes scan execution, not accessibility conformance. Review checks are unresolved automated checks, not completed human testing. Evidence and suggested fixes follow for each page.

Findings and remediation

Page 1: http://127.0.0.1:62243/

Checks needing manual review: 0

Confirmed finding - critical

A button needs an accessible name

Rule: button-name | 1 element occurrence(s)

Why it matters: Screen-reader users need to know what the button does.

Suggested fix: Give the button clear visible text. For an icon-only button, provide an accessible name describing its action. Check it with a screen reader and rescan.

Rule guidanceWCAG 4.1.2

Element locations and scan evidence

Locations are developer selectors, not visible page text. Each entry identifies an element in the scanned state.

  1. ["#checkout"]
    HTML (form values omitted):
<button id="checkout"></button>

Fix any of the following:
  Element does not have inner text that is visible to screen readers
  aria-label attribute does not exist or is empty
  aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
  Element has no title attribute
  Element does not have an implicit (wrapped) <label>
  Element does not have an explicit <label>
  Element's default semantics were not overridden with role="none" or role="presentation"

Manual testing checklist

Use this as a starting point, not a complete accessibility audit. These checks have not been completed by the scanner. Record the tester, date, page state, result and evidence separately.

  • Keyboard: reach and operate links, buttons, menus and forms without a mouse; check for keyboard traps.
  • Focus: confirm the focus indicator stays visible and moves in a meaningful order.
  • Screen reader: check headings, control names, instructions and error announcements.
  • Zoom and reflow: enlarge text and test a narrow viewport for lost content or overlapping controls.
  • Page states: check dialogs, validation errors and important user journeys that the initial-page scan did not exercise.

Recommended next steps

  1. Resolve execution errors, then address critical and serious confirmed findings.
  2. Review each unresolved check with a person; an unresolved result is not a confirmed failure or pass.
  3. Test keyboard navigation, focus order, screen-reader use and complete user journeys.
  4. Repeat the scan after fixes and retain the report alongside manual test evidence.

This report is automated test evidence. It is not a WCAG certification, legal opinion or completed VPAT/ACR.