From 2e0e694f694cf80420d82eeed1102e737c7e3dc1 Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Thu, 12 Oct 2023 15:33:00 -0700 Subject: [PATCH 01/80] Fix links to accessible authentication (minimum) --- understanding/22/accessible-authentication-enhanced.html | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/understanding/22/accessible-authentication-enhanced.html b/understanding/22/accessible-authentication-enhanced.html index 7e9a72224b..06a8c1f045 100644 --- a/understanding/22/accessible-authentication-enhanced.html +++ b/understanding/22/accessible-authentication-enhanced.html @@ -52,7 +52,7 @@

Cognitive function test definition

Intent of Accessible Authentication (Enhanced)

-

The purpose of this Success Criterion is to ensure there is an accessible, easy-to-use, and secure method to log in, access content, and undertake tasks. This criterion is the same as Accessible Authentication but without the exceptions for objects and user-provided content.

+

The purpose of this Success Criterion is to ensure there is an accessible, easy-to-use, and secure method to log in, access content, and undertake tasks. This criterion is the same as Accessible Authentication (Minimum) but without the exceptions for objects and user-provided content.

Any required step of the authentication process:

Resources

From a4271f08e4a5ed09c798377618c14d3bbaf81975 Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Mon, 16 Oct 2023 10:12:11 -0700 Subject: [PATCH 11/80] Scr36 make one URL relative, update another to 2.2 --- techniques/client-side-script/SCR36.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/techniques/client-side-script/SCR36.html b/techniques/client-side-script/SCR36.html index c5745a1012..15ee709981 100644 --- a/techniques/client-side-script/SCR36.html +++ b/techniques/client-side-script/SCR36.html @@ -20,7 +20,7 @@

Description

Some Web pages display scrolling text because there is limited space available. Scrolling the text in a small text window makes the content available for users who can read quickly enough, but causes problems for users who read more slowly or use assistive technology. This technique provides a mechanism to stop the movement and make the entire block of text available statically. The text may be made available in a separate window or in a (larger) section of the page. Users can then read the text at their own speed.

This technique does not apply when the text that is moving can not be displayed all at once on the screen (e.g., a long chat conversation).

-

This technique can be used in combination with a style switching technique to present a page that is a conforming alternate version for non-conforming content. Refer to C29: Using a style switcher to provide a conforming alternate version and Understanding Conforming Alternate Versions for more information.

+

This technique can be used in combination with a style switching technique to present a page that is a conforming alternate version for non-conforming content. Refer to C29: Using a style switcher to provide a conforming alternate version and Understanding Conforming Alternate Versions for more information.

From 5c3056719ddb473c0c00c4c83880f3d217837b7f Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Mon, 16 Oct 2023 10:12:58 -0700 Subject: [PATCH 12/80] Scr38 update absolute urls to relative, fix anchors --- techniques/client-side-script/SCR38.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/techniques/client-side-script/SCR38.html b/techniques/client-side-script/SCR38.html index 808c8aa7c3..fd213761f3 100644 --- a/techniques/client-side-script/SCR38.html +++ b/techniques/client-side-script/SCR38.html @@ -144,9 +144,9 @@

Related Techniques

Resources

From c444eba4b5c74df890f63249be80c0ccb9b2f767 Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Mon, 16 Oct 2023 10:24:50 -0700 Subject: [PATCH 13/80] Update C7 to change absolute URL to relative --- techniques/css/C7.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/techniques/css/C7.html b/techniques/css/C7.html index a21e87c8fc..2bcbb30ba7 100644 --- a/techniques/css/C7.html +++ b/techniques/css/C7.html @@ -22,7 +22,7 @@

Description

This technique is not a method for hiding complete links, only a section of text within a link. The resources section includes methods for hiding and showing links aimed at screen reader users.

This technique to hide link text has been advocated by some screen reader users and corporate Web authors. It has proved effective on some Web sites. Other screen reader users and accessibility experts don't recommend this as a general technique because the results can be overly chatty and constrain the ability of the experienced screen reader user to control the verbosity. The working group believes the technique can be useful for Web pages that do not have repetitive content in the hidden text areas.

-

This technique can be used in combination with a style switching technique to present a page that is a conforming alternate version for non-conforming content. Refer to C29 and Understanding Conforming Alternate Versions for more information.

+

This technique can be used in combination with a style switching technique to present a page that is a conforming alternate version for non-conforming content. Refer to C29 and Understanding Conforming Alternate Versions for more information.

From 7e0ceafa6997fd8ddb9480f774aa525c450dd6a0 Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Mon, 16 Oct 2023 10:26:52 -0700 Subject: [PATCH 14/80] Update C30 change absolute URL to relative --- techniques/css/C30.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/techniques/css/C30.html b/techniques/css/C30.html index 2be01691ac..3dfd82fdb0 100644 --- a/techniques/css/C30.html +++ b/techniques/css/C30.html @@ -21,7 +21,7 @@

Description

This technique can be used to meet Success Criterion 1.4.5 or 1.4.9 if a presentation that does not include images of text is available and as long as the user interface control that is provided to allow users to switch to an alternate presentation meets the relevant criteria. Where possible, authors should deliver the presentation that does not include images of text as the default presentation. In addition, the control used to switch should be located near the beginning of the page.

A variety of "image replacement" techniques have been developed to address a variety of user agent, configuration and compatibility with assistive technology issues (See resources for more information). While there are a variety of approaches authors may use to replace text, it is important to consider compatibility with assistive technology, whether the technique will work correctly if scripting, CSS, images (or combinations of these) are turned off. Since it can be difficult to find a single solution that works in all cases, this technique recommends the use of a control that allows users to switch to a presentation that does not include an image replacement technique.

-

This technique can be used in combination with a style switching technique to present a page that is a conforming alternate version for non-conforming content. Refer to C29 and Understanding Conforming Alternate Versions for more information.

+

This technique can be used in combination with a style switching technique to present a page that is a conforming alternate version for non-conforming content. Refer to C29 and Understanding Conforming Alternate Versions for more information.

From edde949cb8e3bbc5afbb70ca09f7cf5ac4fc96fe Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Fri, 3 Nov 2023 14:26:55 -0700 Subject: [PATCH 15/80] Remove references to XHTML --- techniques/failures/F36.html | 2 +- techniques/failures/F37.html | 2 +- techniques/failures/F38.html | 2 +- techniques/failures/F39.html | 2 +- techniques/failures/F41.html | 2 +- techniques/failures/F42.html | 2 +- techniques/failures/F43.html | 2 +- techniques/failures/F44.html | 2 +- techniques/failures/F46.html | 4 ++-- techniques/failures/F47.html | 2 +- techniques/failures/F48.html | 2 +- techniques/failures/F49.html | 2 +- techniques/failures/F59.html | 2 +- techniques/failures/F63.html | 2 +- techniques/failures/F65.html | 2 +- techniques/failures/F84.html | 2 +- techniques/failures/F90.html | 2 +- techniques/failures/F91.html | 2 +- techniques/failures/F92.html | 2 +- 19 files changed, 20 insertions(+), 20 deletions(-) diff --git a/techniques/failures/F36.html b/techniques/failures/F36.html index c12222ac96..ed73fc2b89 100644 --- a/techniques/failures/F36.html +++ b/techniques/failures/F36.html @@ -3,7 +3,7 @@ given a value

Failure of Success Criterion 3.2.2 due to automatically submitting a form and presenting new content without prior warning when the last field in the form is given a value

ID: F36

Technology: failures

Type: Failure

When to Use

-

HTML and XHTML

+

HTML

Description

Forms are frequently designed so that they submit automatically when the user has filled in all the fields, or when focus leaves the last field. There are diff --git a/techniques/failures/F37.html b/techniques/failures/F37.html index 1f40363aa8..0cdeeab5ee 100644 --- a/techniques/failures/F37.html +++ b/techniques/failures/F37.html @@ -1,7 +1,7 @@ Failure of Success Criterion 3.2.2 due to launching a new window without prior warning when the selection of a radio button, check box or select list is changed

Failure of Success Criterion 3.2.2 due to launching a new window without prior warning when the selection of a radio button, check box or select list is changed

ID: F37

Technology: failures

Type: Failure

When to Use

-

HTML and XHTML

+

HTML

Description

This document describes a failure that occurs when changing the selection of a radio button, a check box or an item in a select list causes a new window to diff --git a/techniques/failures/F38.html b/techniques/failures/F38.html index d3121bad25..975f700170 100644 --- a/techniques/failures/F38.html +++ b/techniques/failures/F38.html @@ -1,5 +1,5 @@ Failure of Success Criterion 1.1.1 due to not marking up decorative images in HTML in a way that allows assistive technology to ignore them

Failure of Success Criterion 1.1.1 due to not marking up decorative images in HTML in a way that allows assistive technology to ignore them

ID: F38

Technology: failures

Type: Failure

When to Use

-

HTML and XHTML

+

HTML

Description

This describes a failure condition for text alternatives for images that should be ignored by AT. If there is no alt attribute at all assistive diff --git a/techniques/failures/F39.html b/techniques/failures/F39.html index 038c860ca0..31645f9e86 100644 --- a/techniques/failures/F39.html +++ b/techniques/failures/F39.html @@ -2,7 +2,7 @@

Failure of Success Criterion 1.1.1 due to providing a text alternative that is not null (e.g., alt="spacer" or alt="image") for images that should be ignored by assistive technology

ID: F39

Technology: failures

Type: Failure

When to Use

-

Applies to HTML and XHTML.

+

HTML

Description

This technique describes a failure condition for images that should be ignored by assistive technologies. A text alternative for an image diff --git a/techniques/failures/F41.html b/techniques/failures/F41.html index ac8f21e0e2..8450d4b88c 100644 --- a/techniques/failures/F41.html +++ b/techniques/failures/F41.html @@ -1,5 +1,5 @@ Failure of Success Criterion 2.2.1, 2.2.4, and 3.2.5 due to using meta refresh to reload the page

Failure of Success Criterion 2.2.1, 2.2.4, and 3.2.5 due to using meta refresh to reload the page

ID: F41

Technology: failures

Type: Failure

When to Use

-

HTML and XHTML

+

HTML

Description

meta diff --git a/techniques/failures/F42.html b/techniques/failures/F42.html index 38ada7ca82..e87d28bbb8 100644 --- a/techniques/failures/F42.html +++ b/techniques/failures/F42.html @@ -1,5 +1,5 @@ Failure of Success Criteria 1.3.1, 2.1.1, 2.1.3, or 4.1.2 when emulating links

Failure of Success Criteria 1.3.1, 2.1.1, 2.1.3, or 4.1.2 when emulating links

ID: F42

Technology: failures

Type: Failure

When to Use

-

HTML and XHTML

+

HTML

Description

This failure occurs when JavaScript event handlers are attached to elements to emulate links. A link created in this manner cannot be tabbed to from the keyboard and does not gain keyboard focus like other controls and/or links. diff --git a/techniques/failures/F43.html b/techniques/failures/F43.html index 3065159169..14c0c03c58 100644 --- a/techniques/failures/F43.html +++ b/techniques/failures/F43.html @@ -1,7 +1,7 @@ Failure of Success Criterion 1.3.1 due to using structural markup in a way that does not represent relationships in the content

Failure of Success Criterion 1.3.1 due to using structural markup in a way that does not represent relationships in the content

ID: F43

Technology: failures

Type: Failure

When to Use

-

HTML and XHTML

+

HTML

Description

The objective of this technique is to describe a failure that occurs when structural markup is used to achieve a presentational effect, but indicates diff --git a/techniques/failures/F44.html b/techniques/failures/F44.html index a33f1d36c0..dda6c738f2 100644 --- a/techniques/failures/F44.html +++ b/techniques/failures/F44.html @@ -1,7 +1,7 @@ Failure of Success Criterion 2.4.3 due to using tabindex to create a tab order that does not preserve meaning and operability

Failure of Success Criterion 2.4.3 due to using tabindex to create a tab order that does not preserve meaning and operability

ID: F44

Technology: failures

Type: Failure

When to Use

-

HTML and XHTML

+

HTML

Description

This document describes a failure that occurs when the tab order does not follow logical relationships and sequences in the content.

diff --git a/techniques/failures/F46.html b/techniques/failures/F46.html index 02bc9a7dc0..c4e71ebdd8 100644 --- a/techniques/failures/F46.html +++ b/techniques/failures/F46.html @@ -3,13 +3,13 @@ layout tables

Failure of Success Criterion 1.3.1 due to using th elements, caption elements, or non-empty summary attributes in layout tables

ID: F46

Technology: failures

Type: Failure

When to Use

-

HTML and XHTML

+

HTML

Description

The objective of this technique is to describe a failure that occurs when a table used only for layout includes either th elements, a summary attribute, or a caption element. This is a failure because it uses structural (or semantic) markup only for - presentation. The intent of the HTML and XHTML table elements is to present data.

+ presentation. The intent of the HTML table elements is to present data.

Although not commonly used in a layout table, the following structural markup would also be failures of Success Criterion 1.3.1 if used in a layout table:

  • diff --git a/techniques/failures/F47.html b/techniques/failures/F47.html index 4dd3bb335f..dd43fa9340 100644 --- a/techniques/failures/F47.html +++ b/techniques/failures/F47.html @@ -1,5 +1,5 @@ Failure of Success Criterion 2.2.2 due to using the blink element

    Failure of Success Criterion 2.2.2 due to using the blink element

    ID: F47

    Technology: failures

    Type: Failure

    When to Use

    -

    HTML and XHTML

    +

    HTML

    Description

    The blink element, while not part of the official HTML or XHTML specification, is supported by many user agents. It causes any text inside diff --git a/techniques/failures/F48.html b/techniques/failures/F48.html index d57758719d..8b94dfe5ef 100644 --- a/techniques/failures/F48.html +++ b/techniques/failures/F48.html @@ -1,7 +1,7 @@ Failure of Success Criterion 1.3.1 due to using the pre element to markup tabular information

    Failure of Success Criterion 1.3.1 due to using the pre element to markup tabular information

    ID: F48

    Technology: failures

    Type: Failure

    When to Use

    -

    HTML and XHTML

    +

    HTML

    Description

    This document describes a failure caused by use of the HTML pre element to markup tabular information. The pre element diff --git a/techniques/failures/F49.html b/techniques/failures/F49.html index c626f83cd0..959953d926 100644 --- a/techniques/failures/F49.html +++ b/techniques/failures/F49.html @@ -1,7 +1,7 @@ Failure of Success Criterion 1.3.2 due to using an HTML layout table that does not make sense when linearized

    Failure of Success Criterion 1.3.2 due to using an HTML layout table that does not make sense when linearized

    ID: F49

    Technology: failures

    Type: Failure

    When to Use

    -

    HTML and XHTML

    +

    HTML

    Description

    Although WCAG 2 does not prohibit the use of layout tables, CSS-based layouts are recommended in order to retain the defined semantic meaning of the HTML table elements and to conform to the coding practice of separating presentation from content. If a layout table is used, however, it is important that the content make sense when linearized.

    diff --git a/techniques/failures/F59.html b/techniques/failures/F59.html index a21272cf21..9115c73e52 100644 --- a/techniques/failures/F59.html +++ b/techniques/failures/F59.html @@ -1,5 +1,5 @@ Failure of Success Criterion 4.1.2 due to using script to make div or span a user interface control in HTML without providing a role for the control

    Failure of Success Criterion 4.1.2 due to using script to make div or span a user interface control in HTML without providing a role for the control

    ID: F59

    Technology: failures

    Type: Failure

    When to Use

    -

    HTML and XHTML

    +

    HTML

    Description

    This failure demonstrates how using generic HTML elements to create user interface controls can make the controls inaccessible to assistive diff --git a/techniques/failures/F63.html b/techniques/failures/F63.html index ae0d983204..360bd622a7 100644 --- a/techniques/failures/F63.html +++ b/techniques/failures/F63.html @@ -1,5 +1,5 @@ Failure of Success Criterion 2.4.4 due to providing link context only in content that is not related to the link

    Failure of Success Criterion 2.4.4 due to providing link context only in content that is not related to the link

    ID: F63

    Technology: failures

    Type: Failure

    When to Use

    -

    HTML and XHTML

    +

    HTML

    Description

    This describes a failure condition when the context needed for understanding the purpose of a link is located in content that is not programmatically determined link context. If the context for the link is not provided in one of the following ways:

      diff --git a/techniques/failures/F65.html b/techniques/failures/F65.html index fafd580011..2e9516f9ac 100644 --- a/techniques/failures/F65.html +++ b/techniques/failures/F65.html @@ -1,5 +1,5 @@ Failure of Success Criterion 1.1.1 due to omitting the alt attribute or text alternative on img elements, area elements, and input elements of type "image"

      Failure of Success Criterion 1.1.1 due to omitting the alt attribute or text alternative on img elements, area elements, and input elements of type "image"

      ID: F65

      Technology: failures

      Type: Failure

      When to Use

      -

      HTML and XHTML

      +

      HTML

      Description

      This describes a failure condition for text alternatives on images. If there is no source of text to provide an alternative for the image then assistive technologies are not able to identify the image or to convey its purpose to the user. The alt attribute continues to be the preferred way to provide alternative text for images. Appropriate WAI-ARIA attributes may be used to provide alternative text, as long as they are accessibility supported. For more information about accessibility support, see Documenting Accessibility Support. The Accessible Name and Description Computation described the method of deriving text alternative from the HTML and WAI-ARIA attributes of an element.

      diff --git a/techniques/failures/F84.html b/techniques/failures/F84.html index ee30a67652..4b4a4eb0c5 100644 --- a/techniques/failures/F84.html +++ b/techniques/failures/F84.html @@ -1,5 +1,5 @@ Failure of Success Criterion 2.4.9 due to using a non-specific link such as "click here" or "more" without a mechanism to change the link text to specific text.

      Failure of Success Criterion 2.4.9 due to using a non-specific link such as "click here" or "more" without a mechanism to change the link text to specific text.

      ID: F84

      Technology: failures

      Type: Failure

      When to Use

      -

      HTML and XHTML

      +

      HTML

      Description

      This failure describes a common condition where links such as "click here" or "more" are used as anchor elements where you need to have the surrounding text to understand their purpose and where there isn't any mechanism to make the destination clear by itself, such as a button to expand the link text.

      Many blind people who use screen readers call up a dialog box that has a list of links from the page. They use this list of links to decide where they will go. But if many of the links in that list simply say "click here" or "more" they will be unable to use this feature in their screen reader, which is a core navigation strategy. That's why it's a failure of 2.4.9 to not provide any way of allowing them to know the destination from the link text alone. It is also true for people who tab through links. If all they hear as they tab through the document is "click here, click here, click here etc." they will become confused.

      diff --git a/techniques/failures/F90.html b/techniques/failures/F90.html index 84ff174b75..4de5a6db89 100644 --- a/techniques/failures/F90.html +++ b/techniques/failures/F90.html @@ -1,5 +1,5 @@ Failure of Success Criterion 1.3.1 for incorrectly associating table headers and content via the headers and id attributes

      Failure of Success Criterion 1.3.1 for incorrectly associating table headers and content via the headers and id attributes

      ID: F90

      Technology: failures

      Type: Failure

      When to Use

      -

      HTML and XHTML.

      +

      HTML

      Description

      One way for authors to explicitly associate header cells to data cells is by using the id and headers attributes. These allow the author to associate multiple header cells to a particular data cell, which can be necessary when complex data tables with more than one level of heading are used.

      The failure occurs when the relationship between data cells and corresponding header cells cannot be programmatically determined correctly because the association of id and headers attributes is faulty. This can happen, for example, when copying code within tables and forgetting to update the code.

      diff --git a/techniques/failures/F91.html b/techniques/failures/F91.html index 8ba51aa782..f7b8cf70e3 100644 --- a/techniques/failures/F91.html +++ b/techniques/failures/F91.html @@ -1,5 +1,5 @@ Failure of Success Criterion 1.3.1 for not correctly marking up table headers

      Failure of Success Criterion 1.3.1 for not correctly marking up table headers

      ID: F91

      Technology: failures

      Type: Failure

      When to Use

      -

      HTML and XHTML.

      +

      HTML

      Description

      This failure occurs when data tables do not use header elements (th) or other appropriate table mark-up (the scope attribute, headers and id or the ARIA columnheader and rowheader) roles to make the headers programmatically determinable from within table content. Making headers programmatically determinable is especially important when data cells are only intelligible together with header information. When screen reader users navigate through the table content horizontally or vertically, the headers that change can be read out to provide the necessary context for the information in the data cells.

      Examples

      diff --git a/techniques/failures/F92.html b/techniques/failures/F92.html index dfae33407e..926e9e12d1 100644 --- a/techniques/failures/F92.html +++ b/techniques/failures/F92.html @@ -1,5 +1,5 @@ Failure of Success Criterion 1.3.1 due to the use of role presentation on content which conveys semantic information

      Failure of Success Criterion 1.3.1 due to the use of role presentation on content which conveys semantic information

      ID: F92

      Technology: failures

      Type: Failure

      When to Use

      -

      HTML and XHTML

      +

      HTML

      Description

      This failure occurs when a role of presentation is applied to an element whose purpose is to convey information or relationships in the content. Elements such as table, can convey information about the content contained in them via their semantic markup. The WAI-ARIA role of presentation From 3725e547dda7edc5ed10f4ea512884fd5dc09196 Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Mon, 6 Nov 2023 10:05:04 -0800 Subject: [PATCH 16/80] Replace absolute URL with relative --- techniques/failures/F65.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/techniques/failures/F65.html b/techniques/failures/F65.html index 2e9516f9ac..985e3d3363 100644 --- a/techniques/failures/F65.html +++ b/techniques/failures/F65.html @@ -1,9 +1,9 @@ Failure of Success Criterion 1.1.1 due to omitting the alt attribute or text alternative on img elements, area elements, and input elements of type "image"

      Failure of Success Criterion 1.1.1 due to omitting the alt attribute or text alternative on img elements, area elements, and input elements of type "image"

      ID: F65

      Technology: failures

      Type: Failure

      When to Use

      HTML

      Description

      -

      This describes a failure condition for text alternatives on images. If there is no source of text to provide an alternative for the image then assistive technologies are not able to identify the image or to convey its purpose to the user. The alt attribute continues to be the preferred way to provide alternative text for images. Appropriate WAI-ARIA attributes may be used to provide alternative text, as long as they are accessibility supported. For more information about accessibility support, see Documenting Accessibility Support. The Accessible Name and Description Computation described the method of deriving text alternative from the HTML and WAI-ARIA attributes of an element.

      +

      This describes a failure condition for text alternatives on images. If there is no source of text to provide an alternative for the image then assistive technologies are not able to identify the image or to convey its purpose to the user. The alt attribute continues to be the preferred way to provide alternative text for images. Appropriate WAI-ARIA attributes may be used to provide alternative text, as long as they are accessibility supported. For more information about accessibility support, see Documenting Accessibility Support. The Accessible Name and Description Computation described the method of deriving text alternative from the HTML and WAI-ARIA attributes of an element.

      -Some Assistive Technologies attempt to compensate for the missing text alternatives by reading the file name of the image. But it is insufficient to rely simply on the file name for many reasons. For example, file names may not be descriptive (e.g., images/nav01.gif), and technology specifications do not require descriptive file names. And some Assistive Technologies do not read the file name if there is no text alternative provided via HTML attributes. +Some Assistive Technologies attempt to compensate for the missing text alternatives by reading the file name of the image. But it is insufficient to rely simply on the file name for many reasons. For example, file names may not be descriptive (e.g., images/nav01.gif), and technology specifications do not require descriptive file names. And some Assistive Technologies do not read the file name if there is no text alternative provided via HTML attributes.

      Examples

      From 6754a31c3eafedd3d8bf7e3ddbdbda17ecf11a4e Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Mon, 6 Nov 2023 10:05:31 -0800 Subject: [PATCH 17/80] Replace absolute URLs with relative --- techniques/failures/F75.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/techniques/failures/F75.html b/techniques/failures/F75.html index f6cb1ba3b4..7c9fc18bd6 100644 --- a/techniques/failures/F75.html +++ b/techniques/failures/F75.html @@ -1,7 +1,7 @@ Failure of Success Criterion 1.2.2 by providing synchronized media without captions when the synchronized media presents more information than is presented on the page

      Failure of Success Criterion 1.2.2 by providing synchronized media without captions when the synchronized media presents more information than is presented on the page

      ID: F75

      Technology: failures

      Type: Failure

      When to Use

      Any technology.

      Description

      -

      The objective of this failure is to avoid situations in which synchronized media alternatives provide more information than the text for which they are alternatives, but do not provide their own text alternatives to provide access to the extra information. Synchronized media alternatives provide enhanced access to users for whom synchronized media is a more effective format than text. Since they are alternatives to text, they do not need themselves to have redundant text alternatives in the form of captions, audio descriptions or full text alternatives. However, if they provide more information than the text for which they are an alternative, then they are not just alternatives but are synchronized media content in their own right. In this case they are subject to the full requirements of Success Criterion 1.2.2 to provide captions and to Success Criterion 1.2.3 and 1.2.5.

      +

      The objective of this failure is to avoid situations in which synchronized media alternatives provide more information than the text for which they are alternatives, but do not provide their own text alternatives to provide access to the extra information. Synchronized media alternatives provide enhanced access to users for whom synchronized media is a more effective format than text. Since they are alternatives to text, they do not need themselves to have redundant text alternatives in the form of captions, audio descriptions or full text alternatives. However, if they provide more information than the text for which they are an alternative, then they are not just alternatives but are synchronized media content in their own right. In this case they are subject to the full requirements of Success Criterion 1.2.2 to provide captions and to Success Criterion 1.2.3 and 1.2.5.

      Examples

      Tests

      Procedure

        From 2196c2b356d874c3eef7fe3b8b180a4f9785d2ec Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Mon, 6 Nov 2023 10:05:49 -0800 Subject: [PATCH 18/80] Replace absolute URL with relative --- techniques/failures/F89.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/techniques/failures/F89.html b/techniques/failures/F89.html index fd4befce63..0af360ca0b 100644 --- a/techniques/failures/F89.html +++ b/techniques/failures/F89.html @@ -2,7 +2,7 @@

        Content that contains links.

      Description

      This failure condition occurs when a link contains only non-text content, such as an image, and that link cannot be identified by an accessible name. The accessible name for a link is defined according to the Accessible Name and Description Computation.

      -

      This also applies when both text and images are used separately on a page to link to the same target. In this case success technique H2: Combining adjacent image and text links for the same resource is the recommended approach to reduce the number of separate links and the undesirable redundancy.

      +

      This also applies when both text and images are used separately on a page to link to the same target. In this case success technique H2: Combining adjacent image and text links for the same resource is the recommended approach to reduce the number of separate links and the undesirable redundancy.

      Examples

      Search Results

      From 8f950c9842ed20e6e51c7762a906bdf8f55d6920 Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Mon, 6 Nov 2023 10:06:15 -0800 Subject: [PATCH 19/80] Fix 404, replace absolute URL with relative --- techniques/failures/F94.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/techniques/failures/F94.html b/techniques/failures/F94.html index b01f72e13e..d6e4c284e5 100644 --- a/techniques/failures/F94.html +++ b/techniques/failures/F94.html @@ -19,9 +19,9 @@

      Metadata

      Description

      The objective of this technique is to document the failure of text to re-scale when viewport units are used on text. As these units are relative to the viewport, it means they cannot be resized by zooming or adjusting text-size.

      There are various methods to increase and decrease the size of text and other content, but viewport units applied to text (generally via font-size in CSS) prevent most available methods. Attempts to use browser controls to zoom or adjust text-size will not work. Only methods that completely override the CSS will work, and those could cause other issues such as layouts collapsing or text overlapping.

      -

      Some uses of viewport units may not prevent text-size adjustments, but if they are used as the primary method for defining text-size, they are likely to cause a failure of Success Criterion 1.4.4.

      +

      Some uses of viewport units may not prevent text-size adjustments, but if they are used as the primary method for defining text-size, they are likely to cause a failure of Success Criterion 1.4.4.

      -

      If media queries were used to adjust the size of text or unit of measure at different screen sizes, it may not be a failure of Resize Text. On-page controls provided by the author are also a way of passing the resize text success criteria.

      +

      If media queries were used to adjust the size of text or unit of measure at different screen sizes, it may not be a failure of Resize Text. On-page controls provided by the author are also a way of passing the resize text success criteria.

      Examples

      From 5dd2c90e9fcdf0f0f3026b2833c9c0a2517230f5 Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Mon, 6 Nov 2023 10:06:34 -0800 Subject: [PATCH 20/80] Replace absolute URL with relative --- techniques/failures/F61.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/techniques/failures/F61.html b/techniques/failures/F61.html index 27216a6d3e..58b66d94e1 100644 --- a/techniques/failures/F61.html +++ b/techniques/failures/F61.html @@ -3,7 +3,7 @@ automatic update that the user cannot disable from within the content

      ID: F61

      Technology: failures

      Type: Failure

      When to Use

      General

      Description

      -

      This document describes a failure that occurs when the content in the main viewport viewport is automatically updated, and there is no option for a user to disable this behavior.

      +

      This document describes a failure that occurs when the content in the main viewport viewport is automatically updated, and there is no option for a user to disable this behavior.

      Two procedures are presented below to test for the existence of a failure against Success Criterion 3.2.5. Procedure 1 is the preferred procedure and assumes that content authors have access to the code that generates the viewport content.

      However there may be instances where this may not be possible (eg: in certain content management systems, application environments such as django or ruby-on-rails, or content generated through scripting languages such as AJAX or PHP that are generated by third parties.) To that end, the second procedure is supplied to allow testing in these instances. Note that timeframes are indicative only, and that any change after any amount of time should be treated as a failure if the test otherwise does not pass the other step evaluations.

      Examples

      From ea6e8846cfc88980d5b6dcc252d6994d64153b42 Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Mon, 6 Nov 2023 10:06:44 -0800 Subject: [PATCH 21/80] Replace absolute URL with relative --- techniques/failures/F58.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/techniques/failures/F58.html b/techniques/failures/F58.html index 11d29d9695..882510789d 100644 --- a/techniques/failures/F58.html +++ b/techniques/failures/F58.html @@ -41,7 +41,7 @@

      Procedure

      1. Check to see if the web page automatically redirects to another page after some period of time without the user taking any action.
        2. -
      2. Check if the page qualifies for Real-time or Essential Exceptions in Success Criterion 2.2.1 Timing Adjustable.
        3. +
      3. Check if the page qualifies for Real-time or Essential Exceptions in Success Criterion 2.2.1 Timing Adjustable.
      4. Check if the user is provided an opportunity to turn off, extend, or adjust the timing of the page refresh.
      From b3db6c4f667c235265498e66056975d7bd871e25 Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Mon, 6 Nov 2023 10:07:21 -0800 Subject: [PATCH 22/80] Replace absolute URL with relative --- techniques/failures/F50.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/techniques/failures/F50.html b/techniques/failures/F50.html index c1af5c094a..c75c1ef80f 100644 --- a/techniques/failures/F50.html +++ b/techniques/failures/F50.html @@ -3,7 +3,7 @@ mechanism to stop the blinking at 5 seconds or less

      ID: F50

      Technology: failures

      Type: Failure

      When to Use

      Technologies that support script-controlled blinking of content.

      Description

      -

      Scripts can be used to blink content by toggling the content's visibility on and off at regular intervals. It is a failure for the script not to include a mechanism to stop the blinking at 5 seconds or earlier. See Using scripts to control blinking and stop it in five seconds or less for information about how to modify the technique to stop the blinking.

      +

      Scripts can be used to blink content by toggling the content's visibility on and off at regular intervals. It is a failure for the script not to include a mechanism to stop the blinking at 5 seconds or earlier. See Using scripts to control blinking and stop it in five seconds or less for information about how to modify the technique to stop the blinking.

      Examples

      From 08de5bcdfd0d0398c68e717aa0e7ff6b05da9547 Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Mon, 6 Nov 2023 10:07:26 -0800 Subject: [PATCH 23/80] Replace absolute URL with relative --- techniques/failures/F41.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/techniques/failures/F41.html b/techniques/failures/F41.html index 8450d4b88c..0dba0909cf 100644 --- a/techniques/failures/F41.html +++ b/techniques/failures/F41.html @@ -38,7 +38,7 @@
      1. Check that the numerical value for seconds until refresh in the content attribute is present.
      2. Check that the numerical value for seconds until refresh in the content attribute is less than one or greater than 72,000.
        3. -
      3. Check if the page qualifies for Real-time or Essential Exceptions in Success Criterion 2.2.1 Timing Adjustable.
        4. +
      4. Check if the page qualifies for Real-time or Essential Exceptions in Success Criterion 2.2.1 Timing Adjustable.
      5. Check if the user is provided an opportunity to turn off, extend, or adjust the timing of the page refresh.
      6. Check if the page does not refresh after the duration specified in the content attribute.
      From fbf4eff0cf4a17fdec10fbb7a6d11fb8f59a918f Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Mon, 6 Nov 2023 10:07:44 -0800 Subject: [PATCH 24/80] Replace absolute URL with relative --- techniques/failures/F40.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/techniques/failures/F40.html b/techniques/failures/F40.html index 54a61fca0b..eaf6949fd3 100644 --- a/techniques/failures/F40.html +++ b/techniques/failures/F40.html @@ -9,7 +9,7 @@

      It is acceptable to use the meta element to create a redirect when the time-out is set to zero, since the redirect is instant and will not be perceived as a change of context. However, it is preferable to use - server-side methods to accomplish this. See Implementing automatic redirects on the server side + server-side methods to accomplish this. See Implementing automatic redirects on the server side instead of on the client side.

      Examples

      @@ -37,7 +37,7 @@
      1. Check that the numerical value for seconds until refresh in the content attribute is present.
      2. Check that the numerical value for seconds until refresh in the content attribute is less than one or greater than 72,000.
        3. -
      3. Check if the page qualifies for Real-time or Essential Exceptions in Success Criterion 2.2.1 Timing Adjustable.
        4. +
      4. Check if the page qualifies for Real-time or Essential Exceptions in Success Criterion 2.2.1 Timing Adjustable.
      5. Check if the user is provided an opportunity to turn off, extend, or adjust the timing of the page refresh.
      6. Check if the page does not redirect after the duration specified in the content attribute.
      From 680dcdc24cb1f97716768d9d06720c361996fc8c Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Mon, 6 Nov 2023 10:07:52 -0800 Subject: [PATCH 25/80] Replace absolute URL with relative --- techniques/failures/F37.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/techniques/failures/F37.html b/techniques/failures/F37.html index 0cdeeab5ee..31f2e14da6 100644 --- a/techniques/failures/F37.html +++ b/techniques/failures/F37.html @@ -8,7 +8,7 @@ open. It is possible to use scripting to create an input element that causes a change of context (submit the form, open a new page, a new window) when the element is selected. Developers can instead use a - submit button (see Providing a submit + submit button (see Providing a submit button to initiate a change of context) or clearly indicate the expected action.

      Examples

      From a11432a1235e9b34258ce7a3ac71d74629f56135 Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Mon, 6 Nov 2023 10:07:58 -0800 Subject: [PATCH 26/80] Replace absolute URL with relative --- techniques/failures/F107.html | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/techniques/failures/F107.html b/techniques/failures/F107.html index 8ae2478905..bd6fa1c631 100644 --- a/techniques/failures/F107.html +++ b/techniques/failures/F107.html @@ -19,7 +19,7 @@

      Applicability

      Description

      The purpose of this technique is to identify a failure condition where form inputs do not have the correct autocomplete attribute values for inputs that request information about the user of the form.

      -

      Success Criterion 1.3.5 uses a fixed list of tokens in Input Purposes for user interface components (based on the HTML 5.2 autocomplete attribute's fixed list of token values) because the programmatic association of specified token values (metadata) allows for other machine processing, such as expressing the input label in different modalities.

      +

      Success Criterion 1.3.5 uses a fixed list of tokens in Input Purposes for user interface components (based on the HTML 5.2 autocomplete attribute's fixed list of token values) because the programmatic association of specified token values (metadata) allows for other machine processing, such as expressing the input label in different modalities.

      Another important part of this Success Criterion is that the token values are associated with inputs that are scoped directly to the primary end user.

      @@ -67,10 +67,10 @@

      Related Techniques

      Resources

      From 9d70bc272c1467b2ce5d3e9004ce8218965661e1 Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Mon, 6 Nov 2023 10:08:06 -0800 Subject: [PATCH 27/80] Replace absolute URL with relative --- techniques/failures/F103.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/techniques/failures/F103.html b/techniques/failures/F103.html index 5f619d69e9..c519d2aa52 100644 --- a/techniques/failures/F103.html +++ b/techniques/failures/F103.html @@ -29,7 +29,7 @@

      Description

    • the new content does not take focus (does not change context);
    • the new content provides information to the user on the outcome of an action, the state of an application, the progress of a process, or the existence of errors.
      • - Where updated content does not conform to the definition of status message, a failure of 4.1.3 has not taken place.

      + Where updated content does not conform to the definition of status message, a failure of 4.1.3 has not taken place.

      The second step in this failure technique involves examining code. Where dynamic content meets the definition of a status message, its container can be examined for an appropriate WAI-ARIA role or property which allows it to be programmatically determinable as a status message. Currently there are only a small number of techniques available to indicate status messages to assistive technologies. They are:

      • the HTML output element
        • From c75cf99736ecb2363e54127bfd7080b4653569cd Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Mon, 6 Nov 2023 10:13:00 -0800 Subject: [PATCH 28/80] Replace absolute URL with relative --- techniques/failures/F105.html | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/techniques/failures/F105.html b/techniques/failures/F105.html index c7279574fc..3dc0d05b21 100644 --- a/techniques/failures/F105.html +++ b/techniques/failures/F105.html @@ -20,7 +20,7 @@

        Applicability

        Description

        The objective of this Failure is to describe situations where authors have implemented a function that is operated via a path-based gesture, and no alternative ways of operating this function via simple pointer gestures exist.

        -

        If you did not create the content and functionality you can find path-based gestures by exploring the content on a touch screen, or checking the page code for the existence of specific event handlers such as touchstart or touchend. See the Understanding document for Pointer Gestures for more on the path-based gestures.

        +

        If you did not create the content and functionality you can find path-based gestures by exploring the content on a touch screen, or checking the page code for the existence of specific event handlers such as touchstart or touchend. See the Understanding document for Pointer Gestures for more on the path-based gestures.

        Note: For functionality implemented with a path-based gesture, the possibility of also operating it via the keyboard is beneficial (and may serve to meet Success Criterion 2.1.1 Keyboard). The point of Success Crtierion 2.5.1, however, is to ensure that pointer users who on many devices will have no keyboard available, have alternative ways of operating the function via simple pointer input.

        @@ -51,8 +51,8 @@

        Expected Results

        From 033897ea704e7a609e8ea16615b296bbc292b6d5 Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Mon, 6 Nov 2023 10:13:08 -0800 Subject: [PATCH 29/80] Replace absolute URL with relative --- techniques/failures/F107.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/techniques/failures/F107.html b/techniques/failures/F107.html index bd6fa1c631..98ce191827 100644 --- a/techniques/failures/F107.html +++ b/techniques/failures/F107.html @@ -60,7 +60,7 @@

        Expected Results

        From be82bdbde5d0632552969b25526bc8319efbe49e Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Mon, 6 Nov 2023 10:13:16 -0800 Subject: [PATCH 30/80] Replace absolute URL with relative --- techniques/failures/F90.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/techniques/failures/F90.html b/techniques/failures/F90.html index 4de5a6db89..799c62ffc4 100644 --- a/techniques/failures/F90.html +++ b/techniques/failures/F90.html @@ -4,7 +4,7 @@

        One way for authors to explicitly associate header cells to data cells is by using the id and headers attributes. These allow the author to associate multiple header cells to a particular data cell, which can be necessary when complex data tables with more than one level of heading are used.

        The failure occurs when the relationship between data cells and corresponding header cells cannot be programmatically determined correctly because the association of id and headers attributes is faulty. This can happen, for example, when copying code within tables and forgetting to update the code.

        Examples

        -

        Note: The example below is based on the complex data table presented as example 1 of Technique H43: Using id and headers attributes to associate data cells with header cells in data tables. +

        Note: The example below is based on the complex data table presented as example 1 of Technique H43: Using id and headers attributes to associate data cells with header cells in data tables.

        Table content not correctly associated to nested headers

        From fd3795e3fb17fa49ecac1a564492ce11776e2e2a Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Mon, 6 Nov 2023 10:19:23 -0800 Subject: [PATCH 31/80] Remove link to rawgit stylesheet --- techniques/aria/ARIA24.html | 1 - 1 file changed, 1 deletion(-) diff --git a/techniques/aria/ARIA24.html b/techniques/aria/ARIA24.html index aba60e88c6..92253619ec 100644 --- a/techniques/aria/ARIA24.html +++ b/techniques/aria/ARIA24.html @@ -2,7 +2,6 @@ Semantically identifying a font icon with role="img" - From f169090a214f50f789b42d1008aaff029fad64f1 Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Mon, 6 Nov 2023 10:21:13 -0800 Subject: [PATCH 32/80] Replace absolute URL with relative --- techniques/general/G1.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/techniques/general/G1.html b/techniques/general/G1.html index 94824fcd3b..ff61c30477 100644 --- a/techniques/general/G1.html +++ b/techniques/general/G1.html @@ -3,7 +3,7 @@

        Description

        The objective of this technique is to provide a mechanism to bypass blocks of material that are repeated on multiple Web pages by skipping directly to the main content of the Web page. The first interactive item in the Web page is a link to the beginning of the main content. Activating the link sets focus beyond the other content to the main content. This technique is most useful when a Web page has one main content area, rather than a set of content areas that are equally important, and when there are not multiple navigation sections on the page.

        -

        It is preferable for links to be visible at all times, since users navigating via the keyboard include switch users, those using techniques that generate keyboard strokes slowly, screen magnification software users, screen reader users working with sighted colleagues, keyboard only users and those navigating using voice recognition software. However, Success Criterion 2.4.1 does not require that they be visible when they do not have focus, and links that are visible only when they have focus can meet this success criterion.

        +

        It is preferable for links to be visible at all times, since users navigating via the keyboard include switch users, those using techniques that generate keyboard strokes slowly, screen magnification software users, screen reader users working with sighted colleagues, keyboard only users and those navigating using voice recognition software. However, Success Criterion 2.4.1 does not require that they be visible when they do not have focus, and links that are visible only when they have focus can meet this success criterion.

        Examples

        From fcd9c5349ef504b932b0f3f9d02f983af44cc09e Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Mon, 6 Nov 2023 10:21:52 -0800 Subject: [PATCH 33/80] Replace absolute URL with relative --- techniques/general/G62.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/techniques/general/G62.html b/techniques/general/G62.html index 0f4c453ff7..8fbe692b0a 100644 --- a/techniques/general/G62.html +++ b/techniques/general/G62.html @@ -3,7 +3,7 @@

        Description

        The objective of this technique is to make the definition of a word, phrase, or abbreviation available by providing the definition in a glossary. A glossary is an alphabetical list of words, phrases, and abbreviations with their definitions. Glossaries are most appropriate when the words, phrases, and abbreviations used within the content relate to a specific discipline or technology area. A glossary can also provide the pronunciation of a word or phrase.

        The glossary is included at the end of the Web page or the glossary is located via one of the mechanisms for locating content within a set of Web pages. (See - Understanding Success Criterion 2.4.5.)

        + Understanding Success Criterion 2.4.5.)

        If the glossary contains several definitions for the same word, phrase, or abbreviation, simply providing the glossary is not sufficient to satisfy this Success Criterion. A different technique should be used to find the correct definition. This is especially important if the uses of the word, phrase, or abbreviation are not unique within the Web page, that is, if different occurrences of the item have different definitions.

        Examples

        From a3dc527e40b1080fb437d1996c2cd15843fdc9ef Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Mon, 6 Nov 2023 10:37:43 -0800 Subject: [PATCH 34/80] Remove link to rabbit CSS file --- techniques/general/G214.html | 1 - 1 file changed, 1 deletion(-) diff --git a/techniques/general/G214.html b/techniques/general/G214.html index fb3b34914c..bb57c83235 100644 --- a/techniques/general/G214.html +++ b/techniques/general/G214.html @@ -2,7 +2,6 @@ Using a control to allow access to content in different orientations which is otherwise restricted -

        Using a control to allow access to content in different orientations which is otherwise restricted

        From 1fb520e2dd328a5954d69faa9043e5e604cdfc8b Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Mon, 6 Nov 2023 10:46:35 -0800 Subject: [PATCH 35/80] Replace absolute URL with relative --- techniques/general/G103.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/techniques/general/G103.html b/techniques/general/G103.html index 12635cdcdf..b15e8d15f9 100644 --- a/techniques/general/G103.html +++ b/techniques/general/G103.html @@ -15,7 +15,7 @@

        An annual report for a company

        An annual report discusses multiple factors that influenced the company's performance in the past year. The report also includes charts and graphs that illustrate how these factors interact. Each chart or graph has a text alternative as required by - Success Criterion 1.1.1. Each one also has a number in its caption (e.g., “Figure 7"). These numbers are used in the text to reference the charts or graphs.

        + Success Criterion 1.1.1. Each one also has a number in its caption (e.g., “Figure 7"). These numbers are used in the text to reference the charts or graphs.

        Screen shots in technical documentation

        From 6225be3cec8d11d698cb678b6258bbbaaf21dbe7 Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Mon, 6 Nov 2023 10:47:04 -0800 Subject: [PATCH 36/80] Replace absolute URL(s) with relative --- techniques/general/G110.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/techniques/general/G110.html b/techniques/general/G110.html index f5783ee103..150a3d31be 100644 --- a/techniques/general/G110.html +++ b/techniques/general/G110.html @@ -3,7 +3,7 @@

        Description

        The objective of this technique is to enable redirects on the client side without confusing the user. Redirects are preferably implemented on the - server side (see Implementing automatic redirects on the server side instead of on the client side), because a server-side + server side (see Implementing automatic redirects on the server side instead of on the client side), because a server-side redirect does not cause new content to be displayed before the server sends the content located at the new URI. However, authors do not always have control over server-side technologies; in that case, they can use a @@ -25,7 +25,7 @@

        HTML: meta element: see - Using + Using meta refresh to create an instant client-side redirect.

        From d76d4169450dba996d57c42e7b4fc5b9f94602c7 Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Mon, 6 Nov 2023 10:47:13 -0800 Subject: [PATCH 37/80] Replace absolute URL(s) with relative --- techniques/general/G130.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/techniques/general/G130.html b/techniques/general/G130.html index 952b591c76..bdaf310b69 100644 --- a/techniques/general/G130.html +++ b/techniques/general/G130.html @@ -15,7 +15,7 @@

        When to Use

        Description

        -

        The objective of this technique is to make section headings within Web content descriptive. Descriptive headings and titles (see Providing descriptive titles for Web pages) work together to give users an overview of the content and its organization. Descriptive headings identify sections of the content in relation both to the Web page as a whole and to other sections of the same Web page.

        +

        The objective of this technique is to make section headings within Web content descriptive. Descriptive headings and titles (see Providing descriptive titles for Web pages) work together to give users an overview of the content and its organization. Descriptive headings identify sections of the content in relation both to the Web page as a whole and to other sections of the same Web page.

        Descriptive headings help users find specific content and orient themselves within the Web page.

        Authors may also want to consider putting the most important information at the beginning of each heading. This helps users "skim" the headings to locate the specific content they need, and is especially helpful when browsers or assistive technology allow navigation from heading to heading.

        From ddb85448a84b8f5f0755b31aaed9ab8072d58c36 Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Mon, 6 Nov 2023 10:47:29 -0800 Subject: [PATCH 38/80] Replace absolute URL(s) with relative --- techniques/general/G156.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/techniques/general/G156.html b/techniques/general/G156.html index a16291e5e7..f115c79edc 100644 --- a/techniques/general/G156.html +++ b/techniques/general/G156.html @@ -3,7 +3,7 @@

        Description

        Some people with cognitive disabilities require specific color combinations of foreground text and background to help them successfully understand the contents of the Web page. Most popular browsers provide the option to change colors settings globally within the browser. In this case the colors selected by the user override the foreground and background colors specified by the Web author.

        In order to meet this success criterion, the Web author would design the page so that it works with browsers that have these controls, and the author does not override these controls.

        -

        Note that overriding the foreground and background colors of all text on a page may hide visual clues to the grouping and organization of the Web page, making it much more difficult to understand and use. This technique may not be appropriate when background colors are used to delineate areas of the page. This technique may be appropriate for technologies and user agents that do not alter border colors when background colors are overridden. If background colors are used to delineate areas of the page, "Specifying text and background colors of secondary content such as banners, features and navigation in CSS while not specifying text and background colors of the main content" may be used to permit the user to control the colors of the main text while retaining the visual structure of the Web page.

        +

        Note that overriding the foreground and background colors of all text on a page may hide visual clues to the grouping and organization of the Web page, making it much more difficult to understand and use. This technique may not be appropriate when background colors are used to delineate areas of the page. This technique may be appropriate for technologies and user agents that do not alter border colors when background colors are overridden. If background colors are used to delineate areas of the page, "Specifying text and background colors of secondary content such as banners, features and navigation in CSS while not specifying text and background colors of the main content" may be used to permit the user to control the colors of the main text while retaining the visual structure of the Web page.

        Examples

        • A Web page is designed using HTML and CSS to specify the foreground and background colors. The user sets their own colors in Internet Explorer 7 and they can view the content with their chosen foreground and background colors.
          • From e3bc5b2018a0ac20ac58ea384138fce661a881c4 Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Mon, 6 Nov 2023 10:47:36 -0800 Subject: [PATCH 39/80] Replace absolute URL(s) with relative --- techniques/general/G160.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/techniques/general/G160.html b/techniques/general/G160.html index 9e91cbd8fe..1fa73e27a5 100644 --- a/techniques/general/G160.html +++ b/techniques/general/G160.html @@ -55,6 +55,6 @@

        See also - Related Resources for Success Criterion 1.2.6 - Sign Language.

        + Related Resources for Success Criterion 1.2.6 - Sign Language.

        \ No newline at end of file From 87a915a2e2abb1f1ad3c9d417ae8c7c57bb212a6 Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Mon, 6 Nov 2023 10:47:53 -0800 Subject: [PATCH 40/80] Replace absolute URL(s) with relative --- techniques/general/G167.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/techniques/general/G167.html b/techniques/general/G167.html index 571658ab94..b87b0f8a5b 100644 --- a/techniques/general/G167.html +++ b/techniques/general/G167.html @@ -4,7 +4,7 @@

        When a button invokes a function on an input field, has a clear text label, and is rendered adjacent to the input field, the button also acts as a label for the input field. This label helps users understand the purpose of the field without introducing repetitive text on the Web page. Buttons that label single text fields typically follow the input field.

        The field must also have a programmatically determined name, per - Success Criterion 4.1.2.

        + Success Criterion 4.1.2.

        Examples

        From 75e805a9c787f34183a7fe0629c037ac8951705b Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Mon, 6 Nov 2023 10:48:00 -0800 Subject: [PATCH 41/80] Replace absolute URL(s) with relative --- techniques/general/G172.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/techniques/general/G172.html b/techniques/general/G172.html index bfc2f214fe..cdf6f9eb2e 100644 --- a/techniques/general/G172.html +++ b/techniques/general/G172.html @@ -7,9 +7,9 @@

        This technique can be used in combination with a style switching technique to present a page that is a conforming alternate version for non-conforming content. Refer to - C29: Using a style switcher to provide a conforming alternate version + C29: Using a style switcher to provide a conforming alternate version and - Understanding Conforming Alternate Versions + Understanding Conforming Alternate Versions for more information.

        Examples

        From 2dc42439e5be6128b28bfade45624f362b625508 Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Mon, 6 Nov 2023 11:02:37 -0800 Subject: [PATCH 42/80] Fix broken links, replace absolute link with relative --- techniques/server-side-script/SVR3.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/techniques/server-side-script/SVR3.html b/techniques/server-side-script/SVR3.html index 5b596e0011..3f20f31335 100644 --- a/techniques/server-side-script/SVR3.html +++ b/techniques/server-side-script/SVR3.html @@ -17,7 +17,7 @@

        When to Use

        Description

        The objective of this technique is to ensure that users can obtain an accessible version of content where both non-conforming and conforming versions are provided.

        -

        Conformance Requirement 1 allows non-conforming pages to be included within the scope of conformance as long as they have a "conforming alternate version". It is not always possible for authors to include accessibility supported links to conforming content from within non-conforming content. Therefore, authors may need to rely on the use of Server Side Scripting technologies (ex. PHP, ASP, JSP) to ensure that the non-conforming version can only be reached from a conforming page.

        +

        Conformance Requirement 1 allows non-conforming pages to be included within the scope of conformance as long as they have a "conforming alternate version". It is not always possible for authors to include accessibility supported links to conforming content from within non-conforming content. Therefore, authors may need to rely on the use of Server Side Scripting technologies (ex. PHP, ASP, JSP) to ensure that the non-conforming version can only be reached from a conforming page.

        This technique describes how to use information provided by the HTTP referer to ensure that non-conforming content can only be reached from a conforming page. The HTTP referer header is set by the user agent and contains the URI of the page (if any) which referred the user agent to the non-conforming page.

        To implement this technique, an author identifies the URI for the conforming version of the content, for each non-conforming page. When a request for the non-conforming version of a page is received, the server compares the value of the HTTP referer header against the URI of the conforming version to determine whether the link to the non-conforming version came from the conforming version. The non-conforming version is only served if the HTTP referer matches the URI of the non-conforming version. Otherwise, the user is redirected to the conforming version of the content. Note that when comparing the URI in the HTTP referer header, non-relevant variations in the URI, such as in the query and target, should be taken into account.

        From d96048fe42072b758e50bebfdbdf163c9320b7bf Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Mon, 6 Nov 2023 11:04:25 -0800 Subject: [PATCH 43/80] Replace absolute link with relative --- techniques/pdf/PDF5.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/techniques/pdf/PDF5.html b/techniques/pdf/PDF5.html index 98469df6c8..045d35e2fa 100644 --- a/techniques/pdf/PDF5.html +++ b/techniques/pdf/PDF5.html @@ -16,7 +16,7 @@

        When to Use

        Description

        The objective of this technique is to notify the user when a field that must be completed has not been completed in a PDF form. Required fields are implemented using the /Ff entry in the form field's dictionary. This is normally accomplished using a tool for authoring PDFs.

        -

        If errors are found, an alert dialog describes the nature of the error in text. This may be accomplished through scripting created by the author (see, for example, SCR18: Providing client-side validation and alert). User agents, such as Adobe Acrobat Pro and LiveCycle, can provide automatic alerts (as described in the examples below).

        +

        If errors are found, an alert dialog describes the nature of the error in text. This may be accomplished through scripting created by the author (see, for example, SCR18: Providing client-side validation and alert). User agents, such as Adobe Acrobat Pro and LiveCycle, can provide automatic alerts (as described in the examples below).

        Once the user dismisses the alert dialog, it may be helpful if the script positions the keyboard focus on the field where the error occurred, although some users may expect the focus to remain on the last control focused prior to the alert appearing. Authors should exercise care to ensure that any movement of the focus will be expected. For example, if the alert announces a missing required phone number, positioning the focus on the phone number field when the alert is dismissed can be regarded as helpful and expected. In some cases, however, this may not be possible. If multiple input errors occur on the page, another approach must be taken to error reporting. (See, for example, the Adobe SDK.)

        From cbb640f4328296aa1b716f13289b590fdd4f0576 Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Mon, 6 Nov 2023 11:05:08 -0800 Subject: [PATCH 44/80] Fix broken link --- techniques/pdf/PDF22.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/techniques/pdf/PDF22.html b/techniques/pdf/PDF22.html index 195d2d538c..177636931a 100644 --- a/techniques/pdf/PDF22.html +++ b/techniques/pdf/PDF22.html @@ -22,7 +22,7 @@

        Description

        date fields) is not submitted in that format.

        If the required format is not used, an alert dialog describes the nature of the error in text. This may be accomplished through scripting - created by the author (see, for example, SCR18: Providing client-side validation and alert). User agents can provide automatic alerts (as described in the examples below).

        + created by the author (see, for example, SCR18: Providing client-side validation and alert). User agents can provide automatic alerts (as described in the examples below).

        Once the user dismisses the alert dialog, it may be helpful if the script positions the keyboard focus on the field where the error occurred, although some users may expect the focus to remain on the last control focused prior to the alert appearing. Authors should exercise care to ensure that any movement of the focus will be expected. For example, if the alert announces an error in a phone number format, positioning the focus on the phone number field when the alert is dismissed can be regarded as helpful and expected. In some cases, however, this may not be possible. If multiple input errors occur on the page, an alternative approach to error notification should be implemented.

        From ec03f85c5c859f913da867403791a15433899526 Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Mon, 6 Nov 2023 11:06:03 -0800 Subject: [PATCH 45/80] Replace absolute URL(s) with relative --- techniques/pdf/PDF11.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/techniques/pdf/PDF11.html b/techniques/pdf/PDF11.html index 9994d27f79..063af13b9a 100644 --- a/techniques/pdf/PDF11.html +++ b/techniques/pdf/PDF11.html @@ -40,12 +40,12 @@

        Description

        general techniques:

        From 18e004b91e1a5a4d83861837bfed6df7f91cc3da Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Mon, 6 Nov 2023 11:10:57 -0800 Subject: [PATCH 46/80] Fix broken link --- techniques/html/H98.html | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/techniques/html/H98.html b/techniques/html/H98.html index a52d88337e..1aaf9cf601 100644 --- a/techniques/html/H98.html +++ b/techniques/html/H98.html @@ -13,7 +13,7 @@

        Using HTML 5.2 autocomplete attributes

        When to Use

        -

        All HTML form fields that map to the HTML 5.2 autofill tokens.

        +

        All HTML form fields that map to the HTML 5.2 autofill tokens.

        Description

        @@ -26,7 +26,7 @@

        Description

        The autocomplete attribute allows the browser to do a pattern match against a list of values locally stored with the browser, and supplies the appropriate corresponding value when the input is programmatically tagged. This is a user setting that can be turned on or off, or modified by the end user. This reduces typing and reliance on memory because it uses stored values to fill in the fields.

        -

        It's important to note the Success Criterion Identify Input Purpose and autocomplete attribute only place requirements on input fields collecting information about the user.

        +

        It's important to note the Success Criterion Identify Input Purpose and autocomplete attribute only place requirements on input fields collecting information about the user.

        For the Success Criterion, it is assumed that the autocomplete attribute is not used on form fields that do not correspond to an autocomplete field described in the HTML autocomplete attribute specification. If the autocomplete field is used to describe a "custom" taxonomy, rather than that described in the specification, this rule may produce incorrect results.

        @@ -78,7 +78,7 @@

        A user's credit card information

        Tests

        Procedure

        -

        For each form field that collects information about the user and corresponds to an autocomplete field described in WCAG 2.1 7. Section 7: Input Purposes for User Interface Components, check the following:

        +

        For each form field that collects information about the user and corresponds to an autocomplete field described in WCAG 2.1 7. Section 7: Input Purposes for User Interface Components, check the following:

        1. The form field has a valid and well-formed autocomplete attribute and value pair.
        2. The purpose of the form field indicated by the label corresponds with the autocomplete token on the input.
          3. From 05bb8aa4645f740f721ca05c58e250f9969f1ba0 Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Mon, 6 Nov 2023 11:11:27 -0800 Subject: [PATCH 47/80] Replace absolute URL(s) with relative --- techniques/html/H95.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/techniques/html/H95.html b/techniques/html/H95.html index 34a468b19f..6672f29ecd 100644 --- a/techniques/html/H95.html +++ b/techniques/html/H95.html @@ -5,7 +5,7 @@

          The src attribute of the track element is a URL that is the address of the text track data.

          The kind attribute of the track element indicates the kind of information in the timed text. captions text tracks provide a text version of dialogue and other sounds important to understanding the video. Subtitles contain only the dialogue. If other audio information is important to understanding the video, a subtitle track will not be sufficient to meet the success criterion.

          -

          Some regions use the term "subtitle" for any visible text representation of the audio track. An author may mark up a timed text track in the language of the audio track as kind=subtitles, instead of kind=captions, and may include additional relevant audio information. It is not best practice to use subtitles in this situation, since it may confuse users who are trying to find captions, but such a timed text track would meet the requirements of Success Criterion 1.2.2.

          +

          Some regions use the term "subtitle" for any visible text representation of the audio track. An author may mark up a timed text track in the language of the audio track as kind=subtitles, instead of kind=captions, and may include additional relevant audio information. It is not best practice to use subtitles in this situation, since it may confuse users who are trying to find captions, but such a timed text track would meet the requirements of Success Criterion 1.2.2.

        Examples

        From 885264d19fdc962e3316376c4d9e43fcf907ab74 Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Mon, 6 Nov 2023 11:11:41 -0800 Subject: [PATCH 48/80] Replace absolute URL(s) with relative --- techniques/html/H94.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/techniques/html/H94.html b/techniques/html/H94.html index de4b7317d7..2ac780ff44 100644 --- a/techniques/html/H94.html +++ b/techniques/html/H94.html @@ -50,7 +50,7 @@

        HTML Validators

        do I validate my code or check for possible errors? describes the tools in the free editor HTML-Kit for checking HTML, CSS and XML.

      -

      For other resources, see G134: +

      For other resources, see G134: Validating Web pages.

      \ No newline at end of file From 381181988954466b6cc363983eed2f1f1964eb97 Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Mon, 6 Nov 2023 11:11:54 -0800 Subject: [PATCH 49/80] Replace absolute URL(s) with relative --- techniques/html/H93.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/techniques/html/H93.html b/techniques/html/H93.html index a77d4c0d64..e1560d8682 100644 --- a/techniques/html/H93.html +++ b/techniques/html/H93.html @@ -51,6 +51,6 @@

      HTML Validators

      do I validate my code or check for possible errors? describes the tools in the free editor HTML-Kit for checking HTML, CSS and XML.
    -

    For other resources, see G134: Validating Web pages.

    +

    For other resources, see G134: Validating Web pages.

    \ No newline at end of file From a1dc0ebe92b56b3e8542af35d63dd2e87a44b751 Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Mon, 6 Nov 2023 11:12:06 -0800 Subject: [PATCH 50/80] Replace absolute URL(s) with relative --- techniques/html/H88.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/techniques/html/H88.html b/techniques/html/H88.html index c803b982fd..f58f4f7965 100644 --- a/techniques/html/H88.html +++ b/techniques/html/H88.html @@ -34,7 +34,7 @@
  • H75

Resources

-

Refer to the resources section of Validating Web +

Refer to the resources section of Validating Web pages.

\ No newline at end of file From 2ca76605079e7dde45914c0bdbe272c941d64c35 Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Mon, 6 Nov 2023 11:12:15 -0800 Subject: [PATCH 51/80] Replace absolute URL(s) with relative --- techniques/html/H86.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/techniques/html/H86.html b/techniques/html/H86.html index d2c3e9a6cd..502bc11935 100644 --- a/techniques/html/H86.html +++ b/techniques/html/H86.html @@ -23,7 +23,7 @@

Description

ASCII art was common on the internet before graphics became widely used. ASCII characters were arranged to form pictures, pictures of text, or graphs. Although ASCII content is not used frequently on the Web anymore, it must be remembered that, when it is used, it can be very confusing to people who are accessing the internet using screen readers. If ASCII art is used, it should also have a text explanation of what the picture is. It is also suggested that, if the ASCII picture isn't marked up as an image using ARIA, that there is a link to skip over the art (although this is not required).

-

Leet used to be a fairly-common part of Internet culture and slang, but is now hardly used. Leetspeak uses various combinations of characters, including numerals and special characters, to replace standard characters. Leet is often incomprehensible to people using screen readers, and therefore requires a text alternative in order to conform to Success Criterion 1.1.1 (Non-Text Content).

+

Leet used to be a fairly-common part of Internet culture and slang, but is now hardly used. Leetspeak uses various combinations of characters, including numerals and special characters, to replace standard characters. Leet is often incomprehensible to people using screen readers, and therefore requires a text alternative in order to conform to Success Criterion 1.1.1 (Non-Text Content).

From 1e69b4e8110e4749c3bc92beb165cbed27bc627c Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Mon, 6 Nov 2023 11:12:23 -0800 Subject: [PATCH 52/80] Replace absolute URL(s) with relative --- techniques/html/H76.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/techniques/html/H76.html b/techniques/html/H76.html index 5de7980b09..51d0e3590c 100644 --- a/techniques/html/H76.html +++ b/techniques/html/H76.html @@ -17,7 +17,7 @@

When to Use

Description

-

The objective of this technique is to enable redirects on the client side without confusing the user. Redirects are preferably implemented on the server side (see Implementing automatic redirects on the server side instead of on the client side), but authors do not always have control over server-side technologies.

+

The objective of this technique is to enable redirects on the client side without confusing the user. Redirects are preferably implemented on the server side (see Implementing automatic redirects on the server side instead of on the client side), but authors do not always have control over server-side technologies.

In HTML, one can use the meta element with the value of the http-equiv attribute set to refresh and the value of the content attribute set to 0 (meaning zero seconds), followed by the URI that the browser should request. It is important that the time-out is set to zero, to avoid that content is displayed before the new page is loaded. The page containing the redirect code should only contain information related to the redirect.

@@ -63,7 +63,7 @@

Related Techniques

Resources

From 8cd5ea0f3ae926d609c722c667fa2a01e55795cc Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Mon, 6 Nov 2023 11:12:32 -0800 Subject: [PATCH 53/80] Replace absolute URL(s) with relative --- techniques/html/H75.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/techniques/html/H75.html b/techniques/html/H75.html index d8a40a9006..e93460ad99 100644 --- a/techniques/html/H75.html +++ b/techniques/html/H75.html @@ -70,7 +70,7 @@

Entities in Extensible Markup Language (XML) 1.1, W3C Recommendation 04 February 2004. -

For other resources, see Validating Web +

For other resources, see Validating Web pages.

\ No newline at end of file From 3c4951de38d8ebb275193cafaf985494b0d277c8 Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Mon, 6 Nov 2023 11:12:40 -0800 Subject: [PATCH 54/80] Replace absolute URL(s) with relative --- techniques/html/H74.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/techniques/html/H74.html b/techniques/html/H74.html index d4ed30216b..34263a9723 100644 --- a/techniques/html/H74.html +++ b/techniques/html/H74.html @@ -57,7 +57,7 @@

Resources

HTML - The doctype.
  • - Validating Web pages. + Validating Web pages.
  • The W3C's Nu HTML Checker. From c9415e2748ce1195d6dea6401428b77f1213061d Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Mon, 6 Nov 2023 11:12:54 -0800 Subject: [PATCH 55/80] Replace absolute URL(s) with relative --- techniques/html/H70.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/techniques/html/H70.html b/techniques/html/H70.html index e0c29718ab..6c87f3c630 100644 --- a/techniques/html/H70.html +++ b/techniques/html/H70.html @@ -13,7 +13,7 @@

    This technique is appropriate when framesets are already used to organize the content of the page; other techniques are preferred for pages that are not already using framesets, because many people using assistive technology have trouble with frames . An - advisory technique about using noframes is available in Success Criterion 1.1.1.

    + advisory technique about using noframes is available in Success Criterion 1.1.1.

    In HTML5 the frame element is marked as obsolete.

    • Examples

    From 24eb5a1d02d83e40a2cf56f2a966d56b212b6215 Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Mon, 6 Nov 2023 11:13:09 -0800 Subject: [PATCH 56/80] Replace absolute URL(s) with relative --- techniques/html/H69.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/techniques/html/H69.html b/techniques/html/H69.html index 3dd1770291..c439abacb0 100644 --- a/techniques/html/H69.html +++ b/techniques/html/H69.html @@ -108,8 +108,8 @@

    Procedure

    Expected Results

    From 4239fd674669a77ff5d419dfa56dfd0c8f4c3dbd Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Mon, 6 Nov 2023 11:13:18 -0800 Subject: [PATCH 57/80] Replace absolute URL(s) with relative --- techniques/html/H54.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/techniques/html/H54.html b/techniques/html/H54.html index f389c0946b..6c69d3b9e4 100644 --- a/techniques/html/H54.html +++ b/techniques/html/H54.html @@ -5,7 +5,7 @@ word or phrase where it is defined. The dfn element is used to indicate the defining instance of the enclosed term. In other words, it marks the occurrence of the term where the term is defined. Note that it encloses the term, not the definition. This - technique would be used in combination with Using + technique would be used in combination with Using inline definitions to provide the definition.

    Examples

    From 7fe6397f46def0bcdb5b6f041e310f6bb60c852f Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Mon, 6 Nov 2023 11:13:34 -0800 Subject: [PATCH 58/80] Replace absolute URL(s) with relative --- techniques/html/H44.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/techniques/html/H44.html b/techniques/html/H44.html index a8fe0efad0..c4414d7685 100644 --- a/techniques/html/H44.html +++ b/techniques/html/H44.html @@ -19,7 +19,7 @@

    When to Use

    Description

    The objective of this technique is to use the label element to explicitly associate a form control with a label. A label is attached to a specific form control through the use of the for attribute. The value of the for attribute must be the same as the value of the id attribute of the form control.

    The id attribute may have the same value as the name attribute, but both must be provided, and the id must be unique in the Web page.

    -

    This technique is sufficient for Success Criteria 1.1.1 (Non-Text Content), 1.3.1 (Info and Relationships) and 4.1.2 (Name, Role, Value) whether or not the label element is visible. That is, it may be hidden using CSS. However, for Success Criterion 3.3.2 (Labels or Instructions), the label element must be visible since it provides assistance to all users who need help understanding the purpose of the field.

    +

    This technique is sufficient for Success Criteria 1.1.1 (Non-Text Content), 1.3.1 (Info and Relationships) and 4.1.2 (Name, Role, Value) whether or not the label element is visible. That is, it may be hidden using CSS. However, for Success Criterion 3.3.2 (Labels or Instructions), the label element must be visible since it provides assistance to all users who need help understanding the purpose of the field.

    An additional benefit of this technique is a larger clickable area for the control, since clicking on the label or the control will activate the control. This can be helpful for users with impaired motor control.

    Note that the label is positioned after input elements of type="checkbox" and type="radio".

    From 1383dd89abe8382dfd5cd2f95103c6232ca3fbf7 Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Mon, 6 Nov 2023 11:13:47 -0800 Subject: [PATCH 59/80] Replace absolute URL(s) with relative --- techniques/html/H39.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/techniques/html/H39.html b/techniques/html/H39.html index f29eb2a672..97b6ddd379 100644 --- a/techniques/html/H39.html +++ b/techniques/html/H39.html @@ -22,7 +22,7 @@

    Description

    The caption element is the appropriate markup for such text and it ensures that the table identifier remains associated with the table, including visually (by default). In addition, using the caption element allows screen reading software to navigate directly to the caption for a table if one is present.

    -

    Although WCAG 2 does not prohibit the use of layout tables, CSS-based layouts are recommended in order to retain the defined semantic meaning of the HTML table elements and to conform to the coding practice of separating presentation from content. If a table is used for layout, the caption element is not used. The purpose of a layout table is simply to control the placement of content; the table itself is "transparent" to the user. A caption would "break" this transparency by calling attention to the table. See F46 for details.

    +

    Although WCAG 2 does not prohibit the use of layout tables, CSS-based layouts are recommended in order to retain the defined semantic meaning of the HTML table elements and to conform to the coding practice of separating presentation from content. If a table is used for layout, the caption element is not used. The purpose of a layout table is simply to control the placement of content; the table itself is "transparent" to the user. A caption would "break" this transparency by calling attention to the table. See F46 for details.

    From 3f32b74361185bd52e0477f5d071203efc2db848 Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Mon, 6 Nov 2023 11:14:53 -0800 Subject: [PATCH 60/80] Replace absolute URL(s) with relative --- techniques/html/H33.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/techniques/html/H33.html b/techniques/html/H33.html index d929197766..c39dacd898 100644 --- a/techniques/html/H33.html +++ b/techniques/html/H33.html @@ -8,7 +8,7 @@ through the title attribute is something the user should know before following the link, such as a warning, then it should be provided in the link text rather than in the title attribute.

    -

    Because of the extensive user agent limitations in supporting access to the title attribute, authors should use caution in applying this technique. For this reason, it is preferred that the author use technique C7: Using CSS to hide a portion of the link text or H30: Providing link text that describes the purpose of a link for anchor elements.

    +

    Because of the extensive user agent limitations in supporting access to the title attribute, authors should use caution in applying this technique. For this reason, it is preferred that the author use technique C7: Using CSS to hide a portion of the link text or H30: Providing link text that describes the purpose of a link for anchor elements.

    Examples

    Clarifying the purpose of a link

    From 0b70119c270516ec63ad0dd7fa456c5477ad2c5c Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Mon, 6 Nov 2023 11:17:01 -0800 Subject: [PATCH 61/80] Fix broken link --- techniques/html/H2.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/techniques/html/H2.html b/techniques/html/H2.html index 669d718cfd..3df77fc687 100644 --- a/techniques/html/H2.html +++ b/techniques/html/H2.html @@ -19,7 +19,7 @@

    When to Use

    Description

    This objective of this technique is to provide both text and iconic representations of links without making the web page more confusing or difficult for keyboard users or assistive technology users. Since different users finding text and icons more usable, providing both can improve the accessibility of the link.

    Many links have both a text and iconic representation adjacent to each other, but rendered in separate a elements. Visually they appear to be a single link, but many users encounter them as adjacent identical links. For a keyboard user, it is tedious to navigate through redundant links. For users of assistive technologies, it can be confusing to encounter successive identical links. When the text alternative for the icon is a duplicate of the link text, it is repetitive as screen readers read the description twice.

    -

    If the author omitted alternative text from the link image, it would fail Success Criterion 1.1.1 because the text alternative would not serve the same purpose as the graphical link.

    +

    If the author omitted alternative text from the link image, it would fail Success Criterion 1.1.1 because the text alternative would not serve the same purpose as the graphical link.

    This technique provides such links by putting the text and image together in one a element and providing null alternative text on the image to eliminate duplication of text. In this way, both representations of the link are provided, but keyboard users only encounter one link and assistive technology that provides users with link lists for a web page do not include duplicate links.

    Sometimes the text and the icon link are rendered in separate, adjacent table cells to facilitate page layout. Although WCAG 2 does not prohibit the use of layout tables, CSS-based layouts are recommended in order to retain the defined semantic meaning of the HTML table elements and to conform to the coding practice of separating presentation from content. If CSS is used, this technique can be applied to combine the links.

    From f5352753bf3863f1359dba491138cb9afa4b13b7 Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Mon, 6 Nov 2023 11:17:30 -0800 Subject: [PATCH 62/80] Replace absolute URL(s) with relative --- techniques/general/G217.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/techniques/general/G217.html b/techniques/general/G217.html index d4a75d5a2f..74ff1fdbb5 100644 --- a/techniques/general/G217.html +++ b/techniques/general/G217.html @@ -22,7 +22,7 @@

    Description

    To prevent accidental activation, authors must allow users to turn off or reconfigure shortcuts that are made up of only character keys. Reconfiguring the shortcut may involve the ability to add a modifier key such as Ctrl, or authors may elect to allow users to alter the character keys assigned in addition to adding a modifer. Providing a mechanism to turn off or reassign the shortcut ensures more users can successfully interact with the application.

    If the keyboard shortcut is only active when a particular user interface component has focus, then the author does not need to provide an override mechanism. For example, in a select element, it is expected behaviour that pressing a letter key will reposition to the next item within the select element that begins with that character. This shortcut is only triggered when the select element has focus, and so it does not interfere with a user's ability to interact with the rest of the page.

    Locating and testing for character key shortcuts

    -

    An initial challenge for testers is identifying if author-created shortcuts exist, and then determining if existing shortcuts are triggered by character keys without modifiers. Where testers have access to the develop team, the existence and nature of shortcut keys can often be determined simply by asking involved designers and developers. Where reliable information from the authors is not available, the presence of shortcuts can possibly be identified by checking code (for example, in javascript, the presence of keydown, keyup and keypress listeners). Another means of identifying shortcuts is to review documentation. Where none of these strategies provide information on the presence of keyboard shortcuts, manual tests will need to be completed to search for the existence of character key shortcuts. Review the test procedure in failure technique F99 for guidance.

    +

    An initial challenge for testers is identifying if author-created shortcuts exist, and then determining if existing shortcuts are triggered by character keys without modifiers. Where testers have access to the develop team, the existence and nature of shortcut keys can often be determined simply by asking involved designers and developers. Where reliable information from the authors is not available, the presence of shortcuts can possibly be identified by checking code (for example, in javascript, the presence of keydown, keyup and keypress listeners). Another means of identifying shortcuts is to review documentation. Where none of these strategies provide information on the presence of keyboard shortcuts, manual tests will need to be completed to search for the existence of character key shortcuts. Review the test procedure in failure technique F99 for guidance.

    From 110837024a08b986e156a987728c1b289cd6cebf Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Mon, 6 Nov 2023 11:17:50 -0800 Subject: [PATCH 63/80] Replace absolute URL(s) with relative --- techniques/general/G212.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/techniques/general/G212.html b/techniques/general/G212.html index 89751b935a..55bff4f304 100644 --- a/techniques/general/G212.html +++ b/techniques/general/G212.html @@ -38,7 +38,7 @@

    Using a native button or link in HTML

    Using a native button in iOS or Android

    In native buttons in iOS and Android onclick events are triggered on the up-event by default.

    -

    The WCAG standard itself applies to web pages at a URL, and therefore this example is provided as helpful supplementary advice for those looking to implement the WCAG2ICT for native applications.

    +

    The WCAG standard itself applies to web pages at a URL, and therefore this example is provided as helpful supplementary advice for those looking to implement the WCAG2ICT for native applications.

    From 4231c896f9076b24a5988340db62293cbc6aa8d5 Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Mon, 6 Nov 2023 11:18:00 -0800 Subject: [PATCH 64/80] Replace absolute URL(s) with relative --- techniques/general/G211.html | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/techniques/general/G211.html b/techniques/general/G211.html index cfd2352cf1..bdb662955b 100644 --- a/techniques/general/G211.html +++ b/techniques/general/G211.html @@ -22,13 +22,13 @@

    Description

    When speech input users interact with a web page, they usually speak a command followed by the reference to some visible label (such as text beside an input field or inside a button or link). For example, they may say "click search" to activate a button labelled Search. When speech recognition software processes speech input and looks for matches, it uses the accessible name of controls. Where there is a mismatch between the text in the label and the text in the accessible name, it can cause issues for the user. The simplest way to enable speech input users and meet 2.5.3 Label in Name is to ensure that the accessible name matches the visible text label.

    Determining the appropriate label

    Sometimes more than one text string will be positioned in the vicinity of a control that could be considered a candidate for its label. For example, a set of inputs that each have their own labels may also be preceded by a heading, an instruction or a group label (such as an HTML legend/fieldset or an ARIA group or radiogroup). Note that the term "group label" means something different than "label", both programmatically and in regard to 2.5.3 Label in Name.

    -

    The Understanding 2.5.3 Label in Name document recommends that only the text string adjacent to or in close proximity to an input should be treated as the label when assessing a control's label for the purposes of meeting 2.5.3 (see the section "Identifying label text for components"). There are both practical and technical reasons for restricting the designation of an input's label in this way. The technical reasons are discussed in the Understanding document's section called Accessible Name and Description Computation specification.

    +

    The Understanding 2.5.3 Label in Name document recommends that only the text string adjacent to or in close proximity to an input should be treated as the label when assessing a control's label for the purposes of meeting 2.5.3 (see the section "Identifying label text for components"). There are both practical and technical reasons for restricting the designation of an input's label in this way. The technical reasons are discussed in the Understanding document's section called Accessible Name and Description Computation specification.

    Examples

    -

    Mapping a visible label to the accessible name is achieved in many technologies by meeting 1.3.1 Information and Relationships through the proper use of native semantics. Many controls derive accessible names by correct nesting of elements, while other elements have specific attributes which are a valid means of providing or referencing an accessible name.

    +

    Mapping a visible label to the accessible name is achieved in many technologies by meeting 1.3.1 Information and Relationships through the proper use of native semantics. Many controls derive accessible names by correct nesting of elements, while other elements have specific attributes which are a valid means of providing or referencing an accessible name.

    The accessible name should be assigned through native elements and semantics where possible. That helps ensure an exact match between the visible label and name.

    Anchor text provides both the link's label and its accessible name

    @@ -69,7 +69,7 @@

    Simple Radio Button Group

    Call me when balance exceeds $10,000, Yes No
    Figure 1 "Call me when balance exceeds $10,000 radio group, with Yes and No choices
    -

    The label for each component should be restricted to "Yes" and "No". To meet 1.3.1 Information and Relationships and 3.3.2 Labels or Instructions, the "Call me…" text can be coded to convey the relationship to ATs, in this example by using a fieldset and legend.

    +

    The label for each component should be restricted to "Yes" and "No". To meet 1.3.1 Information and Relationships and 3.3.2 Labels or Instructions, the "Call me…" text can be coded to convey the relationship to ATs, in this example by using a fieldset and legend.

    If the label is not restricted to the string adjacent to the radio button, multiple interpretations of what constitutes the label can result in less uniform functionality. If "Yes" alone is not the label for the first radio button, is it "Call me when balance exceeds $10,000"? Or is it a combination of text strings, in which case is the order "Call me when balance exceeds $10,000 Yes" or "Yes, Call me when balance exceeds $10,000"? Decisions to combine text strings can have negative effects on screen reader users since the order of concatenation can affect meaning. In this example, "No, call me when balance exceeds $10,000" could be very confusing to a screen reader user.

    <fieldset>
    From a2c744d9e2f9087d148b5ae69ae0fa5a7d0e3254 Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Mon, 6 Nov 2023 11:18:48 -0800 Subject: [PATCH 65/80] Replace absolute URL(s) with relative --- techniques/general/G206.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/techniques/general/G206.html b/techniques/general/G206.html index 2d8347efa8..02f024b29d 100644 --- a/techniques/general/G206.html +++ b/techniques/general/G206.html @@ -5,7 +5,7 @@

    It should be noted that it is also sufficient to lay out the content in such a way that horizontal scrolling is required to access content, but that it is not necessary to scroll horizontally in order to read a line of text.

    For instance, a spreadsheet that requires horizontal scrolling is acceptable if no horizontal scrolling is necessary for each column individually (i.e., scrolling is only necessary to see other columns, but not for the left or right edges of each individual column).

    -

    This technique can be used in combination with a style switching technique to present a page that is a conforming alternate version for non-conforming content. Refer to C29: Using a style switcher to provide a conforming alternate version and Understanding Conforming Alternate Versions for more information.

    +

    This technique can be used in combination with a style switching technique to present a page that is a conforming alternate version for non-conforming content. Refer to C29: Using a style switcher to provide a conforming alternate version and Understanding Conforming Alternate Versions for more information.

    Examples

    From 5e426c4bc6bc8c8c29cef03666dd470f69067052 Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Mon, 6 Nov 2023 11:18:57 -0800 Subject: [PATCH 66/80] Replace absolute URL(s) with relative --- techniques/general/G193.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/techniques/general/G193.html b/techniques/general/G193.html index d90c41b595..5e8e7b36fc 100644 --- a/techniques/general/G193.html +++ b/techniques/general/G193.html @@ -4,7 +4,7 @@

    The purpose of this technique is to provide help using a multimedia avatar that provides assistance in using the Web page. An avatar can be particularly helpful to people with cognitive disabilities who may have trouble reading text. The use of visuals will help some people to focus on the material presented.

    The multimedia avatar must also satisfy relevant Success Criterion in - Guideline 1.2.

    + Guideline 1.2.

    Examples

      From d3f7ac5b5b36c6707e4f226d92db1fd975d5c7a1 Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Mon, 6 Nov 2023 11:19:48 -0800 Subject: [PATCH 67/80] Replace absolute URL(s) with relative --- techniques/general/G191.html | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/techniques/general/G191.html b/techniques/general/G191.html index 5aa870cbcd..8e482963fb 100644 --- a/techniques/general/G191.html +++ b/techniques/general/G191.html @@ -2,7 +2,7 @@

      This technique relates to all technologies.

    Description

    This is a general technique for allowing people who cannot use a page with blinking content to turn the blinking content off. - Conformance Requirement 1 + Conformance Requirement 1 allows for conforming alternate pages to be used to meet conformance. This technique is an example of that approach applied to success criteria 2.2.2.

    It is important that the page without blinking content contain all of the information that was on the page with blinking content.

    @@ -10,9 +10,8 @@

    This technique can be used in combination with a style switching technique to present a page that is a conforming alternate version for non-conforming content. Refer to - - and - Understanding Conforming Alternate Versions + Using a style switcher to provide a conforming alternate version + and Understanding Conforming Alternate Versions for more information.

    Examples

    From 92d573de3ec18a51b76e092ff5418518bd52f080 Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Mon, 6 Nov 2023 11:19:58 -0800 Subject: [PATCH 68/80] Replace absolute URL(s) with relative --- techniques/general/G189.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/techniques/general/G189.html b/techniques/general/G189.html index 932584e581..5520453fe2 100644 --- a/techniques/general/G189.html +++ b/techniques/general/G189.html @@ -22,7 +22,7 @@

    Description

    If the control for switching to the alternate version is a link, it must always be possible to understand the purpose of the control directly from its link text.

    This technique provides the alternate version for the current page view. It is also possible, and in some cases would be advisable, to save this preference in a cookie or server-side user profile, so that users would only have to make the selection once per site and would automatically be taken to their preferred version.

    -

    This technique can be used in combination with a style switching technique to present a page that is a conforming alternate version for non-conforming content. Refer to C29: Using a style switcher to provide a conforming alternate version and Understanding Conforming Alternate Versions for more information.

    +

    This technique can be used in combination with a style switching technique to present a page that is a conforming alternate version for non-conforming content. Refer to C29: Using a style switcher to provide a conforming alternate version and Understanding Conforming Alternate Versions for more information.

    From 37b0591236368edcade69f17246d7dfa0b59b64e Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Mon, 6 Nov 2023 11:20:06 -0800 Subject: [PATCH 69/80] Replace absolute URL(s) with relative --- techniques/general/G188.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/techniques/general/G188.html b/techniques/general/G188.html index 77f2ea79cc..3e89a2758a 100644 --- a/techniques/general/G188.html +++ b/techniques/general/G188.html @@ -19,7 +19,7 @@

    When to Use

    Description

    Many people with cognitive disabilities have trouble reading text that is single spaced. A button that increases the line height will help them read the content. In order to retain the separation of paragraphs, the space between paragraphs should also increase so that it is at least 1.5 times as high as the line spacing.

    -

    This technique can be used in combination with a style switching technique to present a page that is a conforming alternate version for non-conforming content. Refer to C29: Using a style switcher to provide a conforming alternate version and Understanding Conforming Alternate Versions for more information.

    +

    This technique can be used in combination with a style switching technique to present a page that is a conforming alternate version for non-conforming content. Refer to C29: Using a style switcher to provide a conforming alternate version and Understanding Conforming Alternate Versions for more information.

    From 7cf6d1f0658f49eb2963ce3249e8a7f2b21c1b64 Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Mon, 6 Nov 2023 11:20:12 -0800 Subject: [PATCH 70/80] Replace absolute URL(s) with relative --- techniques/general/G185.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/techniques/general/G185.html b/techniques/general/G185.html index cbe91e00df..5f4f80f5d3 100644 --- a/techniques/general/G185.html +++ b/techniques/general/G185.html @@ -4,7 +4,7 @@

    The objective of this technique is to make it possible for users to locate all the information in a small Web site by providing links to all Web pages from the home page. When the number of pages in the site is small enough, the home page can contain site map information directly. The other pages in the Web site contain links to the home page.

    In this way, the home page serves as two mechanisms in one. It provides the usual navigation to pages. It also is a de facto site map to the site.

    All the Web pages in the site may contain links to all the other pages, and those sets of links satisfy - Success Criterion 3.2.3 (Consistent Navigation).

    + Success Criterion 3.2.3 (Consistent Navigation).

    Examples

    • A small commercial Web site for a consultant contains a home page, a Contacts page for contacting the consultant, a page describing the consultant's background, and a page with examples of the consultant's work. Each page contains a navigation bar that links to all the other pages in the site.
      • From ae3302b2eb0f8235c5b565b9d89f4ca3d87b01a8 Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Mon, 6 Nov 2023 11:20:19 -0800 Subject: [PATCH 71/80] Replace absolute URL(s) with relative --- techniques/general/G182.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/techniques/general/G182.html b/techniques/general/G182.html index c44abfa655..691b02edaf 100644 --- a/techniques/general/G182.html +++ b/techniques/general/G182.html @@ -9,7 +9,7 @@

      To use this technique, an author incorporates a visual cue in addition to color for each place where color alone is used to convey information. Visual cues can take many forms including changes to the font style, the addition of underlines, bold, or italics, or changes to the font size.

      While this technique is sufficient to meet the visual requirements of Success Criterion 1.4.1, the information conveyed by the color must also be available programmatically to satisfy Success Criterion 1.3.1. See - How to Meet 1.3.1.

      + How to Meet 1.3.1.

    Examples

      From 1fd6b7ed2b26efb95ab3d1773fda8a54bb997415 Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Mon, 6 Nov 2023 11:20:31 -0800 Subject: [PATCH 72/80] Replace absolute URL(s) with relative --- techniques/general/G174.html | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/techniques/general/G174.html b/techniques/general/G174.html index e4d13fd915..53c3fe99c4 100644 --- a/techniques/general/G174.html +++ b/techniques/general/G174.html @@ -2,9 +2,9 @@

      Any technology.

    Description

    When the contrast between the text and its background for some portion of the page has not been designed to meet the contrast level for - Success Criterion 1.4.3 + Success Criterion 1.4.3 or - 1.4.6, it is possible to meet these guidelines using the "Alternate Version" clause in the conformance requirements (Conformance Requirement 1). A link or control on the page can either change the page so that all aspects conform, or it could take the viewer to a new version of the page that does conform at the desired level. Placing the link or control prominently on the page will assist users in accessing the conforming content readily.

    + 1.4.6, it is possible to meet these guidelines using the "Alternate Version" clause in the conformance requirements (Conformance Requirement 1). A link or control on the page can either change the page so that all aspects conform, or it could take the viewer to a new version of the page that does conform at the desired level. Placing the link or control prominently on the page will assist users in accessing the conforming content readily.

    For this technique to be used successfully, three things must be true:

    1. The link or control on the original page must itself meet the contrast requirement of the desired SC. (If the user cannot see the control they may not be able to use it to go to the new page.)
      2. @@ -16,9 +16,9 @@

      This technique can be used in combination with a style switching technique to present a page that is a conforming alternate version for non-conforming content. Refer to - C29: Using a style switcher to provide a conforming alternate version + C29: Using a style switcher to provide a conforming alternate version and - Understanding Conforming Alternate Versions + Understanding Conforming Alternate Versions for more information.

    Examples

    From 0bc3a34b29bca2f5a912904c8b1631bb2fbedcca Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Mon, 6 Nov 2023 11:26:00 -0800 Subject: [PATCH 73/80] Replace absolute URLs with relative --- techniques/aria/ARIA22.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/techniques/aria/ARIA22.html b/techniques/aria/ARIA22.html index ced163f1cb..b26a3f3024 100644 --- a/techniques/aria/ARIA22.html +++ b/techniques/aria/ARIA22.html @@ -18,7 +18,7 @@

    When to Use

    Description

    - This technique uses the status role from the ARIA specification to notify Assistive Technologies (AT) when content has been updated with information about the user's or application's status. This is done by adding role="status" to the element that contains the status message. The aria live region role of status has an implicit aria-live value of polite, which allows a user to be notified via AT (such as a screen reader) when status messages are added. The role of status also has a default aria-atomic value of true, so that updates to the container marked with a role of status will result in the AT presenting the entire contents of the container to the user, including any author-defined labels (or additional nested elements). Such additional context can be critical where the status message text alone will not provide an equivalent to the visual experience. The content of the aria-live container is automatically read by the AT, without the AT having to focus on the place where the text is displayed. See WAI-ARIA status (role) for more details.

    + This technique uses the status role from the ARIA specification to notify Assistive Technologies (AT) when content has been updated with information about the user's or application's status. This is done by adding role="status" to the element that contains the status message. The aria live region role of status has an implicit aria-live value of polite, which allows a user to be notified via AT (such as a screen reader) when status messages are added. The role of status also has a default aria-atomic value of true, so that updates to the container marked with a role of status will result in the AT presenting the entire contents of the container to the user, including any author-defined labels (or additional nested elements). Such additional context can be critical where the status message text alone will not provide an equivalent to the visual experience. The content of the aria-live container is automatically read by the AT, without the AT having to focus on the place where the text is displayed. See WAI-ARIA status (role) for more details.

    @@ -45,7 +45,7 @@

    Updating the shopping cart status

    Tests

    Procedure

    -

    For each status message:

    +

    For each status message:

    1. Check that the container destined to hold the status message has a role attribute with a value of status before the status message occurs.
    2. Check that when the status message is triggered, it is inside the container.
      3. From a0b546c99a8dd8dfddc07b513f8522a80e8a26f7 Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Mon, 6 Nov 2023 11:27:29 -0800 Subject: [PATCH 74/80] Remove .html extension --- techniques/aria/ARIA20.html | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/techniques/aria/ARIA20.html b/techniques/aria/ARIA20.html index 4754fb999d..d4091d6ca1 100644 --- a/techniques/aria/ARIA20.html +++ b/techniques/aria/ARIA20.html @@ -1,7 +1,7 @@ Using the region role to identify a region of the page

      Using the region role to identify a region of the page

      ID: ARIA20

      Technology: aria

      Type: Technique

      When to Use

      Technologies that support Accessible Rich Internet Applications.

      Description

      -

      This technique demonstrates how to assign a generic region role to a section of a page so that user agents and assistive technologies may be able to programmatically identify it. The region role demarcates a segment of the page that contains content of significance so that it is more readily discoverable and navigable. The generic region should be used when the section cannot be marked up using a standard document landmark role (see ARIA11).

      +

      This technique demonstrates how to assign a generic region role to a section of a page so that user agents and assistive technologies may be able to programmatically identify it. The region role demarcates a segment of the page that contains content of significance so that it is more readily discoverable and navigable. The generic region should be used when the section cannot be marked up using a standard document landmark role (see ARIA11).

      It is important to name regions, because they are generic grouping elements and users will need some way to tell which region they are in. Regions can be named using aria-labelledby, aria-label, or another technique. Doing so helps to better expose content and information relationships on the page. The role of region should be used prudently, because if overused they can make the page overly verbose for screen reader users.

      Examples

      @@ -93,9 +93,9 @@

      Identifying a portlet with a generic region

      Resources

        From e997492b8f843008e35ae6b497880cd6e762f165 Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Mon, 6 Nov 2023 11:29:27 -0800 Subject: [PATCH 75/80] Replace absolute URL with relative --- techniques/client-side-script/SCR19.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/techniques/client-side-script/SCR19.html b/techniques/client-side-script/SCR19.html index e4ec640b61..7107e44b38 100644 --- a/techniques/client-side-script/SCR19.html +++ b/techniques/client-side-script/SCR19.html @@ -119,7 +119,7 @@ Accessible Forms using WCAG 2.0
      • - Change of context definition + Change of context definition
      From 38d1cb6ff8e250dcb81ce719a08e89b2b7693b9a Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Mon, 6 Nov 2023 11:34:03 -0800 Subject: [PATCH 76/80] Replace absolute URL with relative --- techniques/client-side-script/SCR36.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/techniques/client-side-script/SCR36.html b/techniques/client-side-script/SCR36.html index 15ee709981..d47af14f33 100644 --- a/techniques/client-side-script/SCR36.html +++ b/techniques/client-side-script/SCR36.html @@ -20,7 +20,7 @@

      Description

      Some Web pages display scrolling text because there is limited space available. Scrolling the text in a small text window makes the content available for users who can read quickly enough, but causes problems for users who read more slowly or use assistive technology. This technique provides a mechanism to stop the movement and make the entire block of text available statically. The text may be made available in a separate window or in a (larger) section of the page. Users can then read the text at their own speed.

      This technique does not apply when the text that is moving can not be displayed all at once on the screen (e.g., a long chat conversation).

      -

      This technique can be used in combination with a style switching technique to present a page that is a conforming alternate version for non-conforming content. Refer to C29: Using a style switcher to provide a conforming alternate version and Understanding Conforming Alternate Versions for more information.

      +

      This technique can be used in combination with a style switching technique to present a page that is a conforming alternate version for non-conforming content. Refer to C29: Using a style switcher to provide a conforming alternate version and Understanding Conforming Alternate Versions for more information.

      From 936e8add5fcba9234e717d06548527ecd812ef29 Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Mon, 6 Nov 2023 11:44:59 -0800 Subject: [PATCH 77/80] Replace absolute url with relative --- techniques/general/G223.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/techniques/general/G223.html b/techniques/general/G223.html index a6e13b3993..76db0b0cf9 100644 --- a/techniques/general/G223.html +++ b/techniques/general/G223.html @@ -1,7 +1,7 @@ Using an author-supplied, highly visible focus indicator

      Using an author-supplied, highly visible focus indicator

      ID: G195

      Technology: general

      Type: Technique

      When to Use

      Generally applicable.

      Description

      -

      The objective of this technique is enhance the focus indicator in the browser, by creating a highly visible one in the content. This technique is very similar to G195, but with a stronger indicator to meet Focus Appearance.

      +

      The objective of this technique is enhance the focus indicator in the browser, by creating a highly visible one in the content. This technique is very similar to G195, but with a stronger indicator to meet Focus Appearance.

      Examples

      From 8e32d03cf7106100c517ea26d23a600c45ee5843 Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Mon, 6 Nov 2023 12:51:43 -0800 Subject: [PATCH 78/80] Fix broken techniques and GitHub links --- techniques/about.html | 64 +++++++++++++++++++++---------------------- 1 file changed, 32 insertions(+), 32 deletions(-) diff --git a/techniques/about.html b/techniques/about.html index efa73399eb..4a5a0361bd 100644 --- a/techniques/about.html +++ b/techniques/about.html @@ -80,79 +80,79 @@

      Change Log

      : Removed Flash techniques.
    3. - : Added Failure of Success Criterion 2.5.1 due to providing functionality via a path-based + : Added Failure of Success Criterion 2.5.1 due to providing functionality via a path-based gesture without simple pointer alternative
    4. - : Added Failure due to inability to deactivate motion actuation
      5. + : Added Failure due to inability to deactivate motion actuation
    5. - : Added Failure of Success Criterion 1.4.12 due to clipped or overlapped content when text + : Added Failure of Success Criterion 1.4.12 due to clipped or overlapped content when text spacing is adjusted
    6. - : Added Failure of Success Criterion 4.1.3 due to providing status messages that cannot be + : Added Failure of Success Criterion 4.1.3 due to providing status messages that cannot be programmatically determined through role or properties
    7. - : Added Failure of Success Criterion 1.4.10 due to content disappearing and not being available + : Added Failure of Success Criterion 1.4.10 due to content disappearing and not being available when content has reflowed
    8. - : Added Providing single point activation for a control slider
      9. + : Added Providing single point activation for a control slider
    9. - : Added Providing controls to achieve the same result as path based or multipoint gestures
      10. + : Added Providing controls to achieve the same result as path based or multipoint gestures
    10. - : Added Failure of Success Criterion 1.3.4 due to showing a message asking to reorient device
      11. + : Added Failure of Success Criterion 1.3.4 due to showing a message asking to reorient device
    11. - : Added Using a control to allow access to content in different orientations which is otherwise + : Added Using a control to allow access to content in different orientations which is otherwise restricted
    12. - : Added Creating a two-color focus indicator to ensure sufficient contrast
      13. + : Added Creating a two-color focus indicator to ensure sufficient contrast
    13. - : Added Failure of Success Criterion 2.1.4 due to implementing character key shortcuts that + : Added Failure of Success Criterion 2.1.4 due to implementing character key shortcuts that cannot be turned off or remapped
    14. - : Added Making content on focus or hover hoverable, dismissible, and persistent
      15. + : Added Making content on focus or hover hoverable, dismissible, and persistent
    15. - : Added Using native controls to ensure functionality is triggered on the up-event
      16. + : Added Using native controls to ensure functionality is triggered on the up-event
    16. - : Added Failure of Success Criterion 2.5.6 due to interactions being limited to touch-only + : Added Failure of Success Criterion 2.5.6 due to interactions being limited to touch-only on touchscreen devices
    17. - : Added Provide conventional controls and an application setting for motion activated input
      18. + : Added Provide conventional controls and an application setting for motion activated input
    18. - : Added Semantically identifying a font icon with role="img"
      19. + : Added Semantically identifying a font icon with role="img"
    19. - : Added Failure due to locking the orientation to landscape or portrait view
      20. + : Added Failure due to locking the orientation to landscape or portrait view
    20. - : Removed F52 from SC 3.2.1 (still attached to SC 3.2.5) + : Removed F52 from SC 3.2.1 (still attached to SC 3.2.5)
    21. - : Added Provide sufficient contrast at the boundaries between adjoining colors
      22. + : Added Provide sufficient contrast at the boundaries between adjoining colors
    22. - : Added Using the CSS reduce-motion query to prevent motion
      23. + : Added Using the CSS reduce-motion query to prevent motion
    23. - : Added Ensuring that a contrast ratio of 3:1 is provided for icons
      24. + : Added Ensuring that a contrast ratio of 3:1 is provided for icons
    24. - : Added Using CSS width, max-width and flexbox to fit labels and inputs
      25. + : Added Using CSS width, max-width and flexbox to fit labels and inputs
    25. - : Added F95 of 1.4.13 due to content shown on hover not being hoverable
      26. + : Added F95 of 1.4.13 due to content shown on hover not being hoverable
    26. - : Added C34 Using media queries to un-fixing sticky headers / footers
      27. + : Added C34 Using media queries to un-fixing sticky headers / footers
    27. - : Added C36 Allowing for text spacing override
      28. + : Added C36 Allowing for text spacing override
    28. - : Added C37 Using CSS max-width and height to fit images
      29. + : Added C37 Using CSS max-width and height to fit images
    29. - : Added G207 Ensuring that drag-and-drop actions can be cancelled
      30. + : Added G207 Ensuring that drag-and-drop actions can be cancelled
    30. - : Added F95 Failure of Success Criterion 1.4.13 due to content shown on hover not being hoverable
      31. + : Added F95 Failure of Success Criterion 1.4.13 due to content shown on hover not being hoverable
    31. - : Added F96 Failure of Success Criterion 2.5.3 due to "accessible name" not containing the + : Added F96 Failure of Success Criterion 2.5.3 due to "accessible name" not containing the visible label text
    32. - : Added C38 Using CSS width, max-width and flexbox to fit labels and inputs
      33. + : Added C38 Using CSS width, max-width and flexbox to fit labels and inputs
    33. - : Added G207 Ensuring that a contrast ratio of 3:1 is provided for icons
      34. + : Added G207 Ensuring that a contrast ratio of 3:1 is provided for icons
    -

    For a more detailed view of recent changes to the informative documents see the github updates. +

    For a more detailed view of recent changes to the informative documents see the github updates.

    From a4f65eb1a0d5d126eddd761d01d4fd2aea204bb1 Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Mon, 6 Nov 2023 14:31:31 -0800 Subject: [PATCH 79/80] Replace absolute link with relative --- techniques/general/G178.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/techniques/general/G178.html b/techniques/general/G178.html index 97d36b9c33..d09e31461b 100644 --- a/techniques/general/G178.html +++ b/techniques/general/G178.html @@ -10,9 +10,9 @@

    This technique can be used in combination with a style switching technique to present a page that is a conforming alternate version for non-conforming content. Refer to - C29: Using a style switcher to provide a conforming alternate version + C29: Using a style switcher to provide a conforming alternate version and - Understanding Conforming Alternate Versions + Understanding Conforming Alternate Versions for more information.

    Examples

    From 555af1cb6ea314eda8056f7d0d5671ffae8412a1 Mon Sep 17 00:00:00 2001 From: Mike Gower Date: Tue, 28 May 2024 08:22:50 -0700 Subject: [PATCH 80/80] Update techniques/failures/F42.html --- techniques/failures/F42.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/techniques/failures/F42.html b/techniques/failures/F42.html index 33f123b885..001e1962f5 100644 --- a/techniques/failures/F42.html +++ b/techniques/failures/F42.html @@ -122,7 +122,7 @@

    Scripting a div element