Potentially complimentary work, or collaboration, with APA WG

Hello all,

Good to virtually meet you! I'm looking forward to following the work here.
My name's Matthew. I'm Head of Web Standards at Samsung Research and
Development Institute UK, and I'm also involved with some efforts in W3C
groups that I think share a similar spirit with this group. I'd like to
introduce those efforts, and invite us to discuss our goals together, so we
can see how we could help each other. Here are the things that I think are
most relevant to your work...

1. The Adapt TF of the Accessible Platform Architectures (APA) WG [1] is
working on ways to introduce small amounts of element- or sometimes
page-level metadata in order to support adaptations to make content more
accessible. We have a fairly long roadmap, but are working on two things in
particular at the moment:

   a. 'Discoverable Destinations' (draft explainer at [2]) which is a way to
signpost different common areas of a site.

   b. Bringing AAC symbols to web content (draft explainer at [3]) which
seeks to help people who struggle to read text to participate on the web.

   We'd love to hear more about the work you're proposing (the issues in the
repo sound very interesting). Would you be able to make an upcoming Adapt TF
call on the 28th of this Month [4] (hopefully the calendar link works for
you)? It would be great to discuss your plans for this group. We may need to
finesse the date, but just wondering if that timeslot could work for you.

2. The Accessible Platform Architectures (APA) WG itself [5] is tasked with
providing horizontal review for accessibility. In non-W3C-speak, this means:
we provide advice to people working on specs (or things that could become
specs) to help them ensure that the things _built_ with those specs promote
accessibility for people with disabilities. We'd love to keep tabs on your
work, and provide advice where we can (possibly linking you up with other
accessibility-related groups at W3C). There are two ways you could seek our
advice:

   a. For any upcoming proposal, say you have an explainer you're working on
- you could fill in this Accessibility Screener [6] - it will result in a
GitHub issue in your repo. Hopefully in future you will be able to add the
'a11y-tracker' label to automatically flag this to APA (so we could either
review it, or just follow the work) - but I just checked and it doesn't look
like your repo has that label, so I've asked if it could be added. In the
meantime, you could point us to anything you're working on that you think
may be relevant by filing a simple request with us (should only take a
minute) [7].

   b. You can always email us on the APA mailing list (I have CC'd both the
Adapt and APA lists).

Once again, we look forward to following your work, and I hope we can be of
help.

best regards,


Matthew

[1] Adapt TF of the APA WG:
<https://www.w3.org/WAI/about/groups/task-forces/adapt/>

[2] Discoverable Destinations (explainer draft):
<https://github.com/w3c/adapt/blob/main/explainers/discoverable-destinations
.md>

[3] Symbols (explainer draft):
<https://github.com/w3c/adapt/blob/main/explainers/symbols.md>

[4] Upcoming Adapt TF call (28th of April):
<https://www.w3.org/events/meetings/54e9a3f5-fd58-4371-be54-5af629aec28b/202
60428T100000/>

[5] APA WG (you can find out about other work APA WG does here, too):
<https://www.w3.org/WAI/about/groups/apawg/>

[6] Accessibility Screener (this was made by the Technical Architecture
Group (TAG), and is designed for early stages proposals, and to be simple):
<https://w3ctag.github.io/accessibility-screener/>

[7] You can point APA WG to the screener results (or anything else you want
to flag with us) by filing a request:
<https://github.com/w3c/a11y-request/issues/new?template=request-a-check-of-
a-self-review.md>

Received on Friday, 10 April 2026 09:31:57 UTC