Listening to the web, part one: thinking in accessibility
Part 1 of a 3 part series in which I share my thoughts on thinking about accessibility while developing and working with screen readers
- Part 1: thinking in accessibility
- Part 2: it’s all semantics
- Part 3: working with screen readers
“We have some concerns around the way some of the form controls are designed. They’ll need to be completely customized in order to make them keyboard accessible and match the design. This means more time will be spent coding and making sure they’re usable. It also means a slightly longer loading time.”
“Yes, okay that’s fine. Just make it work.”
“We also wanted to bring up issues we found with the colour contrast of the primary text. The way things are now it will be difficult to read for some people who may have low vision…”
“Listen, we don’t care about accessibility. We just want the site to look as it was designed. Let’s move on.”
This was an actual, slightly paraphrased, conversation I overheard between my agency at the time and a design firm. I was floored.
We don’t care?
