W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > January to March 2005

W3C User Agent Teleconference for 24 February 2005

From: Jim Allan <jimallan@tsbvi.edu>
Date: Thu, 24 Feb 2005 14:23:10 -0600
To: WAU-ua <w3c-wai-ua@w3.org>
Message-id: <HDEAKIPKOHBCMDILOOPNCEFOPPAA.jimallan@tsbvi.edu>

W3C User Agent Teleconference for 24 February 2005
Chair: Jon Gunderson
Date: Thursday, 24 February 2005
Time: 2:00-3:00 pm Boston Local Time, USA (19:00-20:00
Jon Gunderson
Cathy Laws
Jim Allan
Peter Korn
Matt May

David Poehlman

1. Road Map on Web Application Accessibility Document - meeting Tuesday afn
current technique to make something focusable is to set tabindex=0,
contradicts xhtml. but does talk about prevfocus later in the document.
caret function - if caret is in element (by mouse or any device) then
"title" value should appear as tooltip,

2. XHTML 2.0 review
General Comments
how does XHTML relate to XForms
should be device independent...no mouse only. 508 1194.a
user should be able to ignore author style
is there a defined concept of "focus", it is implied. which elements are
focusable, how does it get focus, how does it relate to "access", also
problems with visual useragent rendering conditional content. How does AT
gain access to conditional content in non-DOM world (unix),
how are attributes to be exposed to the user (style may be an option), how
will the uri's become actionable when it is revealed/rendered.

Specific comments
section 18 - image map - don't specifically state the rendering behavior
conditional content, if image not available, present nl or source.
--uaag - should say if UA is configured to not show images or image not
available then render in some fashion.
module 10 - hypertext - put hypertext on anything, not just limited to <a>
--uaag - implications for assistive technology
module 10 - prevfocus, nextfocus - no tab index, focus change based on
element id, does not follow visual layout.
-- uaag -
module 13 - access - replacement for accesskey -
-- uaag - keybindings?, UA to provide a list to the user (list presentation
needs to be standardized), UA should provide default binding for "standard"
items (nav list, toc, etc.), how does this relate to xforms (does xforms
have shortcut keys).
is there a normative list of attribute value for "access" that authors and
tools will use, should be a list of default bindings, and extendable list,
users can change default binding, an access point does not have to be
Access point
module 12 - title -
-- uaag - need keyboard access to "tooltip", user configurable in the UA to
turn "tooltips" on or off
module 11 - list -  nav list must have a label (required), can add label to
ul and ol
-- uaag - no rendering model,
module 26 - tables - need accessible markup in examples (use headers, ids,

meeting with xhtml on Thursday.
Received on Thursday, 24 February 2005 20:20:42 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:38:35 UTC