As an ICT design engineer, you should be aware of a few key things about EN 301 549
2025.02.25
EN 301 549 is the European accessibility standard for ICT products and services. Since you need to comply with Chapters 5, 8, 9, 10, 11, and 12, here are the key considerations for each:
- Chapter 5: General Requirements
- Ensure that your ICT product or service is accessible to all users, including those with disabilities.
- Functional accessibility requirements must be met, focusing on perceivability, operability, and compatibility.
- Provide accessible documentation and user support.
- Chapter 8: Hardware
- Industry Standard Connections - Your ICT device must include at least one widely used, non-proprietary connection format.
- Assistive Technology Compatibility - Ensure that assistive devices (e.g., screen readers, alternative input devices) can connect to your ICT.
- Colour is never the sole means of conveying information.
- Alternative indicators (text, symbols, icons, patterns) are always provided.
- Sufficient contrast is maintained for readability.
- Chapter 9: Web Content
Follow WCAG 2.1 Level A and AA guidelines:
- Provide alt text for images to support screen readers.
- Ensure full keyboard navigation and avoid relying solely on a mouse.
- Maintain sufficient color contrast and allow font size adjustments.
- Support assistive technologies, such as voice control and braille displays.
- Chapter 10: Non-Web Documents
- Ensure that non-web documents (e.g., PDFs, Word files, eBooks) meet accessibility requirements:
- Use structured headings and well-defined document hierarchy.
- Include descriptive text for images and tables.
- Ensure compatibility with screen readers.
- Chapter 11: Non-Web Software
- Desktop and mobile applications must be accessible:
- Support assistive technologies (e.g., screen readers, voice input).
- Provide keyboard operability and customizable UI settings.
- Avoid flashing elements that could trigger seizures.
- Chapter 12: Documentation and Support Services
- Product documentation, help content, and customer support must be accessible:
- Documents should be available in accessible formats (HTML, structured PDFs).
- Ensure support channels (e.g., phone, chat, email) are usable by people with disabilities.
- Provide real-time assistance options, such as text relay services.
Final Notes
You should use accessibility testing tools (e.g., WAVE, AXE, or Lighthouse) to verify compliance. If your product is web-based, focus on WCAG 2.1 guidelines. For software, ensure it integrates well with assistive technologies