What’s Accessibility Testing and why is it important? In this lesson, you’ll learn how to add Accessibility checks into your UI tests.
Make sure you are comfortable with the following mabl concepts:
By the end of this you will be able to:
Your websites and applications should be accessible for all users, with elements like visuals, buttons, and interactions that are easy to understand and navigate. When manual testing, you may miss areas or features that do not contribute to an accessible user experience. This can lead to negative user feedback, loss of brand loyalty, or potential legal repercussions.
Mabl's Accessibility Testing, available in Chrome on the unified runner, allows you to improve your automated test resilience and build Accessibility Checks directly into your regularly scheduled tests. Now you can finds opportunities to create a more equitable experience for all users!
Web accessibility pertains to how universally robust, perceivable, operable, and understandable your websites, applications, and tools are for your users. In other words? It means visitors and members can equitably enjoy content on your website, regardless of ability.
Accessibility testing is part discovery, part validation. It shines a light on areas within your websites, applications, and web tools in need of improvement to be usable for as many people as possible. Testing helps your design or implementation teams improve based on the criteria of Web Content Accessibility Guidelines.
Web Content Accessibility Guidelines are a series of standards set for developers to define testable success criteria for web content accessibility. You can read more about these standards here WCAG Levels A, AA, AAA Guidelines.
Let’s start by showing you how to add Accessibility Checks as a new test.
Accessibility checks are a part of functional UI tests. You can create tests that are dedicated to accessibility checks, or integrate these into your regular testing cadence. In this section, you’ll see how to create an individual accessibility check on a web page or element.
Based on your Accessibility Guidelines, you may want to trigger Accessibility Checks based on Tags or Rules.
While it’s important to add checks as individual tests or steps within your UI tests, you also need to know how to review the results of an individual test. Don’t worry, we’ve got you covered.
Now that you’ve seen how to review an individual Accessibility Check test result, it’s important to review your application’s accessibility performance at a high-level. Let’s do this!
Reflect - What did we learn?
Connect - How is it related to what you know and are doing?
Apply - How to use this going forward?