TPAC Actions Inside: Register and Promote Breakout

Hi all,

As you know, the Post-Source report is now published! Time to bring on the wider discussion!

Our first and best opportunity is in just a few days, so act now. Our upcoming TPAC 2025 Breakout session is scheduled for Wednesday 12th November at 10 AM Japan time: that means, Wednesday 1 am London time and previous day, Tuesday 11th November 8pm NYC time. Watch your time zone!

  1.
Please register for TPAC to allow your remote participation. The link opens on Monday the 10th, so kindly set yourselves a reminder. Registration link, https://www.w3.org/register/tpac2025
  2.
Please promote the breakout session in your channels. The session link is here, https://www.w3.org/events/meetings/c986882c-0da9-48d9-8eab-6313cde178ea/

Helpful links:

  *
We created a short link to our document that’s easily communicated verbally, https://bit.ly/a11yedge

  *
The long link to our report: https://www.w3.org/community/reports/a11yedge/CG-FINAL-a11yedge-capabilities-20251104/
  *
The blog announcement is here, https://www.w3.org/community/a11yedge/2025/11/09/w3c-accessibility-at-the-edge-community-group-report-is-published/

Our announcement text below:

The W3C Accessibility at the Edge Community Group announces publication of its Final Report addressing the trade-offs and benefits of applying dynamic accessibility remediations to web content<https://www.w3.org/2023/09/breakouts/recording-51.html>. Today’s typical web page is a complex blend of multiple original sources, yielding experiences that work well for some users but fail for others, leaving many websites and online applications inaccessible to people with disabilities. In development since Fall 2022<https://www.w3.org/community/a11yedge/2022/10/07/tpac-2022-overlays-breakout-report/>, the report titled: Accessibility Capabilities: Post-Source Code and Content<https://www.w3.org/community/reports/a11yedge/CG-FINAL-a11yedge-capabilities-20251104/> features cross-references to WCAG<http://w3.org/tr/wcag> throughout, because WCAG remains the valid yardstick whether applied in-source or post-source.

Comments are welcome in the github, a11yedge/capabilities<https://github.com/a11yedge/capabilities/> or by sending an email to the list, public-a11yedge@w3.org<mailto:public-a11yedge@w3.org>.

A special thanks to the W3C Information Architecture Community Group<https://www.w3.org/community/informationarchitecture> for their assistance.

Thanks again for everything you did to contribute to this important report.


  *
Lionel


--
Lionel Wolberger, Ph.D.
VP Business Operations
Level Access
https://levelaccess.com
https://userway.org