From 52b808d3dd4391f0e67e601433a109a29c66a312 Mon Sep 17 00:00:00 2001 From: "Patrick H. Lauke" Date: Tue, 24 Oct 2023 23:51:55 +0100 Subject: [PATCH] Change `
    ` to ` diff --git a/guidelines/terms/20/changes-of-context.html b/guidelines/terms/20/changes-of-context.html index 9992de5ac6..a9d694a58a 100644 --- a/guidelines/terms/20/changes-of-context.html +++ b/guidelines/terms/20/changes-of-context.html @@ -7,7 +7,7 @@

    Changes in context include changes of:

    -
      +
    +

    A change of content is not always a change of context. Changes in content, such as an expanding outline, dynamic menu, or a tab control do not necessarily change the diff --git a/guidelines/terms/20/general-flash-and-red-flash-thresholds.html b/guidelines/terms/20/general-flash-and-red-flash-thresholds.html index 1713d8ab13..270e54237d 100644 --- a/guidelines/terms/20/general-flash-and-red-flash-thresholds.html +++ b/guidelines/terms/20/general-flash-and-red-flash-thresholds.html @@ -4,7 +4,7 @@

    a flash or rapidly changing image sequence is below the threshold (i.e., content passes) if any of the following are true:

    -
      +
      • there are no more than three general flashes and / or no more than three red flashes within any one-second period; or
        • @@ -14,7 +14,7 @@ degree visual field on the screen) at typical viewing distance -
    +

    where:

    diff --git a/guidelines/terms/20/structure.html b/guidelines/terms/20/structure.html index acc6615aec..07a3cd8f92 100644 --- a/guidelines/terms/20/structure.html +++ b/guidelines/terms/20/structure.html @@ -1,7 +1,7 @@
    structure
    -
      +
      • The way the parts of a Web page are organized in relation to each other; and
        • @@ -9,6 +9,6 @@
      • The way a collection of Web pages is organized
        • -
    +
    \ No newline at end of file diff --git a/understanding/20/headings-and-labels.html b/understanding/20/headings-and-labels.html index e83cea87c6..449dcca034 100644 --- a/understanding/20/headings-and-labels.html +++ b/understanding/20/headings-and-labels.html @@ -116,14 +116,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 1f52cc6284..5a52de123b 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 8385ba19ff..19b363878a 100644 --- a/understanding/21/content-on-hover-or-focus.html +++ b/understanding/21/content-on-hover-or-focus.html @@ -20,11 +20,11 @@

    In brief

    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:

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

    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:

      diff --git a/understanding/21/interruptions-minimum.html b/understanding/21/interruptions-minimum.html index 008f35af8f..fac4d01338 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 06165d6628..d52924acaa 100644 --- a/understanding/21/text-spacing.html +++ b/understanding/21/text-spacing.html @@ -95,10 +95,10 @@

    Benefits

    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

    @@ -108,11 +108,11 @@

    Research

    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:

    -
      +
    +

    Results

    diff --git a/understanding/22/accessible-authentication-enhanced.html b/understanding/22/accessible-authentication-enhanced.html index 7e9a72224b..330f3b4939 100644 --- a/understanding/22/accessible-authentication-enhanced.html +++ b/understanding/22/accessible-authentication-enhanced.html @@ -95,7 +95,7 @@

    Techniques for Accessible Authentication (Enhanced)

    Sufficient Techniques for Accessible Authentication

    -
      +
      • Email link authentication
        • @@ -111,7 +111,7 @@

        Sufficient Techniques for Accessible Authentication

      • Using two techniques to provide 2 factor authentication (Potential future technique)
        • -
    +
    @@ -122,11 +122,11 @@

    Additional Techniques (Advisory) for Accessible Authentication (Enhanced)

    Failures for Accessible Authentication (Enhanced)

    -
      +
    +
    diff --git a/understanding/22/accessible-authentication-minimum.html b/understanding/22/accessible-authentication-minimum.html index e3fb367031..e2152c0663 100644 --- a/understanding/22/accessible-authentication-minimum.html +++ b/understanding/22/accessible-authentication-minimum.html @@ -36,11 +36,11 @@

    Accessible Authentication (Minimum) Success Criteria text

    "Object recognition" and "Personal content" may be represented by images, video, or audio.

    Examples of mechanisms that satisfy this criterion include: -
      +
      • support for password entry by password managers to reduce memory need;
      • copy and paste to reduce the cognitive burden of re-typing;
      • Support for on-device biometric authentication.
        • -
    +
    @@ -168,7 +168,7 @@

    Techniques for Accessible Authentication

    Sufficient Techniques for Accessible Authentication

    -
      +
      • Email link authentication
        • @@ -184,7 +184,7 @@

        Sufficient Techniques for Accessible Authentication

      • Using two techniques to provide 2 factor authentication (Potential future technique)
        • -
    +
    @@ -195,11 +195,11 @@

    Additional Techniques (Advisory) for Accessible Authentication

    Failures for Accessible Authentication (Minimum)

    -
      +
    +
    diff --git a/understanding/22/consistent-help.html b/understanding/22/consistent-help.html index bf652266fc..2a6c361537 100644 --- a/understanding/22/consistent-help.html +++ b/understanding/22/consistent-help.html @@ -150,9 +150,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 9db1a3aac8..05ca5605f9 100644 --- a/understanding/22/dragging-movements.html +++ b/understanding/22/dragging-movements.html @@ -110,11 +110,11 @@

    Techniques for Dragging

    Sufficient Techniques for Dragging Movements

    -
      +
    +
    diff --git a/understanding/22/focus-appearance.html b/understanding/22/focus-appearance.html index 37ddea2d23..bb3f7aeb2f 100644 --- a/understanding/22/focus-appearance.html +++ b/understanding/22/focus-appearance.html @@ -464,7 +464,7 @@

    Techniques

    Sufficient Techniques

    -
      +
    +

    Failures

    -
      +
      • Using a CSS border for inline text which can wrap (Potential future technique)
        • -
    +
    diff --git a/understanding/22/focus-not-obscured-enhanced.html b/understanding/22/focus-not-obscured-enhanced.html index 1bf24bad0b..7a4087562a 100644 --- a/understanding/22/focus-not-obscured-enhanced.html +++ b/understanding/22/focus-not-obscured-enhanced.html @@ -59,9 +59,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 12d996f2f4..b12d9da9ad 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 c81edfbc2c..15cdac1a7c 100644 --- a/understanding/22/target-size-minimum.html +++ b/understanding/22/target-size-minimum.html @@ -193,11 +193,11 @@

    Techniques for Target Size (Minimum)

    Sufficient Techniques for Target Size (Minimum)

    -
      +
    +