I captured a few notes, hardly exhaustive, but a few interesting points I picked up during the presentation. (As with the Shirky notes from last week, please excuse the slap-dash style, this was taken on my phone.)
Not just disabled, also if tired, on mobile, ill, hangover etc
Don’t just build for disabled, make it easy for everyone… Usability and accessibility go hand in hand.
Accessibility at each stage
Recently changed mind about text resized widgets (three different sized As), conventional view is not to them because browsers already let users resize text, BUT be pragmatic esp where users have multiple disabilities which would make it hard to invoke zooming
Flash, don’t throw out just because not everyone can use it
Eg consistent headings
Skip links (skip to middle of page etc):
Not actually so useful for blind users as they tend to load a list of links, but useful for someone who can’t mouse around easily Access keys. Browser supported keyboard shortcuts. BBC myweb myway site is a very good source to link to, to help users understand how to use them. Also BBC use the same set across their asseys and American sites are using similar conventions so a pattern of standards is emrging (1=search etc)
hijax POSH first (plain old semantic html), then JS later BUT with screenreaders how do you tell user something’s changed above the part they’re listening to? WAI-ARIA standard is helping as a stopgap until html5 defines standard regions of the page and control types, and areas likely to update.
Not just colour blindness but failing eyesight. (David will be posting links to some good resources he demo’d on the meetup page I believe.)