Posts

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

Labels:

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:

Labels:

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

Surveys

Articles

Upcoming Events

Global Accessibility Awareness Day

Labels: , ,

Suggestions for the new Disability.gov

Last month (March 2012), Disability.gov (@DisabilityGov) relaunched its website; there is an announcement in its newsletter. I discovered this actually by coming across an article posted on Twitter, A Look behind the Scenes – Part I: Making Disability.gov Accessible which discusses considerations made when developing an accessible website.

Naturally, this peaked my curiosity and was compelled to investigate. I found mixed results. Every website, no matter how great the foundation, is a work in progress and could use improvements. Disability.gov is no exception. Here's my review of the home page.

After completing this review, I unfortunately wouldn't agree with the claim in the footer that the Disability.gov website adheres to WCAG 2 level AA.

The site's accessibility statement states:

If you experience any technical problems or have issues with accessibility, please contact dgovdeveloper AT devis DOT com with your feedback, and we'll do our best to respond to your concerns.

I have emailed a link to a link to this blog and hope more improvements can be made soon. -Dennis

Labels: ,

Web Accessibility Jobs, April 2012

Great opportunities in US, UK, and Australia!

For more, be sure to follow me, accessible_jobs and @a11yjobs on Twitter!

Labels:

Response to blog Web Accessibility Initiative

This is a response to the blog Web Accessibility Initiative by Nathan Crause. Contrary to the title, the article attempts to disclaim the need for web accessibility, particularly for visual impairments. I submitted a comment but it wasn't posted. So here it is:

A 3.8% population with visual impairment is not minor at all. If your company has 1 million potential customers, you are ignoring 38,000 chances to make money! And if they're already customers, be prepared to receive up to 38,000 complaints.

Keep in mind that accessibility also benefits people who have mobile, hearing, and cognitive impairments. They are potential customers, too, and they themselves add up to much more than 3.8% of the U.S. population. The 2009 stats from DisabilityStatistics.org say about 2% of the U.S. population is visually impaired, while total percentage of people who are disabled is around 12%.

Java Applets...seriously?

Content of SVG can be made accessible. And even the accessibility of HTML5 canvas is being worked out.

In addition, Flash can be made accessible. Adobe has made huge improvements here, although not on the Mac. The problem is that developers have the tools to make web sites/apps accessible, but just hardly ever do it.

JavaScript libraries are usually not an issue either. For example, YUI3 and jQuery UI incorporates ARIA which help screen reader users with the interaction.

Still don't believe me? Check out the W3C's Developing a Web Accessibility Business Case for Your Organization.

If you current with web technologies, an accessible website doesn't have to be "crippling". The bar is now set much higher with modern coding practices available such as progressive enhancement, ARIA, and managing focus. A good example of an accessible web application is Yahoo! email.

The real issue here is ignorance. Ignorance in business, empathy, and proper development technologies and practices. I do agree with you [the author, Nathan] on one point, though; accessibility is a touchy subject.

Labels:

CSUN12 Quick Review

Another CSUN conference has come and gone and this year was better than ever. I met many great people for the first time including Joe Dolson, who's been on the Web Axe podcast a couple times in the past. The conference included much discussion on Google and accessibility, the announcement of WAVE5 beta by WebAIM, and the Tweetup was a bash! Special thanks to Adobe, Deque, and Accessible Media for being such great hosts. On Saturday morning, I attended the SS12 finals in which @Jennison was one of three judges (I judged last year). Be sure to check out the Great Big List by @mactoph which includes many links to presentations, round-ups, podcasts, and more. Also, here's my Flickr CSUN12 photo album. -Dennis

Joe, Jennison, Dennis, and John sitting at table for lunch.
Photo: Joe, Jennison, Dennis, and John at lunch. Credit: Angela Hooker.

Labels: