Personalizing the Web
for Better Accessibility

Welcome

This is a presentation on the latest work of the WAI-Adapt Task Force.

Facilitators: Sharon Snider; Lionel Wolberger

Task Force home: https://www.w3.org/WAI/APA/task-forces/adapt/

This talk: https://w3c.github.io/adapt/TPAC/2023/

What is this all about?

1. Who needs a more adptive web?

2. Long-term goals and approach

3. Current focus: symbols

4. Exploratory work: semantics and adaptations

5. How to get involved

A more adaptive web

Who needs a more adaptive web?

• People with cognitive and learning disabilities, such as dyscalculia, AD(H)D, short-term memory loss, etc.
• People who are in a time of crisis; have a migraine; are busy
• People who use Augmentative and Alternative Communication (AAC) (with varying vocabulary sizes)
• People who struggle to learn/recognise new icons

All of us, at some time or another!

Day-to-day impact

Accessing critical services…

• Joining meetings at work (on time…)
• Can I make a doctor's appointment?
• Can I make a complaint to the water company?
• Can I turn on the heating?

Standards exist to make these interfaces accessible such as the Web Content Accessibility Guidelines (WCAG)

But…

User needs differ

An approach like this needs semantics.

Where are we going?

Content Usable

How are we supporting increased adaptation?

1. Working with community organizations such as Blissymbolics, with whom we've published the Alternative and Augmented Communication (AAC) Symbol Registry.

2. Developing a specification for content authors, where a small addition of machine-readable semantic metadata can support a range of helpful adaptations.. The Symbols Module is a Candidate Recommendation.

3. Working with other groups to build adaptivity upon existing specs.

Access to web content for symbol users

Augmentative and alternative communication (AAC)

<ul>
  <li><span adapt-symbol="22380">Ingredients</span></li>
  <li><span adapt-symbol="16245">Prepping</span></li>
  <li><span adapt-symbol="22909">Cooking</span></li>
  <li><span adapt-symbol="13690">Plate</span> and taste</li>
</ul>
			

We are only mapping individual concepts to individual symbols—not translating.

Blissymbolics Concepts

AAC Symbol Registry

Authoring tool demo

Authoring/Bootstrapping

• The approach needs input from authors.
• We aim to make this as easy as possible. Authoring-time tooling support is being investigated.
• We've seen things like <main> work very well, because there is wide potential applicability/neatness for developers.
• If we can show the potential gains for users, we can create demand.
• We're aiming for the sweet spot, where a small addition of machine-readable semantics supports a wide range of helpful adaptations.

Further work and explorations

Further work

This work is currently being explored…

Simplification: Many people find too many on-screen options to be problematic. Extra example: someone with a migraine. Simplification demo

Purpose: Icons, symbols and pictograms help people identify the purpose of interactive elements. There are many different icons and symbols. Purpose, action, and destination demo

Action, Destination: Users need to understand what a button will do, or where a link will take them. Purpose, action, and destination demo

Distraction: Content of various types and purposes can distract users.

Roadmap

• Multiple stages to the plan
  • WAI-Adapt Explainer
  • WAI-Adapt: Symbols Module (at wide community review)
  • WAI-Adapt: Help and Support Module
  • WAI-Adapt: Tools Module
• Years in the making, and to come—get in on the ground floor!

Getting involved

Move the needle—your input is critical

We need implementations based on the specification.

• Sites, content
• Extensions
• User Agent changes

More ways you can take part

• There is a wide review of the Symbols Module.
• We need implementations, and feedback from authors, implementers and users.
• You can provide feedback via our GitHub repo—no need to be a W3C member.
• You can follow the mailing list.
• Or even join the group. (Please do!)