***Update*** 6/25/2015: I finally got a response to my letter telling council and top management staff about accessibility issues with the newly-launched city website. Someone had handed off the letter to DeKalb’s management analyst, Lauren Stott (one of the staff members who withheld estimates for a simple accessibility fix vs. a complete redesign, despite direct requests for this information from council members). Here’s what she said:
Thanks for your email. The City has worked with CivicPlus to ensure website accessibility is provided for all users. Web-based accessibility checkers such as wave.webaim.org and Powermapper.com access a website’s html code, but aren’t as effective in assessing content customized with CSS (Cascading Style Sheets). The City of DeKalb’s website, in its state of being fully customized, heavily utilizes the CSS design language along with html. Therefore, the Web-based accessibility checkers register items on the site as errors, when in fact they just represent a departure from the typical html language the accessibility tools are designed and equipped to assess. In its contract with the City of DeKalb, the website developer has agreed to follow not only Section 508 of the Rehabilitation Act but also Web Content Accessibility Guidelines 2.0. The portion of the agreement that outlines those specific requirements is included below.
1. While the contract might call for complying with WCAG, that is certainly not what happened. The “Accessibility” page on the website says the site conforms to Section 508 of the Rehabilitation Act, period. Another “tell” is the color contrast problem. Section 508 only mentions contrast in that it requires that applications not interfere with user settings. WCAG 2.0 requires a contrast ratio between text and foreground be set within a certain range. Many pages do not meet this requirement, such as the “Job Opportunities” page that, according to the WAVE checker, contains 27 contrast errors between background and link text.
WAVE evaluates page accessibility after CSS has been applied and account for CSS in identifying potential accessibility issues. The developer’s explanation is not accurate. Each of the errors identified by WAVE indicate an actual end user accessibility issue.
I told Lauren Stott I didn’t wish to discuss this anymore with a person whose word I can’t take at face value. Then I invited city council members to send Stott’s explanation to accessibility checker websites for themselves.
* * * * * * * * * * * * * * * * * * * * * *