EN 301 549 V4.1.1 - Accessibility requirements for ICT products and services
Non-web documents (clause 10) – EN 301 549 V4.1.1 - Accessibility requirements for ICT products and services

EN 301 549 V4.1.1 - Accessibility requirements for ICT products and services 10.2.4: 10.2.4 Navigable

For a non-web document within the ICT, the document has to satisfy the WCAG 2.2 criteria of this group: descriptive titles (10.2.4.2); a focus sequence that preserves meaning (10.2.4.3); each link's purpose clear from its text or surrounding context (10.2.4.4); headings and field labels describing topic or purpose (10.2.4.6); a visible keyboard focus indicator (10.2.4.7); a focused component not fully hidden by author content (10.2.4.11). Bypass blocks and multiple ways are void for single documents; 10.2.4.2 replaces page titled with a requirement that the document has a title describing its name, topic or purpose; focus order is restated in Table 10.9.

Maintained by Gerard Blokdyk

What else in your programme already covers this

This control maps to 7 controls across 2 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

WCAG 2.2 · 6 controls

  • 2.4.11 Focus Not Obscured (Minimum) (Level AA)
  • 2.4.2 Page Titled (Level A)
  • 2.4.3 Focus Order (Level A)
  • 2.4.4 Link Purpose (In Context) (Level A)
  • 2.4.6 Headings and Labels (Level AA)
  • 2.4.7 Focus Visible (Level AA)

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in Non-web documents (clause 10) – EN 301 549 V4.1.1 - Accessibility requirements for ICT products and services

Query this from an agent

The graph holds this control, the 7 it maps to, and the evidence behind each claim, over MCP and REST.