W3C home > Mailing lists > Public > w3c-wai-eo@w3.org > July to September 2010

Comments on Developing Websites for Older People

From: Jennifer Sutton <jsuttondc@gmail.com>
Date: Wed, 01 Sep 2010 12:52:57 -0700
Message-Id: <7.0.1.0.2.20100901124239.027f66b0@gmail.com>
To: "EOWG (E-mail)" <w3c-wai-eo@w3.org>
EOWG:

Here are some comments on Developing Web sites for Older Users (or 
People, whichever it is).

NOTE:  This is a mixture of feedback about the headings, as well as 
some edits. I hope that's okay; I thought splitting the comments 
between the two lists might be confusing.

I'm sorry I won't be able to be on the Friday, sept. 3 call to 
discuss the issue of the "expanding" and collapsing" links.

Jennifer

[Draft] Developing Websites for Older People:
How Web Content Accessibility Guidelines (WCAG) 2.0 Applies
http://www.w3.org/WAI/EO/Drafts/sites-older-users/

Comments on version:
Content last updated: $Date: 2010/08/31 15:29:47 $ by $Author: andrew $ [

1.Feedback on headings at all levels

1.1.  When I skim through the headings, I am seeing ones that are:
"[link] expand,"
But I can't tell what's going to be expanded

NOTE: If JFW makes it clearer, then I suggest this issue be 
disregarded as this may be an issue with Window-Eyes not behaving as 
I personally think it should.

It's not our job to cater to screen-reader oddities.

1.2. When I do expand items, then I also see headings that just show 
links to the linked word "collapse."

To be clear, this is wen I am skimming by heading; I see the full 
heading text when I read line by line.

1.3. I wish I had a simple solution to offer because we need a 
standard way to do expanding and collapsing. Maybe there is one, and 
I've never seen it implemented in a way I've come to expect.

I'm absolutely NOT wedded to this idea, but I wonder how it would 
work for ALL users if the "expand" and "collapse" links came AFTER 
the heading text.

If that looks nonstandard, please ignore the idea.

Do you know whether you want to expand or collapse before you read 
the text to which it pertains?

I want to emphasize that I'm VERY much brainstorming.

1.4.  I wonder if it would seem too screen-reader-centric if there 
were a sentence or two (perhaps as a note after the Intro) to explain 
that there's expanding and collapsing for both the whole document and 
within sections.

1.5.  Here, it may be fine and just me, but I'm not sure why there 
are two "collapse" links:

h3 Understandable information and user interface h3
[link] Collapse
Page organization
[link] Collapse

1.5.1. Another example is here:

[link] Collapse
h4 Understandable language h4
[link] Collapse
Many older people can be overwhelmed by complex sentences, unusual 
words, and technical

If it's all consistent, then it's fine; I'm focusing on skimming 
through the headings which may not be typical of page visitors.

2.  The uri, page title, and heading within the page don't 
match.  Among other issues, is it "people" or "users?"

But there are other inconsistencies, too.

I saw some notes about this issue of the page title in the changelog.

3. When I activate the "[link] expand all," then below it, it shows a 
nested list, but I don't see any content in the bullet-items. I don't 
know what that's trying to accomplish visually.

4.  Shouldn't what's in brackets be a link?
"additional
descriptions, examples, and resources from ["Understanding WCAG 2.0".]

5.  Are the references to "future link" going to be able to be filled 
in before publication, or is it okay to leave them?

One example is:
Using readable fonts (future link)

And there are several more.

6. Maybe it should be CAPTCHA stands for, here:
"CAPTCHA is 'Completely Automated Public Turing tests to tell 
Computers and Humans
Apart')"

7. Please check the word "level," here:
(AAA) requires providing a version that "
does not require reading ability more advanced than the lower 
secondary education
leve
l"

8. I've not seen link words, up to this point, that included the word 
Guideline.  I wonder if "guideline" is necessary, here:

More techniques are listed in "How to Meet WCAG 2.0" under the 
success criteria for
[link] Guideline 3.1 - Readable
.
Literature Review references:
Cognitive decline with age
  and
Previous approaches to 'senior friendly' Web guidelines

9. Two things in here.  I see the word "Guideline" in this link, too, 
so maybe there's a reason for including it sometimes.

I also see the need to add an "as," as I cite in brackets:

More techniques are listed in "How to Meet WCAG 2.0" under the 
success criteria for
[link] Guideline 3.3 - Input Assistance
  as well [JS: add as] under some of the individual success criteria 
listed above

10. Should link words be included here?

[link] WAI/WCAG20/quickref/#time-limits-server-timeout

Literature Review reference:
[link] Aspects of Web Design affecting the elderly - Forms
.
11. I think this is repeated i.e. my items 9 and 10:

More techniques for 'forms and transactions' are listed in "How to 
Meet WCAG 2.0"
under the success criteria for
[link] Guideline 3.3 - Input Assistance
  as well [JS: add as] under some of the individual success criteria 
listed above
WAI/WCAG20/quickref/#time-limits-server-timeout
.
Literature Review reference:
[link] Aspects of Web Design affecting the elderly - Forms
.
[link] Robust content and reliable interpretation

12. I'm not sure what "end definition" means in terms of where this 
definition is coming from.

"Some older people will be using older browsers that might not be as 
capable or fault
tolerant as current releases.
end definition
WCAG 2.0 requirements:"
Received on Wednesday, 1 September 2010 19:54:20 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 10:33:57 GMT