Recent searches
Search options
Do we as accessibility users have a responsibility to bring accessibility challenges to the attention of developers? Or should developers just know? Asking for a friend
@payown I think it's dangerous to ever assume that anyone ever "just knows" anything. Even if it's duplicating that which they know better to try than not to try.
@payown@dragonscave.space as a dev please do let us know. as Robin said duplicate reports are vastly preferable to nothing
@payown In terms of reality? For the time being, it is our job, since nobody else is educating them. However, I do find it very sad that accessibility and consideration for so-called "disability" wasn't part of mainstream training, or even elementary education, years ago.
@payown I we should. Reality has shown that despite efforts on creating guides and guidelines, they can be easily overlooked.
@payown I think it's somewhere in the middle. If it's a corporate accessibility thing, users need to constantly demand better accessibility so that these data-based corpses get the data that these things are important. But also developers should definitely know some things about accessibility.
@payown yes, we should really be bringing accessibility challenges to developers' attention, but I also agree that it's a sad state of affairs they don't always pick up on these things.
When I first started designing websites, I only knew what I knew, and what worked for me. And what the programs I used allowed.
Most individuals creating blogs and small sites likely don't have much tech knowledge. They use a drag and drop builder.
For those over age 45, we didn't have tech in school. Schools rarely had computers, only in the last year or two of high school. Maybe.
A lot of use missed what we need to know.
Of course super techy's can't communicate with nontechy's what they need to know, since techese is not written, and very difficult to learn by sound. Especially for people with late life hearing loss as well as late life vision loss.
So, and individual, yeah, they likely don't know.
Corporations that pay techy's, they should know.
@payown As a sightling, I try to remember to test for accessibility in the apps I test and recommend. If I find issues (with my rudimentary VO skills), I always let the developer know. I would say 90% of the responses I get are positive. In some cases the tools are mostly accessible and the devs are often surprised that it was accessible at all and excited to find out and get problems fixed.
@payown Probably a bit of both. But developers should have the basic idea down, or be willing to learn it. I don't mind filling in some specifics especially if it leads to a more efficient workflow.
@payown It's a mix of both.