3.3.1 Error Identification: If an input error is automatically detected, the item that is in error is identified and the error is described to the user in text. (Level A) Web is built with multiple components. One of the components to collect the data from the users is forms. When the data entered into these […]
Continue reading Understanding SC 3.3.1 Error IdentificationWeb Accessibility
How & Where to report accessibility bugs
As an Accessibility Evangelist I work with various clients & most of the time it show happens that a particular widget or code that is suggested might not work as expected in a Screen Reader & Browser Combination. There is no guarantee that what works with NVDA+Firefox, JAWS+Chrome & VoiceOver+Safari will work as expected on […]
Continue reading How & Where to report accessibility bugsUnderstanding SC 3.2.4 Consistent Identification
3.2.4 Consistent Identification: Components that have the same functionality within a set of Web pages are identified consistently. (Level AA) The guideline requires that functional components (elements) that appear repeatedly in a set of web pages must have the same name/label. This helps Assistive aid users who heavily rely on these functional elements for quick […]
Continue reading Understanding SC 3.2.4 Consistent IdentificationUnderstanding SC 3.2.3 Consistent Navigation
3.2.3 Consistent Navigation: Navigational mechanisms that are repeated on multiple Web pages within a set of Web pages occur in the same relative order each time they are repeated, unless a change is initiated by the user. (Level AA) This success criterion requires that the commonly repeated navigation related user interface elements like skip to […]
Continue reading Understanding SC 3.2.3 Consistent NavigationUnderstanding SC 3.2.2 on Input
3.2.2 On Input: Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behavior before using the component. (Level A) This success criterion conveys that change of context should not occur while user is trying to input data. For example, if […]
Continue reading Understanding SC 3.2.2 on InputUnderstanding SC 3.2.1 on Focus
3.2.1 On Focus: When any component receives focus, it does not initiate a change of context. (Level A) The intent of this success criterion is to make sure that any unwanted actions are not initiated when focus moves on to an element. For example during tab navigation or shift tab navigation if user focus moves […]
Continue reading Understanding SC 3.2.1 on Focus