Category Archives: Accessibility
Is accessibility actually usability?
A couple of days ago I had the pleasure of speaking at the first seminiar on usability in Bulgaria. A great thanks to the people at .net and Lucrat in Bulgaria, it was a great event with great hosts. It was also great to see & meet Peter Merholz, having …
.net standards champion
I was pleased (and rather surprised) to be nominated for “standards champion” in the .net awards. The thing is, the competition is, um, quite fierce! I’m up against the W3C, Mozilla, and some of the best known names in the business (like Zeldman). So I’m not picking out a …
iPods get speech, Apple gets accessible
The new iPod nanos (4th generation) now have speech-enabled menus, so you don’t have to be able to see the screen to operate it. This is obviously a boon for the visualy impaired, but with my old iPod I quite often used it from my pocket, or whilst driving. Could …
Strange sIFR / screen-reader bug
I was writing a little accessibility article for .net magazine about text-replacement techniques, including sIFR. I was blithely saying that "yea, don't worry, it's fine" with a couple of caveats. But, rather than rely on memory I did a quick test, and discovered something strange. ABBR pattern accessibility
I'd been meaning to post on the microformat-accessibility issue, but Patrick Lauke just posted a great sumary. As a sort of +1, I'd just like to share what I would prefer as an accessibility aware developer. Where SEO and accessibility collide
Galleries in WordPress 2.5
The recent (and quite significant) overhaul of Wordpress' admin area is very good, streamlining your blogging and making previously diffiicult things quite simple. One of the new features is the ability to automatically create a gallery within a post of all the picture uploaded to that post. I wasn't very happy with the code output for galleries, so I took it apart and tried to improve it. WCAG Samurai release errata
Voiceover 2 – a WebDev’s guide
VoiceOver has undergone a major update, this article looks at the new functions, and what that means for people browsing websites. I am not looking at VoiceOver in general, just how different aspects of web pages affect the experience when using VoiceOver.