Some statements I've heard every so often about challenges in web accessibility. They reflect common misconceptions that I always try to re-frame into more constructive questions.
- Implementing accessibility features will slow down our development process.
- Accessible design will make our website look boring or ugly.
- We can't afford to spend time on accessibility right now.
- Our target audience doesn't include people with disabilities.
- Accessibility is too complicated and technical for our team to handle.
- We'll add accessibility features later, after the main development is done.
And here's how I re-frame them:
- How can we integrate accessibility into your existing development workflow?
- How can we create an attractive design that's also accessible to all your users?
- How can we prioritise accessibility within your current budget and timeline?
- How might improving accessibility expand your user base?
- What resources or training can I provide to enhance your team's accessibility skills?
- How can we incorporate accessibility from the beginning of your design and development process?
Often it's a matter of changing "this won't work" to "how could this work?"