Author: Dennis

Categories
screenreader survey webaim

About WebAIM Screen Reader Survey 4

As you may have heard, the results of the fourth WebAIM screen reader survey are now available. The survey provides valuable information on about screen reader users such as primary screen readers used, browsers used, and reasons for use.

WebAIM reports that problematic items have changed little over the last 2 years. The top ten are:

  1. The presence of inaccessible Flash content.
  2. CAPTCHA – images presenting text used to verify that you are a human user.
  3. Links or buttons that do not make sense.
  4. Images with missing or improper descriptions (alt text).
  5. Screens or parts of screens that change unexpectedly.
  6. Complex or difficult forms.
  7. Lack of keyboard accessibility.
  8. Missing or improper headings.
  9. Too many links or navigation items.
  10. Complex data tables.

Conclusions from the survey include:

  • JAWS is still the primary screen reader, but usage continues to decrease as usage of NVDA and VoiceOver increases.
  • The perception of accessibility of web content is decreasing.
  • 72% of the respondents use a screen reader on a mobile device, up from only 12% three years ago.
  • iOS device usage is significantly increasing and well above that of the standard population. Screen reader users represent a notable portion of the iOS device user market. Usage of Android devices is well below that of non-disabled users.
  • The use of properly structured headings remains of great importance. 

Here are a few great analyses of the survey:

Categories
design forms html5 label

Placeholder Attribute Is Not A Label!

Just so we’re all clear on this, the HTML5 placeholder attribute in a text input is not a replacement for the label element. Period. The placeholder should only be used as a brief example of the text to be entered.

Besides inconsistent support for screen readers, using a placeholder as an input label can create usability problems and issues for those with cognitive impairments. For example, how does one review the information entered if the placeholder is now gone?

The placeholder should be used like a title attribute (tooltip); it provides only supplementary information. If the information is required for the user (such as a strict text format) then this should be conveyed in the main content of the page, not in an attribute.

The W3C HTML5 placeholder specification specifically states it should be a “short hint…intended to aid the user with data entry” and also states:

The placeholder attribute should not be used as a replacement for a label.

Supporting articles:

Bonus!
On @a11yMemes, check out this humorous take on placeholder.

Addendum (more references):

Also see Web Axe follow-up post: Floated Labels Still Suck.

Related Tweet Jan 2016:

https://twitter.com/shoobe01/status/689221623774220288

Categories
usability

The Usability Principles, Accessibility Style

Steve Grobschmidt (@AquinasWI) recently blogged a three-part series titled The Usability Principles, Accessibility Style. Using Jakob Nielsen’s 10 Usability Heuristics as a guideline, Steve discusses the principles and then explains how they each relate to accessibility. Great stuff!

The 10 principles discussed are:

  1. Visibility of system status
  2. Match between system and the real world
  3. User control and freedom
  4. Consistency and standards
  5. Error prevention
  6. Recognition rather than recall
  7. Flexibility and efficiency of use
  8. Aesthetic and minimalist design
  9. Help users recognize, diagnose, and recover from errors
  10. Help and documentation

Addendum:
For more related information, see my article Popular Mistakes in Universal Web Design which discusses the seven universal design principles.

Categories
gaad

Reflecting on GAAD

[A guest post by Jennison Asuncion (@Jennison), co-founder of GAAD]

On May 9, people from around the world took part in public events, hands-on experiences, and other activities to mark the first Global Accessibility Awareness Day (GAAD). Conceived by Joe Devon, the idea started because Joe, as a developer, and not someone who knew much about accessibility to begin with himself, blogged passionately last November that all devs need to possess basic awareness of and do their part in making the web accessible. He further declared that there needs to be a day to bring focus, and suggested May 9 as a good a day as any.

As someone who is constantly thinking about and actively pursuing ways to make digital accessibility, “accessible”, to the mainstream IT and related communities myself, you cannot imagine my excitement when I stumbled upon, purely by accident via Twitter, Joe’s blog post, on that random Saturday night when it went live. After reading it, I was immediately in touch with Joe, raising my hand to be his co-pilot for the effort. The rest is now history, and a pretty good testimonial of the power of social media in its own right.

What inspired me most, outside of Joe’s genuine interest and enthusiasm, was how willing people were, in stepping forward to either run an event and/or promote GAAD, without much time at all to spare. Thank you everyone. The truth is that Joe and I share a common trait, equally hectic schedules between our day jobs and our other involvements, which meant GAAD crept up on both of us. Thankfully, leaning on our generous networks, social media, and word of mouth, everyone who took part, in what ever way, has much to be proud of. Now that the date is set, and the event is out there, GAAD 2013 and beyond can only keep growing. Check out Joe’s post-event recap to see where he plans bringing his energies next.

Involvement with GAAD has only reinforced my belief that we, working in digital accessibility, only benefit when we engage with and support members of the mainstream design, development, and related communities in raising the profile of and addressing digital accessibility.

Get involved- express interest in holding an event for GAAD 2013. Volunteer to translate some of our text into other languages.

Editor’s Note

There were many blogs and press articles written about GAAD. Here are some:

Categories
event gaad podcast survey

Podcast #95: Global Accessibility Awareness Day, Surveys, more

First, Dennis and Ross discuss a variety of topics including some current surveys and a couple articles about skip-to links. Then Dennis speaks with @JoeDevon and @Jennison about the inaugural Global Accessibility Awareness Day!

Download Web Axe Episode 95 (Global Accessibility Awareness Day, Surveys, more)

[Transcript of podcast 95]

Goings On

  • Ross’ book update.
  • Positive email response to Disability.gov critique.
  • Liz Ellcessor Ph.D. candidate in Media & Cultural Studies at U of Wisc interviews Dennis (Malware warning due to hosting issue).
  • New! a11yBuzz by @KarlGroves, an “accessibility body of knowledge”.
  • 2 updates (validation, open in other browsers) to Web Accessibility Toolbar 2012 by The Paciello Group.
  • Seeing more accessibility jobs in general lately. Hiring good web developers at PayPal in San Jose, San Francisco, Austin; contact @DennisL.

Surveys

Articles

Upcoming Events

Global Accessibility Awareness Day