The WAI Priority 1 guidelines are easy. The second and third sets require some thought, but come with nice badges. Hype 2 could have badges: BSD, PHP, MySQL, WAI and other W3C standards. Maybe a badges page and then I could really go to town ;-)

WAI-AA decries auto-refreshing pages, because it can’t be stopped. This is understandable, what if you are half way down the page reading when it refreshes? Instead I reckon a new message reminder, something that appears at the top of the page to indicate new messages. This would cause a reflow, but perhaps just a visbility: hidden will do. It also bans pop-ups but I’m gonna defy that, it bans them based on their being an annoyance or a distraction, Hype’s will be functional. However, this is more javascript. Hype 2 relies on full javascript capability, handily this is about the best supported out of the enhanced HTML techs, IMHO, never the less it will mean having a non-JS version on standby for the text-mode people and those who believe Javascript can be dangerous.

Probably one of the most important accessibility features relate to readability. Font sizes especially should be flexible, the 1-7 HTML scheme is good, better (maybe) is configuration of font sizes in the profile.

Here are some other things:

• TOC or site map, perhaps combined with the help texts
• More header metadata (i.e. some)
• “13.4 Use navigation mechanisms in a consistent manner.”
• “6.4 For scripts and applets, ensure that event handlers are input device-independent.”

Shouldn’t be too hard. The text only version should be at least AA, hopefully nearer AAA quality accessibility, and I think the main version should be Aa (Priority 1.5).

pspell is enabled on Gradwell, using it is as easy as a short call that takes the message, and runs pspell_check on every non-HTML word. The results can be output with speeling mistaks highlighted somehow. Correcting means correctin based on suggestions (a la that spell check site?) and may mean correcting away from the original word, correcting names etc. or even [sharp intake of breath] correcting colour to color!

No, background-color: red; will do.

I’ve just written a 5 page set of bullet points for a meeting where I will prove that out of basic HTML we can carve gigantic edifice-like applications. It’s great, from tools like the file browse control and the HTTP authentication password box I can build applications that change the face of a company’s working day. The limits are very much the stimulus for going further, creating more.

I’m much more interested in complex web-based apps these days that basic boring brochure-ware web shites.

I would say more, but I have to sleep.