WAI develops strategies, standards, supporting resources to make tech accessible to people with disabilities. Accessibility: Essential for some, useful for all.

worldwide
Joined April 2009
XR Accessibility User Requirements (“XAUR”) is now a published W3C Working Group Note: w3.org/TR/xaur/ XR refers to hardware, applications, and techniques used for virtual reality or immersive environments, augmented or mixed reality, and other related technologies.
2
14
5
26
W3C’s annual meetings (“TPAC”) will be virtual in October 2021. One of the ways @W3C is encouraging diversity and inclusion is providing funds to support participants. #a11y See: Inclusion Fund and Fellowships for TPAC 2021 w3.org/blog/2021/06/diversit…
1
10
10
We’re excited to announce an open European-based position: Web Accessibility Development and Operations Lead What an opportunity to help drive development of accessibility standards and resources! @a11yjobs Check out: w3.org/Consortium/Recruitmen…
1
11
12
Replying to @a11y_mmo @xrhubnue
Hope these help: XR Accessibility User Requirements w3.org/TR/xaur/ and Authoring Tool Accessibility Guidelines (ATAG) Overview w3.org/WAI/standards-guideli…
1
1
Replying to @JonathanDHolden
Hi Jonathan. Thanks for the note. We're working on a better way to present the different versions.
1
We encourage you to start with online resources from W3C WAI. They cover a wide range of situations: "Where do I start?", "Why is it important to include people with disabilities in the process?" & much more. See annotated list of #a11y resources: w3.org/WAI/resources/
1
Getting the "Global" in GAAD. Today you can support Global #Accessibility Awareness by telling others about @W3C WAI resources in 35 languages! w3.org/WAI/translations/ Also links to #WCAG 2 Authorized Translations and in-progress drafts. #i18n #a11y #translation #GAAD @gbla11yday
2
25
2
18
We have defined 2 technical approaches for author-controlled pronunciation in: Specification for Spoken Presentation in HTML w3.org/TR/spoken-html/ Now we would like more input on which approach to refine into a @W3C Standard. #PersonalAssistant #SmartSpeaker #ScreenReader 3/3
3
2
The @W3C WAI Pronunciation Task Force has been exploring this from multiple perspectives: users, content providers, voice assistant developers (“implementors”). For an intro to the issues and links to analysis documents, see: Pronunciation Overview w3.org/WAI/pronunciation/ (2/3)
1
3
3
We pronounce the acronym W-A-I as “way”, but #ScreenReaders and voice assistants often pronounce it “why”. e-#GAAD If only we could define how to pronounce it… This is one example of the reason for W3C work on pronunciation standards. There are more serious examples. (1/3)#a11y
1
18
1
32
That page in العربية , čeština , Deutsch , Ελληνικά , español , français , Bahasa Indonesia , 日本語 , 한국어 , Nederlands , Português do Brasil , русский , язык , 简体汉语 plus additional subtitles فارسی , ગુજરાતી , हिंदी , Magyar , Italiano , कोंकणी , മലയാളം , मराठी , తెలుగు
1
4
Replying to @fstorr
Indeed it did. We need to update that in a couple of places. (please don't go looking for them ;-) It is now updated in w3.org/WAI/standards-guideli… (And I say thank you for the note -- and it's nice to know folks are reading carefully!) ~Shawn
1
Thanks. Fixed. They now go to WCAG 2.2 glossary. ~Shawn