Users can choose to target either WCAG 2.0, 2.1, or 2.2. Additionally, across both WCAG versions, we support identifying guideline violations related to Levels A, AA, and AAA. Refer to the following guides to learn how you can configure the WCAG settings.
What WCAG standards and levels can be targeted within our automatic scanners?
Did this answer your question?
What did you like?
We're sorry to hear that.
Thank you for your feedback.
Related articles
- Why am I seeing a banner that says, “‘BrowserStack Accessibility Toolkit’ started debugging this browser”?
- How can I view snapshots of the component that caused an accessibility violation in my Accessibility Report?
- Will bug reporting on Accessibility Testing work for on-premise test setups?
- What types of accessibility issues can be identified through BrowserStack Accessibility Testing?
- How can the reports generated by the BrowserStack Accessibility Testing tool be shared with developers for issue resolution?
- Does BrowserStack Accessibility Testing have the ability to scan pages that are protected by authentication for Accessibility issues?
- Is it possible to introduce accessibility testing to a pre-existing automation test suite?
