Our News
Latest announcement, articles, and more!
Latest announcement, articles, and more!
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) Requirements Changing the state of any user interface component (like a dropdown or a checkbox) must not automatically cause unexpected changes…
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) Requirements Navigational items that are repeated on multiple pages of a website (e.g. Search field, social…
3.2.4 Consistent Identification: Components that have the same functionality within a set of Web pages are identified consistently. (Level AA) This applies to native apps by replacing “Web pages” with “screens”. Requirements When the same user interface components, with the same functionality, are used in multiple places, they must be identified in a consistent way.…
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 with text. (Level A) Requirements Why is it important? This ensures that the form validation error is available to people who cannot see, distinguish colours, or understand icons and…
3.3.2 Labels or Instructions: Labels or instructions are provided when content requires user input. (Level A) Requirements Labels Required fields Additional instructions Why is it important? This ensures that everyone understands any requirements for entering data, and that screen reader users are made aware of it. Summary Common mistakes Design Guide Examples for Android For…
3.3.3 Error Suggestion: If an input error is automatically detected and suggestions for correction are known, then the suggestions are provided to the user, unless it would jeopardize the security or purpose of the content. (Level AA) Requirements Why is it important? This helps everyone resolve issues more easily, but especially people with cognitive disabilities…
3.3.4 Error Prevention (Legal, Financial, Data): For Web pages that cause legal commitments or financial transactions for the user to occur, that modify or delete user-controllable data in data storage systems, or that submit user test responses, at least one of the following is true: (Level AA) Reversible: Submissions are reversible. Checked: Data entered by…
4.1.1 Parsing: In content implemented using markup languages, elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique, except where the specifications allow these features. (Level A) Requirements (Web only) HTML elements have complete start and end tags; HTML elements…
4.1.2 Name, Role, Value: For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to…
4.1.3 Status Messages: In content implemented using markup languages, status messages can be programmatically determined through role or properties such that they can be presented to the user by assistive technologies without receiving focus. (Level AA) Requirements There are different situations where a status message need to be shown in a way that screen readers…
Sign up with your email address to receive our weekly news