• Hi there

    I work for a company based in Ontario, and in January 2014 all companies with 50 or more employees need to have accessible websites, adhering to the AODA (Accessibility for Ontarians with Disabilities Act).

    All websites need to be WCAG 2.0 (Level A) compliant, and I noticed that the coding in your plugin was giving us a bit of an error. Unfortunately I am in no way knowledgable when it comes to coding, and so I am unable to fix this myself. I was curious as to whether or not you had plans to make your plugin compliant with this code in order to assist those who may have disabilities and would use something like a screen reader?

    If you would like to see the errors that were coming up, I used achecker.ca and our company website is http://www.arntstopsoil.com. I would really love to hear back from you! Thanks.

    http://wordpress.org/plugins/advanced-search-widget/

Viewing 3 replies - 1 through 3 (of 3 total)
  • It might help if you listed exactly what the accessibility issues were in this plugin.

    Plugin Author Aaron Axelsen

    (@axelseaa)

    Please provide details – I fixed some things in 0.3 that may solve your problem, but not knowing specifically what your issue is its hard to know what to fix.

    I don’t mean to butt in, and I don’t know why the original poster hasn’t replied. But just out of curiosity after reading her post I went to http://achecker.ca and entered http://www.arntstopsoil.com in its default Web Page URL box. It reported very specifically on 99 “known problems”, including missing labels or labels with no text for input elements. And looking at the elements reported I’d guess most/some of those issues came from forms that are part of the widget.

    There were also lots of other complaints about low-contrast colors on visited links that probably had nothing to do with the plugin.

    If nothing else, I thought the achecker.ca site itself, and the kinds of errors it reported, were somewhat interesting/educational for someone not overly familiar with accessibility issues.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘WCAG 2.0 (Level A) Compliance’ is closed to new replies.