Understanding SC 1.4.10 Reflow
|

Understanding SC 1.4.10 Reflow

Success Criterion 1.4.10 Reflow (Level AA): Content can be presented without loss of information or functionality, and without requiring scrolling in two dimensions for: Vertical scrolling content at a width equivalent to 320 CSS pixels; Horizontal scrolling content at a height equivalent to 256 CSS pixels. Except for parts of the content which require two-dimensional…

Understanding SC 1.4.12 Text Spacing
|

Understanding SC 1.4.12 Text Spacing

Success Criterion 1.4.12 Text Spacing (Level AA): In content implemented using markup languages that support the following text style properties, no loss of content or functionality occurs by setting all of the following and by changing no other style property: Line height (line spacing) to at least 1.5 times the font size; Spacing following paragraphs…

Understanding SC 1.3.5 Identify Input Purpose
|

Understanding SC 1.3.5 Identify Input Purpose

Success Criterion 1.3.5 Identify Input Purpose (Level AA): The purpose of each input field collecting information about the user can be programmatically determined when: The input field serves a purpose identified in the Input Purposes for User Interface Components section; and The content is implemented using technologies with support for identifying the expected meaning for…

Understanding SC 1.3.4 Orientation
|

Understanding SC 1.3.4 Orientation

Success Criterion 1.3.4 Orientation (Level AA): Content does not restrict its view and operation to a single display orientation, such as portrait or landscape, unless a specific display orientation is essential.Examples where a particular display orientation may be essential are a bank check, a piano application, slides for a projector or television, or virtual reality…

Understanding SC 4.1.2 Name, Role, Value
|

Understanding SC 4.1.2 Name, Role, Value

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…

Understanding SC 4.1.1 Parsing
|

Understanding SC 4.1.1 Parsing

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)Note: Start and end tags that are missing a critical character in their formation,…