A11yGo Toolbar — WCAG 2.1, WCAG 2.2, IS 17802, WAI-ARIA, EN 301 549 & Section 508 Mapping

How the status legend works

Every criterion in this mapping is marked with one of five statuses. The colour is never the only signal — each status also has a text label.

What this mapping means — and what it does not mean

The A11yGo Toolbar is a user-side accommodation layer. It fulfils requirements about giving users controls and preserving their preferences — text size, colour modes, spacing, motion, focus visibility and speech support. That is genuinely valuable, and several success criteria can be met with the toolbar as the mechanism the user operates.

But a website's WCAG / IS 17802 / EN 301 549 conformance is judged on the website's own code: its semantic structure, authored alternative text, captions, form labelling and authored colour contrast. Installing a toolbar does not, by itself, make a site conformant — and no honest mapping should claim that.

1 · WCAG 2.1 / 2.2 — full mapping

WCAG 2.2 includes the additional criteria 2.4.11–2.4.13, 2.5.7–2.5.8 and 3.3.7–3.3.8; they are shown inline below and should be kept separate from WCAG 2.1 in your own tracking.

2 · A11yGo's strongest WCAG areas

Reduced to the criteria where the toolbar can genuinely contribute, the list is:

Perceivable

• 🟡Supports 1.4.1 Use of Color
• 🟡Supports 1.4.3 Contrast (Minimum)
• 🟢Directly addresses 1.4.4 Resize Text
• 🟡Supports 1.4.6 Contrast (Enhanced)
• 🟡Supports 1.4.8 Visual Presentation
• 🟡Supports 1.4.10 Reflow
• 🟡Supports 1.4.11 Non-text Contrast
• 🟢Directly addresses 1.4.12 Text Spacing

Operable

• 🟡Supports 2.1.1 Keyboard
• 🔍Test required 2.1.2 No Keyboard Trap
• 🟡Supports 2.2.2 Pause / Stop / Hide
• 🟡Supports 2.3.3 Animation from Interactions
• 🟢Directly addresses 2.4.1 Bypass Blocks
• 🟡Supports 2.4.3 Focus Order
• 🟢Directly addresses 2.4.7 Focus Visible
• 🟡Supports 2.4.11 Focus Not Obscured
• 🟡Supports 2.4.12 Focus Not Obscured — Enhanced
• 🟡Supports 2.4.13 Focus Appearance
• 🟡Supports 2.5.4 Motion Actuation

Understandable

• ⚪Not addressed by toolbar — Very few direct WCAG requirements in this principle can be satisfied by a toolbar; most belong to the website itself.

Robust

• 🟢Directly addresses 4.1.2 Name, Role, Value
• 🟡Supports 4.1.3 Status Messages

3 · WAI-ARIA — a different kind of requirement

WAI-ARIA is not a conformance standard to "pass" — it is a technical specification for making custom controls accessible through correct roles, states, properties, accessible names and interaction patterns. The A11yGo Toolbar is itself a custom control, so this is where the toolbar is tested as a product, not as a site feature.

What the toolbar should implement correctly

<button type="button"
    aria-label="High contrast"
    aria-pressed="false">
    High Contrast
</button>

4 · EN 301 549 (European ICT standard)

For web pages, EN 301 549's clause 9 requirements are based on WCAG — so it is not an independent checklist to add on top of WCAG; it is the European vehicle for the same criteria. Two further clauses are directly relevant to the toolbar:

• Clause 11.5.1 / 11.7 User preferences: the toolbar persists each visitor's preferred contrast, text size, spacing, font and motion settings (localStorage) and restores them on return visits.
• Clause 12.1.2 Accessible documentation: the toolbar ships with a built-in keyboard-shortcut reference (F12, Esc, Ctrl+Alt combos) available from the UI.

5 · Section 508 (U.S. Rehabilitation Act — ICT Refresh)

The U.S. Revised Section 508 Standards incorporate WCAG 2.0 Level A and AA for applicable electronic content (E205.4). A11yGo's relevant support therefore flows through the corresponding WCAG areas, plus the software-application expectations around keyboard access, focus and user preferences:

The website as a whole must still satisfy the applicable requirements — Section 508 does not become satisfied simply because A11yGo is installed.

6 · IS 17802 (Indian ICT accessibility standard)

For the Indian market this is the standard to treat most carefully. BIS lists two parts as active:

• IS 17802 Part 1:2021 — Accessibility for ICT Products and Services — Requirements (Part 1 is BIS's adoption of EN 301 549).
• IS 17802 Part 2:2022 — Determination of Conformance.

The relevant areas for the toolbar are the website accessibility requirements that correspond to the WCAG-based web requirements, aligned with India's Supreme Court directive (April 2025) and RBI Circular RBI/2025-26/75:

7 · Master table — A11yGo capability across all six frameworks

The complete internal reference: every A11yGo Toolbar capability mapped against WCAG 2.1, WCAG 2.2, WAI-ARIA, IS 17802, EN 301 549 and Section 508.

‡ Roadmap items (Letter Spacing, Reading Mode, Reading Guide, Highlight Links, Highlight Headings): planned capabilities — verify availability in the current build before relying on them in a compliance claim.

8 · What the toolbar does not cover

Being precise about this protects your compliance program. The following always remain the website / application owner's responsibility: