[zersiax]

That is pretty much my dayjob :P Although I'm also a developer myself so can argue from both the blind person's view of "This button doesn't tell my screen reader what it's meant to accomplish", as well as the developer's point of view of " You simply forgot to add an accessible label, don't you dare tell me you don't have capacity to fix something that'd take 10 seconds to fix". ;)

[yencabulator]

The argument is we don't have capacity to learn what needs to be fixed, and it's the unfortunate truth that figuring out other things instead generally has better ROI :-(

[zersiax]

That is the sad part, yeah. You'd think with the ADA existing since the early 90s things like coding bootcamps and CS college degrees would spend more time on this but they really, really don't. I taught that class myself to my peers when I was in college which is depressingly bad, but I'm at least glad I was able to pass that, what we now call, native experience along, i guess. That's really why I stream now, as well.

[yencabulator]

Concrete "this to that" examples are worth their weight in gold[1] for how to make simple steps forward in accessibility, along with some sort of a demonstration of how it changes the experience.

I'm sitting on a codebase with ~20 HTML ARIA warnings from SvelteKit's lint and frankly don't expect to get to fix them any time soon. I'd like to, but there's always something else to put the effort into. And that's when the framework is trying to nudge me in the correct direction, not active effort!

[1]: So, frankly, not that much: https://www.npr.org/sections/krulwich/2011/12/21/144066248/l...

[zersiax]

Feel free to come find me on Masto or similar and AMA. That goes for all of you. Not auditing for free, but happy to answer questions/figure out ARIA warnings or whatever. Linting issues like that are probably stupid easy to fix once you know what's actually going on and I'll happily save you the MDN trip :)