3 ms·
It goes deeper than that. At my enterprise company, our accessibility department explicitly does not gather any data on our users with accessibility needs. We d
by jbob2000 8y ago
It goes deeper than that. At my enterprise company, our accessibility department explicitly does not gather any data on our users with accessibility needs. We don't know who they are, what problems they are facing, or if our solutions work for them or not. The reason? It would infringe on their "rights" (What rights are these? I didn't press further).
What they do is hire a few people with visible disabilities (wheelchair or missing limbs) and then parade them around to development teams to shame us into accessibility "compliance". It is a gross process involving lots of trial-and-error.
- extra88 8y agoPrivacy rights, including personal medical information. Additionally, counting how many people are affected by a particular accessibility barrier too often leads to ignoring them because the numbers tend to be small. > gross process involving lots of trial-and-error. That can be reduced through developer education and changes in processes but doesn't that also describe browser and device testing; it's part of the job.
- anoncake 8y agoHow do you even make a website that is not accessible for wheelchair users?
- DanBC 8y agoOne example: You have fucking tiny up and down vote buttons that aren't separated by anything and you make that vote unchangeable. This means people with motor control disabilities -- some of whom will be wheelchair users -- can't reliably vote using the website supplied buttons. Simple changes are to make the buttons bigger, and to separate them with something other than whitespace, and to allow some changing of the vote.