Comments on Developing Websites for Older People (http://www.w3.org/WAI/EO/Drafts/sites-older-users/Overview.html)
Overall I feel this is a well constructed and thourough document as it applies as a WCAG 2.0 use case.
However - that being said, in addition to comments and feedback below about specific sections, I think that the introductory sections could be fleshed out some more. Specifically I think that certain aspects of Accessibility as it applies to older users should be highlighted or worked into the document in some way, either through specific citation to existing WAI material or as new content. For example:
- the increased potential for this audience/user group to have more than one declining sense (vision and hearing for instance) making accessible web content all the more important.
- the fact that in an ageing population, older users will increasingly become more technically 'savvy' over time and demand greater and equal access to online content
- none of the reviews/studies provided (that I read, and granted I didn't read all of them) appear to address the potential for older users to face an increased likelyhood of being subject to barriers to access such as lower bandwidth / slow connections. (not quite covered by the Robust content and reliable interpretation - Older equipment/software section)
- an increased reliance by government and others on an online service delivery and engagement model means that increasingly WCAG 2.0 as it applies outside of the scope of disability access and overlaps into equity and access for all will become a part of legislative requirements and national standards integration. Where the audience for such services (or online collaboration) is specifically older users, then WCAG 2.0 AAA compliance should strongly be considered.
Perceivable information and user interface - CAPTCHA
As stated above, older people as an audience are more likely to have multiple instances of types of disability or decline in sensory ability. I would suggest changing the weighting of the techniques so that "Providing access to a human customer service representative who can bypass CAPTCHA (future link)" is listed first, to highlight how this simple and likely already supported (at the enterprise/organisational level) as a means of assisting access for older people. Some discussion on preferred modalities might be useful as well?
Operable user interface and navigation - Distractions (audience)
In line with my comments above on identified audiences and AAA compliance, some mention of tailoring content in a targeted environment to ensure that content that constitutes a distraction simply shouldn't be used in these situations? I would also suggest adding a technique around providing/delivering content in such a way as plug-ins are not required to be downloaded or installed.
Robust content and reliable interpretation - Older equipment/software
See comments above on barriers to access - prehaps expand or add comments on connection speeds, low bandwidth alternative content, filesizes etc? I would also suggest adding a technique around writing content in such a way as plug-ins are not required to be downloaded or installed.
-- Chris Beer 14:02, 8 September 2010 (UTC)