diff --git a/_includes/understanding/intro/advisory.html b/_includes/understanding/intro/advisory.html index 3c64c9a91c..f18498ef2a 100644 --- a/_includes/understanding/intro/advisory.html +++ b/_includes/understanding/intro/advisory.html @@ -5,7 +5,7 @@ If there are techniques, however, for addressing this guideline that do not fall under any of the success criteria, they are listed here. These techniques are not required or sufficient for meeting any success criteria, - but can make certain types of Web content more accessible to more people. + but can make certain types of web content more accessible to more people.

{%- else -%}

diff --git a/techniques/client-side-script/SCR27.html b/techniques/client-side-script/SCR27.html index 48ff4a7765..d2067ce184 100644 --- a/techniques/client-side-script/SCR27.html +++ b/techniques/client-side-script/SCR27.html @@ -151,7 +151,7 @@

Tests

Procedure

    -
  1. Find all components in the Web Unit which can be reordered via drag and drop.
  2. +
  3. Find all components which can be reordered via drag and drop.
  4. Check that there is also a mechanism to reorder them using menus build of lists of links.
  5. Check that the menus are contained within the re-orderable items in the DOM.
  6. Check that scripts for reordering are triggered only from the onclick event of links.
  7. diff --git a/techniques/css/C9.html b/techniques/css/C9.html index c8c51cd04b..28d148f6bf 100644 --- a/techniques/css/C9.html +++ b/techniques/css/C9.html @@ -16,7 +16,7 @@

    When to Use

Description

-

The objective of this technique is to provide a mechanism to add purely decorative images and images used for visual formatting to Web content without requiring additional markup within the content. This makes it possible for assistive technologies to ignore the non-text content. Some user agents can ignore or turn off CSS at the user's request, so that background images included with CSS simply "disappear" and do not interfere with display settings such as enlarged fonts or high contrast settings.

+

The objective of this technique is to provide a mechanism to add purely decorative images and images used for visual formatting to web content without requiring additional markup within the content. This makes it possible for assistive technologies to ignore the non-text content. Some user agents can ignore or turn off CSS at the user's request, so that background images included with CSS simply "disappear" and do not interfere with display settings such as enlarged fonts or high contrast settings.

Background images can be included with the following CSS properties:

Description

The objective of this technique is to allow assistive technology to - understand Web content so that it can convey equivalent information to the + understand web content so that it can convey equivalent information to the user through an alternate user interface.

Sometimes content is not created using markup language but rather using a programming language or tools. In many cases, these technologies have diff --git a/techniques/general/G101.html b/techniques/general/G101.html index a372bf4aba..42b98b72a3 100644 --- a/techniques/general/G101.html +++ b/techniques/general/G101.html @@ -14,7 +14,7 @@

A term used in a restricted way

-

The word "technology" is widely used to cover everything from the stone tools used by early humans to contemporary digital devices such as cell phones. But in WCAG 2, the word technology is used in a more restricted way: it means a mechanism for encoding instructions to be rendered, played or executed by user agents, including markup languages, data formats, and programming languages used in producing and delivering Web content.

+

The word "technology" is widely used to cover everything from the stone tools used by early humans to contemporary digital devices such as cell phones. But in WCAG 2.0, the word technology is used in a more restricted way: it means a mechanism for encoding instructions to be rendered, played or executed by user agents, including markup languages, data formats, and programming languages used in producing and delivering web content.

diff --git a/techniques/general/G108.html b/techniques/general/G108.html index 4f5f5ac940..6058112cf6 100644 --- a/techniques/general/G108.html +++ b/techniques/general/G108.html @@ -4,7 +4,7 @@ changes.

Description

The objective of this technique is to allow assistive technology to - understand Web content so that it can convey equivalent information to the + understand web content so that it can convey equivalent information to the user through an alternate user interface and allow them to operate controls through the AT.

This technique involves using standard, documented and supported features to diff --git a/techniques/general/G115.html b/techniques/general/G115.html index b569cfb4a3..bd81d192ed 100644 --- a/techniques/general/G115.html +++ b/techniques/general/G115.html @@ -16,7 +16,7 @@

When to Use

Description

-

The objective of this technique is to mark up the structure of the Web content using the appropriate semantic elements. In other words, the elements are used according to their meaning, not because of the way they appear visually.

+

The objective of this technique is to mark up the structure of the web content using the appropriate semantic elements. In other words, the elements are used according to their meaning, not because of the way they appear visually.

Using the appropriate semantic elements will make sure the structure is available to the user agent. This involves explicitly indicating the role that different units have in understanding the meaning of the content. The nature of a piece of content as a paragraph, header, emphasized text, table, etc. can all be indicated in this way. In some cases, the relationships between units of content should also be indicated, such as between headings and subheadings, or amongst the cells of a table. The user agent can then make the structure perceivable to the user, for example using a different visual presentation for different types of structures or by using a different voice or pitch in an auditory presentation.

In HTML, for example, phrase-level elements such as em, abbr, and cite add semantic information within sentences, marking text for emphasis and identifying abbreviations and citations, respectively. MathML, a markup language designed to maintain important distinctions between structure and presentation in mathematics, includes special "presentation" markup for the complex notations used to represent mathematical ideas as well as "content" (semantic) markup for the mathematical ideas themselves.

diff --git a/techniques/general/G125.html b/techniques/general/G125.html index 94bf3b94f8..8c9ceb4e44 100644 --- a/techniques/general/G125.html +++ b/techniques/general/G125.html @@ -3,7 +3,7 @@

Description

The objective of this technique is to make it possible for users to locate additional information by providing links to related web pages. It is one of a series of techniques for locating content that are sufficient for addressing Success Criterion 2.4.5. - Links are a basic component of the World Wide Web. They are the mechanism that makes the web an interconnected Web of content. Most authors employ this technique automatically when creating web pages.

+ Links are a basic component of the World Wide Web. They are the mechanism that makes the web an interconnected web of content. Most authors employ this technique automatically when creating web pages.

Examples

diff --git a/techniques/general/G130.html b/techniques/general/G130.html index 5a51837ac5..11ba75a358 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.

diff --git a/techniques/general/G131.html b/techniques/general/G131.html index 352036e54e..1cdd7c4d85 100644 --- a/techniques/general/G131.html +++ b/techniques/general/G131.html @@ -1,7 +1,7 @@ Providing descriptive labels

Providing descriptive labels

ID: G131

Technology: general

Type: Technique

When to Use

All technologies.

Description

-

The objective of this technique is to ensure that the label for any interactive component within Web content makes the component's purpose clear. Using the appropriate technology-specific techniques for technologies for associating labels with interactive controls allows assistive technology to recognize the label and present it to the user, therefore allowing the user to identify the purpose of the control.The label may also be used to include text or a text symbol indicating that input is required. +

The objective of this technique is to ensure that the label for any interactive component within web content makes the component's purpose clear. Using the appropriate technology-specific techniques for technologies for associating labels with interactive controls allows assistive technology to recognize the label and present it to the user, therefore allowing the user to identify the purpose of the control.The label may also be used to include text or a text symbol indicating that input is required.

Examples

diff --git a/techniques/general/G133.html b/techniques/general/G133.html index bf3637e517..bc4edfc604 100644 --- a/techniques/general/G133.html +++ b/techniques/general/G133.html @@ -12,7 +12,7 @@

A checkbox for requesting a specific extension

Requesting an indefinite extension

-

A web page contains the first part of a three-part form. Each part of the form includes more than 10 items. Some items require users to follow links for additional information. Immediately following the general instructions for completing the form is a checkbox with the label, “Allow as much time as I need to complete this form. I understand that I must close (quit) the Web browser if I choose to stop before completing the last part of the form."

+

A web page contains the first part of a three-part form. Each part of the form includes more than 10 items. Some items require users to follow links for additional information. Immediately following the general instructions for completing the form is a checkbox with the label, “Allow as much time as I need to complete this form. I understand that I must close (quit) the web browser if I choose to stop before completing the last part of the form."

Tests

diff --git a/techniques/general/G134.html b/techniques/general/G134.html index 7c33d1dc86..2bda8d33bb 100644 --- a/techniques/general/G134.html +++ b/techniques/general/G134.html @@ -71,7 +71,7 @@

Resources

  • Do not forget to add a doctype by the W3C Quality Assurance Initiative explains what doctypes are and why you should use them.
  • - Recommended DTDs to use in your Web document by the W3C Quality Assurance Initiative is a list of commonly used declarations.
  • + Recommended DTDs to use in your web document by the W3C Quality Assurance Initiative is a list of commonly used declarations.
  • How 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.
  • diff --git a/techniques/general/G135.html b/techniques/general/G135.html index 32c584e682..7481e49bf4 100644 --- a/techniques/general/G135.html +++ b/techniques/general/G135.html @@ -7,7 +7,7 @@ to interface with accessibility APIs

    Description

    The objective of this technique is to allow assistive technology to - understand Web content so that it can convey equivalent information to the + understand web content so that it can convey equivalent information to the user through an alternate user interface.

    Sometimes content is not created using markup language but rather using a programming language or tools. In many cases, these technologies have diff --git a/techniques/general/G142.html b/techniques/general/G142.html index 145d6a6018..c9fd1d306d 100644 --- a/techniques/general/G142.html +++ b/techniques/general/G142.html @@ -1,8 +1,8 @@ Using a technology that has commonly-available user agents that support zoom

    Using a technology that has commonly-available user agents that support zoom

    ID: G142

    Technology: general

    Type: Technique

    When to Use

    All technologies with user agent provided zoom capability.

    Description

    -

    The objective of this technique is to ensure content can be scaled uniformly by using a Web technology supported by user agents that change text size via a Zoom tool.

    -

    Content authored in technologies that are supported by user agents that can scale content uniformly (that is, zoom into content) satisfy this Success Criterion. Because this technique relies completely on user agent functionality, it is critical to test with a wide variety of user agents.

    +

    The objective of this technique is to ensure content can be scaled uniformly by using a web technology supported by user agents that change text size via a Zoom tool.

    +

    Content authored in technologies that are supported by user agents that can scale content uniformly (that is, zoom into content) satisfy this success criterion. Because this technique relies completely on user agent functionality, it is critical to test with a wide variety of user agents.

    This technique requires that the zoom function preserve all spatial relationships on the page and that all functionality continues to be available.

    Examples

      diff --git a/techniques/general/G144.html b/techniques/general/G144.html index 8abbd62cb0..e9b5f50ebc 100644 --- a/techniques/general/G144.html +++ b/techniques/general/G144.html @@ -1,4 +1,4 @@ -Ensuring that the Web Page contains another CAPTCHA serving the same purpose using a different modality

      Ensuring that the Web Page contains another CAPTCHA serving the same purpose using a different modality

      ID: G144

      Technology: general

      Type: Technique

      When to Use

      +Ensuring that the web page contains another CAPTCHA serving the same purpose using a different modality

      Ensuring that the web page contains another CAPTCHA serving the same purpose using a different modality

      ID: G144

      Technology: general

      Type: Technique

      When to Use

      Applies to all technologies.

      Description

      The purpose of this technique is to reduce occasions in which a user with a disability cannot complete a CAPTCHA task. Because there are alternate CAPTCHA tasks that use different modalities, a user is more likely to be able to complete one of the tasks successfully.

      diff --git a/techniques/general/G150.html b/techniques/general/G150.html index 66e8c5e5e6..6839e62713 100644 --- a/techniques/general/G150.html +++ b/techniques/general/G150.html @@ -5,7 +5,7 @@

      Real-time typing text entry techniques exist using stenographic and rapid typing technologies. Re-voicing speech-to-text (where a person listens to speech and then carefully re-voices it into a computer trained to their speech) is used today for telephone relay services and may be used in the future for captioning. Eventually speech-to-text with correction will be possible.

      Examples

        -
      • A radio station uses Web based captioning services to provide alternatives for live sporting events; the output from the service is incorporated in a viewport of the web page which also includes a streaming audio control.
      • +
      • A radio station uses web-based captioning services to provide alternatives for live sporting events; the output from the service is incorporated in a viewport of the web page which also includes a streaming audio control.

      Tests

      Procedure

      diff --git a/techniques/general/G151.html b/techniques/general/G151.html index 12cf2aab12..3afbcc689c 100644 --- a/techniques/general/G151.html +++ b/techniques/general/G151.html @@ -5,8 +5,8 @@

      With this technique, a link to the transcript or script is provided and should conform to WCAG 2 and could either be included at another location on the same web page or at another URI.

      Examples

        -
      • A live radio play of a fringe theatre group is being broadcast to the Web. As the actors stick largely to a set script, and the budget for the program is small, the producers provide a link (with the playwright's permission) to the script of the play in HTML.
      • -
      • A member of the government broadcasts an important policy speech on the Web. A transcript of the speech is made available on the website when the speech starts.
      • +
      • A live radio play of a fringe theatre group is being broadcast to the web. As the actors stick largely to a set script, and the budget for the program is small, the producers provide a link (with the playwright's permission) to the script of the play in HTML.
      • +
      • A member of the government broadcasts an important policy speech on the web. A transcript of the speech is made available on the website when the speech starts.

      Tests

      Procedure

      diff --git a/techniques/general/G164.html b/techniques/general/G164.html index 9085af28cb..0598ee8738 100644 --- a/techniques/general/G164.html +++ b/techniques/general/G164.html @@ -2,7 +2,7 @@

      All technologies that provide forms.

      Description

      The objective of this technique is to allow users to recover from errors made when placing an order by providing them with a period of time during which they can cancel or change the order. In general, a contract or an order is a legal commitment and cannot be canceled. However, a website may choose to offer this capability, and it provides a way for users to recover from errors.

      -

      The Web content would need to tell the user how long the cancellation period is after submitting the form and what the procedure would be to cancel the order. The cancellation procedure may not be possible online. It may, for instance, require written notice be sent to an address listed on the web page.

      +

      The web content would need to tell the user how long the cancellation period is after submitting the form and what the procedure would be to cancel the order. The cancellation procedure may not be possible online. It may, for instance, require written notice be sent to an address listed on the web page.

      After submitting the form, the user is informed of the length of the cancellation period and the procedure for canceling the transaction. It's best to provide the cancellation procedure at the same website where the transaction was submitted so that it is as easy to cancel as it was to submit and to accommodate users who may be unable to use other mechanisms. But, if necessary, the cancellation procedure may be provided through some other mechanism or combination of mechanisms as long as it has equivalent cross-disability accessibility. In this case, users are warned prior to submitting the form that they will not be able to cancel their order online.

      Examples

      diff --git a/techniques/general/G171.html b/techniques/general/G171.html index 59f4e3e8e1..07247849d7 100644 --- a/techniques/general/G171.html +++ b/techniques/general/G171.html @@ -1,11 +1,11 @@ Playing sounds only on user request

      Playing sounds only on user request

      ID: G171

      Technology: general

      Type: Technique

      When to Use

      All technologies that can play sound.

      Description

      -

      The intent of this technique is to allow a user to control the use of sounds in Web content. Someone that uses a screen reader may find it very distracting and difficult to listen to their screen reader if there are also sounds coming from Web content. Providing a way to play sounds only upon request will give a user the control needed to listen to any sounds or other audio without interfering with the output from a screen reader.

      +

      The intent of this technique is to allow a user to control the use of sounds in web content. Someone that uses a screen reader may find it very distracting and difficult to listen to their screen reader if there are also sounds coming from web content. Providing a way to play sounds only upon request will give a user the control needed to listen to any sounds or other audio without interfering with the output from a screen reader.

      Examples

      -

      A web page from a grey whale conservation society has a looping background sound of grey whales singing. There are also sounds of water splashing. The sounds do not start automatically. Instead, the Web content provides a link at the top of the page to allow the user to start the sounds manually. The button says "Turn sounds on." After pressing the "turn sounds on" button, the sounds are heard. The user is then presented with an option to "turn sounds off."

      +

      A web page from a grey whale conservation society has a looping background sound of grey whales singing. There are also sounds of water splashing. The sounds do not start automatically. Instead, the web content provides a link at the top of the page to allow the user to start the sounds manually. The button says "Turn sounds on." After pressing the "turn sounds on" button, the sounds are heard. The user is then presented with an option to "turn sounds off."

      diff --git a/techniques/general/G176.html b/techniques/general/G176.html index 49e46bc161..73f8d36e49 100644 --- a/techniques/general/G176.html +++ b/techniques/general/G176.html @@ -1,5 +1,5 @@ Keeping the flashing area small enough

      Keeping the flashing area small enough

      ID: G176

      Technology: general

      Type: Technique

      When to Use

      -

      Appropriate to use for all general Web content including special cases like material that is specifically designed for a display in a foyer.

      +

      Appropriate to use for all general web content including special cases like material that is specifically designed for a display in a foyer.

      Description

      The purpose of this technique is to provide an easy way to pass the success criterion for things that flash, but are small.

      If you have something that flashes @@ -7,7 +7,7 @@ than 3 times in a one second period (so G19 can't be used), but the area that is flashing is less than 25% of 10 degrees of visual field (which represents the central area of vision in the eye), then it would automatically pass.

      The 10 degree of visual field represents the central area of vision in the eye. This area is highly packed with visual sensors. Flashes in this area are transmitted to the visual cortex. For those with photosensitivity, this flashing of activity on the visual cortex can cause seizures. Flashing on other areas of the eye (which have far fewer sensors) has much less effect on the cortex. Hence, the focus on just the 10 degrees of central vision.

        -
      • If the content is for general Web use, you can use +
      • If the content is for general web use, you can use Formula 1: Small Safe Area for Web Content.
      • If the content is for a known display (e.g., in a company foyer) then Formula 2: Small Safe Area for Known Displays diff --git a/techniques/general/G180.html b/techniques/general/G180.html index 1e017573af..8357ad3659 100644 --- a/techniques/general/G180.html +++ b/techniques/general/G180.html @@ -5,7 +5,7 @@

      Examples

      • An airline has an online ticket purchasing application. By default, the application has a 1 minute time limit for each step of the purchase process. At the beginning of the session, a web page includes information that says, "We expect that each step in the purchasing process will take users one minute to complete. Would you like to adjust the time limit?" followed by several radio buttons "1 minute, 2 minutes, 5 minutes, 10 minutes."
      • -
      • A Web based email application automatically logs users out when there has been no activity for 30 minutes. The application includes a preference that allows users to adjust the amount of time to any value.
      • +
      • A web-based email application automatically logs users out when there has been no activity for 30 minutes. The application includes a preference that allows users to adjust the amount of time to any value.

      Tests

      Procedure

      diff --git a/techniques/general/G183.html b/techniques/general/G183.html index b4e7984961..0400e27999 100644 --- a/techniques/general/G183.html +++ b/techniques/general/G183.html @@ -6,12 +6,12 @@

      Colored text when color alone is used to convey information such as words that are links in a paragraph

      Description

      The intent of this technique is to provide a redundant visual cue for users who may not be able to discern a difference in text color. Color (generally defined as a combination of hue, saturation and luminance) is commonly used to indicate words that are links within a paragraph or other block of text. For example, scattered words in text may be hypertext links that are identified only by a difference in color with surrounding text. This technique describes a way to provide a difference in contrast rather than relying on hue.

      -

      To meet success criterion 1.4.1: Use of Color a relative luminance (lightness) difference of 3:1 or greater with the text around can be used. This technique goes beyond the success criterion and asks for visual highlights when the user hovers over each link, such as an underline, a change in font style such as bold or italics, or an increase in font size. Such a hover effect provides confirmation to pointer users that the text is a link, similar to how the link alters its appearance for keyboard users when it receives focus, in order to meet 2.4.7 Focus Visible.

      +

      To meet Success Criterion 1.4.1: Use of Color a relative luminance (lightness) difference of 3:1 or greater with the text around can be used. This technique goes beyond the success criterion and asks for visual highlights when the user hovers over each link, such as an underline, a change in font style such as bold or italics, or an increase in font size. Such a hover effect provides confirmation to pointer users that the text is a link, similar to how the link alters its appearance for keyboard users when it receives focus, in order to meet 2.4.7 Focus Visible.

      While using this technique is sufficient to meet this success criterion, it is not the preferred technique to differentiate link text. This is because links that use the relative luminance of color alone may not be obvious to people with low vision. If there are not a large number of links in the block of text, underlines are recommended for links in blocks of text.

      -

      This technique is about the use of color in addition to luminosity. In this technique, the contrast ratio refers to the contrast between a link and the words around it. In Success Criterion 1.4.3 and 1.4.6, contrast ratio refers to the contrast between a word and its background. The difference is that this technique is about the ability for users to tell the difference (a noticeable difference) between different pieces of text whereas the contrast ratio used in success criterion 1.4.3 and 1.4.6 is about the readability of the text with its background for different color and vision disabilities.

      +

      This technique is about the use of color in addition to luminosity. In this technique, the contrast ratio refers to the contrast between a link and the words around it. In Success Criteria 1.4.3 and 1.4.6, contrast ratio refers to the contrast between a word and its background. The difference is that this technique is about the ability for users to tell the difference (a noticeable difference) between different pieces of text whereas the contrast ratio used in Success Criteria 1.4.3 and 1.4.6 is about the readability of the text with its background for different color and vision disabilities.

      If an author wants to use the color portion of this technique (i.e., using different colors for the words where the colors have sufficient contrast with each other) and the author also wants to conform to SC 1.4.3 (contrast of both words with their backgrounds) the following colors can be used. (e.g., black text in a paragraph on a white background with the links shown as one of the colors in example 1 below.

      -

      If assistive technology or Web browsers at some point all provide an option to underline all links on web pages for users, this could be used instead of an author-provided link highlighting mechanism.

      +

      If assistive technology or web browsers at some point all provide an option to underline all links on web pages for users, this could be used instead of an author-provided link highlighting mechanism.

      Examples

      diff --git a/techniques/general/G190.html b/techniques/general/G190.html index 9dbad064e0..190704f01d 100644 --- a/techniques/general/G190.html +++ b/techniques/general/G190.html @@ -18,14 +18,14 @@

      An image of a historical document

      An animation that is not accessibility supported

      -

      An interactive animation created using a Web technology that is not accessibility supported is displayed on a web page. A link to a conforming alternate version of the animation is adjacent to the non-conforming content.

      +

      An interactive animation created using a web technology that is not accessibility supported is displayed on a web page. A link to a conforming alternate version of the animation is adjacent to the non-conforming content.

      Tests

      Procedure

      For each non-conforming object in a page:

        -
      1. Check to see if there is a non-conforming object on the Web Page.
      2. +
      3. Check to see if there is a non-conforming object on the web page.
      4. Check to see if there is a link to an identifiable conforming version of the object directly after the non-conforming object in the linear reading order.
      5. Check to see if the link goes to a conforming version.
      diff --git a/techniques/general/G199.html b/techniques/general/G199.html index 6ee8730ff7..cb275a1d30 100644 --- a/techniques/general/G199.html +++ b/techniques/general/G199.html @@ -1,7 +1,7 @@ Providing success feedback when data is submitted successfully

      Providing success feedback when data is submitted successfully

      ID: G199

      Technology: general

      Type: Technique

      When to Use

      Content that accepts user data input.

      Description

      -

      The objective of this technique is to reduce the effort required for users to confirm that an action, such as submitting a Web form, was completed successfully. This can be accomplished by providing consistently presented feedback that explicitly indicates success of an action, rather than requiring a user to navigate through content to discover if the action was successful.

      +

      The objective of this technique is to reduce the effort required for users to confirm that an action, such as submitting a web form, was completed successfully. This can be accomplished by providing consistently presented feedback that explicitly indicates success of an action, rather than requiring a user to navigate through content to discover if the action was successful.

      Significant effort can be expended by users who can not easily scan through information to confirm their action (such as that data submitted has been successfully entered into a database, sent to a person, or added to content being edited).

      Examples

        diff --git a/techniques/general/G200.html b/techniques/general/G200.html index 1d2aa617d1..f32e5a7562 100644 --- a/techniques/general/G200.html +++ b/techniques/general/G200.html @@ -1,7 +1,7 @@ Opening new windows and tabs from a link only when necessary

        Opening new windows and tabs from a link only when necessary

        ID: G200

        Technology: general

        Type: Technique

        When to Use

        Pages that open new windows

        Description

        -

        The objective of this technique is to limit the use of links or buttons that open new windows or tabs within Web content. In general, it is better not to open new windows and tabs since they can be disorienting for people, especially people who have difficulty perceiving visual content. However there are some situations where it is preferable from an accessibility perspective to open a new window or tab. Here are two such situations:

        +

        The objective of this technique is to limit the use of links or buttons that open new windows or tabs within web content. In general, it is better not to open new windows and tabs since they can be disorienting for people, especially people who have difficulty perceiving visual content. However there are some situations where it is preferable from an accessibility perspective to open a new window or tab. Here are two such situations:

        1. Opening a page containing context-sensitive information, such as help instructions, or an alternate means of completing a form, such as a calendar-based date picker, will significantly disrupt a multi-step workflow, such as filling in and submitting a form, if the page is opened in the same window or tab.
        2. The user is logged into a secured area of a site, and following a link to a page outside of the secured area would terminate the user's logon. In this case opening external links in an external window allows the user to access such references while keeping their login active in the original window.
        3. diff --git a/techniques/general/G21.html b/techniques/general/G21.html index dc5c0ec830..50aa9d9cfc 100644 --- a/techniques/general/G21.html +++ b/techniques/general/G21.html @@ -8,7 +8,7 @@
        4. Providing a keyboard function to move the focus out of the subset of the content. Be sure to document the feature in an accessible manner within the subset.
        5. If the technology used in the subset of the content natively provides a "move to parent" keyboard command, documenting that command before the user enters the plug-in so they know how to get out again.
      -

      If the author uses a technology that allows users to enter the sub-content with keyboard and does not allow users to exit the sub-content with keyboard by default (i.e., it is not a feature of the Web content technology or its user agents) then, in order to implement this technique the author would either build such a capability into their content or not use the technology.

      +

      If the author uses a technology that allows users to enter the sub-content with keyboard and does not allow users to exit the sub-content with keyboard by default (i.e., it is not a feature of the web content technology or its user agents) then, in order to implement this technique the author would either build such a capability into their content or not use the technology.

      Examples

      • Once a user tabs into an applet, further tabs are handled by the applet preventing the person from tabbing out. However, the applet is designed so that it returns keyboard focus back to the parent window when the person finishes tabbing through the tab sequence in the applet.
      • diff --git a/techniques/general/G225.html b/techniques/general/G225.html index ab84f2dc22..3567aee618 100644 --- a/techniques/general/G225.html +++ b/techniques/general/G225.html @@ -23,7 +23,7 @@

        Description

        Examples

        A product carousel

        -

        The homepage of an online retail website includes several informational sections, some of which feature carousels showcasing highlighted products. These carousels require horizontal scrolling and have a computed height greater than 256 CSS pixels. Each panel is 320 CSS pixels wide, allowing users to see the full width of the card without horizontal scrolling. Consequently, users only need to scroll vertically to view the entire card, ensuring compliance with success criterion 1.4.10 Reflow for that section.

        +

        The homepage of an online retail website includes several informational sections, some of which feature carousels showcasing highlighted products. These carousels require horizontal scrolling and have a computed height greater than 256 CSS pixels. Each panel is 320 CSS pixels wide, allowing users to see the full width of the card without horizontal scrolling. Consequently, users only need to scroll vertically to view the entire card, ensuring compliance with Success Criterion 1.4.10 Reflow for that section.

        Working example: Carousel panels that scroll horizontally are designed to fit within a width of 320 CSS pixels on a vertically scrolling page.

      diff --git a/techniques/general/G55.html b/techniques/general/G55.html index 962eb82ab9..96de670bc4 100644 --- a/techniques/general/G55.html +++ b/techniques/general/G55.html @@ -35,7 +35,7 @@

      Examples

      The word jargon is linked to its definition in the WCAG2 Glossary.

      -

      The word "modulo" is jargon used in Web content about mathematics. A definition for modulo is included within the web page. Each occurrence of the word modulo is linked to its definition.

      +

      The word "modulo" is jargon used in web content about mathematics. A definition for modulo is included within the web page. Each occurrence of the word modulo is linked to its definition.

      A Japanese idiom is linked to its definition. This example uses a link within the page to navigate to the definition of an idiomatic expression.

      diff --git a/techniques/general/G60.html b/techniques/general/G60.html index f2472e354d..d50debc3dd 100644 --- a/techniques/general/G60.html +++ b/techniques/general/G60.html @@ -2,7 +2,7 @@

      Applies to all technologies except those for voice interaction.

      Description

      The purpose of this technique is to allow authors to play a sound on their - Web page but avoid the problem of users not being able to use their screen + web page but avoid the problem of users not being able to use their screen readers due to interference by the content sound. It also allows the author to avoid putting controls on the web page to control the sound - and the problem faced by users with screen readers in finding the control (when unable diff --git a/techniques/general/G61.html b/techniques/general/G61.html index ea3be9a7b2..93fe409133 100644 --- a/techniques/general/G61.html +++ b/techniques/general/G61.html @@ -5,7 +5,7 @@

      Description

      The objective of this technique is to make content easier to use by making the placement of repeated components more predictable. This technique helps - maintain consistent layout or presentation between web pages by presenting components that are repeated in these Web units in the same relative order each time they appear. Other + maintain consistent layout or presentation between web pages by presenting components that are repeated in the set of web pages in the same relative order each time they appear. Other components can be inserted between them, but their relative order is not changed.

      This technique also applies to navigational components that are repeated. diff --git a/techniques/general/G70.html b/techniques/general/G70.html index fb10a855c6..492e0f6bdf 100644 --- a/techniques/general/G70.html +++ b/techniques/general/G70.html @@ -1,7 +1,7 @@ Providing a function to search an online dictionary

      Providing a function to search an online dictionary

      ID: G70

      Technology: general

      Type: Technique

      When to Use

      All technologies

      Description

      -

      The objective of this technique is to provide the definition of words, phrases, jargon, or abbreviation expansions by adding a mechanism to access an on-line dictionary to the web page. This technique uses existing resources on the Web to provide the definition rather than requiring the author to create a glossary or other mechanism within the site. By providing access from within the web page, a user can easily locate the desired definition. This technique can only be used if the online dictionary returns the correct definition.

      +

      The objective of this technique is to provide the definition of words, phrases, jargon, or abbreviation expansions by adding a mechanism to access an on-line dictionary to the web page. This technique uses existing resources on the web to provide the definition rather than requiring the author to create a glossary or other mechanism within the site. By providing access from within the web page, a user can easily locate the desired definition. This technique can only be used if the online dictionary returns the correct definition.

      Examples

      diff --git a/techniques/html/H4.html b/techniques/html/H4.html index 87e61907c2..5eeb81902c 100644 --- a/techniques/html/H4.html +++ b/techniques/html/H4.html @@ -20,7 +20,7 @@ Elements that have a tabindex value higher than zero will receive focus before elements without a tabindex or a tabindex of 0. After all of the elements with a tabindex higher than 0 have received focus, the rest of the - interactive elements are given focus in the order in which they appear in the Web + interactive elements are given focus in the order in which they appear in the web page.

      Examples

      diff --git a/techniques/html/H74.html b/techniques/html/H74.html index 8b6fed2e08..1261a1818c 100644 --- a/techniques/html/H74.html +++ b/techniques/html/H74.html @@ -56,7 +56,7 @@

      Resources

      Do not forget to add a doctype by the W3C Quality Assurance Initiative.
    • - Recommended DTDs to use in your Web document. + Recommended DTDs to use in your web document.
    • HTML - The doctype. diff --git a/techniques/html/H75.html b/techniques/html/H75.html index 4983b0f3f4..9ecee791b8 100644 --- a/techniques/html/H75.html +++ b/techniques/html/H75.html @@ -75,7 +75,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.

    diff --git a/techniques/html/H80.html b/techniques/html/H80.html index 5bc0475e41..f040ef58ce 100644 --- a/techniques/html/H80.html +++ b/techniques/html/H80.html @@ -19,7 +19,7 @@

    When to Use

    Description

    The objective of this technique is to describe the purpose of a link from the context provided by its heading context. The preceding heading provides context for an otherwise - unclear link. The description lets a user distinguish this link from links in the Web + unclear link. The description lets a user distinguish this link from links in the web page that lead to other destinations and helps the user determine whether to follow the link.

    diff --git a/techniques/html/H88.html b/techniques/html/H88.html index aeb39fd16b..ffed520be3 100644 --- a/techniques/html/H88.html +++ b/techniques/html/H88.html @@ -56,7 +56,7 @@

    Related Techniques

  • 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 diff --git a/techniques/html/H94.html b/techniques/html/H94.html index a317820695..791e772b3d 100644 --- a/techniques/html/H94.html +++ b/techniques/html/H94.html @@ -67,7 +67,7 @@

    Resources

    Do not forget to add a doctype by the W3C Quality Assurance Initiative explains what doctypes are and why you should use them.
  • - Recommended DTDs to use in your Web document by the W3C Quality Assurance Initiative is a list of commonly used declarations. + Recommended DTDs to use in your web document by the W3C Quality Assurance Initiative is a list of commonly used declarations.
  • How 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. diff --git a/techniques/html/H95.html b/techniques/html/H95.html index f7ebf97040..aade323f40 100644 --- a/techniques/html/H95.html +++ b/techniques/html/H95.html @@ -85,7 +85,7 @@

    Resources

    imscJS library. imscJS is a JavaScript library for rendering IMSC 1.0.1 and IMSC 1.1 documents to HTML5.
  • - IMSC: subtitles and captioning for the Web. IMSC documentation on Mozilla Developer Network. + IMSC: subtitles and captioning for the web. IMSC documentation on Mozilla Developer Network.
  • WebVTT: The Web Video Text Tracks Format diff --git a/techniques/server-side-script/SVR1.html b/techniques/server-side-script/SVR1.html index 822c312de5..910ffa6b10 100644 --- a/techniques/server-side-script/SVR1.html +++ b/techniques/server-side-script/SVR1.html @@ -80,7 +80,7 @@

    PHP

    Apache

    -

    Developers can configure the Apache Web server to handle redirects, as in the following example.

    +

    Developers can configure the Apache web server to handle redirects, as in the following example.

    redirect 301 /oldUserLogin.jsp http://www.example.com/newUserLogin.do
    diff --git a/techniques/silverlight/SL1.html b/techniques/silverlight/SL1.html index 383da1c4b7..78bd414c7c 100644 --- a/techniques/silverlight/SL1.html +++ b/techniques/silverlight/SL1.html @@ -26,7 +26,7 @@

    Media encoding

    not described in this technique because configuring and encoding audio channels for media formats is a technique for any usage of media in a computer application, not just a Silverlight-specific technique or - a Web technology technique. For more information on one possible procedure + a web technology technique. For more information on one possible procedure for encoding the media in WMV format, see Microsoft Expression Encoder Overview. Often, Silverlight authors will receive the media from a third party, such as a video production facility, and are not directly involved diff --git a/techniques/silverlight/SL22.html b/techniques/silverlight/SL22.html index cca8c0403c..8a67a6341a 100644 --- a/techniques/silverlight/SL22.html +++ b/techniques/silverlight/SL22.html @@ -18,12 +18,12 @@ as any surrounding HTML content.

    Browser zoom is relevant for accessibility and Silverlight because it is likely to be the zoom /scaling feature enabled by the browser - host that Web technology users are the most familiar with as a technique - for increasing the text size in Web content.

    + host that web technology users are the most familiar with as a technique + for increasing the text size in web content.

    Legacy behavior in Silverlight version 2

    Built-in support for browser zoom was introduced as a feature in Silverlight - version 3. Older documents on the Web might describe techniques that + version 3. Older documents on the web might describe techniques that were relevant for Silverlight version 2, where dealing with browser zoom required JavaScript handling of the Resized event, and developers manually applied a ScaleTransform to Silverlight diff --git a/techniques/silverlight/SL27.html b/techniques/silverlight/SL27.html index c06efd7c42..d41aac2e92 100644 --- a/techniques/silverlight/SL27.html +++ b/techniques/silverlight/SL27.html @@ -29,7 +29,7 @@ content. Avoiding this situation is largely a matter of due diligence on the part of a Silverlight application author, OR on the part of the web page author who authors surrounding HTML, in cases where a - web page is embedding Silverlight content or packages that the Web + web page is embedding Silverlight content or packages that the web page's author did not actively develop and is only consuming/embedding.

    The following is a general recommendation that summarizes the detailed discussion in subsequent subheadings:

    @@ -173,7 +173,7 @@

    CultureInfo

    application as a whole. There are advanced techniques whereby worker threads can be run as separate cultures, but that is not discussed here and is not relevant because only the main UI thread has relevance - to Web content accessibility. So, if an application author wants to + to web content accessibility. So, if an application author wants to declare specific language settings for a part (component, region or control) of the Silverlight application, a different Silverlight-specific property Language is used.

    diff --git a/techniques/silverlight/SL4.html b/techniques/silverlight/SL4.html index a9cbfee90f..5fe0ffb0bf 100644 --- a/techniques/silverlight/SL4.html +++ b/techniques/silverlight/SL4.html @@ -13,7 +13,7 @@ of parts can thus treat all Silverlight content as using that HTML Lang-declared language.

    Most assistive technologies that are capable of determining Language - for Web content will use the HTML Lang tag value as the determinant + for web content will use the HTML Lang tag value as the determinant of the language of the page. Assistive technologies would also use HTML Lang tag values for the language of parts. HTML Lang is not specifically reported in accessibility frameworks. Assistive technologies would @@ -59,13 +59,13 @@

    Silverlight runtime language determination

    Examples

    Two Silverlight object tags, each with different HTML - Lang, to support a simple language-translator application as a Web + Lang, to support a simple language-translator application as a web page

    The Visual Studio solution for this example has a total of 4 project components:

      -
    • The Web project that declares the HTML or ASP page that shows +
    • The web project that declares the HTML or ASP page that shows the framework of how the two Silverlight object tags exist on a page. This is where the HTML Lang is actually set.
    • A project for the English user control, a simple TextBox.
    • diff --git a/understanding/20/audio-only-live.html b/understanding/20/audio-only-live.html index 1f4468f060..c44d046efe 100644 --- a/understanding/20/audio-only-live.html +++ b/understanding/20/audio-only-live.html @@ -53,12 +53,12 @@

      Examples of Audio-only (Live)

        -
      • A public relations firm uses web based caption services to cover live events; the +
      • A public relations firm uses web-based caption services to cover live events; the output from the service is incorporated in a sub frame of the web page which includes the streaming audio control.
      • -
      • A live radio play of a fringe theatre group is being broadcast to the Web. As the +
      • A live radio play of a fringe theatre group is being broadcast to the web. As the actors stick largely to a set script, and the budget for the program is small, the producers provide a link (with the playwright's permission) to the script of the play.
      • diff --git a/understanding/20/consistent-navigation.html b/understanding/20/consistent-navigation.html index 72913dd2dd..29612c16b0 100644 --- a/understanding/20/consistent-navigation.html +++ b/understanding/20/consistent-navigation.html @@ -87,7 +87,7 @@

        Examples of Consistent Navigation

        on every page in a website. The link allows users to quickly bypass heading information and navigational content and begin interacting with the main content of a page.
        Skip to navigation link
        -
        Navigational content is consistently located at the end of each page in a set of Web +
        Navigational content is consistently located at the end of each page in a set of web pages. A "skip to navigation" link is consistently located at the beginning of each page so that keyboard users can easily locate it when needed.
        diff --git a/understanding/20/images-of-text-no-exception.html b/understanding/20/images-of-text-no-exception.html index c60a51f667..88e2b91ba5 100644 --- a/understanding/20/images-of-text-no-exception.html +++ b/understanding/20/images-of-text-no-exception.html @@ -123,7 +123,7 @@

        Resources for Images of Text (No Exception)

      • - CSS Web fonts + CSS @ Ten: The Next Big Thing (A List Apart)
      • diff --git a/understanding/20/images-of-text.html b/understanding/20/images-of-text.html index 932554957a..b2dbcce902 100644 --- a/understanding/20/images-of-text.html +++ b/understanding/20/images-of-text.html @@ -133,7 +133,7 @@

        Examples of Images of Text

        Resources for Images of Text

    diff --git a/understanding/20/keyboard.html b/understanding/20/keyboard.html index d8b8963432..3414cfb94c 100644 --- a/understanding/20/keyboard.html +++ b/understanding/20/keyboard.html @@ -138,7 +138,7 @@

    Examples of Keyboard

    of the simulator is to teach real-time behavior of a model helicopter.
    Example 6: A PDA with an optional keyboard
    A PDA device that is usually operated via a stylus has an optional keyboard that can - be attached. The keyboard allows full web browsing in standard fashion. The Web + be attached. The keyboard allows full web browsing in standard fashion. The web content is operable because it was designed to work with keyboard-only access.
    Example 7: Simple search form with pointer-operable submit button
    A search form includes a text input field followed by a submit button. The submit button itself diff --git a/understanding/20/link-purpose-link-only.html b/understanding/20/link-purpose-link-only.html index 7d0463b1dd..51d53308b0 100644 --- a/understanding/20/link-purpose-link-only.html +++ b/understanding/20/link-purpose-link-only.html @@ -87,7 +87,7 @@

    Benefits of Link Purpose (Link Only)

      -
    • This success criterion helps people with motion impairment by letting them skip Web +
    • This success criterion helps people with motion impairment by letting them skip web pages that they are not interested in, avoiding the keystrokes needed to visit the referenced content and then return to the current content.
    • diff --git a/understanding/20/multiple-ways.html b/understanding/20/multiple-ways.html index 041068d101..addac3dcb6 100644 --- a/understanding/20/multiple-ways.html +++ b/understanding/20/multiple-ways.html @@ -47,7 +47,7 @@

      Benefits of Multiple Ways

      large navigation bar using a screen magnifier or screen reader. A person with cognitive disabilities may prefer a table of contents or site map that provides an overview of the site rather than reading and traversing through several web pages. Some users - may prefer to explore the site in a sequential manner, moving from web page to Web + may prefer to explore the site in a sequential manner, moving from web page to web page in order to best understand the concepts and layout. @@ -75,7 +75,7 @@

      Examples of Multiple Ways

      or backward through the web pages. In addition, each web page contains a list of links to reach each of the other web pages.
    Where content is a result of a process or task - Funds transfer confirmation
    -
    An on-line banking site allows fund transfer between accounts via the Web. There is +
    An on-line banking site allows fund transfer between accounts via the web. There is no other way to locate the confirmation of fund transfer until the account owner completes the transfer.
    Where content is a result of a process or task - Search engine results
    diff --git a/understanding/20/no-keyboard-trap.html b/understanding/20/no-keyboard-trap.html index 541938c8b9..dbc294b718 100644 --- a/understanding/20/no-keyboard-trap.html +++ b/understanding/20/no-keyboard-trap.html @@ -41,7 +41,7 @@

    Benefits of No Keyboard Trap

      -
    • People who rely on a keyboard or keyboard interface to use the Web including people +
    • People who rely on a keyboard or keyboard interface to use the web including people who are blind and people with physical disabilities.
    • @@ -55,7 +55,7 @@

      Examples of No Keyboard Trap

      A calendar widget
      A calendar widget allows users to add, remove or update items in their calendar using - the keyboard. The controls in the widget are part of the tab order within the Web + the keyboard. The controls in the widget are part of the tab order within the web page, allowing users to tab through the controls in the widget as well as to any links or controls that follow.
      A puzzle applet
      diff --git a/understanding/20/non-text-content.html b/understanding/20/non-text-content.html index cfd8a41a52..118bd9d2e1 100644 --- a/understanding/20/non-text-content.html +++ b/understanding/20/non-text-content.html @@ -757,7 +757,7 @@

      Situation E: If non-text content is a CAPTCHA:

      AND - Ensuring that the Web Page contains another CAPTCHA serving the same purpose using + Ensuring that the web page contains another CAPTCHA serving the same purpose using a different modality diff --git a/understanding/20/section-headings.html b/understanding/20/section-headings.html index e82c47db07..18806569af 100644 --- a/understanding/20/section-headings.html +++ b/understanding/20/section-headings.html @@ -22,7 +22,7 @@

      In brief

      Intent of Section Headings

      -

      The intent of this success criterion is to provide headings for sections of a Web +

      The intent of this success criterion is to provide headings for sections of a web page, when the page is organized into sections. For instance, long documents are often divided into a variety of chapters, chapters have subtopics, etc. When such sections exist, they need to have headings that introduce them. This clearly indicates the organization @@ -34,7 +34,7 @@

      Intent of Section Headings

      This provision is included at Level AAA because it cannot be applied to all types of content and it may not always be possible to insert headings. For example, when - posting a pre-existing document to the Web, headings that an author did not include + posting a pre-existing document to the web, headings that an author did not include in the original document cannot be inserted. Or, a long letter would often cover different topics, but putting headings into a letter would be very strange. However, if a document can be broken up into sections with headings, it facilitates both understanding and diff --git a/understanding/20/sign-language-prerecorded.html b/understanding/20/sign-language-prerecorded.html index 0939c00928..4d4252bcf0 100644 --- a/understanding/20/sign-language-prerecorded.html +++ b/understanding/20/sign-language-prerecorded.html @@ -61,8 +61,8 @@

      Examples of Sign Language (Prerecorded)

    • Example 1. A corporation is making an important announcement to all of its employees. The announcement - will be held in the main headquarters and later streamed to the Web. A sign language interpreter - is provided at the announcement location for the employees that are present in the meeting room. For the Web version of + will be held in the main headquarters and later streamed to the web. A sign language interpreter + is provided at the announcement location for the employees that are present in the meeting room. For the web version of the announcement, the sign language interpreter is shown/superimposed in the corner of the display.
    • diff --git a/understanding/20/timing-adjustable.html b/understanding/20/timing-adjustable.html index cf437542a3..59084bd971 100644 --- a/understanding/20/timing-adjustable.html +++ b/understanding/20/timing-adjustable.html @@ -26,7 +26,7 @@

      Intent of Timing Adjustable

      given adequate time to interact with web content whenever possible. People with disabilities such as blindness, low vision, dexterity impairments, and cognitive limitations may require more time to read content or to perform functions such as filling out on-line - forms. If Web functions are time-dependent, it will be difficult for some users to + forms. If web functions are time-dependent, it will be difficult for some users to perform the required action before a time limit occurs. This may render the service inaccessible to them. Designing functions that are not time-dependent will help people with disabilities succeed at completing these functions. Providing options to disable diff --git a/understanding/20/understanding-metadata.html b/understanding/20/understanding-metadata.html index 550d2a5f38..8c483a1c09 100644 --- a/understanding/20/understanding-metadata.html +++ b/understanding/20/understanding-metadata.html @@ -16,7 +16,7 @@

      Understanding Metadata

      both describe and find resources.

      -

      Metadata is a powerful tool that can be used for describing Web pages and accessible +

      Metadata is a powerful tool that can be used for describing web pages and accessible components of web pages as well as associating alternate versions of web content to each other. These descriptions in turn allows users to locate specific information they need or prefer. diff --git a/understanding/21/reflow.html b/understanding/21/reflow.html index 3aee7b84ed..fb8833e66f 100644 --- a/understanding/21/reflow.html +++ b/understanding/21/reflow.html @@ -355,7 +355,7 @@

      Resources

    • Operational Overhead Caused by Horizontal Scrolling Text by Wayne Dick, 2017. The study shows the impact of horizontal scrolling on reading effort
    • Accessibility Requirements for People with Low Vision. W3C First Public Working Draft 17 March 2016
    • -
    • Responsive design resources from MDN Web docs
    • +
    • Responsive design resources from MDN web docs
    • Responsive web design basics tutorial from Google
    @@ -389,7 +389,7 @@

    Advisory Techniques

    Failures

  • diff --git a/understanding/conformance.html b/understanding/conformance.html index 1ed27e16fb..1732610221 100644 --- a/understanding/conformance.html +++ b/understanding/conformance.html @@ -11,7 +11,7 @@

    Understanding Conformance

    All WCAG 2 success criteria are written as testable criteria for objectively determining if content satisfies them. Testing the success criteria would involve a combination of automated testing and human evaluation. The content should be tested by those who - understand how people with different types of disabilities use the Web. + understand how people with different types of disabilities use the web.

    Testing and testable in the context refer to functional testing, that is verifying @@ -887,7 +887,7 @@

    "Accessibility Supported" vs. "Programmatically Determined"

    user agents (browsers and players etc.).

    -

    "Programmatically determined" relates to the information in Web Content. If technologies +

    "Programmatically determined" relates to the information in web content. If technologies that are accessibility supported are used properly, then assistive technologies and user agents can access the information in the content (i.e., programmatically determine the information in the content) and present it to the user. @@ -1200,18 +1200,18 @@

    Examples of Conforming Alternate Versions

    -

    Understanding "Web Page"

    +

    Understanding "web page"

    -

    The definition of a Web Page is:

    +

    The definition of a web page is:

    web page

    It is important to note that, in this standard, the term "web page" includes much - more than static HTML pages. The term 'Web Page' was used in these guidelines to allow + more than static HTML pages. The term 'web page' was used in these guidelines to allow the guidelines to be more understandable. But the term has grown in meaning with advancing technologies to encompass a wide range of technologies, many of which are not at all 'page-like'. It also includes the increasingly dynamic web pages that are emerging - on the Web, including "pages" that can present entire virtual interactive communities. + on the web, including "pages" that can present entire virtual interactive communities. For example, the term "web page" would include an immersive interactive movie-like experience that you find at a single URI.

    diff --git a/understanding/intro.html b/understanding/intro.html index 4c4554c1bf..f383b1e3ec 100644 --- a/understanding/intro.html +++ b/understanding/intro.html @@ -78,7 +78,7 @@

    Understanding the Four Principles of Accessibility

    -

    If any of these are not true, users with disabilities will not be able to use the Web.

    +

    If any of these are not true, users with disabilities will not be able to use the web.

    Under each of the principles are guidelines and success criteria that help to address these principles for people with disabilities. There are many general usability guidelines that make content more usable by all people, including those with disabilities. However, in WCAG {{ versionDecimal }}, we only include those guidelines that address problems particular to people with disabilities. This includes issues that block access or interfere with access to the web more severely for people with disabilities.

    @@ -92,7 +92,7 @@

    Success Criteria

    Under each guideline, there are success criteria that describe specifically what must be achieved in order to conform to this standard. They are similar to the "checkpoints" in WCAG 1.0. Each success criterion is written as a statement that will be either true or false when specific web content is tested against it. The success criteria are written to be technology neutral.

    All WCAG {{ versionDecimal }} success criteria are written as testable criteria for objectively determining if content satisfies the success criteria. While some of the testing can be automated using software evaluation programs, others require human testers for part or all of the test.

    Although content may satisfy the success criteria, the content may not always be usable by people with a wide variety of disabilities. Professional reviews utilizing recognized qualitative heuristics are important in achieving accessibility for some audiences. In addition, usability testing is recommended. Usability testing aims to determine how well people can use the content for its intended purpose.

    -

    The content should be tested by those who understand how people with different types of disabilities use the Web. It is recommended that users with disabilities be included in test groups when performing human testing.

    +

    The content should be tested by those who understand how people with different types of disabilities use the web. It is recommended that users with disabilities be included in test groups when performing human testing.

    Each success criterion for a guideline has a link to the section of the How to Meet document that provides: