From ce91353a0d2d192568c52b8c24e6f14ea2f71f62 Mon Sep 17 00:00:00 2001 From: "Patrick H. Lauke" Date: Tue, 14 May 2024 18:26:41 +0100 Subject: [PATCH] Change `
    ` to `

Themes from Research

@@ -1217,7 +1190,7 @@

Themes from Research

  • Specific success criteria for failure - 1.1.1 , 2.2., 4.1.2 (Keith et al., 2012)
    • -
  • Reliably Human Testable, not reliably testable Is Accessibility Conformance an Elusive Property? (Brajnik et al. 2012), found the average agreement was at the 70-75% mark, while the error rate was around 29%. +
  • Reliably Human Testable, not reliably testable Is Accessibility Conformance an Elusive Property? (Brajnik et al. 2012), found the average agreement was at the 70-75% mark, while the error rate was around 29%.
    • Expertise appears to improve (by 19%) the ability to avoid false positives. Finally, pooling the results of two independent experienced evaluators would be the best option, capturing at most 76% of the true problems and producing only 24% of false positives. Any other independent combination of audits would achieve worse results.
    • This means that an 80% target for agreement, when audits are conducted without communication between evaluators, is not attainable, even with experienced evaluators.
      • @@ -1225,13 +1198,13 @@

      Themes from Research

    • Challenges and Recommendations (Alonso et al., 2010)
        -
      • accessibility supported ways of using technologies
        • +
      • accessibility supported ways of using technologies
      • Testability of Success Criteria
      • Openness of Techniques and Failures
      • Aggregation of Partial Results
      • -
    • Silver needs to expand the scope beyond web to include apps, documents, authoring, user agents, wearables, kiosks, IoT, VR, etc. and be inclusive of more disabilities. (UX Professionals Use of WCAG: Analysis)
      • +
    • Silver needs to expand the scope beyond web to include apps, documents, authoring, user agents, wearables, kiosks, IoT, VR, etc. and be inclusive of more disabilities. (UX Professionals Use of WCAG: Analysis)
    • Accessibility Supported allows inadequate assistive technologies to be claimed for conformance, particularly in non-native English speaking countries. (Interviews on Conformance)
    • @@ -1269,25 +1242,25 @@

    Evolving Technology

    Acknowledgments

    -
    -

    Participants of the AG WG who contributed to the development of this document:

    -
      -
    • Charles Adams (Oracle)
      • -
    • Alastair Campbell (Nomensa)
      • -
    • Michael Cooper (W3C)
      • -
    • Joe Cronin (Amazon)
      • -
    • Detlev Fischer (Invited Expert)
      • -
    • Charles Hall (Invited Expert)
      • -
    • Andrew Kirkpatrick (Adobe)
      • -
    • Peter Korn (Amazon)
      • -
    • Shawn Lauriat (Google)
      • -
    • Mary Jo Mueller (IBM)
      • -
    • Janina Sajka (Invited Expert; Was Amazon until 14 November 2021)
      • -
    • Jeanne Spellman (TetraLogical)
      • -
    • Jason White (ETS)
      • -
    -
    -
    +
    +

    Participants of the AG WG who contributed to the development of this document:

    +
      +
    • Charles Adams (Oracle)
      • +
    • Alastair Campbell (Nomensa)
      • +
    • Michael Cooper (W3C)
      • +
    • Joe Cronin (Amazon)
      • +
    • Detlev Fischer (Invited Expert)
      • +
    • Charles Hall (Invited Expert)
      • +
    • Andrew Kirkpatrick (Adobe)
      • +
    • Peter Korn (Amazon)
      • +
    • Shawn Lauriat (Google)
      • +
    • Mary Jo Mueller (IBM)
      • +
    • Janina Sajka (Invited Expert; Was Amazon until 14 November 2021)
      • +
    • Jeanne Spellman (TetraLogical)
      • +
    • Jason White (ETS)
      • +
    +
    +
    diff --git a/understanding/20/headings-and-labels.html b/understanding/20/headings-and-labels.html index 42e3e8dfa9..018e2eb24a 100644 --- a/understanding/20/headings-and-labels.html +++ b/understanding/20/headings-and-labels.html @@ -117,14 +117,14 @@

    Techniques for Headings and Labels

    Sufficient Techniques for Headings and Labels

    -
      +
    +
    diff --git a/understanding/20/use-of-color.html b/understanding/20/use-of-color.html index ebd406cc0b..e71b9d3b53 100644 --- a/understanding/20/use-of-color.html +++ b/understanding/20/use-of-color.html @@ -105,7 +105,7 @@

    Intent of Use of Color

    Most user agents provide users with a color-only cue that a link has been previously activated by them ("visited"). However, several technical constraints result in authors having very limited control over these color-only indications of visited links. The technical constraints are as follows:

    -
      +
      • User agents constrain the exposure of a link's visited state due to privacy concerns. Author queries to user agents will indicate all links have not been visited.
        • @@ -119,7 +119,7 @@

        Intent of Use of Color

        Authors also cannot set the visited state of links. The anchor element does not include a "visited" attribute; therefore the author has no ability to alter the state through an attribute setting. As such, authors cannot achieve 1.3.1 Info and Relationships or 4.1.2 Name, Role, Value in regard to visited links. -
    +

    For these reasons, setting or conveying a link's visited status is not an author responsibility. Where color alone distinguishes between visited and unvisited links, it does not result in a failure of this Success Criterion, even where the contrast between the two link colors is below 3:1. Note that authors must continue to ensure that all text links meet contrast minimums against the page background (SC 1.4.3).

    diff --git a/understanding/21/content-on-hover-or-focus.html b/understanding/21/content-on-hover-or-focus.html index 3d9d5478e2..cdca887970 100644 --- a/understanding/21/content-on-hover-or-focus.html +++ b/understanding/21/content-on-hover-or-focus.html @@ -15,17 +15,16 @@

    In brief

    What to do
    If hover or focus causes content changes, ensure interaction is predictable.
    Why it's important
    Unpredictable temporary content can be hard for some to consume and may disrupt others.
    -

    Intent

    Additional content that appears and disappears in coordination with keyboard focus or pointer hover often leads to accessibility issues. Reasons for such issues include:

    -
      -
    1. the user may not have intended to trigger the interaction
      2. -
    2. the user may not know new content has appeared
      3. -
    3. the new content may intefere with a user's ability to do a task
      4. -
    +

    Examples of such interactions can include custom tooltips, sub-menus and other nonmodal popups which display on hover and focus. The intent of this success criterion is to ensure that authors who cause additional content to appear and disappear in this manner must design the interaction in such a way that users can:

    Additional Notes

    - -
    + +

    Benefits

      -
    • Users with low vision who view content under magnification will be better able to view content on hover or focus without reducing their desired magnification.
      • -
    • Users who increase the size of mouse cursors via platform settings or assistive technology will be able to employ a technique to view obscured content on hover.
      • -
    • Users with low vision or cognitive disabilities will have adequate time to perceive additional content appearing on hover or focus and to view the trigger content with less distraction.
      • -
    • users with low pointer accuracy will be able to more easily dismiss unintentionally-triggered additional content
      • +
    • Users with low vision who view content under magnification will be better able to view content on hover or focus without reducing their desired magnification.
      • +
    • Users who increase the size of mouse cursors via platform settings or assistive technology will be able to employ a technique to view obscured content on hover.
      • +
    • Users with low vision or cognitive disabilities will have adequate time to perceive additional content appearing on hover or focus and to view the trigger content with less distraction.
      • +
    • users with low pointer accuracy will be able to more easily dismiss unintentionally-triggered additional content
    - +

    Examples

    - +

    Example 1: Dismissable Tooltip

    @@ -102,7 +101,7 @@

    Example 1: Dismissable Tooltip

    The button's tooltip also appears on focus and can be removed with the Escape key. The screen shot shows the same LVTF button with focus, but the tooltip has been dismissed and is no longer visible.
    - +

    Example 2: Hoverable Tooltip

    @@ -119,7 +118,7 @@

    Resources

  • Tooltip design described in WAI-ARIA Authoring Practices
    • - +

    Techniques

    diff --git a/understanding/21/interruptions-minimum.html b/understanding/21/interruptions-minimum.html index f6517a9adc..f493e03deb 100644 --- a/understanding/21/interruptions-minimum.html +++ b/understanding/21/interruptions-minimum.html @@ -11,12 +11,12 @@

    Understanding Interruptions (Minimum)

    Intent

    The intent of this Success Criterion is to avoid interrupting users during their interaction with a Web page. When users are distracted, especially users with impaired attention or memory, they may forget what they were doing and abandon the task. This can happen even when the original task is extremely important.

    Where a site may generate interruptions, the user must be able to postpone or suppress them, such that:

    -
      +
      • Popups and other interruptions can be easily delayed or turned off [Editor: do we need a definition for popup?]
      • Media events can be easily delayed or turned off [Editor: how is this different from Pause, Hide, Stop?]
      • Chat functions can be easily turned off and on again
      • Non-critical messages can easily be turned off and on again
        • -
    +

    Changes in content that are not initiated by the user must be avoided. Secondary content (such as special offers or complementary material) should be easily identified, controlled and turned off.

    Other potential distractions are covered by existing WCAG Success Criteria Pause, Stop, Hide, Audio Control, Three Flashes or Below Threshold, Low or No Background Audio, Timing Adjustable. These success criteria are aimed at specific considerations which can have repercussions on certain user groups, but also have a broader effect of reducing distractions for all users.

    diff --git a/understanding/21/text-spacing.html b/understanding/21/text-spacing.html index 47d7c7ab98..77b6c1f708 100644 --- a/understanding/21/text-spacing.html +++ b/understanding/21/text-spacing.html @@ -1,175 +1,170 @@ - - - Understanding Text Spacing - - - -

    Understanding Text Spacing

    + + + Understanding Text Spacing + + + +

    Understanding Text Spacing

    +
    +

    In brief

    +
    +
    Goal
    Users can adjust text spacing to make it easier to read.
    +
    Author task
    Ensure content adapts to user-defined text settings.
    +
    Why it's important
    Some people need text with different spacing or font characteristics.
    +
    +
    +
    +

    Intent

    +

    The intent of this Success Criterion (SC) is to ensure that when people override author specified text spacing to improve their reading experience, content is still readable and operable. Each of the requirements stipulated in the SC's four bullets helps ensure text styling can be adapted by the user to suit their needs.

    +

    The specified metrics set a minimum baseline. The values in between the author's metrics and the metrics specified in this SC should not have loss of content or functionality.

    +

    This SC focuses on the adaptability of content to an increase in spacing between lines, words, letters, and paragraphs. Any combination of these may assist a user with effectively reading text. As well, ensuring that content correctly adapts when users override author settings for spacing also significantly increases the likelihood other style preferences can be set by the user. For example, a user may need to change to a wider font family than the author has set in order to effectively read text.

    +
    +

    Author Responsibility

    +

    This SC does not dictate that authors must set all their content to the specified metrics, nor does the SC intend to imply that all users will adjust the specified metrics. Rather, it specifies that should a user choose to set any of these metrics they can do so without any loss of content or functionality. The author requirement is both to not interfere with a user's ability to override the author settings, and to ensure that content thus modified does not break content in the manners shown in figures 1 through 3 in Effects of Not Allowing for Spacing Override.

    -
    -

    In brief

    -
    -
    Goal
    Users can adjust text spacing to make it easier to read.
    -
    Author task
    Ensure content adapts to user-defined text settings.
    -
    Why it's important
    Some people need text with different spacing or font characteristics.
    -
    - -
    -
    -

    Intent

    -

    The intent of this Success Criterion (SC) is to ensure that when people override author specified text spacing to improve their reading experience, content is still readable and operable. Each of the requirements stipulated in the SC's four bullets helps ensure text styling can be adapted by the user to suit their needs.

    -

    The specified metrics set a minimum baseline. The values in between the author's metrics and the metrics specified in this SC should not have loss of content or functionality.

    -

    This SC focuses on the adaptability of content to an increase in spacing between lines, words, letters, and paragraphs. Any combination of these may assist a user with effectively reading text. As well, ensuring that content correctly adapts when users override author settings for spacing also significantly increases the likelihood other style preferences can be set by the user. For example, a user may need to change to a wider font family than the author has set in order to effectively read text.

    -
    -

    Author Responsibility

    -

    This SC does not dictate that authors must set all their content to the specified metrics, nor does the SC intend to imply that all users will adjust the specified metrics. Rather, it specifies that should a user choose to set any of these metrics they can do so without any loss of content or functionality. The author requirement is both to not interfere with a user's ability to override the author settings, and to ensure that content thus modified does not break content in the manners shown in figures 1 through 3 in Effects of Not Allowing for Spacing Override.

    +

    In some human languages and scripts, some of the metrics specified by the SC are inapplicable. For example, languages such as Japanese do not use spacing following paragraphs, meaning that users are unlikely to make any paragraph spacing changes in practice. The exception in this SC allows authors to ignore text style properties which are inapplicable to the combination of language and script being used.

    -

    In some human languages and scripts, some of the metrics specified by the SC are inapplicable. For example, languages such as Japanese do not use spacing following paragraphs, meaning that users are unlikely to make any paragraph spacing changes in practice. The exception in this SC allows authors to ignore text style properties which are inapplicable to the combination of language and script being used.

    +

    It is beneficial for users if authors use any locally available guidance for improving readability in the local language or writing system. If the user chooses to go beyond the metrics specified, any resulting loss of content or functionality is the user's responsibility.

    -

    It is beneficial for users if authors use any locally available guidance for improving readability in the local language or writing system. If the user chooses to go beyond the metrics specified, any resulting loss of content or functionality is the user's responsibility.

    - -

    Further, this SC is not concerned with how users change the line height and spacing metrics. It does not require that content implement its own mechanisms to allow users to do this. It is not a failure of the content if a user agent or platform does not provide a way for users to do this. Content does not fail this SC if the method chosen by the user - for instance, the use of an extension or bookmarklet - fails to correctly set the line height and spacing text properties on the content (provided that the content is not actively and purposely preventing the properties from being added).

    -
    -

    Applicability

    -

    If the markup-based technologies being used are capable of overriding text to the Success Criterion's metrics, then this SC is applicable. For instance Cascading Style Sheet/HTML technologies are quite able to allow for the specified spacing metrics. Plugin technologies would need to have a built-in ability to modify styles to the specified metrics. Currently, this SC does not apply to PDF as it is not implemented using markup.

    -

    Examples of text that are typically not affected by style properties and not expected to adapt are:

    -
      -
    • Video captions embedded directly into the video frames and not provided as an associated caption file
      • -
    • Images of text
      • -
    -

    For this SC, canvas implementations of text are considered to be images of text.

    -
    -
    -

    Use of ellipses

    -

    There may be regions of a page where text containers cannot expand due to design constraints (such as a maximum width for the left navigation or table column headers). A common convention if text exceeds its space is to replace truncated text with an ellipsis. Where ellipses appear as a result of modifying text style properties, the page can still meet the Text Spacing requirements, so long as the content is still available. For example:

    -
      -
    • a mechanism is provided to reveal the truncated text on the page (for instance, the text appears on focus or on activation)
      • -
    • where the ellipsis is part of a section of - content which includes a link, the truncated text is revealed on the linked page
      • -
    - -

    Where text is not truncated but it is when text is spaced, if there is no mechanism to show the truncated text, it fails this Success Criterion.

    -
    -
    -
    -

    User Responsibility

    -

    The ability to read and derive meaning from the overridden spacing rests with the user. The user may choose to exceed the spacing adjustments in the SC. If the increased spacing causes loss of content or functionality, the user will adjust or return to the author’s original spacing or spacing within the bounds of the SC. Regardless, the user needs the flexibility to adjust spacing within the bounds set in the SC without loss of content or functionality. Such changes may be achieved via user stylesheet, bookmarklet, extension, or application.

    -
    +

    Further, this SC is not concerned with how users change the line height and spacing metrics. It does not require that content implement its own mechanisms to allow users to do this. It is not a failure of the content if a user agent or platform does not provide a way for users to do this. Content does not fail this SC if the method chosen by the user - for instance, the use of an extension or bookmarklet - fails to correctly set the line height and spacing text properties on the content (provided that the content is not actively and purposely preventing the properties from being added).

    +
    +

    Applicability

    +

    If the markup-based technologies being used are capable of overriding text to the Success Criterion's metrics, then this SC is applicable. For instance Cascading Style Sheet/HTML technologies are quite able to allow for the specified spacing metrics. Plugin technologies would need to have a built-in ability to modify styles to the specified metrics. Currently, this SC does not apply to PDF as it is not implemented using markup.

    +

    Examples of text that are typically not affected by style properties and not expected to adapt are:

    +
      +
    • Video captions embedded directly into the video frames and not provided as an associated caption file
      • +
    • Images of text
      • +
    +

    For this SC, canvas implementations of text are considered to be images of text.

    -
    -

    Effects of Not Allowing for Spacing Override

    -

    The following images show some types of failures when authors do not take into consideration that users may override spacing to the metrics specified in this Success Criterion.

    -
    -

    Text Cut Off

    -

    The bottom portion of the words "Your Needs" is cut off in a heading making that text unreadable in Figure 1. It should read "We Provide a Mobile Application Service to Meet Your Needs."

    -
    -
    Vertical text cut off is a failure.
    - Heading text truncated vertically. -
    -

    In Figure 2 the last portion of text is cut off in 3 side-by-side headings. The 1st heading should read "A cog in the wheel." But it reads "A cog in the whe". Only half of the second "e" is visible and the letter "l" is completely missing. The 2nd heading should read "A penny for your thoughts". But it reads "A penny for your". The 3rd should read "Back to the drawing board." But it reads "Back to the drawi".

    -
    -
    Horizontal text cut off is a failure.
    - 3 side-by-side headings with truncated text. -
    -
    -
    -

    Text Overlap

    -

    In Figure 3 the last 3 words "Groups and Programs" of the heading "Technologists Seeking Input from Groups and Programs" overlap the following sentence. That sentence should read, "You are invited to share ideas and areas of interest related to the integration of technology from a group or program perspective." But the words "You are invited to share ideas" are obscured and unreadable.

    -
    -
    Overlapping text is a failure.
    - Heading text overlaps part of paragraph text. -
    -
    -
    -
    -
    -

    Benefits

    -
      -
    • People with low vision who require increased space between lines, words, and letters are able to read text.
      • -
    • People with dyslexia may increase space between lines, words, and letters to increase reading speed.
      • -
    • Although not required by this SC, white space between blocks of text can help people with cognitive disabilities discern sections and call out boxes.
      • -
    -
    -
    -

    Examples

    -

    When spacing is being overridden to the SC's metrics:

    -
      -
    1. Text fits within the bounds of its containing box without being cut off.
      2. -
    2. Text fits within the bounds of its containing box without overlapping other boxes.
      3. -
    +
    +

    Use of ellipses

    +

    There may be regions of a page where text containers cannot expand due to design constraints (such as a maximum width for the left navigation or table column headers). A common convention if text exceeds its space is to replace truncated text with an ellipsis. Where ellipses appear as a result of modifying text style properties, the page can still meet the Text Spacing requirements, so long as the content is still available. For example:

    +
      +
    • a mechanism is provided to reveal the truncated text on the page (for instance, the text appears on focus or on activation)
      • +
    • where the ellipsis is part of a section of content which includes a link, the truncated text is revealed on the linked page
      • +
    +

    Where text is not truncated but it is when text is spaced, if there is no mechanism to show the truncated text, it fails this Success Criterion.

    -
    -

    Resources

    -
    -

    Research

    -

    The grounds for this SC are based on research. The metrics chosen as measures are based on the McLeish study. She ran from .04 to .25 em tests. McLeish found an increasing curve in reading speed of actual materials up to .25, but it started to flatten at .20. Previous studies that reported no improvement started at .5em. Right at the flat point. Wayne E. Dick, Ph.D. analyzed the McLeish study and translated from points. Dr. Dick recommended the metrics that the Working Group adopted.

    -
    -

    Languages and Scripts

    -

    Roughly 480 different languages and scripts have been tested. Maximum spacing adjustments allowed by the SC were set on the following 3 pages:

    -
      -
    1. Languages in their own writing systems
      2. -
    2. Online Encyclopedia of writing systems and languages – language names
      3. -
    3. Universal Declaration of Human Rights (Article 1)
      4. -
    -
    -
    -

    Results

    -

    No adverse effects occurred. The following are the specific findings:

    -
    -
    Character Spacing
    -
    Individual characters in words remained intact though they were spaced a bit further apart.
    -
    Word Spacing
    -
    Words were spaced farther apart. In languages that do not have words (e.g. Japanese) applying word spacing had no effect. This is expected.
    -
    Line Height
    -
    Changing line height did not separate diacritics from characters, nor did it adversely impact ascenders or descenders.
    -
    -

    As previously discussed, the ability to read text with adjusted spacing is a user responsibility. This is true no matter the language.

    -

    The SC's exception addresses cases where a text style property is not used in a language or script. In such cases, authors are only required to ensure relevant properties do not break the layout.

    -
    -
    -
    -

    Other references

    - -
    +
    +
    +

    User Responsibility

    +

    The ability to read and derive meaning from the overridden spacing rests with the user. The user may choose to exceed the spacing adjustments in the SC. If the increased spacing causes loss of content or functionality, the user will adjust or return to the author’s original spacing or spacing within the bounds of the SC. Regardless, the user needs the flexibility to adjust spacing within the bounds set in the SC without loss of content or functionality. Such changes may be achieved via user stylesheet, bookmarklet, extension, or application.

    +
    + +
    +

    Effects of Not Allowing for Spacing Override

    +

    The following images show some types of failures when authors do not take into consideration that users may override spacing to the metrics specified in this Success Criterion.

    +
    +

    Text Cut Off

    +

    The bottom portion of the words "Your Needs" is cut off in a heading making that text unreadable in Figure 1. It should read "We Provide a Mobile Application Service to Meet Your Needs."

    +
    +
    Vertical text cut off is a failure.
    + Heading text truncated vertically. +
    +

    In Figure 2 the last portion of text is cut off in 3 side-by-side headings. The 1st heading should read "A cog in the wheel." But it reads "A cog in the whe". Only half of the second "e" is visible and the letter "l" is completely missing. The 2nd heading should read "A penny for your thoughts". But it reads "A penny for your". The 3rd should read "Back to the drawing board." But it reads "Back to the drawi".

    +
    +
    Horizontal text cut off is a failure.
    + 3 side-by-side headings with truncated text. +
    +
    +
    +

    Text Overlap

    +

    In Figure 3 the last 3 words "Groups and Programs" of the heading "Technologists Seeking Input from Groups and Programs" overlap the following sentence. That sentence should read, "You are invited to share ideas and areas of interest related to the integration of technology from a group or program perspective." But the words "You are invited to share ideas" are obscured and unreadable.

    +
    +
    Overlapping text is a failure.
    + Heading text overlaps part of paragraph text. +
    +
    +
    +
    +
    +

    Benefits

    +
      +
    • People with low vision who require increased space between lines, words, and letters are able to read text.
      • +
    • People with dyslexia may increase space between lines, words, and letters to increase reading speed.
      • +
    • Although not required by this SC, white space between blocks of text can help people with cognitive disabilities discern sections and call out boxes.
      • +
    +
    +
    +

    Examples

    +

    When spacing is being overridden to the SC's metrics:

    +
      +
    • Text fits within the bounds of its containing box without being cut off.
      • +
    • Text fits within the bounds of its containing box without overlapping other boxes.
      • +
    +
    +
    +

    Resources

    +
    +

    Research

    +

    The grounds for this SC are based on research. The metrics chosen as measures are based on the McLeish study. She ran from .04 to .25 em tests. McLeish found an increasing curve in reading speed of actual materials up to .25, but it started to flatten at .20. Previous studies that reported no improvement started at .5em. Right at the flat point. Wayne E. Dick, Ph.D. analyzed the McLeish study and translated from points. Dr. Dick recommended the metrics that the Working Group adopted.

    +
    +

    Languages and Scripts

    +

    Roughly 480 different languages and scripts have been tested. Maximum spacing adjustments allowed by the SC were set on the following 3 pages:

    +
    -
    -

    Techniques

    -
    -

    Sufficient

    - -
    -
    -

    Advisory

    - -
    -
    -

    Failure

    -
      -
      • -
    -
    +
    +

    Results

    +

    No adverse effects occurred. The following are the specific findings:

    +
    +
    Character Spacing
    +
    Individual characters in words remained intact though they were spaced a bit further apart.
    +
    Word Spacing
    +
    Words were spaced farther apart. In languages that do not have words (e.g. Japanese) applying word spacing had no effect. This is expected.
    +
    Line Height
    +
    Changing line height did not separate diacritics from characters, nor did it adversely impact ascenders or descenders.
    +
    +

    As previously discussed, the ability to read text with adjusted spacing is a user responsibility. This is true no matter the language.

    +

    The SC's exception addresses cases where a text style property is not used in a language or script. In such cases, authors are only required to ensure relevant properties do not break the layout.

    +
    +
    +
    +

    Other references

    + +
    +
    +
    +

    Techniques

    +
    +

    Sufficient

    + +
    - +
    +

    Advisory

    + +
    +
    +

    Failure

    +
      +
      • +
    +
    +
    + diff --git a/understanding/22/accessible-authentication-enhanced.html b/understanding/22/accessible-authentication-enhanced.html index 65e6b5c16d..978c7385dd 100644 --- a/understanding/22/accessible-authentication-enhanced.html +++ b/understanding/22/accessible-authentication-enhanced.html @@ -78,6 +78,7 @@

    Sufficient Techniques

    Using two techniques to provide 2 factor authentication (Potential future technique) +
    diff --git a/understanding/22/accessible-authentication-minimum.html b/understanding/22/accessible-authentication-minimum.html index 73afcd2cc9..ceec50bf01 100644 --- a/understanding/22/accessible-authentication-minimum.html +++ b/understanding/22/accessible-authentication-minimum.html @@ -168,15 +168,13 @@

    Resources

    -
    diff --git a/understanding/22/consistent-help.html b/understanding/22/consistent-help.html index 548fa474d0..f4bcbf851a 100644 --- a/understanding/22/consistent-help.html +++ b/understanding/22/consistent-help.html @@ -125,9 +125,9 @@

    Techniques for Consistent Help

    Sufficient Techniques for Consistent Help

    -
      +
    +
    diff --git a/understanding/22/dragging-movements.html b/understanding/22/dragging-movements.html index cfd95729cb..06537aa102 100644 --- a/understanding/22/dragging-movements.html +++ b/understanding/22/dragging-movements.html @@ -98,11 +98,11 @@

    Techniques for Dragging

    Sufficient Techniques for Dragging Movements

    -
      +
    +
    diff --git a/understanding/22/focus-appearance.html b/understanding/22/focus-appearance.html index fd361b4092..55f6a535a8 100644 --- a/understanding/22/focus-appearance.html +++ b/understanding/22/focus-appearance.html @@ -749,7 +749,7 @@

    Techniques

    Sufficient Techniques

    -
      +
    +

    Failures

    -
      +
    +
    diff --git a/understanding/22/focus-not-obscured-enhanced.html b/understanding/22/focus-not-obscured-enhanced.html index 6a97de1ead..0a97097900 100644 --- a/understanding/22/focus-not-obscured-enhanced.html +++ b/understanding/22/focus-not-obscured-enhanced.html @@ -48,9 +48,9 @@

    Resources

    Techniques for Focus Not Obscured (Enhanced)

    Sufficient Techniques

    -
      +
    +

    Additional Techniques (Advisory)

    diff --git a/understanding/22/focus-not-obscured-minimum.html b/understanding/22/focus-not-obscured-minimum.html index 9002577c39..78ffdb1468 100644 --- a/understanding/22/focus-not-obscured-minimum.html +++ b/understanding/22/focus-not-obscured-minimum.html @@ -173,11 +173,11 @@

    Techniques for Focus Not Obscured (Minimum)

    Sufficient Techniques

    -
      +
    +
    @@ -188,11 +188,11 @@

    Additional Techniques (Advisory)

    Failures

    -
      +
    +
    diff --git a/understanding/22/target-size-minimum.html b/understanding/22/target-size-minimum.html index c6b11a93df..70048d3c36 100644 --- a/understanding/22/target-size-minimum.html +++ b/understanding/22/target-size-minimum.html @@ -175,11 +175,11 @@

    Techniques for Target Size (Minimum)

    Sufficient Techniques for Target Size (Minimum)

    -
      +
    +