Developing Websites for Older People (batch 1 of 3 or so)

Hi Andrew,

I really like how the document has come together! Overall, I think this is the right amount of detail and very good organization.

Comments that apply throughout:

* Most of the techniques are either linked or have "(future link)". What about the ones that aren't, such as the first ones technique listed under bit the Text size and Text style and presentation sections? Are they from WCAG Techniques? (offline on flight now and cant check) If so, why are they not linked or indicated as a future link? If *not*, where did they come from? Is including them if they're not in WCAG saying that WCAG techniques doesn't cover older users needs sufficiently? Should they be submitted for *this* Techniques update?

* I think we need to consider a little more explanation for people who are not familiar with WCAG 2 -- at least about the "(future link)" issue. (note that an EO reviewer asked about it) possibly this is a note at the bottom of the document (linked to from the top of course)? Use case: someone really wants to read & understand this doc, but does not take the time to read up on WCAG first...

* how about "More techniques are listed in "How to Meet WCAG 2.0" under 0.0.0 - Handle."
-> "More techniques are listed under 0.0.0 - Handle in in "How to Meet WCAG 2.0"." so the links come earlier in the sentence (and since it's repeated so much, don't need to have the doc name front loaded.

* consistency. In some places you have:
0.0.0 - Handle (A) says "blaa blaa blaa"
and in other places:
0.0.0 - Handle (A) requires "blaa blaa blaa"
I prefer "says".

* formatting. Why have a dash between the number and the handle? versus: 0.0.0 Handle (A)

* formatting. Why have a WCAG quotes <em>phasized?

* lower case Review in headings "Literature Review references".

Second batch of comments coming later...

~Shawn

Received on Thursday, 2 September 2010 13:24:34 UTC