WAI develops strategies, standards, supporting resources to make tech accessible to people with disabilities. Accessibility: Essential for some, useful for all.
Ah, this issue is too complex to address in tweets. (basically: has some value, yet lots of significant caveats, e.g., a couple mentioned here: w3.org/community/wai-engage/…)
To get multiple perspectives, send e-mail to WAI IG Discussion List per w3.org/wai/ig#mailinglist
Do you want guidance on teaching accessibility? Are you procuring a course and want guidance comparing options?
Check out W3C WAI’s new designer modules in:
Curricula on Web Accessibility
w3.org/WAI/curricula/#a11y#w3c#curricula@teachaccess#HigherEd
Hi Anton. Happily the human contact promptly replied to your e-mail message. :) Please accept my apologies for additional delay. We have multiple people out with medical issues or otherwise not available. Thanks, ~Shawn
Inaccessibility of CAPTCHA (Update) is now published as a W3C Group Draft Note: w3.org/TR/turingtest/ The document looks at cryptographic authentication to verify the user is human, via W3C technologies that remove the need for interactive CAPTCHAs. #accessibility#a11y
w3.org/blog/2021/12/idpd/
Learn about #accessibility translations. And language around speech recognition, voice recognition, description of visual information (audio description, video description, described video), color blind, contrast (luminance contrast, color contrast).
Register today for the online research symposium
"Shape the Future: Research and Development Questions in Digital Accessibility". #a11y#accessibility
For agenda and link to free required registration by
7 November, see: w3.org/WAI/about/projects/wa…
How do you know if a digital textbook or other publication is accessible? The technical metadata isn't clear to most. Enter:
"User Experience Guide for Displaying Accessibility Metadata"
w3.org/publishing/a11y/UX-Gu…
(Comments welcome in GitHub or e-mail.) #a11y#EPUB#metadata
Here is an example of the [Expand All Sections] [Collapse All Sections] buttons: w3.org/WAI/teach-advocate/ac…
We’re interested if that would help the use case you describe? Seems it could significantly decrease scrolling needed.
~Shawn
2/2
Hi Tash. Thank you for the input.
I added it in github.com/w3c/wai-wcag-em-r…
We won’t be able to get it in this update. We might be able to add [Expand All Sections] [Collapse All Sections] buttons in this update, which should help some. github.com/w3c/wai-wcag-em-r…
1/2
Good news: We are now actively working on updating this resource. This pull request is near the top of the list to address. We ask for a little more patience as the new folks learn what is needed for reviewing and updating the policies listings. Thanks.
You are invited to the research symposium "Shape the Future: Research and Development Questions in Digital Accessibility" online 10 November 2021. For submission information and free required registration dates, see: w3.org/WAI/about/projects/wa…
So sorry to hear that. 1. We will submit this issue to edX.
2. It would be helpful if you would also send it to accessibility@edx.org
3. I also need dark mode (+ line spacing). I use Stylus, and it works well on the edX course. e-mail me if you want help with that. ~ Shawn@w3.org
Hi Abbas! If it's the Firefox toolbar, perhaps this will help? support.mozilla.org/en-US/kb…
I encourage you to submit accessibility feedback to the toolbar vendor. Here are some tips for providing accessibility feedback to vendors: w3.org/WAI/teach-advocate/co…
~Shawn
The XAUR document is for designers and developers involved in creating immersive and augmented experiences. It’s also useful for anyone who wants to better understand accessibility in a range of immersive or augmented environments.
@w3c#XAUR#a11y#VR#AR#XR