Funcertainty (sic) with WAVE

I had the surreal experience not too long ago of working with another developer and seeing radically different results through the WAVE Web Accessibility Evaluation Tool. While he saw only 2 errors, I saw over 300.

After comparing notes, we realized I was using the Chrome Extension while he was using the online version of the WAVE Web Accessibility Evaluation Tool. This wouldn’t normally matter, but the development server was using HTTP (port 80) instead of HTTPS (port 443). Since the online WAVE tool was using HTTPS, it was blocking out large portions of the content from the development server which contained issues.

What’s the takeaway?

  • If your development server still uses HTTP, you should upgrade to HTTPS
  • Use a WAVE browser extension instead of the online WAVE tool

Please do not “click here”

I want to tell you a story:

Once upon a time, there was a large public organization with a large staff of web content curators. These curators dealt with a lot of content, and would often use ‘click here’ in their hypertext links to help users move between pages. ┬áLike this:

For a copy of the full summer reading list, click here.

To see only the Elementary level list, click here.

To see the Intermediate level list, click here.

To see the High School level list, click here.

Everyone did it, because that’s how everyone else was doing it, and no one had ever said there might be a valid reason for it to be done differently.

Continue reading “Please do not “click here””