This is a proposal to update the current WCAG2ICT document, which is based on WCAG 2.0, to WCAG 2.1.
From Success Criterion 1.3.4:
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 content where binary display orientation is not applicable.
This applies directly as written, and as described in Intent from Understanding Success Criterion 1.3.4 (also provided below).
Intent from Understanding Success Criterion 1.3.4 in Understanding WCAG 2.1 (View full version of guidance for Success Criterion 1.3.4):
Understanding text here.(left out for this draft because its in development)
From Success Criterion 1.3.5:
The meaning of each input field collecting information about the user can be programmatically determined when:
- The input field has a meaning that maps to the HTML 5.2 Autofill field names; and
- The content is implemented using technologies with support for identifying the expected meaning for form input data.
This applies directly as written, and as described in Intent from Understanding Success Criterion 1.3.5 (also provided below).
Note 1: Mechanisms to determine the meanings of input fields are not currently available in documents. However, if they do appear, this guidance is accurate.
Intent from Understanding Success Criterion 1.3.5 in Understanding WCAG 2.1 (View full version of guidance for Success Criterion 1.3.5):
Understanding text here. (left out for this draft cause its in development)
From Success Criterion 1.4.10:
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.
Note: 320 CSS pixels is equivalent to a starting viewport width of 1280 CSS pixels wide at 400% zoom. For web content which are designed to scroll horizontally (e.g. with vertical text), the 256 CSS pixels is equivalent to a starting viewport height of 1024px at 400% zoom.
Examples of content which require two-dimensional layout are images, maps, diagrams, video, games, presentations, data tables, and interfaces where it is necessary to keep toolbars in view while manipulating content.
This applies directly as written, and as described in Intent from Understanding Success Criterion 1.4.10 (also provided below).
Note 1: It is likely that for software there will be more frequent cases where two-dimensional layout are required for usage or meaning.
Intent from Understanding Success Criterion 1.3.4 in Understanding WCAG 2.1 (View full version of guidance for Success Criterion 1.2.1):
Understanding text here. (left out for this draft cause its in development)
From Success Criterion 1.4.11:
The visual presentation of the following have a contrast ratio of at least 3:1 against adjacent color(s):
- User Interface Components
- Visual information used to indicate states and boundaries of user interface components, 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 to understand the content, except when a particular presentation of graphics is essential to the information being conveyed.
This applies directly as written, and as described in Intent from Understanding Success Criterion 1.4.11 (also provided below).
Intent from Understanding Success Criterion 1.4.11 in Understanding WCAG 2.1 (View full version of guidance for Success Criterion 1.4.11):
Understanding text here. (left out for this draft because its in development)
From Success Criterion 1.4.12:
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 size;
- Letter spacing (tracking) to at least 0.12 times the font size;
- Word spacing to at least 0.16 times the font size.
Exception: Human languages and scripts which do not make use of one or more of these text style properties in written text can conform using only the properties that are used.
This applies directly as written, and as described in Intent from Understanding Success Criterion 4.1.12 (also provided below).
With this substitution, it would read:
1.4.12 Text Spacing: [For non-web documents or software that use markup languages, in such a way that the markup is separately exposed and available to assistive technologies and accessibility features of software or to a user-selectable user agent], elements 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:
Exception: Human languages and scripts which do not make use of one or more of these text style properties in written text can conform using only the properties that are used.
From Success Criterion 1.4.13:
Where receiving and removing pointer hover or keyboard focus triggers additional content to become visible and hidden, respectively, the following are true:
- Dismissable
- A mechanism is available to dismiss the additional content without moving pointer hover or keyboard focus, unless the additional content communicates an input error or does not obscure or replace other content;
- Hoverable
- If pointer hover can trigger the additional content, then the pointer can be moved over the additional content without the additional content disappearing;
- Persistent
- The additional content remains visible until the hover or focus trigger is removed, the user dismisses it, or its information is no longer valid.
Exception: The visual presentation of the additional content is controlled by the user agent and is not modified by the author.
Examples of additional content controlled by the user agent include browser tooltips created through use of the HTML
titleattribute.Custom tooltips, sub-menus, and other nonmodal popups that display on hover and focus are examples of additional content covered by this criterion.
This applies directly as written, and as described in Intent from Understanding Success Criterion 1.4.13 (also provided below).
Intent from Understanding Success Criterion 1.4.13 in Understanding WCAG 2.1 (View full version of guidance for Success Criterion 1.4.13):
Understanding text here. (left out for this draft because its in development)
From Success Criterion 2.1.4:
If a keyboard shortcut is implemented in content using only letter (including upper- and lower-case letters), punctuation, number, or symbol characters, then at least one of the following is true:
- Turn off
- A mechanism is available to turn the shortcut off;
- Remap
- A mechanism is available to remap the shortcut to use one or more non-printable keyboard characters (e.g. Ctrl, Alt, etc).
- Active only on focus
- The keyboard shortcut for a user interface component is only active when that component has focus.
This applies directly as written, and as described in Intent from Understanding Success Criterion 2.1.4 (also provided below).
Intent from Understanding Success Criterion 2.1.4 in Understanding WCAG 2.1 (View full version of guidance for Success Criterion 2.1.4):
Understanding text here. (left out for this draft because its in development)
From Success Criterion 2.5.3:
For user interface components with labels that include text or images of text, the name contains the text presented visually.
A best practice is to have the text of the label at the start of the name.
This applies directly as written, and as described in Intent from Understanding Success Criterion 2.5.3 (also provided below).
Intent from Understanding Success Criterion 2.5.3 in Understanding WCAG 2.1 (View full version of guidance for Success Criterion 2.5.3):
Understanding text here. (left out for this draft because its in development)
From Success Criterion 2.5.1:
All functionality that uses multipoint or path-based gestures for operation can be operated with a single pointer without a path-based gesture, unless a multipoint or path-based gesture is essential.
This requirement applies to web content that interprets pointer gestures (i.e. this does not apply to gestures that are required to operate the user agent or assistive technology).
This applies directly as written, and as described in Intent from Understanding Success Criterion 2.5.1 (also provided below).
Intent from Understanding Success Criterion 2.5.1 in Understanding WCAG 2.1 (View full version of guidance for Success Criterion 2.5.1):
Understanding text here. (left out for this draft because its in development)
From Success Criterion 2.5.2:
For functionality that can be operated using a single pointer, at least one of the following is true:
- No Down-Event
- The down-event of the pointer is not used to execute any part of the function;
- Abort or Undo
- Completion of the function is on the up-event, and a mechanism is available to abort the function before completion or undo the function after completion;
- Up Reversal
- The up-event reverses any outcome of the preceding down-event;
- Essential
- Completing the function on the down-event is essential.
This applies directly as written, and as described in Intent from Understanding Success Criterion 2.5.2 (also provided below).
Intent from Understanding Success Criterion 2.5.2 in Understanding WCAG 2.1 (View full version of guidance for Success Criterion 2.5.2):
Understanding text here. (left out for this draft because its in development)
From Success Criterion 2.5.4:
Functionality that can be operated by device motion or user motion can also be operated by user interface components and responding to the motion can be disabled to prevent accidental actuation, except when:
- Supported Interface
- The motion is used to operate functionality through an accessibility supported interface;
- Essential
- The motion is essential for the function and doing so would invalidate the activity.
This applies directly as written, and as described in Intent from Understanding Success Criterion 2.5.4 (also provided below).
Intent from Understanding Success Criterion 2.5.4 in Understanding WCAG 2.1 (View full version of guidance for Success Criterion 2.5.4):
Understanding text here. (left out for this draft because its in development)
From Success Criterion 4.1.3:
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.
This applies directly as written, and as described in Intent from Understanding Success Criterion 2.6.2 (also provided below).
Intent from Understanding Success Criterion 4.1.3 in Understanding WCAG 2.1 (View full version of guidance for Success Criterion 4.1.3):
Understanding text here. (left out for this draft because its in development)