- From: Richards, Jan <jrichards@ocad.ca>
- Date: Thu, 31 Mar 2011 13:56:20 -0400
- To: UAWG list <w3c-wai-ua@w3.org>
Hi all, Kelly asked us all to use the call time to comment on the proposals. Here are thoughts. Simon has done a lot of good work in a very difficult area, but there are still some things to work out: 2.7.1 http://lists.w3.org/Archives/Public/w3c-wai-ua/2011JanMar/0088.html --------------- - I note Greg L's point about redundancy between 2.7.1 "Discover navigation and activation keystrokes" and the pair 2.1.6 "Present Direct Commands in Rendered Content" and 2.1.7 "Present Direct Commands in User Interface" - typo: buy=>by - Example is a barrier example not an implementation, is this intended? It might be reworded as follows: + Mary cannot use the mouse or keyboard due to a repetitive strain injury, instead she uses voice control technology with uses a mouse-less browsing plug-in to her browser. The plug-in overlays each hyperlink with a number that can then be used to directly select it (e.g. by speaking the command "select link 12"). This prevents X from having to say the work 'tab' numerous times to get to her desired hyperlink. 2.7.2 http://lists.w3.org/Archives/Public/w3c-wai-ua/2011JanMar/0089.html --------------- - This one is tricky because of what counts as an explicitly defined relationship. I wouldn't exactly say an HTML table column header is explicitly defined. - Is the requirement really to provide label-type relationships (would need to be defined)? - intent should not be HTML specific. I think it is sufficient to say "structured content" (e.g. tables, forms, etc.) - the example is ok 2.7.3 http://lists.w3.org/Archives/Public/w3c-wai-ua/2011JanMar/0090.html --------------- - this is quite a wordy SC - I actually don't think I fully understand what it requires. " in which the structure and semantics are implied by presentation" seems to imply that the user agent needs to create explicit structure when it is implied by presentation. - Is this really Level A. 2.7.4 http://lists.w3.org/Archives/Public/w3c-wai-ua/2011JanMar/0095.html --------------- - ok, except the intent should be worded more positively. It's what we intend to enable, not a problem description. 2.7.5 http://lists.w3.org/Archives/Public/w3c-wai-ua/2011JanMar/0092.html --------------- - the SC wording is too general. But trust me that I KNOW hard this is to define. We went through it in ATAG2. 2.7.6 http://lists.w3.org/Archives/Public/w3c-wai-ua/2011JanMar/0094.html --------------- - Good. Just needs a more positive intent. 2.7.7 http://lists.w3.org/Archives/Public/w3c-wai-ua/2011JanMar/0096.html --------------- I think this used to refer to the elements that could be navigated to and helped ground the 2.7.5 requirement. Is the term " Set of Important Elements" attached to anything anymore? Cheers, Jan -- (Mr) Jan Richards, M.Sc. jrichards@ocad.ca | 416-977-6000 ext. 3957 | fax: 416-977-9844 Inclusive Design Research Centre (IDRC) | http://idrc.ocad.ca/ Faculty of Design | OCAD University
Received on Thursday, 31 March 2011 17:56:51 UTC