Accessibility testing is a type of [[Operational testing]] that is involved with verifying that end users can consume or navigate content, usually through assistive devices like screen readers. While most forms of testing begin with the statistically normal user in mind, accessibility testing seeks out the [[Outlier|outliers]] in terms of location, linguistic background, and disability. ## What does "accessible" mean? ### Easily obtainable Anyone should be able to interact with our site regardless of their personal circumstances. Can a hearing- or sight-impaired person navigate your app without difficulties? ### Easily understandable Even if a user can navigate your app and obtain the information, is it presented in a way that they can comprehend? This could be related to [[Linguistic privilege]]. [[English is the most used language on the internet]], and this gives non-native English speakers a distinct disadvantage. ## Benefits ### Legal compliance For some companies and some industries, adherence to accessibility standards is mandatory. ### Accessibility enhances overall user experience Accessibility testing benefits people who have disabilities or are part of minority groups the most, but it still improves the experience for other users as well. [[Pragati Sharma]] [[Accessibility Automation Testing|gives the example]] of most people using ramps when faced with a choice between ramps and stairs, even if they're not disabled. ## Tools ### A tool to automate the browser [[Browser-based testing|Browser-based]] tools seem to be required for accesibility testing, as most accessibility issues need to be tested from the browser. - [[Cypress]] - [[Selenium WebDriver]] ### Accessibility engine Accessibility engines integrate with browser-based tools to enable a suite of checks according to accessibility standards. - [[axe (accessibility tool)]] ## References - [[Accessibility Automation Testing]] ## See also - [[Accessibility vs usability]]