Search

Items tagged with: a11y





#a11y






Many apps are inaccessible for blind/VI people. Developers usually have to implement #Accessibility features from scratch for each platform they develop on, which can scare them away. The good folks over @accesskit are trying to change that with their #Foss project, #AccessKit. Their goal is to create a cross-platform solution for accessibility that only has to be implemented once. I'm posting this to spread the word. Let's help them reach their goals! accesskit.dev/ #Blind #A11Y





Of course TwitterWrite is inaccessible.

• 10,000 characters with no `<p>` or other breaks between paras (all one `<span>`).

• Bold text is in `<span class="r-b88u0q">`

• Italic text is `<span class="r-36ujnk">`

twitter.com/TwitterWrite/statu…

#a11y #accessibility




I failed to note WAI’s Pronunciation Task Force nor did I mention its draft spec in my post, so I added them as an addendum as well as a great comment from Brennan Young on an old post of mine that relates:
adrianroselli.com/2023/04/dont…

#a11y #accessibility


The "Report link destination" command in NVDA 2023.1 is very popular. Press NVDA+k to report exactly where a link goes. This is an important #security feature for users. Do you use it? Read more in our In-Process blog: nvaccess.org/post/in-process-6… #a11y #ScreenReader #NVDA





@ebassi Both bug reports are missing what‘s the cause for Orca failing. Is there some kind of project that lists issues to get #a11y on par again?