From 99a62023045702d8a82128c5ee0f5716af4b6aa8 Mon Sep 17 00:00:00 2001 From: Matt King Date: Mon, 29 Apr 2024 10:33:52 -0700 Subject: [PATCH 01/23] About: Add page that explains AT support tables --- .../at-support-tables/at-support-tables.html | 37 +++++++++++++++++++ 1 file changed, 37 insertions(+) create mode 100644 content/about/at-support-tables/at-support-tables.html diff --git a/content/about/at-support-tables/at-support-tables.html b/content/about/at-support-tables/at-support-tables.html new file mode 100644 index 0000000000..227c2af744 --- /dev/null +++ b/content/about/at-support-tables/at-support-tables.html @@ -0,0 +1,37 @@ + + + + + + AT Support Tables + + + + + + + + + +
+

Introduction

+

+ As reports on assistive technology interoperability are made available by the + ARIA and Assistive Technologies project, + the APG Task Force adds a summary of assistive technology support to the relevant pages showing example implementations of APG patterns. + This page explains how to interpret and use the assistive technology support summaries. +

+ +
+

Purpose of AT Support Tables

+

...

+
+ +
+

next section

+

...

+
+ +
+ + From 5f0b3ef728902b6b417c113b8bf770b495631681 Mon Sep 17 00:00:00 2001 From: Matt King Date: Mon, 29 Apr 2024 10:47:55 -0700 Subject: [PATCH 02/23] Add link to AT support table page from the about page. --- content/about/about.html | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/content/about/about.html b/content/about/about.html index 6433880dd1..9a7a5b4214 100644 --- a/content/about/about.html +++ b/content/about/about.html @@ -58,6 +58,15 @@

Related Specifi Related Specifications.

+
  • +

    Assistive Technology Support Tables

    +

    + Pages that provide example implementations of APG patterns also, when available, provide a summary of assistive technology support of the ARIA used in those examples. + Learn how to interpret and use data in the + Assistive Technology Support Tables. +

    +
    • +

  • Coverage and Quality Report

    From 20a87ee7a27a17ad0cb617d7609954ce07754d47 Mon Sep 17 00:00:00 2001 From: Matt King Date: Mon, 29 Apr 2024 11:03:40 -0700 Subject: [PATCH 03/23] update h1 --- content/about/at-support-tables/at-support-tables.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/about/at-support-tables/at-support-tables.html b/content/about/at-support-tables/at-support-tables.html index 227c2af744..c76b852662 100644 --- a/content/about/at-support-tables/at-support-tables.html +++ b/content/about/at-support-tables/at-support-tables.html @@ -14,7 +14,7 @@

    -

    Introduction

    +

    Assistive Technology Support Tables

    As reports on assistive technology interoperability are made available by the ARIA and Assistive Technologies project, From 2b7eec27c9059f2b3b14eefcef9a336cda3bd0b6 Mon Sep 17 00:00:00 2001 From: Boaz Sender Date: Tue, 7 May 2024 12:15:43 -0700 Subject: [PATCH 04/23] Add first pass at draft of support table interpretation guidance --- .../at-support-tables/at-support-tables.html | 99 +++++++++++++------ 1 file changed, 67 insertions(+), 32 deletions(-) diff --git a/content/about/at-support-tables/at-support-tables.html b/content/about/at-support-tables/at-support-tables.html index c76b852662..652fd84a4f 100644 --- a/content/about/at-support-tables/at-support-tables.html +++ b/content/about/at-support-tables/at-support-tables.html @@ -1,37 +1,72 @@ - - - - AT Support Tables - - - - - - - - - -

    -

    Assistive Technology Support Tables

    + + + + + AT Support Tables + + + + + + + + + + +
    +

    Assistive Technology Support Tables

    +

    + As reports on assistive technology interoperability are made available by the ARIA and Assistive Technologies + project, the APG Task Force adds a summary of assistive technology support to the relevant pages showing example + implementations of APG patterns. This page explains how to interpret and use the assistive technology support + summaries. +

    + +
    +

    Purpose of AT Support Tables

    +

    The purpose of the support tables is to provide APG readers with a legible and actionable summary of the + tests performed in the ARIA-AT project.

    +
    +
    +

    Meaning of scores

    +

    Two scores are presented for each Assistive Technology and Browser combination for APG patterns that have + ARIA-AT data available: Must and Should. “Must” + failures block users. “Should” failures impede users. Learn more about ARIA-AT’s definitions of Must and Should on the + project wiki.

    +
    +
    +

    Recommendations

    + +

    Understand the failures

    +

    Where possible, APG readers should avoid implementing patterns that have a score lower than 100% in the must + column. If, however, you find yourself implementing a pattern with less than 100% in the Must column, you should + take time to understand what is failing. You can learn more about the specific failures of a given pattern by + clicking through to the detailed report on the ARIA-AT website.

    + +

    Don’t Code to the Bugs

    - As reports on assistive technology interoperability are made available by the - ARIA and Assistive Technologies project, - the APG Task Force adds a summary of assistive technology support to the relevant pages showing example implementations of APG patterns. - This page explains how to interpret and use the assistive technology support summaries. + ARIA-AT is working with Assistive Technology vendors to get to 100% Must and Should passing rates. This means + that Assistive Technologies which use ARIA-AT will change over time. + When implementing a pattern that has less than 100% support for either MUST and SHOULD, be careful not to modify + your code to accommodate the Assistive Technology failure, especially if doing so would affect passing Assistive + Technologies. +

    +

    Perform your own tests

    + +

    The original purpose of ARIA-AT data are to help Assistive Technology vendors coordinate the interoperable + rendering of ARIA. The ARIA-AT summary tables on APG should be used as an indicator for web developers about + what + areas to prioritize testing further, not as a final verdict on whether a feature in a web application will work. + You should always test your application’s rendering with multiple assistive technologies.

    +
    + + +
    + -
    -

    Purpose of AT Support Tables

    -

    ...

    -
    - -
    -

    next section

    -

    ...

    -
    - -
    - - + \ No newline at end of file From 3b73891c40efe3f8bccf83a2a955602e176794ea Mon Sep 17 00:00:00 2001 From: Boaz Sender Date: Tue, 7 May 2024 12:17:58 -0700 Subject: [PATCH 05/23] fix lint errors --- content/about/at-support-tables/at-support-tables.html | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/about/at-support-tables/at-support-tables.html b/content/about/at-support-tables/at-support-tables.html index 652fd84a4f..5cf4330f8f 100644 --- a/content/about/at-support-tables/at-support-tables.html +++ b/content/about/at-support-tables/at-support-tables.html @@ -30,15 +30,15 @@

    Purpose of AT Support Tables

    The purpose of the support tables is to provide APG readers with a legible and actionable summary of the tests performed in the ARIA-AT project.

    -
    +

    Meaning of scores

    Two scores are presented for each Assistive Technology and Browser combination for APG patterns that have ARIA-AT data available: Must and Should. “Must” failures block users. “Should” failures impede users. Learn more about ARIA-AT’s definitions of Must and Should on the + href="https://github.com/w3c/aria-at/wiki/Glossary#assertion-priority">definitions of Must and Should on the project wiki.

    -
    +

    Recommendations

    Understand the failures

    From e0d413536f9089a58780982a4f3d39080f4ba041 Mon Sep 17 00:00:00 2001 From: Boaz Sender Date: Wed, 8 May 2024 10:13:07 -0700 Subject: [PATCH 06/23] copy edits to at-support-tables page --- content/about/at-support-tables/at-support-tables.html | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/about/at-support-tables/at-support-tables.html b/content/about/at-support-tables/at-support-tables.html index 5cf4330f8f..f5762cc9fc 100644 --- a/content/about/at-support-tables/at-support-tables.html +++ b/content/about/at-support-tables/at-support-tables.html @@ -28,12 +28,12 @@

    Assistive Technology Support Tables

    Purpose of AT Support Tables

    The purpose of the support tables is to provide APG readers with a legible and actionable summary of the - tests performed in the ARIA-AT project.

    + tests performed in the ARIA-AT project.

    Meaning of scores

    Two scores are presented for each Assistive Technology and Browser combination for APG patterns that have - ARIA-AT data available: Must and Should. “Must” + ARIA-AT data available: "Must-Have Behaviors" and "Should-Have Behaviors". “Must” failures block users. “Should” failures impede users. Learn more about ARIA-AT’s definitions of Must and Should on the project wiki.

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

    Understand the failures

    Where possible, APG readers should avoid implementing patterns that have a score lower than 100% in the must column. If, however, you find yourself implementing a pattern with less than 100% in the Must column, you should take time to understand what is failing. You can learn more about the specific failures of a given pattern by - clicking through to the detailed report on the ARIA-AT website.

    + navigating to the detailed report with the View Complete Report button.

    Don’t Code to the Bugs

    From 185ca6632b82cd57231cb33614d82c5eab8b93a3 Mon Sep 17 00:00:00 2001 From: Boaz Sender Date: Fri, 10 May 2024 14:22:24 -0700 Subject: [PATCH 07/23] respoond to review change requests --- .../about/at-support-tables/at-support-tables.html | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/content/about/at-support-tables/at-support-tables.html b/content/about/at-support-tables/at-support-tables.html index f5762cc9fc..3f17bb7538 100644 --- a/content/about/at-support-tables/at-support-tables.html +++ b/content/about/at-support-tables/at-support-tables.html @@ -27,7 +27,7 @@

    Assistive Technology Support Tables

    Purpose of AT Support Tables

    -

    The purpose of the support tables is to provide APG readers with a legible and actionable summary of the +

    The purpose of the support tables is to provide APG readers with an actionable summary of the tests performed in the ARIA-AT project.

    @@ -43,8 +43,10 @@

    Recommendations

    Understand the failures

    Where possible, APG readers should avoid implementing patterns that have a score lower than 100% in the must - column. If, however, you find yourself implementing a pattern with less than 100% in the Must column, you should - take time to understand what is failing. You can learn more about the specific failures of a given pattern by + column. If, however, the reader finds themselves implementing a pattern with less than 100% in the Must column, + they should + take time to understand what is failing. Readers can learn more about the specific failures of a given pattern + by navigating to the detailed report with the View Complete Report button.

    Don’t Code to the Bugs

    @@ -52,7 +54,7 @@

    Don’t Code to the Bugs

    ARIA-AT is working with Assistive Technology vendors to get to 100% Must and Should passing rates. This means that Assistive Technologies which use ARIA-AT will change over time. When implementing a pattern that has less than 100% support for either MUST and SHOULD, be careful not to modify - your code to accommodate the Assistive Technology failure, especially if doing so would affect passing Assistive + code to accommodate the Assistive Technology failure, especially if doing so would affect passing Assistive Technologies.

    Perform your own tests

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

    Perform your own tests

    rendering of ARIA. The ARIA-AT summary tables on APG should be used as an indicator for web developers about what areas to prioritize testing further, not as a final verdict on whether a feature in a web application will work. - You should always test your application’s rendering with multiple assistive technologies. + Readers should always test their application’s rendering with multiple assistive technologies.

    From e43ebe51d76b7aac24bbc4a46e80a8875894c858 Mon Sep 17 00:00:00 2001 From: Boaz Sender Date: Fri, 10 May 2024 14:33:19 -0700 Subject: [PATCH 08/23] address further PR feedback and stub example sections --- .../at-support-tables/at-support-tables.html | 35 +++++++++++++------ 1 file changed, 25 insertions(+), 10 deletions(-) diff --git a/content/about/at-support-tables/at-support-tables.html b/content/about/at-support-tables/at-support-tables.html index 3f17bb7538..3d3f9c2a57 100644 --- a/content/about/at-support-tables/at-support-tables.html +++ b/content/about/at-support-tables/at-support-tables.html @@ -37,18 +37,14 @@

    Meaning of scores

    failures block users. “Should” failures impede users. Learn more about ARIA-AT’s definitions of Must and Should on the project wiki.

    + +

    Example Must-Have

    +

    TODO

    +

    Example Should-Have

    +

    TODO

    Recommendations

    - -

    Understand the failures

    -

    Where possible, APG readers should avoid implementing patterns that have a score lower than 100% in the must - column. If, however, the reader finds themselves implementing a pattern with less than 100% in the Must column, - they should - take time to understand what is failing. Readers can learn more about the specific failures of a given pattern - by - navigating to the detailed report with the View Complete Report button.

    -

    Don’t Code to the Bugs

    ARIA-AT is working with Assistive Technology vendors to get to 100% Must and Should passing rates. This means @@ -57,9 +53,28 @@

    Don’t Code to the Bugs

    code to accommodate the Assistive Technology failure, especially if doing so would affect passing Assistive Technologies.

    + +

    + When possible, readers should test with an AT that scores 100% in the Must-have column and hew to to that AT + since it is known to be wokring correctly.

    + +

    Understand the failures

    +

    Where possible, APG readers should avoid implementing patterns that have a score lower than 100% in the must + column. If, however, the reader finds themselves implementing a pattern with less than 100% in the Must column, + they should + take time to understand what is failing. Readers should learn what specific part of an implementation is + problematic and design interactions around it that remain within the pattern's guidelines. +

    +

    + Readers can learn more about the specific failures of a given pattern + by + navigating to the detailed report with the View Complete Report button. +

    +

    Perform your own tests

    -

    The original purpose of ARIA-AT data are to help Assistive Technology vendors coordinate the interoperable +

    + The original purpose of ARIA-AT data are to help Assistive Technology vendors coordinate the interoperable rendering of ARIA. The ARIA-AT summary tables on APG should be used as an indicator for web developers about what areas to prioritize testing further, not as a final verdict on whether a feature in a web application will work. From 788b3e739df2bd7a91ca609b63b99c2e188d4370 Mon Sep 17 00:00:00 2001 From: Boaz Sender Date: Fri, 10 May 2024 15:39:48 -0700 Subject: [PATCH 09/23] fix typo --- content/about/at-support-tables/at-support-tables.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/about/at-support-tables/at-support-tables.html b/content/about/at-support-tables/at-support-tables.html index 3d3f9c2a57..d4a65d5dc1 100644 --- a/content/about/at-support-tables/at-support-tables.html +++ b/content/about/at-support-tables/at-support-tables.html @@ -56,7 +56,7 @@

    Don’t Code to the Bugs

    When possible, readers should test with an AT that scores 100% in the Must-have column and hew to to that AT - since it is known to be wokring correctly.

    + since it is known to be working correctly.

    Understand the failures

    Where possible, APG readers should avoid implementing patterns that have a score lower than 100% in the must From 0f672b70fe3ac199e9ce5d0c18952eccd6ffbaf1 Mon Sep 17 00:00:00 2001 From: Matt King Date: Tue, 21 May 2024 07:13:25 -0700 Subject: [PATCH 10/23] editorial revisions to intro --- .../at-support-tables/at-support-tables.html | 27 ++++++++++--------- 1 file changed, 15 insertions(+), 12 deletions(-) diff --git a/content/about/at-support-tables/at-support-tables.html b/content/about/at-support-tables/at-support-tables.html index d4a65d5dc1..aa4bcea7de 100644 --- a/content/about/at-support-tables/at-support-tables.html +++ b/content/about/at-support-tables/at-support-tables.html @@ -19,24 +19,27 @@

    Assistive Technology Support Tables

    - As reports on assistive technology interoperability are made available by the ARIA and Assistive Technologies - project, the APG Task Force adds a summary of assistive technology support to the relevant pages showing example - implementations of APG patterns. This page explains how to interpret and use the assistive technology support - summaries. + As the ARIA and Assistive Technologies Project + 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.

    Purpose of AT Support Tables

    -

    The purpose of the support tables is to provide APG readers with an actionable summary of the - tests performed in the ARIA-AT project.

    +

    + The purpose of the support tables is to provide an actionable summary of the interoperability tests performed by the ARIA-AT project.

    +
    -

    Meaning of scores

    -

    Two scores are presented for each Assistive Technology and Browser combination for APG patterns that have - ARIA-AT data available: "Must-Have Behaviors" and "Should-Have Behaviors". “Must” - failures block users. “Should” failures impede users. Learn more about ARIA-AT’s definitions of Must and Should on the - project wiki.

    +

    Meaning of support levels

    +

    + 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 meaningfully impede users. + Learn more about ARIA-AT’s + definitions of Must and Should on the project wiki. +

    Example Must-Have

    TODO

    From 5c2b3bd9e8fa193876913e64e82c79d9948c4fce Mon Sep 17 00:00:00 2001 From: Matt King Date: Tue, 21 May 2024 07:21:56 -0700 Subject: [PATCH 11/23] add example behaviors --- .../about/at-support-tables/at-support-tables.html | 14 ++++++++++---- 1 file changed, 10 insertions(+), 4 deletions(-) diff --git a/content/about/at-support-tables/at-support-tables.html b/content/about/at-support-tables/at-support-tables.html index aa4bcea7de..0afa9cac1a 100644 --- a/content/about/at-support-tables/at-support-tables.html +++ b/content/about/at-support-tables/at-support-tables.html @@ -41,10 +41,16 @@

    Meaning of support levels

    definitions of Must and Should on the project wiki.

    -

    Example Must-Have

    -

    TODO

    -

    Example Should-Have

    -

    TODO

    +

    Examples of Must-Have behaviors

    +
      +
    • Convey the name of a radio button.
      • +
    • Convey the state of a checked radio button.
      • +
    +

    Examples of Should-Have behaviors

    +
      +
    • Convey the position of a radio button in a radio group, e.g., the button is 1 of 3.
      • > +
    • Convey the number of radio buttons in a radio group.
      • +

    Recommendations

    From 4f2ccb7f6dde326b926ce3ce493c0806500292ac Mon Sep 17 00:00:00 2001 From: Matt King Date: Tue, 21 May 2024 07:39:37 -0700 Subject: [PATCH 12/23] Add descriptions of test constraints --- .../about/at-support-tables/at-support-tables.html | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git a/content/about/at-support-tables/at-support-tables.html b/content/about/at-support-tables/at-support-tables.html index 0afa9cac1a..7aac59dd46 100644 --- a/content/about/at-support-tables/at-support-tables.html +++ b/content/about/at-support-tables/at-support-tables.html @@ -36,7 +36,7 @@

    Meaning of support levels

    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 meaningfully impede users. + Failure to provide a “Should-Have” behavior could impede users. Learn more about ARIA-AT’s definitions of Must and Should on the project wiki.

    @@ -48,10 +48,20 @@

    Examples of Must-Have behaviors

    Examples of Should-Have behaviors

      -
    • Convey the position of a radio button in a radio group, e.g., the button is 1 of 3.
      • > +
    • Convey the position of a radio button in a radio group, e.g., the button is 1 of 3.
    • Convey the number of radio buttons in a radio group.
    +

    Important constraints

    +
      +
    • Unless otherwise noted, all testing is done using the default configuration of an assistive technology.
      • +
    • + 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. +
      • +
    +

    Recommendations

    Don’t Code to the Bugs

    From d37e9eea6bcf1876062b351edc321ea41c32040e Mon Sep 17 00:00:00 2001 From: Matt King Date: Tue, 21 May 2024 07:50:37 -0700 Subject: [PATCH 13/23] do not cap assistive tech except in titles; not a proper noun --- .../about/at-support-tables/at-support-tables.html | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/content/about/at-support-tables/at-support-tables.html b/content/about/at-support-tables/at-support-tables.html index 7aac59dd46..04e07c1c96 100644 --- a/content/about/at-support-tables/at-support-tables.html +++ b/content/about/at-support-tables/at-support-tables.html @@ -34,7 +34,7 @@

    Purpose of AT Support Tables

    Meaning of support levels

    - 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". + 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 @@ -61,16 +61,16 @@

    Important constraints

    • - +

    Recommendations

    Don’t Code to the Bugs

    - ARIA-AT is working with Assistive Technology vendors to get to 100% Must and Should passing rates. This means - that Assistive Technologies which use ARIA-AT will change over time. + ARIA-AT is working with assistive technology vendors to increase their support levels. + This means that assistive technologies which use ARIA-AT will change over time. When implementing a pattern that has less than 100% support for either MUST and SHOULD, be careful not to modify - code to accommodate the Assistive Technology failure, especially if doing so would affect passing Assistive - Technologies. + code to accommodate the assistive technology failure, especially if doing so would affect passing assistive + technologies.

    @@ -93,7 +93,7 @@

    Understand the failures

    Perform your own tests

    - The original purpose of ARIA-AT data are to help Assistive Technology vendors coordinate the interoperable + The original purpose of ARIA-AT data are to help assistive technology vendors coordinate the interoperable rendering of ARIA. The ARIA-AT summary tables on APG should be used as an indicator for web developers about what areas to prioritize testing further, not as a final verdict on whether a feature in a web application will work. From ebfce7190fce8493017ad33e9e4805add985ae40 Mon Sep 17 00:00:00 2001 From: Matt King Date: Tue, 21 May 2024 07:53:55 -0700 Subject: [PATCH 14/23] Consistent case in headings --- .../about/at-support-tables/at-support-tables.html | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/content/about/at-support-tables/at-support-tables.html b/content/about/at-support-tables/at-support-tables.html index 04e07c1c96..6f72a164d3 100644 --- a/content/about/at-support-tables/at-support-tables.html +++ b/content/about/at-support-tables/at-support-tables.html @@ -32,7 +32,7 @@

    Purpose of AT Support Tables

    -

    Meaning of support levels

    +

    Meaning of Support Levels

    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. @@ -41,17 +41,17 @@

    Meaning of support levels

    definitions of Must and Should on the project wiki.

    -

    Examples of Must-Have behaviors

    +

    Examples of Must-Have Behaviors

    • Convey the name of a radio button.
    • Convey the state of a checked radio button.
    -

    Examples of Should-Have behaviors

    +

    Examples of Should-Have Behaviors

    • Convey the position of a radio button in a radio group, e.g., the button is 1 of 3.
    • Convey the number of radio buttons in a radio group.
    -

    Important constraints

    +

    Important Constraints

    • Unless otherwise noted, all testing is done using the default configuration of an assistive technology.
    • @@ -77,7 +77,7 @@

      Don’t Code to the Bugs

      When possible, readers should test with an AT that scores 100% in the Must-have column and hew to to that AT since it is known to be working correctly.

      -

      Understand the failures

      +

      Understand the Failures

      Where possible, APG readers should avoid implementing patterns that have a score lower than 100% in the must column. If, however, the reader finds themselves implementing a pattern with less than 100% in the Must column, they should @@ -90,7 +90,7 @@

      Understand the failures

      navigating to the detailed report with the View Complete Report button.

      -

      Perform your own tests

      +

      Perform Your Own Tests

      The original purpose of ARIA-AT data are to help assistive technology vendors coordinate the interoperable From 4d61a62a2d114c31a7a90187dda79e9db9a85ca1 Mon Sep 17 00:00:00 2001 From: Matt King Date: Tue, 21 May 2024 08:14:18 -0700 Subject: [PATCH 15/23] Revisions to first recommendation --- .../at-support-tables/at-support-tables.html | 16 +++++++++------- 1 file changed, 9 insertions(+), 7 deletions(-) diff --git a/content/about/at-support-tables/at-support-tables.html b/content/about/at-support-tables/at-support-tables.html index 6f72a164d3..63ab39a65b 100644 --- a/content/about/at-support-tables/at-support-tables.html +++ b/content/about/at-support-tables/at-support-tables.html @@ -67,15 +67,17 @@

      Recommendations

      Don’t Code to the Bugs

      ARIA-AT is working with assistive technology vendors to increase their support levels. - This means that assistive technologies which use ARIA-AT will change over time. - When implementing a pattern that has less than 100% support for either MUST and SHOULD, be careful not to modify - code to accommodate the assistive technology failure, especially if doing so would affect passing assistive - technologies. + 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:

      - +
        +
      • Not negatively affect the experience when using assistive technologies that provide 100% support.
        • +
      • Not negatively affect the experience when the failure being accommodated is resolved.
        • +

      - When possible, readers should test with an AT that scores 100% in the Must-have column and hew to to that AT - since it is known to be working correctly.

      + When possible, test implementations of APG patterns with an assistive technology that provides 100% support in both Must-Have and Should-Have columns. +

      Understand the Failures

      Where possible, APG readers should avoid implementing patterns that have a score lower than 100% in the must From fb4b841e11efc0e9be26ad664ce76d88d270a1de Mon Sep 17 00:00:00 2001 From: Matt King Date: Tue, 21 May 2024 08:52:57 -0700 Subject: [PATCH 16/23] Revise recommendations 2 and 3 --- .../at-support-tables/at-support-tables.html | 120 ++++++++++-------- 1 file changed, 66 insertions(+), 54 deletions(-) diff --git a/content/about/at-support-tables/at-support-tables.html b/content/about/at-support-tables/at-support-tables.html index 63ab39a65b..49caf6e4a6 100644 --- a/content/about/at-support-tables/at-support-tables.html +++ b/content/about/at-support-tables/at-support-tables.html @@ -41,66 +41,78 @@

      Meaning of Support Levels

      definitions of Must and Should on the project wiki.

      -

      Examples of Must-Have Behaviors

      -
        -
      • Convey the name of a radio button.
        • -
      • Convey the state of a checked radio button.
        • -
      -

      Examples of Should-Have Behaviors

      -
        -
      • Convey the position of a radio button in a radio group, e.g., the button is 1 of 3.
        • -
      • Convey the number of radio buttons in a radio group.
        • -
      -

      Important Constraints

      -
        -
      • Unless otherwise noted, all testing is done using the default configuration of an assistive technology.
        • -
      • - 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. -
        • -
      +
      +

      Examples of Must-Have Behaviors

      +
        +
      • Convey the name of a radio button.
        • +
      • Convey the state of a checked radio button.
        • +
      +
      + +
      +

      Examples of Should-Have Behaviors

      +
        +
      • Convey the position of a radio button in a radio group, e.g., the button is 1 of 3.
        • +
      • Convey the number of radio buttons in a radio group.
        • +
      +
      + +
      +

      Important Constraints

      +
        +
      • Unless otherwise noted, all testing is done using the default configuration of an assistive technology.
        • +
      • + 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. +
        • +
      +

    Recommendations

    -

    Don’t Code to the Bugs

    -

    - 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: -

    -
      -
    • Not negatively affect the experience when using assistive technologies that provide 100% support.
      • -
    • Not negatively affect the experience when the failure being accommodated is resolved.
      • -
    -

    - When possible, test implementations of APG patterns with an assistive technology that provides 100% support in both Must-Have and Should-Have columns. -

    - -

    Understand the Failures

    -

    Where possible, APG readers should avoid implementing patterns that have a score lower than 100% in the must - column. If, however, the reader finds themselves implementing a pattern with less than 100% in the Must column, - they should - take time to understand what is failing. Readers should learn what specific part of an implementation is - problematic and design interactions around it that remain within the pattern's guidelines. -

    -

    - Readers can learn more about the specific failures of a given pattern - by - navigating to the detailed report with the View Complete Report button. -

    -

    Perform Your Own Tests

    +
    +

    Don’t Code to the Bugs

    +

    + 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: +

    +
      +
    • Not negatively affect the experience when using assistive technologies that provide 100% support.
      • +
    • Not negatively affect the experience when the failure being accommodated is resolved.
      • +
    +

    + When possible, test implementations of APG patterns with an assistive technology that provides 100% support for both must-have and should-have behaviors. +

    +
    + +
    +

    Design Around Critical Support Failures

    +

    + Where feasible, avoid implementing features of APG patterns where support for must-have behaviors is less than 100%. + If the must-have support level is less than 100% for the example implementation of a pattern, that does not mean all variants of that pattern will present assistive technology users with critical problems. + In these cases: +

    +
      +
    1. If there are multiple implementation examples of the pattern, compare support levels across examples to discover whether another method of implementation provides better support.
      2. +
    2. 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.
      3. +
    3. If possible, use the guidelines of the pattern to design interactions such that they avoid the problematic features.
      4. +
    +
    + +
    +

    Perform Your Own Tests

    +

    + A primary purpose of ARIA-AT data are 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. +

    +
    -

    - The original purpose of ARIA-AT data are to help assistive technology vendors coordinate the interoperable - rendering of ARIA. The ARIA-AT summary tables on APG should be used as an indicator for web developers about - what - areas to prioritize testing further, not as a final verdict on whether a feature in a web application will work. - Readers should always test their application’s rendering with multiple assistive technologies. -

    From ba04a3fac70b4dec4fc2c650268b2ad9ffb35194 Mon Sep 17 00:00:00 2001 From: Matt King Date: Tue, 21 May 2024 09:36:17 -0700 Subject: [PATCH 17/23] grammar --- content/about/at-support-tables/at-support-tables.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/about/at-support-tables/at-support-tables.html b/content/about/at-support-tables/at-support-tables.html index 49caf6e4a6..284dec00cf 100644 --- a/content/about/at-support-tables/at-support-tables.html +++ b/content/about/at-support-tables/at-support-tables.html @@ -107,7 +107,7 @@

    Design Around Critical Support Failures

    Perform Your Own Tests

    - A primary purpose of ARIA-AT data are to help assistive technology vendors coordinate interoperable rendering of ARIA. + 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.

    From 3abc7423d3be9b78a0f2c94aa482587f98ae19d6 Mon Sep 17 00:00:00 2001 From: Matt King Date: Tue, 21 May 2024 10:54:09 -0700 Subject: [PATCH 18/23] Add links to about AT support tables page --- content/patterns/alert/examples/alert.html | 1 + content/patterns/button/examples/button.html | 1 + content/patterns/dialog-modal/examples/dialog.html | 1 + content/patterns/link/examples/link.html | 1 + content/patterns/menu-button/examples/menu-button-links.html | 1 + content/patterns/radio/examples/radio-activedescendant.html | 1 + content/patterns/slider/examples/slider-color-viewer.html | 1 + 7 files changed, 7 insertions(+) diff --git a/content/patterns/alert/examples/alert.html b/content/patterns/alert/examples/alert.html index 78687d9239..fe7df259db 100644 --- a/content/patterns/alert/examples/alert.html +++ b/content/patterns/alert/examples/alert.html @@ -122,6 +122,7 @@

    Role, Property, State, and Tabindex Attributes

    Assistive Technology Support

    +

    Learn how to interpret and use assistive technology support data