diff --git a/guidelines/index.html b/guidelines/index.html
index d2717ac5a3..3e8c68329f 100644
--- a/guidelines/index.html
+++ b/guidelines/index.html
@@ -15,7 +15,7 @@
Web Content Accessibility Guidelines (WCAG) 2.2 covers a wide range of recommendations for making web content more accessible. Following these guidelines will make content more accessible to a wider range of people with disabilities, including accommodations for blindness and low vision, deafness and hearing loss, limited movement, speech disabilities, photosensitivity, and combinations of these, and some accommodation for learning disabilities and cognitive limitations; but will not address every user need for people with these disabilities. These guidelines address accessibility of web content on any kind of device (including desktops, laptops, kiosks, and mobile devices). Following these guidelines will also often make web content more usable to users in general. WCAG 2.2 success criteria are written as testable statements that are not technology-specific. Guidance about satisfying the success criteria in specific technologies, as well as general information about interpreting the success criteria, is provided in separate documents. See Web Content Accessibility Guidelines (WCAG) Overview for an introduction and links to WCAG technical and educational material. WCAG 2.2 extends Web Content Accessibility Guidelines 2.1 [[WCAG21]], which was published as a W3C Recommendation June 2018. Content that conforms to WCAG 2.2 also conforms to WCAG 2.0 and WCAG 2.1. The WG intends that for policies requiring conformance to WCAG 2.0 or WCAG 2.1, WCAG 2.2 can provide an alternate means of conformance. The publication of WCAG 2.2 does not deprecate or supersede WCAG 2.0 or WCAG 2.1. While WCAG 2.0 and WCAG 2.1 remain W3C Recommendations, the W3C advises the use of WCAG 2.2 to maximize future applicability of accessibility efforts. The W3C also encourages use of the most current version of WCAG when developing or updating web accessibility policies. WCAG 2.2 extends Web Content Accessibility Guidelines 2.1 [[WCAG21]], which was published as a W3C Recommendation June 2018. Content that conforms to WCAG 2.2 also conforms to WCAG 2.0 and WCAG 2.1. The WG intends that for policies requiring conformance to WCAG 2.0 or WCAG 2.1, WCAG 2.2 can provide an alternative means of conformance. The publication of WCAG 2.2 does not deprecate or supersede WCAG 2.0 or WCAG 2.1. While WCAG 2.0 and WCAG 2.1 remain W3C Recommendations, the W3C advises the use of WCAG 2.2 to maximize future applicability of accessibility efforts. The W3C also encourages use of the most current version of WCAG when developing or updating web accessibility policies. The alternate version does not need to be matched page for page with the original
+ The alternative version does not need to be matched page for page with the original
(e.g., the conforming alternate version may consist of multiple pages).
Alternate versions may be provided to accommodate different technology environments +
Alternative versions may be provided to accommodate different technology environments or user groups. Each version should be as conformant as possible. One version would need to be fully conformant in order to meet conformance requirement 1.
-The conforming alternative version does not need to reside within the scope of conformance, +
The conforming alternate version does not need to reside within the scope of conformance, or even on the same website, as long as it is as freely available as the non-conforming version.
-Alternate versions should not be confused with supplementary content, which support the original page and enhance comprehension. +
Alternative versions should not be confused with supplementary content, which support the original page and enhance comprehension.
Setting user preferences within the content to produce a conforming version is an diff --git a/guidelines/terms/20/media-alternative-for-text.html b/guidelines/terms/20/media-alternative-for-text.html index e1adab92ab..8b7f0f63d5 100644 --- a/guidelines/terms/20/media-alternative-for-text.html +++ b/guidelines/terms/20/media-alternative-for-text.html @@ -5,7 +5,7 @@ or via text alternatives)
-A media alternative for text is provided for those who benefit from alternate representations +
A media alternative for text is provided for those who benefit from alternative representations of text. Media alternatives for text may be audio-only, video-only (including sign-language video), or audio-video.
diff --git a/techniques/client-side-script/SCR38.html b/techniques/client-side-script/SCR38.html index 2400dfcaa5..026fdd382c 100644 --- a/techniques/client-side-script/SCR38.html +++ b/techniques/client-side-script/SCR38.html @@ -18,10 +18,10 @@This objective of this technique is to offer a conforming alternate version for a web page designed with progressive enhancement. The technique demonstrates how to use a scripting technique to accomplish this by:
Web pages designed with progressive enhancement detect features in the web-enabled accessing device (size, capability and software) to allow those supported web technologies to be applied in layers on top of an HTML foundation. The basic content and functionality of such a web page are available through the HTML foundation to anyone using a more simple web-enabled accessing device, whilst enhanced versions of the page are created to suit the different features in more advanced accessing devices.
-The current guidance for web pages delivered in alternate versions reads: "Note 4: Alternate versions may be provided to accommodate different technology environments or user groups. Each version should be as conformant as possible. One version would need to be fully conformant in order to meet conformance requirement 1." With regard to web pages designed with progressive enhancement this leaves the problem of which version to select as the one fully conformant version - all whilst trying to ensure that no set of users is disadvantaged by that choice.
+The current guidance for web pages delivered in alternative versions reads: "Note 4: Alternative versions may be provided to accommodate different technology environments or user groups. Each version should be as conformant as possible. One version would need to be fully conformant in order to meet conformance requirement 1." With regard to web pages designed with progressive enhancement this leaves the problem of which version to select as the one fully conformant version - all whilst trying to ensure that no set of users is disadvantaged by that choice.
One solution to this challenge is to select the pre-enhanced version of the web page (e.g. the DOM state created solely from the HTML in the source code in the absence of support for scripts, styles or non-HTML plugins) as the "fully conformant version", due to its broad reach, with regard to support, across all the possible web-enabled devices accessing the content.
This technique removes all scripts, styles, and plugins, but it is important to state that this is not required for conformance with WCAG 2.x. An author could use a similar technique, but retain a reduced set of styles and scripts in the "pre-enhanced" version.
While this technique offers a way to base conformance claims on a single version, authors should continue to work to ensure that each enhanced version of the web page is as conformant as possible.
@@ -122,7 +122,7 @@When some aspect of the default presentation of a web page does not meet a Success Criterion, it is possible to meet that requirement using the "Alternate Version" clause in the conformance requirements (Conformance Requirement 1). For some requirements, invoking a style switcher via a link or control on the page that can adjust the presentation so that all aspects of the page conform at the level claimed allows authors to avoid having to provide multiple versions of the same information.
+When some aspect of the default presentation of a web page does not meet a Success Criterion, it is possible to meet that requirement using the "Alternative Version" clause in the conformance requirements (Conformance Requirement 1). For some requirements, invoking a style switcher via a link or control on the page that can adjust the presentation so that all aspects of the page conform at the level claimed allows authors to avoid having to provide multiple versions of the same information.
The objective of this technique is to demonstrate how CSS can be used in combination with scripting to provide conforming alternate versions of a web page. In this technique, an author provides alternative views of the content by providing controls that adjust the CSS that is used to control the visual presentation of content. Controls provided within the web page allow users to select or modify the presentation in a way that meets the success criterion at the level claimed. This makes it possible for different visual presentations to be selected by users in situations such as the following:
For this technique to be used successfully, three things must be true.
When using a style switcher, it is important to consider the following challenges and limitations:
The objective of this technique is to demonstrate how CSS can be used to replace structured HTML text with images of text in a way that makes it possible for users to view content according to their preferences. To use this technique, an author starts by creating an HTML page that uses semantic elements to mark up the structure of the page. The author then designs two or more stylesheets for that page. One stylesheet presents the HTML text as text and the second uses CSS features to replace some of the HTML text with images of text. Finally, through the use of server-side or client-side scripting, the author provides a control that allows the user to switch between the available views.
-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.
+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 alternative 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.
@@ -92,7 +92,7 @@Sites that provide alternative, WCAG-conforming versions of nonconforming primary content.
This failure technique describes the situation in which an alternate, conforming version of the content is provided, but there is no direct way for a user to tell that it is available or where to find it. Such content fails the success criterion because the user cannot find the conforming version.
+This failure technique describes the situation in which an alternative, conforming version of the content is provided, but there is no direct way for a user to tell that it is available or where to find it. Such content fails the success criterion because the user cannot find the conforming version.
Embedding information into a background image can also cause problems for people who use alternate backgrounds in order to increase legibility and for users of high contrast mode in some operating systems. These users, would lose the information in the background image due to lack of any alternative text.
+Embedding information into a background image can also cause problems for people who use alternative backgrounds in order to increase legibility and for users of high contrast mode in some operating systems. These users, would lose the information in the background image due to lack of any alternative text.
alt
attrib
text value of "spacer". This image fails the Success Criterion
because the text alternative does not serve an equivalent purpose.
The image is meant to be ignored but its alternative text "spacer" is
- announced by screen readers and displayed in some alternate color schemes.
+ announced by screen readers and displayed in some alternative color schemes.
<div>
Tree type: <img src="spacer.gif" width="100" height="1" alt="spacer">
Cedrus deodara
diff --git a/techniques/failures/F54.html b/techniques/failures/F54.html
index 30b89d39b5..8bffb20b0b 100644
--- a/techniques/failures/F54.html
+++ b/techniques/failures/F54.html
@@ -10,7 +10,7 @@
When pointing device-specific event handlers are the only mechanism available
to invoke a function of the content, users with no vision (who cannot use
devices such as mice that require eye-hand coordination) as well as users
- who must use alternate keyboards or input devices that act as keyboard
+ who must use alternative keyboards or input devices that act as keyboard
emulators will be unable to access the function of the content.
For Success Criterion 2.1.1 there is an exception for functions that require a path-dependant pointer movement.
diff --git a/techniques/failures/F67.html b/techniques/failures/F67.html
index 56cb1c81ea..b77d7fd66c 100644
--- a/techniques/failures/F67.html
+++ b/techniques/failures/F67.html
@@ -5,7 +5,7 @@
All technologies
This objective of this technique is to describe the failure that occurs when a required field or an error field is marked with color differences only, without an alternate way to identify the required field or error field. This can cause problems for people who are blind or colorblind, because they may not be able to perceive the color differences that indicate which field is required or which field is causing an error.
+This objective of this technique is to describe the failure that occurs when a required field or an error field is marked with color differences only, without an alternative way to identify the required field or error field. This can cause problems for people who are blind or colorblind, because they may not be able to perceive the color differences that indicate which field is required or which field is causing an error.
The objective of this technique is to allow assistive technology to understand Web content so that it can convey equivalent information to the - user through an alternate user interface.
+ user through an alternative user interface.Sometimes content is not created using markup language but rather using a
programming language or tools. In many cases, these technologies have
interface components that are already programmed to interface with
diff --git a/techniques/general/G100.html b/techniques/general/G100.html
index 23328c3cbe..40abaf6f34 100644
--- a/techniques/general/G100.html
+++ b/techniques/general/G100.html
@@ -11,8 +11,8 @@
The objective of this technique is to allow assistive technology to
understand Web content so that it can convey equivalent information to the
- user through an alternate user interface and allow them to operate controls
+ user through an alternative user interface and allow them to operate controls
through the AT. This technique involves using standard, documented and supported features to
expose these properties to AT. It relies on the fact that these standard
diff --git a/techniques/general/G117.html b/techniques/general/G117.html
index 1449e35334..a0d9d54651 100644
--- a/techniques/general/G117.html
+++ b/techniques/general/G117.html
@@ -42,7 +42,7 @@ An on-line test requires students to write a short summary of a longer document. The summary must contain certain words from the original document. When a sentence in the original document contains a word or phrase that must be used in the summary, the word or phrase is shown in a different font than the rest of the sentence. A separate section also lists all the words and phrases that must be used in the summary.
-
diff --git a/techniques/general/G108.html b/techniques/general/G108.html
index 4f5f5ac940..b291c4e8ac 100644
--- a/techniques/general/G108.html
+++ b/techniques/general/G108.html
@@ -5,7 +5,7 @@
Description
Font variations and explicit statements.
Providing an alternate way to know which words in the text have been identified by using a different font.
+ Providing an alternative way to know which words in the text have been identified by using a different font.
The objective of this technique is to allow assistive technology to understand Web content so that it can convey equivalent information to the - user through an alternate user interface.
+ user through an alternative user interface.Sometimes content is not created using markup language but rather using a programming language or tools. In many cases, these technologies have interface components that are already programmed to interface with diff --git a/techniques/general/G136.html b/techniques/general/G136.html index 678b7a4988..23f841707f 100644 --- a/techniques/general/G136.html +++ b/techniques/general/G136.html @@ -1,19 +1,19 @@
Primary content does not conform to WCAG but alternate versions exist that do conform to WCAG. This technique can only be used if a technology makes it possible to create an accessible link to an alternate version.
+Primary content does not conform to WCAG but alternative versions exist that do conform to WCAG. This technique can only be used if a technology makes it possible to create an accessible link to an alternative version.
The objective of this technique is to enable users to access alternate content that conforms to WCAG if the primary content, or the default content that users encounter when visiting a particular URI, does not conform. The alternate page, or conforming alternate version, may make some design or functionality compromises in order to conform, but must meet the requirements described in the definition in order to be a conforming alternate version. The definition of "conforming alternate version" is:
+The objective of this technique is to enable users to access alternative content that conforms to WCAG if the primary content, or the default content that users encounter when visiting a particular URI, does not conform. The alternative page, or conforming alternate version, may make some design or functionality compromises in order to conform, but must meet the requirements described in the definition in order to be a conforming alternate version. The definition of "conforming alternate version" is:
-When using this techique, placing a WCAG-conforming link to alternate content at the top of the page allows users to find the link quickly and to move to the conforming alternate version. To ensure users can always find the alternate version, regardless of where they enter the site, each page that does not conform at the specified level would include a link to the conforming alternate version.
+When using this techique, placing a WCAG-conforming link to alternative content at the top of the page allows users to find the link quickly and to move to the conforming alternate version. To ensure users can always find the alternative version, regardless of where they enter the site, each page that does not conform at the specified level would include a link to the conforming alternate version.
The purpose of this technique is to provide information via the text alternative that identifies the non-text content as a CAPTCHA. Such tests often involve asking the user to type in text that is presented in an obscured image or audio file. From the text alternative, the user can tell that the CAPTCHA requires completing a task and what type of task it is.
-When an alternate version of a CAPTCHA is available, the text alternative should include instructions about how to find the alternate version.
+When an alternative version of a CAPTCHA is available, the text alternative should include instructions about how to find the alternative version.
Applies to all technologies.
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.
+The purpose of this technique is to reduce occasions in which a user with a disability cannot complete a CAPTCHA task. Because there are alternative CAPTCHA tasks that use different modalities, a user is more likely to be able to complete one of the tasks successfully.
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 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 "Alternative 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:
This technique can be used to meet Success Criterion 1.4.3 by having text (or images of text) on the alternate version of the page be 4.5:1 contrast and any large text (or images of large text) be 3:1 contrast with its background. If the alternate version of the page has all text (or images of text) with 7:1 contrast and large text (or images of large text) with 4.5:1 contrast then it would satisfy both Success Criterion 1.4.3 and 1.4.6.
+This technique can be used to meet Success Criterion 1.4.3 by having text (or images of text) on the alternative version of the page be 4.5:1 contrast and any large text (or images of large text) be 3:1 contrast with its background. If the alternative version of the page has all text (or images of text) with 7:1 contrast and large text (or images of large text) with 4.5:1 contrast then it would satisfy both Success Criterion 1.4.3 and 1.4.6.
This technique can be used in combination with a style switching technique to present a page that is a
conforming alternate version
@@ -29,9 +29,9 @@
The objective of this technique is to provide the user with a control near the beginning of the page that takes the user to a conforming alternate version of the web page where the link text alone of each link is sufficient to determine its purpose out of context. Some users prefer to have links that are self-contained, where there is no need to explore the context of the link. Other users find including the context information in each link to be repetitive and to reduce their ability to use a site. Among users of assistive technology, the feedback to the working group on which is preferable has been divided. This technique allows users to pick the approach that works best for them. Users who need or prefer potentially longer but complete link text use this version. 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. If the control for switching to the alternative 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 alternative 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. A web page lists books for download in different formats. Alternate versions of the web page use just the book format as the link text or the book title and format type. A web page lists books for download in different formats. Alternative versions of the web page use just the book format as the link text or the book title and format type. Version with short link text: 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
- 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.Tests
Procedure
-
Expected Results
diff --git a/techniques/general/G178.html b/techniques/general/G178.html
index 16df72c5c6..fac508c436 100644
--- a/techniques/general/G178.html
+++ b/techniques/general/G178.html
@@ -12,7 +12,7 @@
Examples
diff --git a/techniques/general/G189.html b/techniques/general/G189.html
index f8417c6072..d0df48a195 100644
--- a/techniques/general/G189.html
+++ b/techniques/general/G189.html
@@ -19,8 +19,8 @@ alt
text on each button.When to Use
Description
Description
Examples
Providing a Link to another Version
- <h1>Books for download</h1>
<p><a href="books-full-links.html">Full link Version</a></p>
diff --git a/techniques/general/G191.html b/techniques/general/G191.html
index 0b4214da7b..380383fcb6 100644
--- a/techniques/general/G191.html
+++ b/techniques/general/G191.html
@@ -3,7 +3,7 @@
Description
It is important that the page without blinking content contain all of the information that was on the page with blinking content.
Removing the content that was blinking from the page would only be satisfactory if the blinking content was redundant with non blinking content in the original page.
diff --git a/techniques/general/G200.html b/techniques/general/G200.html index 1d2aa617d1..c89f18d720 100644 --- a/techniques/general/G200.html +++ b/techniques/general/G200.html @@ -3,7 +3,7 @@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:
It is recommended that when links are opened to a new window, there is advance warning.
diff --git a/techniques/general/G202.html b/techniques/general/G202.html index 59e16ae2de..82c5619bce 100644 --- a/techniques/general/G202.html +++ b/techniques/general/G202.html @@ -1,7 +1,7 @@All technologies that support interactive operation.
The objective of this technique is to provide keyboard operation for all the functionality of the page. When all functionality of content can be operated through a keyboard or keyboard interface, it can be operated by those with no vision as well as by those who must use alternate keyboards or input devices that act as keyboard emulators like speech input software or on-screen keyboards.
+The objective of this technique is to provide keyboard operation for all the functionality of the page. When all functionality of content can be operated through a keyboard or keyboard interface, it can be operated by those with no vision as well as by those who must use alternative keyboards or input devices that act as keyboard emulators like speech input software or on-screen keyboards.
A keyboard interface allows users to provide keystroke input to programs even if the computing device that they are using does not contain a hardware keyboard. For example, many mobile devices have keyboard interfaces within their operating system as well the option to connect external wireless keyboards. Applications can use the interface to obtain keyboard input either from an external keyboard or from other services that provide simulated keyboard output, such as switch devices, handwriting interpreters or speech-to-text applications.
To implement this technique, first determine what functionality is available to users on the page. In this step, it is important to consider functions performed using both the mouse and the keyboard together. Examples of functionality include the use of physical controls such as links, menus, buttons, checkboxes, radio buttons and form fields as well as the use of features like drag and drop, selecting text, resizing regions or bringing up context menus. Other examples of functionality may based on tasks such as adding or removing an item from a shopping cart or initiating a chat session with a sales representative.
Once the functionality of the content has been determined, the author verifies that each of the functions identified can be performed using only the keyboard.
diff --git a/techniques/general/G69.html b/techniques/general/G69.html index ed2d3d0b97..18730f98e3 100644 --- a/techniques/general/G69.html +++ b/techniques/general/G69.html @@ -27,7 +27,7 @@The short text alternative says "October sales chart for top three salespeople."
Immediately after the non-text content is a small image denoting a - long description. The alternate text for the image is "Long + long description. The alternative text for the image is "Long description of chart". The image links to the bottom of the page where there is a section titled "Description of charts on this page". The link points to this specific description: "Sales for @@ -48,7 +48,7 @@
The short text alternative says "October sales chart for top three salespeople."
Immediately after the non-text content is a small image denoting the - long description. The alternate text for the image is "Long + long description. The alternative text for the image is "Long description of chart". The image links to another page titled "Description of charts in October Sales Report". The description link points to this specific description: "Sales for October show diff --git a/techniques/general/G78.html b/techniques/general/G78.html index 78fdc062c8..1960073974 100644 --- a/techniques/general/G78.html +++ b/techniques/general/G78.html @@ -4,7 +4,7 @@
The objective of this technique is to provide an audio (spoken) version of information that is provided visually so that it is possible for people who cannot see to be able to understand audio-visual material.
Since most user agents today cannot merge multiple sound tracks, this technique adds the additional audio information to synchronized media by providing an option which allows users to replace the soundtrack with a new copy of the original soundtrack that has the additional audio description added in the same human language. This added information focuses on actions, characters, scene changes and on-screen text (not captions) that are important to understanding the content.
Since it is not helpful to have this new information obscure key audio information in the original sound track (or be obscured by loud sound effects), the new information is added during pauses in dialogue and sound effects. This limits the amount of supplementary information that can be added to the program.
-The soundtrack with the audio description (of visual information) can either be an alternate sound track that the user can choose, or it can be the standard sound track that everyone hears.
+The soundtrack with the audio description (of visual information) can either be an alternative sound track that the user can choose, or it can be the standard sound track that everyone hears.
The objective of this technique is to provide a second version of video content that provides extended audio descriptions in the same human language as the video. One of the difficult things about creating traditional audio descriptions is that the narrator sometimes has to provide a lot of information during very short pauses in dialogue. Extended audio description temporarily pauses the audio and video to allow critical information to be delivered when pauses in dialogue are insufficient for adequate description.
Providing a second version of the movie with extended audio descriptions will make this content accessible for blind people who need to hear not only the dialogue but also the context and other aspects of the video that are not communicated by the characters' dialogue alone, and for which there is insufficient time during the natural dialogue.
-Because it disrupts viewing for those who do not need the additional description, techniques that allow you to turn the feature on and off are often provided. Alternately, versions with and without the additional description can be provided.
+Because it disrupts viewing for those who do not need the additional description, techniques that allow you to turn the feature on and off are often provided. Alternatively, versions with and without the additional description can be provided.
An alternate version of an online video of a family escaping from a burning building: there is a continuous dialogue between the husband and wife about where the children are. Meanwhile, in the background, a wall caves in. This is important information in the story because it will block their exit from that part of the building. The video track halts (same frame is repeated) while a narrator gives the details about the wall falling and the video continues.
+An alternative version of an online video of a family escaping from a burning building: there is a continuous dialogue between the husband and wife about where the children are. Meanwhile, in the background, a wall caves in. This is important information in the story because it will block their exit from that part of the building. The video track halts (same frame is repeated) while a narrator gives the details about the wall falling and the video continues.
A training film has narrative that runs almost continuously throughout. An alternate version is available for people who have difficulty viewing the video portion. The alternate version freezes the video and provides audio description of key information.
+A training film has narrative that runs almost continuously throughout. An alternative version is available for people who have difficulty viewing the video portion. The alternative version freezes the video and provides audio description of key information.
The objective of this technique is to use HTML heading markup to provide semantic code for headings in the content. Heading markup will allow assistive technologies to present the heading status of text to a user. A screen reader can recognize the code and announce the text as a heading with its level, beep or provide some other auditory indicator. Screen readers are also able to navigate heading markup which can be an effective way for screen reader users to more quickly find the content of interest. Assistive technologies that alter the authored visual display will also be able to provide an appropriate alternate visual display for headings that can be identified by heading markup.
+The objective of this technique is to use HTML heading markup to provide semantic code for headings in the content. Heading markup will allow assistive technologies to present the heading status of text to a user. A screen reader can recognize the code and announce the text as a heading with its level, beep or provide some other auditory indicator. Screen readers are also able to navigate heading markup which can be an effective way for screen reader users to more quickly find the content of interest. Assistive technologies that alter the authored visual display will also be able to provide an appropriate alternative visual display for headings that can be identified by heading markup.
PDF documents may be enhanced by providing alternative descriptions for images, formulas, and other items that do not translate naturally into text. In fact, such text alternatives are required for accessibility: - alternate descriptions are human-readable text that can be vocalized + alternative descriptions are human-readable text that can be vocalized by text-to-speech technology for the benefit of users with vision disabilities.
When an image contains words that are important to understanding the content, the text alternative should include those words. This will @@ -42,8 +42,8 @@
In the Set Alternative Text dialog that appears, type in your alternative text, then press the Save & Close button.
Links in PDF documents are represented by a Link
tag and objects in
its sub-tree, consisting of a link object reference (or Link annotation)
@@ -35,12 +35,12 @@
Authors should make sure that the alternate text makes sense in context of the screen text before and after the link.
+Authors should make sure that the alternative text makes sense in context of the screen text before and after the link.
This example is shown with Adobe Acrobat Pro. There are other software tools that perform similar functions.
The image below shows a document converted to PDF from Oracle Open Office. Note that the visible link text is the URL for the link target. A screen reader will read the entire URI as the link text.
The next image shows the Link tag structure in the Tag panel.
The last image shows the Alternate Text specified in the Link tag's TouchUp Properties dialog. A screen reader will read the Alternate Text as the link text.
+The last image shows the Alternative Text specified in the Link tag's TouchUp Properties dialog. A screen reader will read the Alternative Text as the link text.
This example is shown in operation in the working example of adding alternate link text (OpenOffice file) and working example of adding alternate link text (PDF file).
+This example is shown in operation in the working example of adding alternative link text (OpenOffice file) and working example of adding alternative link text (PDF file).
/Alt
entry/Alt
entryThe following code fragment illustrates code that is typical for alternative text for a link. This is typically accomplished by an authoring tool.
32 0 obj
<<
@@ -71,10 +71,10 @@ Adding alternate link text in a PDF document using the /Alt
ent
/URI(http://www.boston.com/business/technology/) %Uniform resource identifier(required), the URI to be resolved
>>
endobj
- The following illustrates how to specify alternate text for the URL in the above link:
+The following illustrates how to specify alternative text for the URL in the above link:
11 0 obj
<<
- /Alt(Boston Globe technology page) %Alternate text entry
+ /Alt(Boston Globe technology page) %Alternative text entry
/K [ 1
<<
/Obj 27 0 R
@@ -96,11 +96,11 @@ Tests
Procedure
-
-
For the hyperlink, verify that the alternate link text is properly coded by one of the following:
+ For the hyperlink, verify that the alternative link text is properly coded by one of the following:
- - Read the PDF document with a screen reader, listening to hear that the alternate link text is read correctly.
- - Use a tool that is capable of showing the
/Alt
entry to open the PDF document and view the hyperlink and alternate link text.
- - Use a tool that exposes the document through the accessibility API and verify that the alternate link text is the text for the link.
+ - Read the PDF document with a screen reader, listening to hear that the alternative link text is read correctly.
+ - Use a tool that is capable of showing the
/Alt
entry to open the PDF document and view the hyperlink and alternative link text.
+ - Use a tool that exposes the document through the accessibility API and verify that the alternative link text is the text for the link.
diff --git a/techniques/server-side-script/SVR2.html b/techniques/server-side-script/SVR2.html
index 5453d29185..984af67560 100644
--- a/techniques/server-side-script/SVR2.html
+++ b/techniques/server-side-script/SVR2.html
@@ -17,8 +17,8 @@ When to Use
The objective of this technique is to ensure that users can always access an accessible version of the content when non-conforming versions are also available. Whenever content is provided in a format that does not conform to WCAG, the site as a whole can still conform if alternate versions of the inaccessible content are provided. Conformance Requirement 4 requires that alternate versions can be derived from the nonconforming content or from its URI
.
Since it is not always possible to provide an accessible link from within non-conforming content, this technique describes how authors can use Apache's Module "mod_access" to ensure that non-conforming content can only be accessed from URIs that serve as alternate versions to the non-conforming content or from pages that include links to both the non-conforming version and the alternative version.
+The objective of this technique is to ensure that users can always access an accessible version of the content when non-conforming versions are also available. Whenever content is provided in a format that does not conform to WCAG, the site as a whole can still conform if alternative versions of the inaccessible content are provided. Conformance Requirement 4 requires that alternative versions can be derived from the nonconforming content or from its URI
.
Since it is not always possible to provide an accessible link from within non-conforming content, this technique describes how authors can use Apache's Module "mod_access" to ensure that non-conforming content can only be accessed from URIs that serve as alternative versions to the non-conforming content or from pages that include links to both the non-conforming version and the alternative version.
The objective of this technique is to provide a mechanism for users to select a preference for an alternate conforming version of a web page.
-Providing preferences to allow users to view conforming alternate versions can be accomplished in several ways. One common method is to provide a link which triggers a server-side process that sets a session or persistent cookie that the web server uses to modify the page or redirect the user to the alternate version. Other methods include providing user-specific choices that are stored as part of the user's login information for a system where users sign in to access a web page or service.
-Users requiring an alternate version will need the mechanism provided in the non-conforming page to be accessible in order to find and use it. The mechanism itself should conform to the accessibility level being claimed.
+The objective of this technique is to provide a mechanism for users to select a preference for an alternative conforming version of a web page.
+Providing preferences to allow users to view conforming alternate versions can be accomplished in several ways. One common method is to provide a link which triggers a server-side process that sets a session or persistent cookie that the web server uses to modify the page or redirect the user to the alternative version. Other methods include providing user-specific choices that are stored as part of the user's login information for a system where users sign in to access a web page or service.
+Users requiring an alternative version will need the mechanism provided in the non-conforming page to be accessible in order to find and use it. The mechanism itself should conform to the accessibility level being claimed.
A website offers a link to a "preferences" page on pages within the site. On this page, there is an option to view an alternate version of the site. There may be various aspects of the page that are affected, or the user may be opting to view an entirely alternate version of the site. The preference may be to display a version of the site where video included on the site displays captioning, or it may be offered because the primary site contains accessibility conformance issues that are addressed only via the alternative.
+A website offers a link to a "preferences" page on pages within the site. On this page, there is an option to view an alternative version of the site. There may be various aspects of the page that are affected, or the user may be opting to view an entirely alternative version of the site. The preference may be to display a version of the site where video included on the site displays captioning, or it may be offered because the primary site contains accessibility conformance issues that are addressed only via the alternative.
A web page author may choose to handle this preference via a cookie, which may be handled via a server-side scripting language such as PHP.
The preferences page may be offered as follows:
diff --git a/techniques/silverlight/SL1.html b/techniques/silverlight/SL1.html index 383da1c4b7..608aa29b10 100644 --- a/techniques/silverlight/SL1.html +++ b/techniques/silverlight/SL1.html @@ -1,10 +1,10 @@ -The objective of this technique is to show how to access an alternate +
The objective of this technique is to show how to access an alternative
audio channel in a prepared media file that is played in a Silverlight MediaElement
.
Silverlight supports media file formats that contains additional audio channels in synchronization, beyond the two tracks for stereo audio @@ -16,7 +16,7 @@ this button to listen to an audio-only version of the media presentation" so that the purpose of the media element control interface is clear to the user. That way the same media control can be used to present the - media either as audio-video or as audio-only with alternate track depending + media either as audio-video or as audio-only with alternative track depending on user preference at run time.
The media formats that are supported by Silverlight are documented on MSDN.
@@ -31,10 +31,10 @@Handling the + and - keys as alternate or additional keyboard equivalents +
Handling the + and - keys as alternative or additional keyboard equivalents
for the actions is also possible (if that is desired, handler would
check for Key.Add
or Key.Subtract
values).
The following is the XAML-defined control template for this control.
diff --git a/techniques/silverlight/SL17.html b/techniques/silverlight/SL17.html index 1fb9871206..3f635a0da1 100644 --- a/techniques/silverlight/SL17.html +++ b/techniques/silverlight/SL17.html @@ -124,7 +124,7 @@Captions are not needed when the synchronized media is, itself, an alternate presentation +
Captions are not needed when the synchronized media is, itself, an alternative presentation of information that is also presented via text on the web page. For example, if information on a page is accompanied by a synchronized media presentation that presents no more information than is already presented in text, but is easier for people with cognitive, diff --git a/understanding/20/distinguishable.html b/understanding/20/distinguishable.html index 44587bd76d..edca476527 100644 --- a/understanding/20/distinguishable.html +++ b/understanding/20/distinguishable.html @@ -14,7 +14,7 @@
While some guidelines are focused on making information available in a form that can - be presented in alternate formats, this guideline is concerned with making the default + be presented in alternative formats, this guideline is concerned with making the default presentation as easy to perceive as possible to people with disabilities. The primary focus is on making it easier for users to separate foreground information from the background. For visual presentations this involves making sure that information presented diff --git a/understanding/20/extended-audio-description-prerecorded.html b/understanding/20/extended-audio-description-prerecorded.html index 119ecc17bf..111019f1b0 100644 --- a/understanding/20/extended-audio-description-prerecorded.html +++ b/understanding/20/extended-audio-description-prerecorded.html @@ -31,7 +31,7 @@
Because it disrupts viewing for those who do not need the additional description, - techniques that allow you to turn the feature on and off are often provided. Alternately, + techniques that allow you to turn the feature on and off are often provided. Alternatively, versions with and without the additional description can be provided.
diff --git a/understanding/20/images-of-text-no-exception.html b/understanding/20/images-of-text-no-exception.html index c60a51f667..2442268d81 100644 --- a/understanding/20/images-of-text-no-exception.html +++ b/understanding/20/images-of-text-no-exception.html @@ -30,7 +30,7 @@This means implementing the text in a manner that allows its presentation to be changed - or providing a mechanism by which users can select an alternate presentation. Using + or providing a mechanism by which users can select an alternative presentation. Using images of text is an example of an implementation that does not allow users to alter the presentation of the text within it.
diff --git a/understanding/20/keyboard.html b/understanding/20/keyboard.html index d8b8963432..68c69897d6 100644 --- a/understanding/20/keyboard.html +++ b/understanding/20/keyboard.html @@ -23,13 +23,13 @@The intent of this success criterion is to ensure that, wherever possible, content - can be operated through a keyboard or keyboard interface (so an alternate keyboard - can be used). When content can be operated through a keyboard or alternate keyboard, + can be operated through a keyboard or keyboard interface (so an alternative keyboard + can be used). When content can be operated through a keyboard or alternative keyboard, it is operable by people with no vision (who cannot use devices such as mice that - require eye-hand coordination) as well as by people who must use alternate keyboards + require eye-hand coordination) as well as by people who must use alternative keyboards or input devices that act as keyboard emulators. Keyboard emulators include speech input software, sip-and-puff software, on-screen keyboards, scanning software and - a variety of assistive technologies and alternate keyboards. Individuals with low + a variety of assistive technologies and alternative keyboards. Individuals with low vision also may have trouble tracking a pointer and find the use of software much easier (or only possible) if they can control it from the keyboard.
diff --git a/understanding/20/meaningful-sequence.html b/understanding/20/meaningful-sequence.html index 9889507cfe..1fee82054b 100644 --- a/understanding/20/meaningful-sequence.html +++ b/understanding/20/meaningful-sequence.html @@ -27,7 +27,7 @@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 + components of web pages as well as associating alternative versions of web content to each other. These descriptions in turn allows users to locate specific information they need or prefer.
@@ -26,22 +26,22 @@A mechanism is provided to allow users to disable character-key shortcuts. The character key shortcuts are not the only way to carry out these commands. A speech user disables the shortcuts and can prevent words that are picked up by the microphone from triggering single-key shortcuts.
Keyboard-only users are in a long issues thread. While reading the thread they accidentally hit the S key, which moves focus to the search bar at the top of the document. This causes them to lose their place and train of thought. However, a mechanism is provided to allow users to change character-key shortcuts. They change the shortcut to include another key so they can avoid future interruptions.
Pass: An interface to review code/document changes provides a two-column comparison between the original and modified content. Each column fits within a 320 CSS pixel wide container and a horizontal scrollbar can be used to position each column into the visible viewport.
-An alternate view can show each changed line stacked on top of each other, but the two-column comparison view allows for direct comparison between original and modified lines of code on the same horizontal plane. This can be easier for some users to understand, especially when changes span multiple lines, reducing the need for vertically scrolling between each original and changed block of content.
+An alternative view can show each changed line stacked on top of each other, but the two-column comparison view allows for direct comparison between original and modified lines of code on the same horizontal plane. This can be easier for some users to understand, especially when changes span multiple lines, reducing the need for vertically scrolling between each original and changed block of content.
Authors relying on conforming alternate versions must make end users aware that a conforming alternate version is available. This may be accomplished by providing a link to a more accessible version, identified clearly by link text. Alternatively a link to instructions may be provided which documents how to access a more accessible version as well as the specific ways the alternate version is more accessible (e.g. a "high contrast version").
+Authors relying on conforming alternate versions must make end users aware that a conforming alternate version is available. This may be accomplished by providing a link to a more accessible version, identified clearly by link text. Alternatively a link to instructions may be provided which documents how to access a more accessible version as well as the specific ways the alternative version is more accessible (e.g. a "high contrast version").
Why does WCAG permit conforming alternate versions of web pages to be included in conformance claims? That is, why include pages that do not satisfy the success criteria @@ -938,12 +938,12 @@
A concern when permitting web pages that do not satisfy the success criteria is that people with disabilities will encounter these non-conforming pages, not be able to access their content, and not be able to find the “conforming alternate version." - A key part of the alternate versions provision, therefore, is the ability to find - the conforming page (the alternate version) from the non-conforming page when it is - encountered. The conformance requirement that permits alternate pages, therefore, - also requires a way for users to find the accessible version among the alternate versions. + A key part of the alternative versions provision, therefore, is the ability to find + the conforming page (the alternative version) from the non-conforming page when it is + encountered. The conformance requirement that permits alternative pages, therefore, + also requires a way for users to find the accessible version among the alternative versions.
-Note that providing an alternate version is a fallback option for conformance to WCAG +
Note that providing an alternative version is a fallback option for conformance to WCAG and the preferred method of conformance is to make all content directly accessible.
@@ -1032,11 +1032,11 @@Each numbered item in this section represents a technique or combination of techniques that the WCAG Working Group deems sufficient for meeting this success criterion. However, it is @@ -1049,7 +1049,7 @@
This section discusses metadata techniques that can be employed to satisfy WCAG 2 success criteria. For more information about metadata see resources below.
At its most basic level, metadata is essentially 'data about data' and is used to both describe and find resources.
-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.
+Metadata is a powerful tool that can be used for describing web pages and accessible components of web pages as well as associating alternative versions of web content to each other. These descriptions in turn allows users to locate specific information they need or prefer.
In conjunction with WCAG 2, metadata can play a number of roles including:
Metadata can be used to associate conforming alternate versions of web pages with web pages which do not conform, in order to allow users to find the conforming alternate version when they land on a non-conforming page that they cannot use.
Metadata can be used to locate and also to describe alternate pages where there are multiple versions of a page which have been developed, especially where the alternate pages are optimized for individuals with different disabilities. The user can use the metadata both to locate the alternate versions and to identify characteristics of the versions, so that they can find the one that best meets their needs.
+Metadata can be used to locate and also to describe alternative pages where there are multiple versions of a page which have been developed, especially where the alternative pages are optimized for individuals with different disabilities. The user can use the metadata both to locate the alternative versions and to identify characteristics of the versions, so that they can find the one that best meets their needs.
In addition to being used for whole pages (as in #1 and #2 above), metadata can be used to describe alternate versions of subcomponents of a page. Again, the metadata can be used to find alternate versions of a web page component as well as to get descriptions of the alternate versions (if there are several) in order to determine which one would best meet the user's needs.
+In addition to being used for whole pages (as in #1 and #2 above), metadata can be used to describe alternative versions of subcomponents of a page. Again, the metadata can be used to find alternative versions of a web page component as well as to get descriptions of the alternative versions (if there are several) in order to determine which one would best meet the user's needs.
Evaluators to use for checking if content does not meet WCAG {{ versionDecimal }} success criteria.
-Content that has a failure does not meet WCAG {{ versionDecimal }} success criteria, unless an alternate version is provided without the failure.
+Content that has a failure does not meet WCAG {{ versionDecimal }} success criteria, unless an alternative version is provided without the failure.
If anyone identifies a situation where a documented failure is not correct, please report the situation as a WCAG 2 comment so that it can be corrected or deleted as appropriate.
Thus while the techniques are useful for evaluating content, evaluations must go beyond just checking the sufficient technique tests in order to evaluate how content conforms to WCAG 2 success criteria.
-Failures are particularly useful for evaluations because they do indicate non-conformance (unless an alternate version is provided without the failure).
+Failures are particularly useful for evaluations because they do indicate non-conformance (unless an alternative version is provided without the failure).
Techniques for WCAG {{ versionDecimal }} is not intended to be used as a stand-alone document. Instead, it is expected that content authors will usually use How to Meet WCAG {{ versionDecimal }}: A customizable quick reference to read the WCAG 2 success criteria, and follow links from there to specific topics in Understanding WCAG 2 and to specific techniques.
Some techniques describe how to provide alternate ways for users to get content. For example, mentions a transcript as an alternative for an audio file. Some alternatives must also conform to WCAG 2. For example, the transcript itself must meet all relevant success criteria.
+Some techniques describe how to provide alternative ways for users to get content. For example, mentions a transcript as an alternative for an audio file. Some alternatives must also conform to WCAG 2. For example, the transcript itself must meet all relevant success criteria.
This page documents user agent support notes for Silverlight Techniques.
This page documents user agent support notes for Silverlight Techniques.
Role in UI Automation can be determined through several techniques.
The most straightforward technique for determining a given AutomationElement's
role is to check the value of ControlType.
This value provides an enumeration that reports role as several known
- possibilities plus an alternate role of "Custom" if no enumeration-defined
+ possibilities plus an alternative role of "Custom" if no enumeration-defined
role is a good descriptor. For example, a Silverlight Button
control
describes itself to UI Automation as a ControlType of Button,
and a Silverlight TreeView
describes itself as Tree.
For further information on roles, UI Automation clients can query @@ -536,7 +536,7 @@
See User Agents Supported for general information on user agent support.
See User Agents Supported for general information on user agent support.
This document is available in an expandable / collapsible alternate version in which the “Intent” sections copied from Understanding WCAG 2.0 are hidden and individually expandable, for easier reading.
+This document is available in an expandable / collapsible alternative version in which the “Intent” sections copied from Understanding WCAG 2.0 are hidden and individually expandable, for easier reading.
Copyright © 2012-2013 W3C® (MIT, ERCIM, Keio, Beihang). W3C liability, trademark and document use rules apply.
This document is a Working Group Notean Editors' Draft being developed by the WCAG2ICT Task Force (“Task Force”) operating under the terms of its Work Statement, and under the coordination and review of the Web Content Accessibility Guidelines Working Group (WCAG WG), which is part of the Web Accessibility Initiative (WAI) of the World Wide Web Consortium (W3C). The WCAG2ICT Task Force's work is consistent with the WCAG WG Charter that includes the following under its scope: “Coordinating with other entities adopting and using WCAG 2.0”.
This Working Group Note includes complete guidance for all Levels A and AA Success Criteria, guidance on all glossary terms plus new Key Terms, comments on conformance, and additional background information on some topics. This version includes changes made in response to comments received on the three earlier Working Drafts of this document. It also contains references to an alternate presentation in which the “Intent” sections copied from Understanding WCAG 2.0 are hidden and individually expandable, for easier reading.
+This Working Group Note includes complete guidance for all Levels A and AA Success Criteria, guidance on all glossary terms plus new Key Terms, comments on conformance, and additional background information on some topics. This version includes changes made in response to comments received on the three earlier Working Drafts of this document. It also contains references to an alternative presentation in which the “Intent” sections copied from Understanding WCAG 2.0 are hidden and individually expandable, for easier reading.
As a Working Group Note this content is stable, and the Working Group does not plan to make further changes. Should the need arise, however, the document could be updated. Comments received on this document will help the Working Group to decide if updates are needed, or will be taken into account should a republication be planned. Please send any comments on the “Additional Guidance” sections of this document to the public mailing list public-wcag2ict-comments@w3.org. Please include the following in your comments: the title of the document, location within the document, the concern, the suggested change, and any additional rationale for your comment.
This document includes many excerpts from “Understanding WCAG 2.0,” each of which is prefaced with the words “Intent from…” and which are also visually indicated with a yellow background. Understanding WCAG 2.0 and other WCAG 2.0 supporting documents will continue to focus on web technologies. For comments on Understanding WCAG, please follow the comment instructions in that document.
@@ -467,7 +467,7 @@This applies directly as written, and as described in Intent from Understanding Success Criterion 1.2.1 (also provided below).
-Note 1: The alternative can be provided directly in the non-web document or software – or provided in an alternate version that meets the success criteria.
+Note 1: The alternative can be provided directly in the non-web document or software – or provided in an alternative version that meets the success criteria.
Note 2: See also the discussion on Closed Functionality in the Introduction.
This applies directly as written, and as described in Intent from Understanding Success Criterion 1.2.3 (also provided below).
Note 1: The WCAG 2.0 definition of “audio description” says that “audio description” is “also called ‘video description’ and ‘descriptive narration’”.
-Note 2: Secondary or alternate audio tracks are commonly used for this purpose.
+Note 2: Secondary or alternative audio tracks are commonly used for this purpose.
Note 3: See also the discussion on Closed Functionality in the Introduction.
This applies directly as written, and as described in Intent from Understanding Success Criterion 1.2.5 (also provided below).
Note1: The WCAG 2.0 definition of “audio description” says that audio description is “also called ‘video description’ and ‘descriptive narration’”.
-Note2: Secondary or alternate audio tracks are commonly used for this purpose.
+Note2: Secondary or alternative audio tracks are commonly used for this purpose.
speech recognition software, which may be used by people who have some physical disabilities;
alternative keyboards, which are used by people with certain physical disabilities to simulate the keyboard (including alternate keyboards that use head pointers, single switches, sip/puff and other special input devices.);
+alternative keyboards, which are used by people with certain physical disabilities to simulate the keyboard (including alternative keyboards that use head pointers, single switches, sip/puff and other special input devices.);
alternative pointing devices, which are used by people with certain physical disabilities to simulate mouse pointing and button activations.
@@ -1260,7 +1260,7 @@Note: For those success criteria that use the term “web page”, WCAG2ICT provides specific replacement term(s) for “Web page”.
The following success criteria will be problematic for developers of closed functionality. They either discuss making information available in text (which can be read by assistive technologies) or making it “programmatically determinable” (rendered by a user agent and readable by assistive technologies) or discuss doing something else to make content compatible with assistive technologies. Alternate accessibility provisions that would be needed to address the purpose of these success criteria for the closed functionality aspects of products:
+The following success criteria will be problematic for developers of closed functionality. They either discuss making information available in text (which can be read by assistive technologies) or making it “programmatically determinable” (rendered by a user agent and readable by assistive technologies) or discuss doing something else to make content compatible with assistive technologies. Alternative accessibility provisions that would be needed to address the purpose of these success criteria for the closed functionality aspects of products:
Strategies for making text applications accessible through assistive technology involve two key tasks: (1) obtaining all of the text displayed in the interface, and (2) performing an analysis on that text to discern structural elements and screen updates.
-For example, a text application screen reader might directly access the matrix of character cells in the interface and provide a screen review mechanism for the user to review that matrix of characters (by sending the output to synthetic speech and / or a braille display). Alternately, a text application screen reader might directly consume the output rendered (perhaps by acting as its own terminal application or by analyzing the “TTY” output). The text application screen reader would also analyze the spacing and layout of the text in the matrix to provide features such as reading columns of text in a multi-column layout, discerning headers through analysis of line spacing, indentation and capitalization, and discerning input fields or user interface components, etc. by scanning for the use of inverse video or for text appearing in brackets or text from the character graphics codepage (ASCII codes greater than ‘0x7F’). Some of this analysis might also be done through the use of +
For example, a text application screen reader might directly access the matrix of character cells in the interface and provide a screen review mechanism for the user to review that matrix of characters (by sending the output to synthetic speech and / or a braille display). Alternatively, a text application screen reader might directly consume the output rendered (perhaps by acting as its own terminal application or by analyzing the “TTY” output). The text application screen reader would also analyze the spacing and layout of the text in the matrix to provide features such as reading columns of text in a multi-column layout, discerning headers through analysis of line spacing, indentation and capitalization, and discerning input fields or user interface components, etc. by scanning for the use of inverse video or for text appearing in brackets or text from the character graphics codepage (ASCII codes greater than ‘0x7F’). Some of this analysis might also be done through the use of filter tools that transform the output of a program (e.g. through reformatting “TTY” output rendered to a file or as direct input to a filter too).
Similarly, a text application screen magnifier would gain access to the matrix of character cells in order to magnify them or re-display them in a larger font. It would scan for screen refreshes / updates and apply heuristics to what had changed in order to decide what sub-matrix of character cells should appear in a magnified view. It would also scan for inverse video and a moving text cursor to track text being input by the user (and might combine the text matrix scanning with scanning of the keyboard input to match user input to what is appearing on the screen).