YRA Monitor · WCAG 2.2, Levels A and AA · Report date September 1, 2026
YRA Monitor is an accessibility monitoring product, and we audit it with the same tooling we sell. This report is the result of a self-audit; it is updated after each remediation cycle and re-verified against the live product.
The three criteria marked Does Not Support are carried by a small number of remaining findings (decorative SVG text alternatives, heading-level skips, and a color-only heuristic under review); none requires architectural change and all are scheduled. Success Criterion 4.1.1 Parsing was removed in WCAG 2.2 and is not reported.
| Criterion | Conformance level | Remarks and explanations |
|---|---|---|
| 1.1.1 Non-text Content | Does Not Support | Meaningful images, icon-only buttons and charts on core pages carry text alternatives. Some inline SVG icons on 16 of the 19 audited page templates still lack a text alternative; remediation is scheduled. |
| 1.2.1–1.2.3 Time-based Media (prerecorded audio/video, captions, audio description) | Not Applicable | No prerecorded media on the audited product routes. Media added later must ship with captions and audio description. |
| 1.3.1 Info and Relationships | Does Not Support | Tables carry captions and header scope; sortable report tables announce sort state. Some pages skip heading levels and a few hand-built tables still lack full header associations. |
| 1.3.2 Meaningful Sequence | Supports | Reading and focus order match the visual order; verified manually. |
| 1.3.3 Sensory Characteristics | Supports | Instructions do not rely on shape, size or position alone. |
| 1.4.1 Use of Color | Does Not Support | Links inside text blocks are underlined. An automated heuristic still flags possible color-only meaning on several pages; those are under manual review. |
| 1.4.2 Audio Control | Not Applicable | No auto-playing audio. |
| 2.1.1 Keyboard | Supports | All functionality is keyboard operable. Custom dropdowns and comboboxes were rebuilt on accessible primitives (Escape, arrow keys, focus return). Residual engine heuristics are being triaged. |
| 2.1.2 No Keyboard Trap | Supports | Verified manually across dialogs, menus and editors. |
| 2.1.4 Character Key Shortcuts | Not Applicable | No single-character shortcuts. |
| 2.2.1 Timing Adjustable | Partially Supports | One monitoring view auto-refreshes; a pause control is planned. |
| 2.2.2 Pause, Stop, Hide | Supports | No moving content longer than five seconds; the site honors the reduced-motion preference. |
| 2.3.1 Three Flashes or Below Threshold | Supports | No flashing content. |
| 2.4.1 Bypass Blocks | Supports | A "Skip to main content" link is the first focusable element on every page; keyboard-verified. |
| 2.4.2 Page Titled | Supports | Every route has a descriptive, unique title; sweep-verified. |
| 2.4.3 Focus Order | Partially Supports | Focus order follows the visual order and dialogs return focus to their trigger. A small number of transient focus stops on dialog close are still being verified. |
| 2.4.4 Link Purpose (In Context) | Partially Supports | Repeated link text in long issue tables and the blog index is disambiguated with screen-reader-only text; a final pass on vague link text is pending. |
| 2.5.1 Pointer Gestures | Not Applicable | No path-based or multipoint gestures. |
| 2.5.2 Pointer Cancellation | Supports | Actions trigger on the up-event throughout. |
| 2.5.3 Label in Name | Partially Supports | On four pages a control's accessible name does not begin with its visible label; fix scheduled. |
| 2.5.4 Motion Actuation | Not Applicable | No motion-activated functionality. |
| 3.1.1 Language of Page | Supports | Every page declares its language. |
| 3.2.1 On Focus | Supports | No context changes on focus. |
| 3.2.2 On Input | Supports | No unexpected submissions or context changes on input. |
| 3.2.6 Consistent Help | Partially Supports | Help links appear in a consistent position; previously broken help targets are fixed. Final consistency review pending. |
| 3.3.1 Error Identification | Partially Supports | Errors are shown in text and announced on product forms; programmatic association with the field is being completed on the remaining public forms. |
| 3.3.2 Labels or Instructions | Partially Supports | Most inputs are labeled; a few still rely on placeholder text. |
| 3.3.7 Redundant Entry | Supports | Verified; the sign-up to sign-in hand-off falls under the security exception. |
| 4.1.2 Name, Role, Value | Supports | Zero automated name/role/value violations in the re-audit; custom widgets expose combobox, menu and dialog semantics. A residual role heuristic is being triaged. |
| Criterion | Conformance level | Remarks and explanations |
|---|---|---|
| 1.2.4–1.2.5 Captions (Live), Audio Description (Prerecorded) | Not Applicable | No live or prerecorded media on the audited product routes. |
| 1.3.4 Orientation | Supports | No orientation locks. |
| 1.3.5 Identify Input Purpose | Partially Supports | Sign-in, sign-up and account forms declare input purpose. One public email field does not yet. |
| 1.4.3 Contrast (Minimum) | Supports | Zero contrast failures across all 165 routes at desktop and 320 px widths in the July 2026 re-audit, after a site-wide move to contrast-checked color tokens. Engine "contrast risk" heuristics on dynamic content remain under review. |
| 1.4.4 Resize Text | Partially Supports | Text resizes to 200% without loss of content in testing; some fixed-height containers on 15 audited pages could clip at extreme settings. |
| 1.4.5 Images of Text | Supports | None found. |
| 1.4.10 Reflow | Supports | No reflow failures at 320 px across the product. The one remaining node is the third-party TinyMCE editor menubar on a demo page. |
| 1.4.11 Non-text Contrast | Partially Supports | Focus rings and control boundaries meet 3:1 where measured; measurement is not yet exhaustive. |
| 1.4.12 Text Spacing | Supports | No failures with the WCAG text-spacing overrides applied. |
| 1.4.13 Content on Hover or Focus | Partially Supports | Tooltips and menus are dismissible; some hover-revealed content on 15 pages does not yet meet the hoverable/persistent requirements. |
| 2.4.5 Multiple Ways | Supports | Site navigation, search, and a human-readable sitemap. |
| 2.4.6 Headings and Labels | Partially Supports | Headings are descriptive. A few inputs still rely on placeholder-only labels. |
| 2.4.7 Focus Visible | Partially Supports | Focus is visible on every control. A site-wide pass to strengthen focus-indicator contrast and thickness is planned. |
| 2.4.11 Focus Not Obscured (Minimum) | Supports | No sticky regions obscure focused elements; verified. |
| 2.5.7 Dragging Movements | Supports | No drag-only interactions; verified. |
| 2.5.8 Target Size (Minimum) | Supports | Zero target-size failures, including under the strict interpretation, after enlarging shared checkbox and dense-table hit areas. |
| 3.1.2 Language of Parts | Supports | No failures detected. Multilingual demo content will be language-tagged if promoted to product pages. |
| 3.2.3 Consistent Navigation | Supports | Header, sidebar and footer are consistent across pages. |
| 3.2.4 Consistent Identification | Partially Supports | No confirmed failures; a low-confidence engine heuristic flags inconsistent styling and is under review. |
| 3.3.3 Error Suggestion | Supports | Error messages state how to fix the problem. |
| 3.3.4 Error Prevention (Legal, Financial, Data) | Supports | Checkout provides a review step before purchase. |
| 3.3.8 Accessible Authentication (Minimum) | Supports | Password managers, paste, and magic-link sign-in are all supported; no cognitive function tests. |
| 4.1.3 Status Messages | Partially Supports | Live regions announce filter, table and save results in the product; some public forms do not yet announce status. |
Found something this report does not cover? Email [email protected] with the page and the assistive technology you were using.
