Accessibility in the testing phase

Accessibility is important in all phases, but in the testing phase, we can really spot performance issues or other issues that have arisen during the development process.

It is in this phase that we check that the application is working properly and meets the requirements. 

• • • • • Unit testing: verification of individual components.
        • Integration testing: verification of the interaction between modules.
        • Performance tests: response time, server load.
        • Security testing: vulnerability protection.
        • User testing (UAT): validation of usability and user experience.

4 ways to integrate accessibility into the testing phase 

1. 1. 1. Use automated analysis tools

• • • • • Lighthouse (Chrome DevTools): Accessibility Score
        • DevTools Axis: Detects some of the non-compliances to the WCAG
        • Wave: Analyzes the accessibility of a web page

• • • • • Navigate only with the keyboard (Tab, Enter, Space, Esc).
        • Test with VoiceOver (Mac/iOS), NVDA (Windows), TalkBack (Android).
        • Check the experience on different screens and zooms (up to 200%).

• • • • • Designers: Provide accessible mock-ups.
        • Developers: Code according to best practices.
        • QA (Quality Assurance): Testing features through an accessibility lens.
        • Product Owners: Prioritize accessibility in the Agile backlog.

• • • • • Using Semantic HTML
        • Smooth keyboard navigation
        • Focus and interaction management
        • Sufficient contrast and legible text
        • Screen reader compatibility
        • Automated and manual tests performed

To go further

We offer comprehensive training on important concepts. Find our training catalog here!

In addition, if you have a project in mind and want to discuss with us, don't hesitate to contact us!