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 guidanceElement locations and scan evidence
Locations are developer selectors, not visible page text. Each entry identifies an element in the scanned state.
["#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 guidanceElement locations and scan evidence
Locations are developer selectors, not visible page text. Each entry identifies an element in the scanned state.
[".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 guidanceElement locations and scan evidence
Locations are developer selectors, not visible page text. Each entry identifies an element in the scanned state.
[".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
- Resolve execution errors, then address critical and serious confirmed findings.
- Review each unresolved check with a person; an unresolved result is not a confirmed failure or pass.
- Test keyboard navigation, focus order, screen-reader use and complete user journeys.
- 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.