- Template
- 2.5Rev
- Edition
- WCAG
- Report date
- 2026-11-05
/ Example report · WCAG
Glimmerbank Developer Docs (fictional product): example Accessibility Conformance Report
Example report for a fictional product. 50 criteria reported at Levels A and AA (WCAG 2.1 rows): 27 Supports, 16 Partially Supports, 2 Does Not Support, 5 Not Applicable. The gaps that matter most are the GIF demonstrations that cannot be paused, single-key shortcuts that cannot be turned off, diagrams without text alternatives and the reference layout that does not reflow.
Example only. Glimmerbank Developer Docs (fictional product) is a made-up product, and every finding below is invented to show how a filled report reads. It is not a report on any real product.
- Product
- Documentation website
- Scope
- Example report for an invented company; Glimmerbank and its documentation do not exist. Covers the public developer documentation at docs.glimmerbank.example as deployed on 2026-10-30: guides, the API reference for API version 3, the interactive API console against the sandbox, search, the changelog and the Japanese translations of the guides. The community forum and the signed-in dashboard are out of scope. Standards covered: WCAG 2.0 and 2.1, Levels A and AA. WCAG 2.2 is not covered.
- Evaluation methods
- Manual testing of all page templates (guide, reference endpoint, changelog, search results, console) and of a sample of 45 pages chosen to include every component, by an accessibility tester and a technical writer. Keyboard only; NVDA with Firefox; VoiceOver with Safari on macOS and iOS; zoom to 400 percent; light and dark themes. Automated checks with axe-core on every page in the sitemap.
- What it shows
- A report may leave out the WCAG 2.2 rows if it says it covers 2.0 and 2.1 only, as the template allows. It then has to say so plainly, because a buyer asking about WCAG 2.2 will see the gap at once. Not Applicable is used only where the remark can say why.
Table 1: Success Criteria, Level A
| Criteria | Conformance level | Remarks and explanations |
|---|---|---|
| 1.1.1 Non-text Content | Partially Supports | Logos and icons have text alternatives. Architecture diagrams on 23 of the 40 guide pages are SVG images with no text alternative or prose equivalent. |
| 1.2.1 Audio-only and Video-only (Prerecorded) | Not Applicable | The site contains no audio-only or video-only content. The animated GIFs carry no information that is not also in the text beside them. |
| 1.2.2 Captions (Prerecorded) | Partially Supports | The four product walkthrough videos have edited captions. The embedded conference talks use automatic captions that have not been reviewed and contain errors in code terms. |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) | Partially Supports | Walkthroughs have transcripts. Conference talks have neither a transcript nor audio description. |
| 1.3.1 Info and Relationships | Supports | Parameter tables use header cells, code samples are marked as code, and heading levels are nested correctly. |
| 1.3.2 Meaningful Sequence | Supports | Reading order matches the visual order in the three-column reference layout. |
| 1.3.3 Sensory Characteristics | Supports | Instructions do not rely on shape, position or sound. |
| 1.4.1 Use of Color | Partially Supports | HTTP method badges carry text. In the changelog diff view, added and removed lines are marked only by green and red backgrounds. |
| 1.4.2 Audio Control | Not Applicable | No audio plays automatically; the animated GIFs have no sound. |
| 2.1.1 Keyboard | Partially Supports | The Body and Headers tabs of the API console response panel cannot be reached with a keyboard. Everything else can. |
| 2.1.2 No Keyboard Trap | Supports | In the console's request editor Escape releases focus, and the instruction is shown above the editor. |
| 2.1.4 Character Key Shortcuts | Does Not Support | Pressing / focuses search and j and k move between sections. These single-key shortcuts cannot be turned off or remapped, and they are active everywhere except in text fields. |
| 2.2.1 Timing Adjustable | Supports | No time limits on reading or on the console. The sandbox key expires after 24 hours, longer than the 20-hour exception, and can be regenerated. |
| 2.2.2 Pause, Stop, Hide | Does Not Support | Animated GIF demonstrations in the guides start automatically, loop indefinitely and cannot be paused, stopped or hidden. |
| 2.3.1 Three Flashes or Below Threshold | Supports | No content flashes more than three times per second. |
| 2.4.1 Bypass Blocks | Supports | A skip link and landmarks on every page. |
| 2.4.2 Page Titled | Supports | Titles name the page and the API version. |
| 2.4.3 Focus Order | Supports | Focus order is logical, including in the search overlay. |
| 2.4.4 Link Purpose (In Context) | Partially Supports | Older guides contain links named "here" whose purpose is not clear from the sentence around them. |
| 2.5.1 Pointer Gestures | Supports | No function needs multipoint or path-based gestures. |
| 2.5.2 Pointer Cancellation | Supports | Actions run on release. |
| 2.5.3 Label in Name | Partially Supports | The version switcher shows "v3" but its accessible name is "Select API version", which does not contain the visible text. |
| 2.5.4 Motion Actuation | Not Applicable | No function is operated by device motion. |
| 3.1.1 Language of Page | Supports | English and Japanese pages declare their language. |
| 3.2.1 On Focus | Supports | No change of context on focus. |
| 3.2.2 On Input | Partially Supports | Choosing a version in the version switcher loads the matching page for that version immediately, with no prior notice. |
| 3.3.1 Error Identification | Supports | The console validates request JSON and names the line and the problem in text. |
| 3.3.2 Labels or Instructions | Supports | Console fields and the feedback form have visible labels. |
| 4.1.1 Parsing | Supports | Per the September 2023 errata to WCAG 2.0 and 2.1, this criterion is always supported for content in HTML or XML. |
| 4.1.2 Name, Role, Value | Partially Supports | Search suggestions are not exposed as a list of options, and the language tabs on code samples lack tab roles and selected state. |
Table 2: Success Criteria, Level AA
| Criteria | Conformance level | Remarks and explanations |
|---|---|---|
| 1.2.4 Captions (Live) | Not Applicable | The site has no live audio or video. |
| 1.2.5 Audio Description (Prerecorded) | Partially Supports | The walkthrough narration describes what happens on screen. Conference talks have no audio description. |
| 1.3.4 Orientation | Supports | Pages work in both orientations. |
| 1.3.5 Identify Input Purpose | Supports | Name and email in the feedback form carry autocomplete values. |
| 1.4.3 Contrast (Minimum) | Partially Supports | Comments in code samples measure 3.4:1 in the light theme. The dark theme and all other text pass. |
| 1.4.4 Resize Text | Supports | Text resizes to 200 percent without loss of content or function. |
| 1.4.5 Images of Text | Partially Supports | Two older tutorials show terminal output as screenshots rather than text. |
| 1.4.10 Reflow | Partially Supports | Guides reflow at 320 CSS pixels, and code blocks scroll inside their own box. The API reference keeps its three columns and needs horizontal page scrolling at that width. |
| 1.4.11 Non-text Contrast | Supports | Controls and focus indicators meet 3:1. |
| 1.4.12 Text Spacing | Partially Supports | With increased letter spacing, the parameter type labels in the reference are cut off. |
| 1.4.13 Content on Hover or Focus | Partially Supports | Hovering a parameter name opens a definition popup that cannot be dismissed with Escape. |
| 2.4.5 Multiple Ways | Supports | Pages can be found through navigation, search and the sitemap. |
| 2.4.6 Headings and Labels | Supports | Headings and labels describe their topic or purpose. |
| 2.4.7 Focus Visible | Supports | Visible focus on every interactive element in both themes. |
| 3.1.2 Language of Parts | Supports | Japanese error strings quoted on English pages are marked with their language. |
| 3.2.3 Consistent Navigation | Supports | Navigation is consistent across pages. |
| 3.2.4 Consistent Identification | Supports | Copy buttons, version switchers and feedback controls are identified consistently. |
| 3.3.3 Error Suggestion | Supports | Console errors suggest the correction where one is known. |
| 3.3.4 Error Prevention (Legal, Financial, Data) | Not Applicable | The site takes no legal commitments or financial transactions. The console reaches only the sandbox, and deleting sandbox data asks for confirmation. |
| 4.1.3 Status Messages | Partially Supports | The "Copied" confirmation is not announced. The console's response status is announced. |
Other chapters of the template
- Notes
- This report covers WCAG 2.0 and 2.1 only. Rows marked "2.2 only" in the template were removed, as the template allows when WCAG 2.2 is not reported. A WCAG 2.2 evaluation is planned with the next major release of the documentation site.
- Table 3: Success Criteria, Level AAA
- Not included. The product was not evaluated at Level AAA, and the template allows the table to be removed when a level is not reported.