EN 301 549 Testing Guidelines
Testing for EN 301 549 compliance requires a systematic approach that combines automated tools, manual testing, and user testing. This guide provides comprehensive testing methodologies to ensure your digital products meet European accessibility standards.
Testing Methodology Overview
EN 301 549 testing follows a three-tier approach:
1. Automated Testing
Quick identification of common accessibility issues using specialized tools and software.
2. Manual Testing
Detailed evaluation using assistive technologies and accessibility features.
3. User Testing
Real-world testing with users who have disabilities to validate accessibility.
Automated Testing
Automated testing tools can identify many common accessibility issues quickly and efficiently. However, they should not be the only testing method used.
Web Accessibility Testing Tools
axe DevTools
Comprehensive automated testing tool that identifies accessibility violations according to WCAG guidelines.
- Tests for WCAG 2.1 AA compliance
- Provides detailed violation reports
- Integrates with development workflows
- Supports multiple browsers
WAVE Web Accessibility Evaluator
Free online tool that evaluates web pages for accessibility issues and provides visual feedback.
- Visual indicators of accessibility issues
- Detailed explanations of problems
- Browser extension available
- Free to use
Lighthouse
Google's automated auditing tool that includes accessibility testing as part of its comprehensive analysis.
- Built into Chrome DevTools
- Provides accessibility scores
- Includes performance and SEO audits
- Generates detailed reports
Tenon
API-based accessibility testing tool that can be integrated into development workflows.
- API-based testing
- CI/CD integration
- Detailed reporting
- Customizable testing rules
What Automated Testing Can Detect
- Missing alt text for images and other non-text content
- Color contrast violations that don't meet WCAG requirements
- Missing form labels and form accessibility issues
- Semantic HTML structure problems
- Keyboard navigation issues
- ARIA implementation errors
- Heading structure problems
- Link text issues
What Automated Testing Cannot Detect
- Content quality and meaningfulness of text alternatives
- User experience and usability for people with disabilities
- Complex interactions and dynamic content behavior
- Assistive technology compatibility issues
- Cognitive accessibility concerns
- Mobile accessibility on actual devices
Manual Testing
Manual testing is essential for comprehensive accessibility evaluation. It involves using assistive technologies and accessibility features to test functionality from the perspective of users with disabilities.
Screen Reader Testing
Popular Screen Readers
NVDA (Windows)
Free, open-source screen reader for Windows
- Download from nvaccess.org
- Supports multiple languages
- Regular updates and community support
JAWS (Windows)
Professional screen reader with advanced features
- Industry standard for Windows
- Comprehensive feature set
- Professional support available
VoiceOver (macOS/iOS)
Built-in screen reader for Apple devices
- Free with macOS and iOS
- Gesture-based navigation
- Integrated with Apple ecosystem
TalkBack (Android)
Built-in screen reader for Android devices
- Free with Android
- Gesture-based navigation
- Customizable settings
Keyboard Navigation Testing
Test all functionality using only the keyboard:
Essential Keyboard Commands
- Tab - Navigate between interactive elements
- Shift + Tab - Navigate backwards
- Enter/Space - Activate buttons and links
- Arrow keys - Navigate within components
- Escape - Close dialogs and menus
- Home/End - Navigate to beginning/end of content
What to Test
- All interactive elements are reachable via keyboard
- Focus order is logical and intuitive
- Focus indicators are clearly visible
- No keyboard traps exist
- Keyboard shortcuts work as expected
- Dynamic content updates are announced
Visual Accessibility Testing
Color Contrast Testing
- Use tools like WebAIM Contrast Checker or Stark
- Test all text against its background
- Verify 4.5:1 ratio for normal text (AA)
- Verify 3:1 ratio for large text (AA)
- Test in different lighting conditions
Text Scaling Testing
- Test text scaling up to 200%
- Verify no horizontal scrolling is required
- Check that functionality remains intact
- Test on different screen sizes
Color Blindness Testing
- Use color blindness simulators
- Verify information is not conveyed by color alone
- Test with different types of color blindness
- Check that contrast remains sufficient
User Testing
User testing with people who have disabilities provides the most valuable insights into accessibility. This testing validates that your implementation actually works for real users.
Recruiting Test Participants
Target User Groups
- Users with visual impairments - Test with screen reader users and users with low vision
- Users with motor impairments - Test with users who rely on keyboard navigation or alternative input devices
- Users with hearing impairments - Test with users who are deaf or hard of hearing
- Users with cognitive disabilities - Test with users who have learning difficulties or cognitive impairments
Recruitment Sources
- Local disability organizations
- Accessibility consulting firms
- Online accessibility communities
- University disability services
- Professional accessibility networks
User Testing Methodology
Task-Based Testing
Ask users to complete specific tasks using your product
- Define clear, realistic tasks
- Observe how users approach tasks
- Note any difficulties or workarounds
- Ask for feedback and suggestions
Think-Aloud Protocol
Ask users to verbalize their thoughts while using the product
- Encourage continuous commentary
- Ask clarifying questions
- Document user reactions
- Identify pain points
Assistive Technology Testing
Test with users' preferred assistive technologies
- Use users' own devices and software
- Test with familiar configurations
- Observe real-world usage patterns
- Identify compatibility issues
Testing Checklist
Pre-Testing Preparation
- Define testing scope and objectives
- Select appropriate testing tools
- Prepare test scenarios and tasks
- Set up testing environment
- Recruit test participants
- Prepare consent forms and documentation
During Testing
- Document all findings systematically
- Record testing sessions (with permission)
- Take detailed notes on user interactions
- Ask follow-up questions for clarity
- Test on multiple devices and browsers
- Verify findings across different assistive technologies
Post-Testing Analysis
- Compile and categorize findings
- Prioritize issues by severity and impact
- Create detailed reports with recommendations
- Share findings with development team
- Plan follow-up testing after fixes
- Document lessons learned for future testing
Reporting and Documentation
Comprehensive documentation of testing results is essential for compliance and ongoing improvement.
Test Report Structure
Executive Summary
- Overall compliance status
- Key findings and recommendations
- Risk assessment
- Timeline for remediation
Detailed Findings
- Issue descriptions with examples
- WCAG/EN 301 549 criteria references
- Severity ratings
- Impact on users
- Recommended solutions
Testing Methodology
- Tools and techniques used
- Test participants and demographics
- Test scenarios and tasks
- Testing environment details
Compliance Assessment
- Level A compliance status
- Level AA compliance status
- Level AAA compliance status (if applicable)
- Hardware and software requirements status
Continuous Testing
Accessibility testing should be an ongoing process, not a one-time event. Establish regular testing schedules and integrate accessibility testing into your development workflow.
Integration with Development
- Automated testing in CI/CD pipelines
- Accessibility code reviews
- Pre-release accessibility testing
- Regular accessibility audits
Monitoring and Maintenance
- Regular automated testing
- User feedback collection
- Accessibility issue tracking
- Performance monitoring