Public documentation
Feature methodology
Feature-by-feature evidence sources, calculation boundaries, storage, exports, and limitations.
Methodology format
Each feature is described by data read, technology used, calculation approach, classification, storage/export behaviour, and limitations. This keeps feature claims tied to implementation evidence instead of marketing language.
Core feature methods
| Feature | Data read | Classification | Key limitation |
|---|---|---|---|
| Main scan | Rendered DOM, accessibility tree signals available to axe-core, selectors, snippets, rule metadata | Confirmed, needs review, limitation, diagnostic | Current rendered state only. |
| Metadata check | Document title, description, Open Graph, schema, canonical, previews | Advisory or diagnostic | Metadata is page-quality evidence, not direct WCAG proof. |
| Broken links | Links and same-origin status where safe and supported | Advisory, needs review, limitation | Cross-origin, authenticated, blocked, rate-limited, or timeout states may be unverified. |
| Language and spelling | Visible text, lang attributes, local dictionaries, allowlist state | Advisory or needs review | Short, mixed, unsupported, brand-heavy, or ambiguous text needs human review. |
| Headings and images | Headings, image alt/name evidence, nearby context where available | Confirmed, needs review, advisory | Information architecture and alternative-text quality remain contextual. |
| Contrast | axe color-contrast results, computed colours, ratios/thresholds, ambiguity reasons | Confirmed only with strong evidence; otherwise review or unable-to-determine | Complex paint composition requires inspection. |
| Screen Reader Review aid | Rendered structure, visible content, virtual review output, user notes | Review support | Does not prove real AT behaviour. |
| Exports | Current scan evidence, selected module state, diagnostics, notes, screenshot where captured | User-triggered evidence artefact | Exports can contain sensitive page context. |
Contrast handling detail
Main scanner confirmed contrast findings are shown only for confirmed axe-core color-contrast violations or custom rendered-text contrast failures that pass every reliability gate. Custom contrast review candidates and unable-to-determine items remain review/diagnostic evidence while the Contrast Inspector UI is roadmap work and is not exposed in the active extension.
Design screenshot handling
For imported PNG, JPG, or WebP screenshots, findings must be labelled visual review or design review. A screenshot can support visible layout, hierarchy, spacing, contrast concern, and content clarity comments; it cannot verify implementation details that are not present in the image.