I’ve recently been struck by a parallel: the differences between usability and accessibility are very similar to the differences between writing the HTML5 spec and covering accessibility requirements. Perhaps that can help explain the friction, and why WAI-ARIA is needed.

The “UK Accessibility Roundtable for Microsoft Office SharePoint Server 2010″, a HiSoftware event at Microsoft’s offices in London Victoria. The day revolved around several demos of SharePoint 2010 and Compliance Sheriff, and was fleshed it out with some quite good accessibility information. These are my notes on the event, with a lot of interspersed commentary.

I’m putting up my notes from the talks I saw at Techshare 2009, and Richard Schwerdtfeger‘s was the first.

You may have noticed the W3C was asking for contributions for the running the validator. There is a way that you can support the W3c validation service – by not using it. The public version that is. If you use OSX, you can install it locally.

Joe Clark has released the final WCAG Samurai’s errata, an update to the (almost) 9 year old Web Content Accessibility Guidelines 1.0 guidelines.

I’m just back from @media, and thought I’d post up brief notes (such as they are) for my own reference and anyone else’s gain. Obviously, I will only comment on the presentations I saw, and it’s all from my own particular perspective.

Jesse James Garrett – Beyond AJAX

I…

A little while ago Joe Clark asked me to review the WCAG Samurai’s WCAG 1 errata, which Joe has announced will be published today.

Also available is my independent review of the errata: WCAG Samurai Errata Review. Unbeknownst to me, Joe had also asked Gian Sampson-Wild, who’s review…

In my previous article on responsibilities in accessibility you might have noticed that I’d fallen into the traditional accessibility trap of only really referring to (X)HTML/CSS sites and guidelines. I’m quite aware of other technologies, but it’s worth looking at why other formats are harder to make accessible.

The W3C has defined what to do for accessibility at each ‘end’ (i.e. client side or web site site), but there is quite a lot of overlap, and scant advice on who should be responsible for what. I’m going to try and show who’s responsible now, and where things should go.

I had submitted a comment on WCAG about relative units, and looking through my incoming links with Google’s new external links tool, I discovered that they had taken it on, partially.