The votes are in, looks like #biden won this one, sorry #trump
"Both sites are better than average pages found in the #WebAIM Million, but both could improve significantly with a few relatively simple changes that would not require throwing out an entire widget or design. They would just involve tweaks to what’s already there."
As a front-end developer, there are some things that jumped out to me in the recent screen-reader survey. I'll share a couple of them, but keep in mind that I don't typically use a screen reader myself. You can take a look at the results yourself at:
A few words on the results of the #WebAIM Screen Reader #a11y survey, as they have just come out:
The results are likely not very representative of current screen reader usage at all, as the survey targets the same audiences each year. They are completely missing out on #blind people who are not as competent with computers - and to become competent gets harder and harder each year.
Finally got around to completing the #WebAIM Screen Reader Survey and noticed that they still list Window Eyes as a choice for primary screen readers. Is anyone still using Window Eyes in 2024? Surely updates to UIA and #accessibility APIs in Windows 10 have rendered it almost unusable at this point for real productivity, let alone Windows 11.
#WebAim#Screenreader survey is open until January 31, 2024. If you're a Screenreader user or know someone who is, ask them if they want to participate.
I always found the results very interesting, especially when it came to headings / heading levels. It helped to make a point why this is so important (and easy to implement and fix).
I don't think #WebAIM has an account on the fediverse yet, but the 10th iteration of their Screen Ready survey is now live.
The vital #a11y insights created from these surveys help inform our understanding of the technological and usability landscape. This helps to shape how accessible, and importantly usable experiences are created on the web.