Public documentation
UI Feature Guide
The operational hub for visible extension features, workflows, evidence, and limitations.
How to use this guide
Each feature is documented by purpose, use case, implementation approach, inputs, output, user action, evidence value, and limitations. Use this page as the hub, then follow child pages for deeper scanner, export, privacy, and troubleshooting detail.
Result classification quick reference
| Classification | Meaning | Needs human review? | Primary action |
|---|---|---|---|
| Confirmed | Highest-confidence issues that can be presented in the main scanner results for the current rendered state. | Review context and user impact before release decisions. | Prioritise remediation, retest, and record evidence. |
| Needs review | Items that need human judgement before being treated as failures. | Yes. | Inspect manually, then decide whether a defect exists. |
| Advisory | Helpful signals that may improve quality but should not be treated as definite WCAG failures. | Usually. | Use as quality guidance or backlog input. |
| Limitation | A known boundary of what the extension could not test or prove. | Yes, if the uncovered state matters. | Use another test method and avoid coverage overclaims. |
| Diagnostic | Technical support information for debugging or understanding scan coverage. | Not as a page failure. | Use for troubleshooting, support, and repeatability. |
Specialist workflow boundaries
Contrast Inspector roadmap
Confirmed contrast issues appear in the main scanner only when evidence is strong enough. The former Contrast Inspector UI is not exposed in the active extension; uncertain cases such as gradients, images, transparency, overlays, dynamic backgrounds, CSS effects, text over media, decorative/logo text, and BugHerd-style overlays remain review or diagnostic evidence until the workflow is rebuilt.
Design screenshot review
Image-only review can discuss visible layout, hierarchy, spacing, contrast concerns, content clarity, and likely accessibility risks. It cannot verify DOM, selectors, focus order, ARIA, names, semantic HTML, tab order, labels, or real screen reader output.
Screen Reader Review aid
Supports note-taking, expected reading order checks, visible-content review, and evidence organisation. It is not a replacement for NVDA, JAWS, VoiceOver, TalkBack, Narrator, keyboard-only testing, or real user-task testing.
Exports and local history
Exports are generated locally after user action and can include sensitive URLs, selectors, snippets, diagnostics, notes, and screenshots where captured.
Primary visible features
| Feature | User action | Evidence value | Limitation |
|---|---|---|---|
| Toolbar launch and scan workflow | Open the action on an authorised tab and run a scan. | Current-page automated and review evidence. | Restricted pages and unvisited states may not scan. |
| Results and filters | Use classification, severity, source, and search filters. | Keeps confirmed issues separate from review and diagnostics. | Filters do not change classification. |
| Language and spelling | Review flagged terms, skipped languages, and allowlist decisions. | Supports editorial and language review. | Not complete language validation. |
| Screen Reader Review aid | Use expected reading order and notes to plan real AT testing. | Organises review evidence. | Does not prove real screen reader behaviour. |
| Exports, diagnostics, and history | Export evidence or clear local state when appropriate. | Supports handoff and reproducibility. | Exported files leave browser control. |
Feature-to-guide map
| Feature area | Primary guide | Privacy or evidence note |
|---|---|---|
| Scan workflow and result queues | Understanding results | May include URLs, selectors, snippets, and issue state in exports. |
| Scanner modules | Scanner modules | Reads current page state; output can be exported. |
| Review workflows | Review workflows | User review state may be stored locally or exported. |
| Screen Reader Review aid | Screen Reader Review aid | Organises review evidence but does not prove real AT behaviour. |
| Exports/local state/history | Exports and local data | Exports can contain sensitive page evidence. |
| Diagnostics/support | Diagnostics and limitations | Diagnostics can include runtime and page context for support. |