- From: Stacey Swinehart <stacey.swinehart@gmail.com>
- Date: Sun, 4 Jan 2026 16:18:35 -0600
- To: "Jason J.G. White" <jason@jasonjgw.net>
- Cc: public-rqtf@w3.org
- Message-ID: <CADZgR=-Lkhuv1fYUeRB1ZyjcA-Ryb=j2EQHyWCxdZSroU8DERQ@mail.gmail.com>
Two of the operational requirements in the Standard align well with an exercise I developed, called Friction Mapping™ (in my upcoming book). For mandatory human fallbacks, Friction Mapping™ can help an organization design intervention points in a workplace adjustment system (when a human is necessary) by identifying context gaps. When you identify mismatches in the system, you build human fallback protocols around them (low-friction can be automated; high-friction is human-led or human-in-the-loop). AI can check for pattern deviation (a mismatch) relative to a known friction point and trigger a human check-in protocol in the system. For transparency logs — Example: An employee contests an AI decision, such as an automated shift scheduling denial or a filtered-out resume. Friction Mapping™ can help categorize these events not just as "bugs," but as systemic interactions/structural conflict. - The Rigid Structure (the AI): The automated policy or algorithm that made the decision. - The Circumstance (the employee): The disability-related reality or work style that the AI failed to predict. - The Mismatch (the friction): The specific point where the AI’s rigidity clashed with the human reality. - By documenting the Mismatch rather than just the complaint, the Transparency Log can evolve into a roadmap to improve AI models. (I'm using some specific wording from Friction Mapping, such as Mistmatch and Circumstance. I'm happy to share the Friction Mapping content info with y'all, but not on the public channel ;) See everyone on Wed! Stacey On Sat, Jan 3, 2026 at 11:28 AM Jason J.G. White <jason@jasonjgw.net> wrote: > Welcome to RQTF in 2026. I hope that all participants enjoyed a > refreshing holiday. > > I propose that we all review the Canadian standard cited below, as it is > germane to our ongoing work. We can start to idscuss it at our upcoming > Task Force meeting. > > Jason J.G. White <jason@jasonjgw.net> wrote: > >Overview page: > https://accessible.canada.ca/creating-accessibility-standards/asc-62-accessible-equitable-artificial-intelligence-systems > > > >Text of standard: > https://accessible.canada.ca/creating-accessibility-standards/asc-62-accessible-equitable-artificial-intelligence-systems?mode=full-html > > > > > > > >
Received on Sunday, 4 January 2026 22:19:17 UTC