Categories
links usability writing

Links: Don’t “Click Here”

So it’s the end of 2013, and sadly, the phrase “click here” continues to be used in text links all around the web. This is poor usability, accessibility, and sure makes the author look silly!

Reasoning

  • “Click” places focus on mouse mechanics (and many people don’t use a mouse).
  • “Click here” hides the target of the link; it’s not a good call-to-action.
  • Poor for visually scanning the page.
  • Users must make the extra effort to read before or after “Click here” to determine to where the link goes. (Don’t make me think!)
  • “Click here” has no context for when a list of links is provided to the user by the user agent.

Examples

To correct the problem, don’t use phrases like “click here” but use meaningful phrases which make sense out of context.

Before: I like the beaches herehere, and here.
After: I like the beaches in Maui, Sarasota, and Saugatuck.

Before: Click here to see if your bill is ready yet.
After: To see if your bill is ready, check the foo app.

Do you have any other examples?

Supporting articles

  1. Why Your Links Should Never Say “Click Here” (Smashing Magazine)
  2. I Don’t Want to Read More or Click Here (Karen Mardahl)
  3. Don’t say ‘click here’ on link text (goodusability.co.uk)
  4. Links and Hypertext (WebAIM)
  5. Click Here and Other Link Text (Jim Thatcher)

Notes

  • In addition to “click here”, the same can be said for “read more” and other similar link phrases.
  • Except for tool tips available to mouse users, the title attribute adds no value (touch devices, keyboard users, most screen reader users).
Categories
conference expert podcast

Podcast #98: AHG13

The 16th Annual Accessing Higher Ground Accessible Media, Web and Technology Conference (hash tag #AHG13) was held recently in Westminster, Colorado at a very nice venue, the Westin Westminster. Representing my day-job employer, I was able to attend and present one session, Usability and Accessibility CSS Gotchas. I was happy to learn that it was being recorded and live broadcast over one the conference’s two virtual tracks. While there, I had the opportunity to interview a few great folks in the business; namely, Greg Kraus, Jayme Johnson, and Kathy Wahlbin. Have a listen!

Download Web Axe Episode 98 (AHG13)

[transcript of podcast 98]

Greg Kraus Greg Kraus (@gdkraus), the University IT Accessibility Coordinator at North Carolina State University. He presented The Gamification of Accessibility, which included details about a great online tool he implemented at NCSU.

Jayme Johnson Jayme Johnson (@hippyjo), Instructor at HTCTU The High Tech Center Training Unit, provides training and support to the faculty and staff of all California Community Colleges. Jayme was on the panel at the plenary lunch during the second day of the conference.

Kathy Wahlbin Kathy Wahlbin (@wahlbin), CEO/Founder of Interactive Accessibility and invited expert in the W3C. She presented Accessible Responsive Web Design.

I met Greg and Kathy in person for the first time which was great. I also met keynote speaker David Sloan (@sloandr) in person for the first time as well. Wonderful people.

Categories
application socialmedia twitter

Easy Chirp 2 soft beta launched!

Web Axe author Dennis Lembree has announced the soft release of Easy Chirp 2 beta! Easy Chirp, originally named Accessible Twitter, is a web-based Twitter application which is developed to be easy to use, robust (even works without JavaScript), and of course accessible. The service was down for a few months during a complete re-build mostly due to the closure of Twitter’s original API.

The soft launch is on the dot org domain; the service will be available on the dot com domain during the official release. Currently on the dot com domain, you can sign up for an announcement when the official launch occurs.

For more information, check out this blog about the Easy Chirp 2 beta by Laura Legendary (@Accessible_Info) on her Accessible Insights blog.

You can follow Easy Chirp on Twitter at @EasyChirp.

EasyChirp2 logo beta

Categories
firefox html5 longdesc

Longdesc Links, History, Future

Recently I Twittered daily about longdesc, the classic unsung HTML attribute which supports long descriptions of images. Here’s a summary of the tweets/links:

Some History

To make a long story short (pun intended), longdesc was made obsolete in HTML5 but then returned. I applaud @JohnFoliot, @Laura_Carlson, and @Chaals in their dedicated efforts to return longdesc. I agree it should remain as there is no sufficient ARIA replacement.

Here are more great links on the topic on long description over the last few years.

The Future

Check out the ARIA 1.1 spec for aria-describedat ARIA 1.1 spec for aria-describedat! The aria-describedby attribute is like a combination of longdesc and aria-describedby. I’m pretty excited about this as it seems to provide a method for long description that we can all agree on.

Categories
apple jobs

Accessibility Jobs, September 2013

Wow, great opportunities!