Welcome to the MNIT DOT Accessibility Testing GitHub site, your go-to resource for ensuring digital content is inclusive for all users. Our comprehensive guidance and tools are designed to help you effectively test and improve the accessibility of your web, desktop and native applications. Explore the site features, which include:
The checklists for Web, Desktop and Native Apps are designed to ensure our digital products are accessible to all users. Quality analysts, developers, or designers can use the checklists to build testing scenarios for individual components. Testing is focused on keyboard and screen reader testing. Each component includes steps that walk you through testing scenarios and the expected behaviors and a link to a full information page that provides comprehensive details on testing scenarios, with developer notes, code examples, video demonstrations, and references to WCAG 2.1 Level A and AA and WAI-ARIA documentation.
The Web accessibility checklist information is provided in Gherkin and Condensed formats; choose the version based on your preference.
A Web Application is delivered over the Internet from a remote server using a web browser. It works primarily with resources made available over the Internet, such as storage and processing power. The use of modern web browsers increases web application capabilities. This allows developers to create more interactive interfaces that mimic a desktop application. Web applications may be limited by bandwidth.
Software is an application that runs locally on a desktop or laptop computer or a native application for a mobile phone. It must be developed and installed for a particular operating system. Software can have specific hardware requirements that must be met to function correctly. Software is often dependent on the storage and processing power of the computer. Updates must be applied directly to the desktop or laptop installation.
A native mobile app is built for a specific platform, such as iOS for an Apple iPhone or Android for a Samsung tablet. Apps are downloaded and installed via an app store. They may have access to system resources, like Global Positioning Systems (GPS) or the camera. Native mobile apps live and run on the device. They require the user to download updates and may be able to work offline.
This is not a comprehensive list of all WCAG success criteria or techniques required to become WCAG 2.1 Level A and AA compliant and should not be used as such.
Adherence to this list also does not guarantee that a digital asset will be free from accessibility issues or complaints.
MNIT DOT A11y was sourced from MagentaA11y by T-Mobile. It was created by Charlie Triplett, author of The Book on Accessibility.
MagentaA11y is open-sourced by T-Mobile and released under the Apache 2.0 License.