[November 15, 2019 Update: The company that delivered the 66 million dollar website (described in this post) to the State of California tried to get the case thrown out of court. The judge said no. Read an article about the judge’s Order. Read the judge’s Order in the case.]
[Start of original post] Imagine this: Two companies charge the State of California sixty six million dollars to build a website for a state park reservation system. (Yes, $66,000,000.00). The contract requires the website to work for all California residents, including those with disabilities. (In other words, the website is supposed to be accessible.) The website gets delivered and rolled out, but is not in fact accessible.
These are the facts alleged in a lawsuit filed earlier this year by the disability civil rights firm TRELegal. The lawsuit seeks damages on behalf of the State of California and injunctive relief on behalf of a blind representative plaintiff. I’ve illustrated this post with an image of a pile of money — money that would have been better spent building accessibility into this website.
The press release announcing the case is titled “Fraud Whistleblower Seeks Redress for Inaccessible Public Website that Cost California $66 Million.” You can read the whistleblower press release here.
- Jump to a Simplified Summary of this Article, a feature of this website designed to meet WCAG Success Criteria 3.1.5 (a WCAG 2.1 AAA Reading Level requirement).
Accessible Procurement Matters
At its core, this web accessibility lawsuit is about procurement. It is a serious civil rights case brought by a respected civil rights firm with a lesson for anyone selling and purchasing technology.
The lesson? It is not enough to put language in a contract and hope for the best. Technology must be tested for accessibility and usability throughout the development process, on delivery, and once it is in use. Especially in a situation like this, where accessibility was identified as a deliverable, remediation must happen before roll-out.
And not just automated or even manual accessibility testing. Websites — and all digital technology — must be evaluated by a cross-section of users with disabilities to ensure the technology will really work for everyone. In the California whistleblower case, the website at issue was for a state-wide park reservation system.
How hard would it have been to bring in groups of disabled users along the way to make sure the site could be used by all Californians, including those who cannot hold a mouse, see a screen, or hear audible content? Couldn’t some of that 66 million have been allocated to real usability testing?
The access barriers behind the whistleblower suit should have been identified long before the site was deployed for California residents. A robust accessible procurement process would have helped bake accessibility into every element of the process. [A new resource from the non-profit Disability:IN that I helped develop offers tips and best practices for developing such a process. Visit Disability:IN’s Disability:INclusive Workplaces – Accessible Technology Procurement Toolkit]
In his firm’s press release, attorney Tim Elder compares the park system website to a physical building without a ramp:
California’s taxpayers should be outraged that they’re paying big money for such a shoddy website. The disability access violations are on the level of a new multimillion-dollar public rec center built with stairs up to the front door and no wheelchair ramp.” Timothy Elder, Principal Attorney at TRE Legal Practice.
It is 2019, and long past time for technology to be born accessible. I cannot predict what will happen with this lawsuit as it makes its way through the court system. But regardless of outcome, I invite technology purchasers and developers to take its core message to heart: be sure the technology you are purchasing can be used by everyone, and remember that “everyone” includes people with disabilities.