Tag Archives: WCAG 2.1

1.4.12 Text Spacing

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 to at least 2 times the font… Continue Reading 1.4.12 Text Spacing

WCAG 2.1 color contrast analyzer

During June 2018, W3C WAI recommended the new accessibility standard Web Content Accessibility Guidelines 2.1 i.e. WCAG 2.1. Along with many new success criteria specific success criterion is added that speaks about color contrast for non-text content. While the existing 1.4.3 contrast (minimum)  and 1.4.6 contrast (Enhanced) still exist. 1.4.11 Non-text contrast The success criteria… Continue Reading WCAG 2.1 color contrast analyzer

1.4.11 Non-text Contrast

the following have a contrast ratio of at least 3:1 against adjacent color(s): User Interface Components Visual information required to identify user interface components and states, except for inactive components or where the appearance of the component is determined by the user agent and not modified by the author; Graphical Objects Parts of graphics required… Continue Reading 1.4.11 Non-text Contrast

1.4.10 Reflow

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 layout for usage or meaning. Description People with… Continue Reading 1.4.10 Reflow

1.3.5 Identify Input Purpose

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 form input data. (Level AA) Description   While… Continue Reading 1.3.5 Identify Input Purpose

1.3.4 Orientation

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. (Level AA) 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 content where binary… Continue Reading 1.3.4 Orientation