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
Filter
Exclude
Time range
-
Near
How to Make Your Presentations Accessible to All w3.org/WAI/teach-advocate/ac…
1
4
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
For example: Video Introduction to Web Accessibility and W3C Standards w3.org/WAI/videos/standards-… is a 4-minute video that introduces @W3C WAI's perspective that Web accessibility is: ✨Essential for some, useful for all.✨ (more in w3.org/WAI/perspective-video…)
4
2
7
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
Many thanks to all who have translated @W3C accessibility resources: w3.org/WAI/translations/ If you might want to contribute new translations or to updating existing translations, see: w3.org/WAI/about/translating… #GAAD #i18n #a11y #accessibility #translation @gbla11yday
2
21
3
28
That page in العربية , čeština , Deutsch , Ελληνικά , español , français , Bahasa Indonesia , 日本語 , 한국어 , Nederlands , Português do Brasil , русский , язык , 简体汉语 plus additional subtitles فارسی , ગુજરાતી , हिंदी , Magyar , Italiano , कोंकणी , മലയാളം , मराठी , తెలుగు
1
4
For your GAAD event, would you tell others about @W3C WAI accessibility awareness resources in many languages? For example: Video Introduction to Web Accessibility and W3C Standards w3.org/WAI/videos/standards-… #GAAD #i18n #a11y #accessibility #translation @gbla11yday
1
26
2
49
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
Agree some will end up on specific page, not overview. Date was already there, e.g., "Last Updated: 4 April 2017 – Added Netherlands accessibility laws and policies." It's just not as clearly highlighted. Will consider for next update. Thanks.
1
Yes, it needs updating. Thankfully we recently got resources to update it. That should happen later this year. I added an additional note to the top of the first page to help people know that it’s not the latest info now. ~Shawn
3
2