W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > October to December 2006

FW: discussion of Techniques 9.7-9.10

From: Jim Allan <jimallan@tsbvi.edu>
Date: Thu, 16 Nov 2006 13:08:36 -0600
To: WAU-ua <w3c-wai-ua@w3.org>
Message-id: <HDEAKIPKOHBCMDILOOPNOEOEHAAB.jimallan@tsbvi.edu>



-----Original Message-----
From: Jim Allan [mailto:jimallan@tsbvi.edu]
Sent: Thursday, November 16, 2006 12:10 PM
To: Jan Richards
Subject: discussion of Techniques 9.7-9.10



> 9.7 Move content focus in reverse (P2)
> - it might be simpler to combine forward and reverse navigation into 9.3
> as ATAG 2.0 does (A.2.1, SC4).

JA: agree

> 9.8 Provide text search (P2)
> -Ex. Tech. 7 is "Allow users to search the element content of form
> elements (where applicable) and any label text." - does "element
> content" sufficiently imply that search should include information in
> text boxes etc.?

JA: I think Ex. Tech. 7 does sufficiently imply that search should include
information in
text boxes. However, it does not (or should not) imply that user entered
content (i.e. my first name that I typed into a input element) should be
searchble. The checkpoint specifically refers to "rendered" content. Since
the UA did not render my name from the author supplied source this
checkpoint should not cover user entered content.

9.8 I have issues with this checkpoint. Screen reader users hear the 'alt'
of images, including image links. The screen reader allows them to search
for the 'alt'.
With image on non-screen reader users cannot search for 'alt' content. This
makes sense, the 'alt' is conditional content. However, if images are turned
off. The 'alt' content is then rendered by the UA. The 'alt' content should
be searchable by the UA. Is this correct? Tested in IE 6, Firefox 2, and
Opera 9. Am only able to search for 'alt' with images off and 'alt' content
rendered in Firefox 2.
Does searching for rendered 'alt' with images off need to be made more
explicit?

> 9.9 Allow structured navigation (P2)
> - not just "allow" - maybe this should be phrased "Allow structured
> navigation"

JA: ???, you repeated the text of 9.9. I think you meant to provide
alternate phrasing.

> - this checkpoint seems extremely central to the document - but the
> requirements are perhaps overly general
> - I wonder if the checkpoint could be enhanced by examples.

JA: do you mean examples other than the 12 example techniques already
provided? Or are you suggesting a different placement of a small subset
(i.e. headings and forms) be included in the Note: that follows the 2
requirements.
>
> 9.10 Configure important elements (P3)
> - "Similarity" is always tricky: "Allow the user to navigate according
> to similar styles"

JA: I agree. I know there are many ways of applying style to an element.
Among them is assigning a style to a "class". The Doing More example seems
very "similar" to (or a generalization of) Example Tech. 1 Allow the user to
navigate HTML elements that share the same "class" attribute.
Do you want to remove the Doing More, or change the wording?
Received on Thursday, 16 November 2006 19:08:45 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 October 2009 06:51:37 GMT