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

Re: Comments on Developing Websites for Older People

From: Sylvie Duchateau <sylvie.duchateau@snv.jussieu.fr>
Date: Thu, 02 Sep 2010 13:05:16 +0200
Message-ID: <4C7F84EC.6010009@snv.jussieu.fr>
To: Jennifer Sutton <jsuttondc@gmail.com>
Cc: "EOWG (E-mail)" <w3c-wai-eo@w3.org>
  Hello Jennifer and all,
Here are some reactions to Jennifer's comments while having another look 
at the document:
Developing Websites for Older People: Applying the Web Content 
Accessibility Guidelines (WCAG) 2.0
http://www.w3.org/WAI/EO/Drafts/sites-older-users/'m sorry I won't be 
able to be on the Friday, sept. 3 call to discuss the issue of the
> 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.
>
> [...]
>
SD: Using Jaws, I see the same as Jenniffer.
I read: "h4 expand h4" then h4 "text size" H4.

> 1.2. When I do expand items, then I also see headings that just show 
> links to the linked word "collapse."
SD: I note the same with Jaws. While reading through all the page, the 
screen reader separates the words expand or collapse from the heading it 
refers to. But when displaying headings list I can read the words 
collapse or expand associated with their text.
Looking at the page with screen reader NVDA gives better results. the 
icons collapse or Expand are read altogether with their corresponding 
heading text in all situations.

> 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.
SD: I agree with this point.
[...]
> 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.
SD: I agree also with this point.
> [...]
> 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.
SD: I could not see the list you are talking about. but I think it is 
confusing, when you activate the link "expand all", that you still have 
both links "collapse all" and "expand all". So if you do not have a 
  global view of the page, you don't know if actual status is "collapse" 
or "expand".
[...]
>
> 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)
SD: I think it is the technique as it is written in WCAG 2.0 techniques. 
All techniques that are not yet written are (future link). The others 
are numbered and have a link.
But therre is an inconsistency in quoting future techniques as some do 
not have the indication future link such as:
"Avoiding centrally aligned and fully-aligned text
".
>
> 6. Maybe it should be CAPTCHA stands for, here:
> "CAPTCHA is 'Completely Automated Public Turing tests to tell 
> Computers and Humans
> Apart')"
SD: I agree with this point.
>
> 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"
SD: I just checked and SC 3.1.5 is called reading level.
I have some more comments on content:
1. In section  "links"  from "operable user interface...":
reference to CS iss orted with link to 2.4.4 (level A), 2.4.9 (level 
AAA) and 2.4.7 level AA. Is this choice and error or intended to group 
the idea of "link purpose" together?
2. Same note for section  "navigation and location" where the reference 
to SC 2.4.2 page titled is the last of the list, while it is priority 
level A.
3. Section mouse use:
Something seems confusing to me. While this section is located in part 
"operable" one can find reference to sc 1.1.1 (principle perceivable) 
and 3.3.2 labels  or instructions that belongs to principle Understandable.
4. In section distractions are also examples of references to other 
principles and references that are not ordered  according to priority 
level.
That is all for my comments.
Best
Sylvie
Received on Thursday, 2 September 2010 11:03:10 GMT

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