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

Action: Review HTML Section 7 on User Interaction

From: Kelly Ford <Kelly.Ford@microsoft.com>
Date: Thu, 27 Aug 2009 15:52:42 +0000
To: WAI-UA list <w3c-wai-ua@w3.org>
Message-ID: <3386240A0CB7B345B60441C3B253B2A10467C8EB@TK5EX14MBXW652.wingroup.windeploy.ntdev.microsoft.com>
The following are based on the version of the HTML 5 spec at http://dev.w3.org/html5/spec/Overview.html 25 Aug working draft.



HTML section: 7.1, the hidden attribute



issue: Accessibility APIs must honor this.



Comment:
User agents will need to ensure to reflect the state of this attribute in their accessibility APIs.  This may be stating the obvious but is worth calling out since there are various situations today where AT products do or do not show the same text that is visually displayed and this is another potential variable to keep in mind.


UAWG: We need to develop some kind of test criteria around this, espeically for AT support/compat

HTML section: 7.3 scroll into view

Accessibility Issue: What should happen to focus here, especially keyboard focus?  This is an interesting one.  The GL talks about calling attention at times as in The scrollIntoView([top]) method, when called, must cause the element on which the method was called to have the attention of the user called to it.  Exactly what this means for accessibility and how UA should do this in an accessible fashion are good things to think about.

HTML section: 7.9 drag and drop
Accessibility Issue:  This still seems plagued with accessibility actions.  This needs more discussion around accessibility.  Is it enough to say that the start/end point experiences of the drag/drop must be accessible.  What about everything that can happen along the journey?  I think we need to discuss this one further with PF and ourselves.
Received on Thursday, 27 August 2009 15:53:36 GMT

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