About: Add page to about section that explains the AT support tables #3000
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,122 @@ | ||
| <!DOCTYPE html> | ||
| <html lang="en"> | ||
|
|
||
| <head> | ||
| <meta charset="UTF-8"> | ||
| <meta content="width=device-width, initial-scale=1.0" name="viewport"> | ||
| <title>AT Support Tables</title> | ||
|
|
||
| <!-- Core JS and CSS shared by all About content --> | ||
| <link rel="stylesheet" href="https://www.w3.org/StyleSheets/TR/2016/base.css"> | ||
| <link rel="stylesheet" href="../../shared/css/core.css"> | ||
| <script src="../../shared/js/highlight.pack.js"></script> | ||
| <script src="../../shared/js/app.js"></script> | ||
| <script data-skipto="colorTheme:aria; displayOption:popup; containerElement:div" | ||
| src="../../shared/js/skipto.js"></script> | ||
| </head> | ||
|
|
||
| <body> | ||
| <main> | ||
| <h1>Assistive Technology Support Tables</h1> | ||
| <p> | ||
| As the <a href="https://aria-at.w3.org/">ARIA and Assistive Technologies Project</a> | ||
| makes reports on assistive technology interoperability for APG examples available, | ||
| the APG Task Force adds summaries of assistive technology support to the relevant example pages. | ||
| This page explains how to interpret and use the assistive technology support summaries. | ||
| </p> | ||
|
|
||
| <section id="purpose"> | ||
| <h2>Purpose of AT Support Tables</h2> | ||
| <p> | ||
| The purpose of the support tables is to provide an actionable summary of the interoperability tests performed by the <a href="http://aria-at.w3.org/">ARIA-AT project</a>.</p> | ||
| </section> | ||
|
|
||
| <section id="meaning"> | ||
| <h2>Meaning of Support Levels</h2> | ||
| <p> | ||
| The assistive technology support tables present two percentages for each assistive technology and browser combination that have been tested: "Must-Have Behaviors" and "Should-Have Behaviors". | ||
| A behavior designated as “Must-Have" is essential; if not provided, users could be blocked from using the UI element. | ||
| Failure to provide a “Should-Have” behavior could impede users. | ||
| Learn more about ARIA-AT’s | ||
| <a href="https://github.com/w3c/aria-at/wiki/Glossary#assertion-priority">definitions of Must and Should on the project wiki</a>. | ||
| </p> | ||
|
|
||
| <section> | ||
| <h3>Examples of Must-Have Behaviors</h3> | ||
| <ul> | ||
| <li>Convey the name of a radio button.</li> | ||
| <li>Convey the state of a checked radio button.</li> | ||
| </ul> | ||
| </section> | ||
|
|
||
| <section> | ||
| <h3>Examples of Should-Have Behaviors</h3> | ||
| <ul> | ||
| <li>Convey the position of a radio button in a radio group, e.g., the button is 1 of 3.</li> | ||
| <li>Convey the number of radio buttons in a radio group.</li> | ||
| </ul> | ||
| </section> | ||
|
|
||
| <section> | ||
| <h3>Important Constraints</h3> | ||
| <ul> | ||
| <li>Unless otherwise noted, all testing is done using the assistive technology vendor's default configuration of an assistive technology.</li> | ||
| <li> | ||
| ARIA-AT interoperability tests do not prescribe exactly how to satisfy a need. | ||
| For example, they do not specify exactly what a screen reader should speak. | ||
| Two different screen readers may convey the same information in different ways. | ||
| </li> | ||
| </ul> | ||
| </section> | ||
| </section> | ||
|
|
||
| <section id="recommendations"> | ||
| <h2>Recommendations</h2> | ||
|
|
||
| <section> | ||
| <h3>Don’t Code to the Bugs</h3> | ||
| <p> | ||
| ARIA-AT is working with assistive technology vendors to increase their support levels. | ||
| This means that assistive technologies that align with ARIA-AT interoperability tests will change over time. | ||
| Exercise caution when implementing a pattern where support levels are less than 100%. | ||
| Avoid modifying code to accommodate an assistive technology failure unless you are confident that the modification will: | ||
| </p> | ||
| <ul> | ||
| <li>Not negatively affect the experience when using assistive technologies that provide 100% support.</li> | ||
| <li>Not negatively affect the experience when the assistive technology vendor resolves the failure being accommodated.</li> | ||
|
There was a problem hiding this comment. @mcking65 did you intend to remove "being accommodated" from the the sentence? There was a problem hiding this comment. I reworded so it is simpler with a new commit I will push soon. |
||
| </ul> | ||
| <p> | ||
| When possible, test implementations of APG patterns with an assistive technology that provides 100% support for both must-have and should-have behaviors. | ||
| </p> | ||
| </section> | ||
|
|
||
| <section> | ||
| <h3>Design to Mitigate Critical Support Failures</h3> | ||
| <p> | ||
| Where feasible, avoid designing experiences that rely on features of APG patterns that have less than 100% support for must-have behaviors. | ||
| If the must-have support level is less than 100% for the example implementation of a pattern, that does not mean all ways of implementing that pattern will present assistive technology users with critical problems. | ||
|
There was a problem hiding this comment. @mcking65 Can we change "all ways of implementing that pattern" with "multiple ways of implementing that pattern" which was used in the suggestion below? "If there are multiple implementation examples of..." There was a problem hiding this comment. that would change the meaning. I revised the wording a bit to hopefully resolve the lack of clarity ...
|
||
| In these cases: | ||
| </p> | ||
| <ol> | ||
| <li>If there are multiple implementation examples of the pattern, compare support levels across examples to discover whether another method of implementation provides better support.</li> | ||
| <li>learn about the specific aspects of an example implementation that are not fully supported by navigating to the detailed report with the View Complete Report button.</li> | ||
| <li>If possible, use the guidelines of the pattern to design interactions such that they avoid the problematic features.</li> | ||
| </ol> | ||
| </section> | ||
|
|
||
| <section> | ||
| <h3>Perform Your Own Tests</h3> | ||
| <p> | ||
| A primary purpose of ARIA-AT data is to help assistive technology vendors coordinate interoperable rendering of ARIA. | ||
| While the ARIA-AT summary tables on APG example pages can be used as a guide of where to prioritize testing, the data is not as a final verdict on whether a feature in a web application will work. | ||
| It is essential for all developers to test applications with multiple assistive technologies to ensure a good user experience. | ||
| </p> | ||
| </section> | ||
|
|
||
| </section> | ||
|
|
||
|
|
||
| </main> | ||
| </body> | ||
|
|
||
| </html> | ||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mcking65 Would it be clearer if we update "that provide 100% support" as "that provide 100% must-have support"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It does not matter if it is a must or should that is being accomodated. However, your question prompted me to clarify by avoiding the need to use support levels as the factor that needs to be considered when making this judgment.