Building a Testing Framework for Digital Accessibility
Software testing frameworks are popular tools in some areas of testing. Many mistakenly believe frameworks are applicable only to test automation because they provide easy test implementation, enhanced productivity for testers, and empower dependable quality for the product. However, testers should look at building test frameworks in other areas of testing, as well.
Accessibility is a rich ground for frameworks to be built and leveraged. We continue to see discussions that support manual testing over automation in the space of accessibility, so let’s explore how and why to create an accessibilty framework.
A robust accessibility framework is one that encapsulates testing methodologies, best practices, tools, compliance, checklists, and core scenarios under one umbrella. This creates a holistic implementation of accessibility from both regulatory and end-user standpoints. Each part of the framework need not be very verbose but should cover the core points in full essence, ensuring that the framework is scalable and maintainable.
Testing methodologies: Include processes such as promoting paired accessibility testing, implementing manual reviews on static code as well as dynamic implementation, leveraging accessibility toolbars such as WAVE, bringing in realistic end-users to test, etc.
Best practices: Include providing accessibility training to engineers (even ones who do no work on accessibility), keeping track of technology advancements and newer devices, engaging from early stages of product design, building a strong and productive business case, specifying information to include while filing accessibility defects, defining good use cases for automated accessibility testing, and researching accessibility devices and software to invest in.
Tools: Cover assistive tools such as screen readers, magnifiers, OCRs, and voice dictation solutions. Having such a toolkit helps testers jump into accessibility testing at short notice.
Compliance: Digital accessibility is growing in significance, from ensuring compliance to regulatory standards. Section 508 in the US, DDA in the UK, and WCAG are not just mandates, but also good checklists for organizations to adhere to.
Checklists: Use lists such as VPAT to align testing efforts with requirements of compliances such as Section 508.
Core scenarios: Include verifying keyboard accessibility, audio/video, text tags, text resizing, color-contrast ratio, navigation links, overall site readability, time delays, semantic tagging, forms, cross-browser compatibility, etc.
Specific to accessibility, the utmost benefit of having an overarching framework is to ensure coverage for the disabled is not compromised. Given the time and cost constraints that a team often operates within, accessibility is at a crossroad. On one hand, we have regulations to enforce digital accessibility. On the other hand, we have product teams trying to push accessibility to a back seat given the constraints.
Having a testing framework such as the one above empowers testers to objectively speak up for the need for accessibility testing, while also serving as a tool for use over the course of the testing lifecycle.
