Fictional sample / Audit reporting
Illustrative Website Accessibility Findings
Example Public Portal — fictional website and findings
Fictional demonstration report. No website was assessed for these findings, and this is not a statement of conformance or a completed paid audit.
What a scoped report can explain
An actual audit documents observed barriers, where they occur, their user impact, applicable success criteria, recommended changes, and retesting evidence. The examples below are invented to demonstrate format and clarity.
FINDING 01 / HIGH IMPACT — ILLUSTRATIVE
Keyboard focus is not visible on navigation links
- Example
- Fictional navigation: a keyboard user tabs to a link without any visible indicator.
- Why it matters
- Users navigating without a mouse cannot confidently identify their location.
- Reference
- WCAG 2.1 success criterion 2.4.7 — Focus Visible.
- Recommendation
- Add a high-contrast
:focus-visibleoutline that is not removed by other styles. - Retest
- Tab through the links at desktop and mobile widths and confirm the focused element is visible.
FINDING 02 / HIGH IMPACT — ILLUSTRATIVE
A form field has no accessible name
- Example
- Fictional service request form: an email input uses only a placeholder.
- Why it matters
- Screen-reader users may not hear the intended purpose once the placeholder disappears.
- Reference
- WCAG 2.1 success criterion 3.3.2 — Labels or Instructions.
- Recommendation
- Associate a persistent visible
<label>with the input usingforandid. - Retest
- Check accessible-name exposure with a screen reader and submit an incomplete form to evaluate feedback.
FINDING 03 / MODERATE IMPACT — ILLUSTRATIVE
A visual list lacks list semantics
- Example
- Fictional meeting page: agenda items are plain paragraphs preceded by decorative numbers.
- Why it matters
- Assistive technology cannot announce the list structure or number of items.
- Reference
- WCAG 2.1 success criterion 1.3.1 — Info and Relationships.
- Recommendation
- Use semantic
<ol>and<li>elements in logical source order. - Retest
- Verify announcements and order using keyboard and a screen reader.
Handoff expectations
A real engagement should distinguish an automated scan from an agreed manual audit scope, list what was not tested, and retain observations sufficient for a developer to reproduce each issue.
Every finding here is invented. Severity categories are illustrative, not results from automated scanning or live user testing.