Jump ahead four years and open data is on almost every major government website. Embedded into the site, most users can gain access to large data sets. However, for individuals using assistive technology, or requiring additional tools to help with engagement, garnering usable information from these data sets is virtually impossible.
One of my co-workers accesses the Internet through the most commonly used screen reader, JAWS. When I sent him the link, he called me over and said, “What is on my screen? It’s just reading me jumbled numbers.” I called the open data company and asked the technical support team if their platform worked with screen readers. They responded that it depended on which one, but since they are 508-compliant, “it should.” I said thank you and hung up the phone.
Wishing that her answer had been different, I was brought back to something I talk about every day: 508-compliant does not mean accessible. It would be like building a ramp into a restaurant at an angle so steep that no one in a wheelchair could access the door. It isn’t actually accessible, but technically there is a ramp.
I have conversations like these all too frequently. When talking about accessibility, I hear that there isn’t enough of a reason to be accessible in the commercial sector. On the government side, development contractors assure program managers that they have met basic 508 compliance, but their websites are still inaccessible. These inaccessible websites leave behind users that need assistance engaging with content despite the current federal mandate. Companies must look for additional ways to solve their accessibility issues. When it comes to data tables, charts and graphs, there are specific Web accessibility best practices that must be adhered to in order to ensure access for all users. Open data companies hold a set of invaluable tools for citizens and that comes with a responsibility to maintain accessible websites. Equal access for all is not optional.
