All posts by AlastairC
WYSIWYG editor spec – checklist
After the 10 previous posts on WYSIWYG editors, I have compiled all the 'tips' into a checklist of things to look for in an editor. At this stage, I'd like to ask for any comments, questions or criticisms before I start applying it to editors. Accessibility vs Universality – implications
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.
Dissecting CSS Polygons
I've been meaning to sit down and take apart Tantek's polygons for a while, partly because it looks impossible, and partly because it might be useful. Five years later and today was the day, although it turns out that the usefulness has some limits. Perceptions of page loading speed
It is fairly amusing when people (clients or otherwise) demand that a page load in under x seconds (where 'x' varies by which guru article they were reading). This hit home today when David Hyatt (lead developer of Safari) highlighted people's mis-perceptions.
WCAG 2 response on relative units
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.
WYSIWYG editor spec – preventing problems
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. Firefox 3 accessibility
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. OpenID and trust
I noticed OpenID a while ago, as a possible way to do single-sign-on for internet applications. Recently I wondered why Google used CAPTCHA, and despite it being the most viewed article on this blog (thanks to Matthew Mullenweg), no one pointed out the obvious problem with my argument.
Elastic layout – wrong term?
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.