Testing Web Accessibility #133
Replies: 1 comment
-
Aquí tenéis el resumen de mi charla en Español:
|
Beta Was this translation helpful? Give feedback.
-
Aquí tenéis el resumen de mi charla en Español:
|
Beta Was this translation helpful? Give feedback.
-
Speaker: Adrián Bolonio
"When we develop a new website, we often put a lot of work into the design, to make it beautiful and usable. In other words, we want our website to be effective, efficient and satisfactory for the user. But many times we don't think about the user experience for people with disabilities, including people with age-related disabilities.
Web accessibility (a11y) means that people with disabilities can perceive, understand, navigate and interact with websites and tools, and that they can contribute equally without barriers." (Source: W3C - Web Accessibility Initiative). Our role as frontend developers is to create clear interfaces for people to understand and care about data, regardless of their disabilities or impairments, but what we developers often forget is to make sure that the code we write follows the Web Content Accessibility Guidelines (WCAG), and the only way to achieve this is through testing, either manual or automated.
Automated web accessibility tests can free our QA team from manual testing of every part of our application, but they cannot make our site automatically and magically accessible.
We should use automated web accessibility tests as a step in a larger testing process. Let's not forget that only 20% to 50% of all accessibility issues can be automatically detected.
I will teach some testing tools, libraries and techniques to increase the test coverage of your code with a simple example with a React application."
Beta Was this translation helpful? Give feedback.
All reactions