GatekeeperQA
GATEKEEPERQA

Accessibility assessment

Clear findings.
Practical next steps.

GatekeeperQA: FAIL

Prepared 2026-09-25 12:00:00 UTC

Executive summary

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

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

What to do next

  1. Fix confirmed findings. Start with the missing form label, then the text contrast finding.
  2. Complete manual checks. Review the unresolved contrast check and test keyboard, focus and screen-reader behavior.
  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
1serious
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.

Illustrative sample using synthetic findings, not a live scan or customer assessment. Automated checks do not certify accessibility. 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 form field needs a label

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

    Connect a clear visible label to the field, such as a label with a for attribute matching the input id. Do not use placeholder text as the only label.

  2. SERIOUS: Text is difficult to read against its background

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

    Adjust the text or background color. Aim for at least 4.5:1 for normal text, or 3:1 for large text (24px, or about 19px bold). Check the rendered colors, including opacity and gradients, then rescan.

Page-by-page coverage

Scanned pageRunConfirmed occurrencesReview checks
Page 1: https://example.com/contact/Completed21

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: https://example.com/contact/

Checks needing manual review: 1

Confirmed finding - critical

A form field needs a label

Rule: label | 1 element occurrence(s)

Why it matters: People using assistive technology need to know what information to enter.

Suggested fix: Connect a clear visible label to the field, such as a label with a for attribute matching the input id. Do not use placeholder text as the only label.

Rule guidance

Element locations and scan evidence

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

  1. ["#email"]
    Example evidence: this field has no associated accessible label.

Confirmed finding - serious

Text is difficult to read against its background

Rule: color-contrast | 1 element occurrence(s)

Why it matters: People with low vision may struggle to read faint text.

Suggested fix: Adjust the text or background color. Aim for at least 4.5:1 for normal text, or 3:1 for large text (24px, or about 19px bold). Check the rendered colors, including opacity and gradients, then rescan.

Rule guidance

Element locations and scan evidence

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

  1. [".help-text"]
    Example evidence: gray helper text has insufficient contrast against its background.

Needs manual review

These checks are unresolved. They are not confirmed failures and are not counted in the severity totals.

Needs manual review - not a confirmed failure

Review: text contrast

Rule: color-contrast | 1 element occurrence(s)

Why it matters: The automated scan could not decide this check. This is not a confirmed failure.

How to review: Inspect each listed element in the browser. Measure contrast against the background behind the text, including gradients and opacity. Decide whether short separators convey information. Record the outcome and supporting evidence.

Rule guidance

Element locations and scan evidence

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

  1. [".hero-title"]
    Example evidence: a background image prevents an automated contrast decision.

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.