- Template
- 2.5Rev
- Edition
- WCAG
- Report date
- 2026-11-05
/ Example report · WCAG
Tallowmere Invoicing 4.2 (fictional product): example Accessibility Conformance Report
Example report for a fictional product. 56 criteria reported at Levels A and AA (WCAG 2.2 rows): 30 Supports, 20 Partially Supports, 2 Does Not Support, 4 Not Applicable. The gaps that matter most are the drag-only line reordering, the one-time code that cannot be pasted, the line-item grid without table semantics and colour-only invoice status.
Example only. Tallowmere Invoicing 4.2 (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
- B2B invoicing web app
- Scope
- Example report for an invented product; Tallowmere Invoicing and its vendor do not exist. Covers the signed-in web application at app.tallowmere.example, version 4.2: sign-in with a one-time code, dashboard, customer list, new customer wizard, invoice editor, send and reminder dialogs, settings and the help widget. The embedded third-party card payment form, the PDF invoices the app generates and the marketing site are out of scope and noted as such. Standards covered: WCAG 2.0, 2.1 and 2.2, Levels A and AA.
- Evaluation methods
- Manual testing by two testers who use the product daily, on every in-scope screen and on the complete flows for creating, sending and voiding an invoice. Keyboard-only operation; NVDA with Firefox and JAWS with Chrome on Windows; VoiceOver with Safari on macOS; browser zoom at 200 and 400 percent and a 320 CSS pixel viewport; text spacing overrides; Windows contrast themes. Automated checks with axe-core on each screen state. Contrast measured with a colour picker against the rendered pixels.
- What it shows
- The two Does Not Support rows come from WCAG 2.2 additions (dragging and accessible authentication). A report that claimed 2.2 without those rows, or answered them Supports from an automated scan, would be caught by the first buyer who tried to reorder an invoice line without a mouse.
Table 1: Success Criteria, Level A
| Criteria | Conformance level | Remarks and explanations |
|---|---|---|
| 1.1.1 Non-text Content | Partially Supports | Toolbar and status icons have text alternatives. The revenue and ageing charts on the dashboard are images with the alt text "Chart" and no data table or summary of the values. |
| 1.2.1 Audio-only and Video-only (Prerecorded) | Not Applicable | The application contains no audio-only or video-only content. |
| 1.2.2 Captions (Prerecorded) | Partially Supports | The four onboarding videos in the help widget have edited captions. The "What's new in 4.2" video has no captions. |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) | Partially Supports | Three onboarding videos are narrated and the narration describes what happens on screen. The "Bulk import" screen recording has no narration, transcript or audio description. |
| 1.3.1 Info and Relationships | Partially Supports | Headings, landmarks and form labels are marked up. The invoice line-item grid is built from generic elements with no table semantics, so a screen reader announces quantity, price and tax as unrelated text. |
| 1.3.2 Meaningful Sequence | Supports | Reading order follows the visual order on every screen, including the invoice editor side panel. |
| 1.3.3 Sensory Characteristics | Supports | Instructions do not rely on shape, position or sound. |
| 1.4.1 Use of Color | Partially Supports | Invoice status in the customer list and on the dashboard is shown by a coloured dot only (green paid, amber due, red overdue). The invoice detail page shows the status as text. |
| 1.4.2 Audio Control | Not Applicable | No audio plays automatically. |
| 2.1.1 Keyboard | Partially Supports | All functions except reordering invoice lines are keyboard operable. Line order can only be changed by dragging the handle. |
| 2.1.2 No Keyboard Trap | Supports | No keyboard traps found, including in the date picker, the rich text note field and modal dialogs. |
| 2.1.4 Character Key Shortcuts | Supports | Single-key shortcuts (n for new invoice, / for search) can be turned off under Settings, Keyboard. |
| 2.2.1 Timing Adjustable | Supports | Sessions end after 30 minutes of inactivity. A warning appears two minutes before, and the session can be extended from it with one key press. |
| 2.2.2 Pause, Stop, Hide | Supports | No moving, blinking or auto-updating content runs for more than five seconds. The dashboard refreshes only on request. |
| 2.3.1 Three Flashes or Below Threshold | Supports | No content flashes. |
| 2.4.1 Bypass Blocks | Supports | A skip link moves to the main content, and every screen uses header, navigation and main landmarks. |
| 2.4.2 Page Titled | Supports | Each screen has a title naming the screen and, in the editor, the invoice number. |
| 2.4.3 Focus Order | Partially Supports | Focus is not moved into the Send invoice dialog when it opens; keyboard users reach it only after tabbing through the page behind it. Other dialogs manage focus correctly. |
| 2.4.4 Link Purpose (In Context) | Partially Supports | Rows in the customer list end with links named "View" and "Edit" that do not say which customer they act on. |
| 2.5.1 Pointer Gestures | Supports | The chart zoom uses a two-finger gesture and also has zoom in and zoom out buttons. |
| 2.5.2 Pointer Cancellation | Supports | Actions run on release, and dragging off a button cancels it. |
| 2.5.3 Label in Name | Partially Supports | The button labelled "Send" in the editor has the accessible name "Dispatch invoice email", so a voice command for "Send" does not activate it. |
| 2.5.4 Motion Actuation | Not Applicable | No function is operated by device motion. |
| 3.1.1 Language of Page | Supports | Every screen declares English as its language. |
| 3.2.1 On Focus | Supports | No change of context on focus. |
| 3.2.2 On Input | Partially Supports | Choosing a customer in the customer selector on the new invoice screen opens that customer's draft immediately, without a submit step or prior warning. |
| 3.2.6 Consistent Help | Supports | The help widget and the support email link sit in the same place in the header on every screen. |
| 3.3.1 Error Identification | Supports | Errors are described in text next to the field and summarised at the top of the form. |
| 3.3.2 Labels or Instructions | Supports | All fields have visible labels; date and amount fields state the expected format. |
| 3.3.7 Redundant Entry | Partially Supports | Step 3 of the new customer wizard asks for the billing address again after it was entered as the postal address in step 1, with no option to copy it. |
| 4.1.1 Parsing | Supports | WCAG 2.0 and 2.1: always supported, per the September 2023 errata to both. WCAG 2.2: obsolete and removed, does not apply. |
| 4.1.2 Name, Role, Value | Partially Supports | The toggle switches in Settings expose no role or checked state. The currency selector is a custom list that does not expose its expanded state or the selected option. |
Table 2: Success Criteria, Level AA
| Criteria | Conformance level | Remarks and explanations |
|---|---|---|
| 1.2.4 Captions (Live) | Not Applicable | The application contains no live audio or video. |
| 1.2.5 Audio Description (Prerecorded) | Partially Supports | The narrated onboarding videos describe the on-screen actions. The "Bulk import" recording has no audio description. |
| 1.3.4 Orientation | Supports | All screens work in portrait and landscape. |
| 1.3.5 Identify Input Purpose | Supports | Contact fields for the user and for customers carry the matching autocomplete values. |
| 1.4.3 Contrast (Minimum) | Partially Supports | Body text and buttons pass. Placeholder text in search fields measures 3.1:1 and the "Draft" badge 2.8:1. |
| 1.4.4 Resize Text | Supports | Text resizes to 200 percent without loss of content or function. |
| 1.4.5 Images of Text | Supports | The only image of text is the product logo. |
| 1.4.10 Reflow | Partially Supports | Most screens reflow at 320 CSS pixels. In the invoice editor the totals panel overlaps the line-item grid at that width and the Save button can only be reached by scrolling sideways. |
| 1.4.11 Non-text Contrast | Partially Supports | Text field borders measure 1.9:1 against the background. Focus indicators and icons pass. |
| 1.4.12 Text Spacing | Supports | No loss of content with the text spacing overrides applied. |
| 1.4.13 Content on Hover or Focus | Partially Supports | Tooltips on the status dots disappear when the pointer moves onto them and cannot be dismissed with Escape. |
| 2.4.5 Multiple Ways | Supports | Screens can be reached from the main navigation and from global search. |
| 2.4.6 Headings and Labels | Supports | Headings and labels describe their topic or purpose. |
| 2.4.7 Focus Visible | Supports | Every interactive element shows a visible focus indicator. |
| 2.4.11 Focus Not Obscured (Minimum) | Partially Supports | The sticky totals bar at the bottom of the invoice editor covers focused fields in the last line item until the page is scrolled. |
| 2.5.7 Dragging Movements | Does Not Support | Reordering invoice lines and moving invoices between columns on the board view work only by dragging. Neither has a single-pointer alternative. |
| 2.5.8 Target Size (Minimum) | Partially Supports | Row action icons in the customer list are 18 by 18 CSS pixels with 2 pixels between them. |
| 3.1.2 Language of Parts | Supports | The French and German invoice templates mark their language. Text typed by users is not in scope. |
| 3.2.3 Consistent Navigation | Supports | Navigation appears in the same order on every screen. |
| 3.2.4 Consistent Identification | Supports | Components with the same function have the same names throughout. |
| 3.3.3 Error Suggestion | Supports | Error messages suggest the correction, such as the expected date or tax number format. |
| 3.3.4 Error Prevention (Legal, Financial, Data) | Supports | Invoices are shown for review before sending, and a sent invoice can be voided from its detail page. |
| 3.3.8 Accessible Authentication (Minimum) | Does Not Support | Sign-in requires a six-digit code sent by email, and the code field blocks paste, so the code must be transcribed by hand. No other sign-in method is offered. |
| 4.1.3 Status Messages | Partially Supports | "Invoice saved" and "Reminder scheduled" messages appear as toasts that are not announced by screen readers. Form errors are announced. |
Other chapters of the template
- 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.
- Notes
- The card payment form is supplied by a third-party processor in an iframe and is not covered; ask the processor for its own report. Generated PDF invoices will be reported separately.