A while back I linked to an article at Jim Thatcher’s site that showed his accessibility test results on whitehouse.gov. He recently ran some checks on Accessibility of Recovery.gov and got quite a few accessibility errors at that site, too. As he explains in A Postscript on Recovery.gov the official response to his article was a bit “disappointing.”
Since Section 508 Accessibility Standards requires government web sites to comply with accessibility standards, it’s surprising that the results are so blatantly bad. They include missing alt text and lack of proper heading semantics.
The surprising thing about this story and the response to it is that we have watched this administration use technology so well and show an understanding of technology issues. This business of getting it wrong in terms of accessibility is a bit odd.
I, for one, expect this administration to get it right.
There’s a draft version of an article at the W3C about Contacting Organizations with Inaccessible Websites. Here are some ideas from the section on how to approach such organizations.
There are several ways you can let an organization know that there are accessibility problems with their website, including:
- Contacting them directly
- Seeking assistance from a local or national disability or older peoples’ organization
- Taking a more public approach via the press or through online platforms after contacting the organization without resolution
Regardless of the approach you take, you will need to clearly describe the problem being experienced:
- Which page; which part of the site
- What the problem is; what you were trying to do
- If possible, tell them about your computer and software
My approach is obviously to take the public route. I hope people using the technology to access the site who can list the problems error by error will take some time to contact them with specific errors.
It isn’t enough to expect them to get it right. We need to insist it be done right.