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 periodically receive emails from Sitemorse, despite trying to unsubscribe a couple of years ago. This one escaped my usual filters, and I noticed an interesting statistic about the number of accessible PDFs in the wild.

I attend my first Microsoft (MS) oriented user group meeting yesterday, the SharePoint User Group on search and accessibility. Unfortunately our developers werre either too busy or on holiday, so I got volunteered.

I was a bit quiet over the Christmas period, because .net magazine had asked me to do an article on accessibility. I’m very pleased with the result, it’s great to see it in print, although also quite nerve-wracking: I’m used to making post-publish edits!

If there was one thing I could get across to project managers, company owners, and CTOs, it would be Struan Robertson’s advice from a recent article “Legal reasons to make intranets, extranets and software accessible” on Out-Law.

Mike Davies has stirred up something of a hornets nest with his thoughts on where accessibility as a discipline should be going, especially with statements like The current web-developer focused organisations are tainted, constrained by universality, with sour to nonexistent relationships with assistive technology providers and browser vendors.

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.

If the editor has followed the earlier HTML and CSS guidelines, many accessibility issues have been avoided already. This post is essentially a list of things a WYSIWYG editor could do to help authors not create accessibility barriers.

I’ve noticed that the Mozilla org has been doing quite a bit on accessibility, from working with IBM on Rich-apps accessibility, to funding people to make Firefox accessible with VoiceOver. Mark Pilgrim reports that Firefox 3 will include the option to block meta-redirects.

This post is far too late, I really should have said this earlier, but the terms being used for various layout types are confusing. The top articles for “Elastic Design” on Google refer to elastic as being a a font-based layout. I think elastic is the wrong term for what the layouts achieve. Also, there is an assumption that these layouts are good for accessibility.