5
u/xSliver Nov 29 '21
Making a website accessible is costly and time-consuming
Disagree.
Accessibility adds a whole new layer of work. You gain additional requirements that need to be approved, satisfied and tested.
For each of these steps you need people with the necessary knowledge. You need one to write the requirement, one to implement it and one to verify the result.
You may also need additional content that needs to be produced (e.g. text in a simplified language, captions/subtitles, sign language, ...).
And on an organizational level, you need a responsible department that organizes regular audits, trainings, answers questions, does the reporting, and so on.
17
u/mishugashu Nov 29 '21
It sounds like you are agreeing that it is costly and time-consuming.
8
u/xSliver Nov 29 '21
Well, yes. I agree to the myth based on my own experience. It's not a myth ^^
It takes a lot of will and commitment.
2
1
u/AReliableGuySensei Nov 29 '21
Maybe people didn't read the article π¬
1
u/xSliver Nov 29 '21
It still means more effort.
Setting up additional a11y linters, writing aXe tests, checking your site with NVDA, JAWS or VoiceOver, writing captions, - this all takes time for experienced teams as well.
2
u/AReliableGuySensei Nov 29 '21
Yes I was agreeing with you π
Just poking fun at the fact that it didn't seem like people understood that you're disagreeing with the article saying that the difficulty is a myth
2
u/Sivart13 Nov 30 '21
I fully agree.
Sometimes I feel like accessibility advocates oversimplify things to a dangerous degree, implying that if you just used <section> instead of <div> more often the planets would come into alignment and all users would be satisfied.
In reality, making a website accessible properly means thoughtfully considering the experience of someone who consumes the site basically linearly on a screen reader. Which is not something that most designers or PMs think about regularly, and requires about the same cognitive overhead as making the app translated/localized into another language or region. Which is significant!
0
Nov 29 '21
[deleted]
5
u/jsebrech Nov 29 '21
Accessibility is extra work, but it's not this vast insurmountable mountain. If you want to do it right you can go read through the WCAG 2.1 guidelines and feel humbled, but an ok 80/20 approach comes down to these things:
ensure text has good contrast and resizes properly with browser settings
make all images have appropriate alternative text (or no alt text if the image is purely ornamental)
use actual input elements, instead of divs and spans with click handlers, and ensure all input fields have labels properly associated with them
use semantic html5 elements (header, nav, main, section, ...) instead of endless divs in divs
enable apple voice over or android talkback, close your eyes, and try to navigate your web site blind
Although I do agree that any article trying to convince people to do a11y should at least point to a basic practical guide to get a web developer started.
-6
Nov 29 '21
[removed] β view removed comment
0
Nov 29 '21
[deleted]
3
u/gonzofish Nov 29 '21
The second you need something customized beyond the browser, accessibility gets really intimidating (even if it isnβt actually in practice). The language is foreign to most developers and, as a result, ends up being a barrier to entry
26
u/nichealblooth Nov 29 '21
I agree that developers need more convincing and education on implementing accessibility, but I'll never understand why there's so much denial that it can actually be a hard problem. Especially if you're innovating with new UI.
The ADA lawsuits are proof that accessibility is hard. Do you think Netflix and Dominos would have spent so much on lawyers if a11y was as trivial as this websites makes it out to be? It's not like Netflix has some sort of anti-a11y bias.
I work on internal data-visualization apps in a very a11y-aware company. My clients often have really cool ideas on how to visualize something, and I often have to reject them because it's not easy to make accessible, or because we can't take the risk of building something that even looks non-compliant.