Categories
conference event presentations twitter

Speaking on “Twitter and Web Accessibility” at AHG

Web Axe host Dennis Lembree will be speaking on “Twitter and Web Accessibility” at the 12th Annual Accessing Higher Ground conference in Colorado this mid-November.

The conference is November 10 thru 14. The labs are scheduled for a Tuesday and Wednesday, then the main conference is Thursday, Friday, and Saturday. (One day longer than last year!) Dennis is scheduled to speak on Thursday at 9:15am.

The keynote speaker is T.V. Raman, Research Scientist, Google, Inc. Dolphin Computer Access, LTD will sponsor one of the conference computer labs. They will also present 2 hand-on sessions on alternate format conversion.

The location of the conference is the Westin Hotel in Westminster, which is about 30 miles from the Denver International Airport (DEN). The hotel, or resort I should say, looks very nice!

You may register here. The shortened URL is tinyurl.com/ahg2009. Hope to see you there!

Categories
design html5 podcast twitter

Podcasts from Tweeps: Universal Design, SitePoint, Heretech

Some great recent podcasts from some great Tweeps (if you’ve been on Mars, that means users of Twitter).

Categories
"assistive technology" input mac testing yahoo

Visit to Yahoo! Accessibility Testing Lab

I was fortunate enough to get invited for a visit to Yahoo! Accessibility Testing Lab (in Sunnyvale, California). Victor Tsaran (@vick08) and Alan Brightman (@abrightman) were kind enough to spend about an hour and a half with me and several other computer professionals. Here are some notes from the meeting:

  • Learned a lot about Mac’s accessibility features. You can find them under under System Preferences/System/Universal Settings. Apparently they’ve been present since 1985, but most people don’t know they exist.
  • Apple computers come with a screen reader VoiceOver, which is now on the iPhone. On the Mac, it displays the text which it’s speaking; a great for blind person to work with a deaf person.
  • The demo of alternative input devices and software (including switch devices, head tracking, and an alternative keyboard) really creates awareness of others’ needs.
  • Saw a demo of a braille output device. It was noted that this type of device is best for the deaf-blind. They are very expensive, and more popular in Europe as there tends to be more subsidy.
  • Issues and features with mobile devices including screen magnifiers, speaking menus, camera-scanner-reader combo.
  • Some excellent links:

Victor, Rob and Alan in the lab

Categories
guidelines heading usability wcag2

Article Headings, Please!

This has become an issue for me of late, and it needs more attention. And that is lack of sub-headings in articles. Not just the page heading and/or article heading, but headings  throughout an article to make it more accessible and usable. Especially so the longer an article is. (And of course, use proper markup! H1, H2, etc.)

Examples, Poor

Among many, I came across the following articles which could really use more headings. The articles are fairly long, and could no doubt be broken up into sections.

Why Headings?

Why are headings so important? First of all, it’s part of accessibility guidelines such as WCAG 2.0; see section 2.4.6 Headings and Labels. The W3C points out that headings create meaning when read out of context. And they help people with limited short-term memory. In addition, headings provide:

  • Better navigation for screenreaders.
  • Default formatting when CSS is not available.
  • More semantic.
  • Scanning more usable and readable document.
  • SEO.

Examples, Good

Here are examples of articles with good use of headings:

Please use headings and sub-headings as it creates more web accessible and usable articles.

Categories
standards

Accessibility Versus Standards

A few weeks ago, an article was published on Smashing Magazine 10 Ways To Make Your XHTML Site Accessible Using Web Standards.

The article drew well over 150 comments, including much criticism from web accessibility experts such as Jared, Patrick Louke, Joe Dolson, and yours truly.

As Andy points out in comment 17, a web page can be 100% XHTML Strict (or standards-compliant) but not be accessible.

In comment 41, the “some random ten things one can do to be more of a web standardista, per se”

In comment 29, Jared list several

Why not?