- From: Janina Sajka <janina@rednote.net>
- Date: Tue, 28 May 2024 12:23:22 -0400
- To: Accessibility at the Edge <public-a11yedge@w3.org>
Colleagues: I have just pushed edits to our Capabilities document reflecting decisions from our teleconference discussions last week. As always our document is here: https://a11yedge.github.io/capabilities/ You'll recall we determined our Accessibility Statement subsection needed to be broken into two sections. That is now accomplished as: 6.2.2 Accessibility Statement Provisioning 7.1.2 Accessibility Statement Discoverability I have also chased down a few markup errors in the Javascript H1 section that will, hopefully, clear up strange display artifacts we see as we continue work to finish defining our consensus on feature automatability. We have 11 of these remaining beginning at: 6.2.3 Accessibility Provider Identification Lastly, I have added "Does Not Apply" to our automatability categories in the Introduction. In working on that I have noticed we shifted from "many cases," the category we identify in the Introduction, to writing "most cases" as we consider features. Something to return to at some point, I suppose! Looking forward to greeting you on our call Wednesday, Janina -- Janina Sajka (she/her/hers) Accessibility Consultant https://linkedin.com/in/jsajka The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI) Co-Chair, Accessible Platform Architectures http://www.w3.org/wai/apa Linux Foundation Fellow https://www.linuxfoundation.org/board-of-directors-2/
Received on Tuesday, 28 May 2024 16:23:28 UTC