w3c · mcking65 · May 22, 2024 · Apr 29, 2024 · Apr 29, 2024 · Apr 29, 2024
diff --git a/content/about/about.html b/content/about/about.html
@@ -58,6 +58,15 @@ <h2><a href="related-specifications/related-specifications.html">Related Specifi
             <a href="related-specifications/related-specifications.html">Related Specifications</a>.
           </p>
         </li>
+        <li>
+          <h2><a href="at-support-tables/at-support-tables.html">Assistive Technology Support Tables</a></h2>
+          <p>
+            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
+            <a href="at-support-tables/at-support-tables.html">Assistive Technology Support Tables</a>.
+          </p>
+        </li>
+
         <li>
           <h2><a href="coverage-and-quality/coverage-and-quality-report.html">Coverage and Quality Report</a></h2>
           <p>

diff --git a/content/about/at-support-tables/at-support-tables.html b/content/about/at-support-tables/at-support-tables.html
@@ -0,0 +1,72 @@
+<!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 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.
+    </p>
+
+    <section id="purpose">
+      <h2>Purpose of AT Support Tables</h2>
+      <p>The purpose of the support tables is to provide APG readers with a legible and actionable summary of the
+        tests performed in the <a href="http://aria-at.w3.org/">ARIA-AT project</a>.</p>
+    </section>
+    <section id="meaning">
+      <h2>Meaning of scores</h2>
+      <p>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 <a
+          href="https://github.com/w3c/aria-at/wiki/Glossary#assertion-priority">definitions of Must and Should on the
+          project wiki</a>.</p>
+    </section>
+    <section id="recommendations">
+      <h2>Recommendations</h2>
+
+      <h3>Understand the failures</h3>
+      <p>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
+        navigating to the detailed report with the View Complete Report button.</p>
+
+      <h3>Don’t Code to the Bugs</h3>
+      <p>
+        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.
+      </p>
+      <h3>Perform your own tests</h3>
+
+      <p>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.
+      </p>
+    </section>
+
+
+  </main>
+</body>
+
+</html>