Why WebAIM’s Report Only Found 6 Issues on a Million Pages, by (not on Mastodon or Bluesky):

Why WebAIM’s Report Only Found 6 Issues on a Million Pages, by (not on Mastodon or Bluesky):

I am using this great tool from https://wave.webaim.org/ for web accessibility, does anyone else use it?
I wonder if there are any alternatives that is better.
#til <progress> elements need labels for #accessibility
I think because I've only used one in the context of a form's submission I figured it was unnecessary to label it for visual or non-visual users, but I'm sure I'm being ignorant of something, so I'll add a "form submitting" label! I also learnt about aria-busy and aria-described by to point to the progress.
https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/progress
Thanks to #WebAIM's #wave accessibility checker extension:
https://addons.mozilla.org/en-GB/firefox/addon/wave-accessibility-tool/
How to Audit Web Accessibility With [the] WAVE Extension, by (not on Mastodon or Bluesky):
For those who don't know, WebAIM @webaim is a non-profit service centre operating out of Utah State University.
They run the WebAIM Million project, which reports on the accessibility of the home pages of the top 1000,000 websites. [1]
Over the years, I've found their resources on Creating Accessible Documents to be a reliable link to share with folks to begin learning about document accessibility. [2]
[1] https://webaim.org/projects/million/
Sad news: the WebAIM mailing list is shutting down on August 27.
The archives will remain available.
Since 1999, the WebAIM @webaim email list has distributed discussions on web accessibility and provided a virtual community for a diverse range of members. I've been subscribed since 2002, and I learned more about accessibility from the list and its members than from any other single source on the web.
End of an era.
3 Tools to Help Fix the Web’s Most Common WCAG 2.2 Failures, by (not on Mastodon or Bluesky):