When I initially started in the accessibility space more than a decade ago there were limited resources available for learning accessibility; how to interpret Web Content Accessibility Guidelines (WCAG) and record the failures of the WCAG. The official W3C documentation Web Content Accessibility Guidelines (WCAG) has been very academic in nature for novices like me,…
When WCAG 2.1 came out in 2018, it introduced a new success criterion namely 1.3.5 – Identify Input Purpose. It aims to ease the auto-fill capability of browsers and other assistive technologies when web sites and apps ask the users to fill out personal information. One of the sufficient techniques suggested to test for the…
Digital accessibility is an immense subject, and jobs within the accessibility space have seen a tremendous uptick in the last few years. When I initially started in web accessibility, there werehardly any jobs available, and the one or two openings had a lot of competition. The rise in awareness and active pursuit of accessible services…
The goal of this success criterion is to make the processes where repeated steps are found easier by: For example, a checkout flow in an e-commerce site asks shipping address and billing address to be entered. If both the addresses are the same, the site can provide a “My shipping address is the same as…
The goal of this success criterion is to ensure that the users find the help to complete a task in a consistent location across a set of web pages. When a help the mechanism is available in a set of web pages it is available in the same order relative to other contents of the…
The intent of this success criterion is to ensure the target of any UI element has 24 by 24 CSS PX target size or there is enough spacing provided between two targets that have undersize targets. Note that zooming or other style changes adopted by users with disabilities must not modify the target sizes. So,…
