For all the web developers out there, are you intentionally leaving out ADA and WCAG accessibility compliance from your client agreements? Also, do you think this approach would hold up in court if challenged?
5 Answers
I shared a link to a similar discussion in another thread. Maybe that could help you think through this topic more.
I've noticed some teams trying to wiggle out of it by adding statements like "does not include full ADA/WCAG compliance" in their contracts. But honestly, that won't really protect you if a lawsuit comes up. It's best to define what you'll test, what isn't included, and to remember that true accessibility is a process. Courts generally care more about the end result than what's written in the contract, so plan for it from the start!
It's definitely a matter of professional responsibility. Just like an electrician should use the right materials, web developers should prioritize accessibility. Ignoring it can lead to serious liabilities.
Only include it if it's necessary for the project, and if that's the case, definitely factor it into the costs. This is especially true for governmental projects. Sometimes, I pass the compliance responsibility to a third-party tool that's more about the framework rather than the design itself.
You should definitely consider accessibility when developing for clients, especially if they plan on monetizing the site. Excluding users isn't a good business strategy! It might be worth including these considerations in your overall costs.
Totally agree! Accessibility isn't just a checkbox, it's crucial for user experience.