The A11y Path

Clause 4 - Functional Performance (EN 301 549)

So, the normative part of EN 301 549 starts from Clause 4, and honestly? I like that it doesn't just jump straight into standards and technical specs.

Clause 4 starts with why the rest of the standard exists. It's like saying: Let's talk about what people actually need before we get into how you're going to meet those needs.

Clause 4.2 - Functional Performance Statements

Clause 4.2 lists out 11 functional needs, basically saying your product should let people:

1. Use it without vision (e.g. screen readers, audio feedback)
2. Use it with limited vision (e.g. zoom, high contrast)
3. Use it without perceiving color (e.g. labels, icons)
4. Use it without hearing (e.g. captions, visual alerts)
5. Use it with limited hearing (e.g. volume control, noise reduction)
6. Use it without speech (e.g. text or touch alternatives)
7. Use it with limited dexterity or strength (e.g. keyboard navigation, single-handed interaction)
8. Use it with limited reach (e.g. reachable touchpoints, wheelchair-friendly layouts)
9. Avoid seizure triggers (e.g. no rapid flashing)
10. Use it with cognitive or learning challenges (e.g. clear instructions, step-by-step flows, word prediction)
11. Use accessibility features privately and securely (e.g. headphone jacks, masked inputs)

What Stood Out the Most

Privacy.

Clause 4.2.11 says that people who rely on accessibility features shouldn't have to sacrifice their privacy to use a product. I totally agree with that because so many accessibility tools are public, loud, or revealing and that can expose sensitive information.

It's one of the first standards I've read that acknowledges privacy. It's not something WCAG talks about, and it feels like a big step toward dignity-centered accessibility.

Conclusion

I like that Clause 4 reframe accessibility as not just technical compliance, but human-centered design. To me it feels like a pep talk before all the technical clauses, like saying This is why we're doing this.