- From: <bugzilla@wiggum.w3.org>
- Date: Mon, 11 Jan 2010 19:55:43 +0000
- To: public-html-a11y@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8715
Summary: Scrolling elements into view
Product: HTML WG
Version: unspecified
Platform: PC
URL: http://dev.w3.org/html5/spec/editing.html#scrolling-
elements-into-view
OS/Version: All
Status: NEW
Keywords: a11y, a11ytf
Severity: normal
Priority: P2
Component: HTML5 spec bugs
AssignedTo: dave.null@w3.org
ReportedBy: joshue.oconnor@cfit.ie
QAContact: public-html-bugzilla@w3.org
CC: ian@hixie.ch, mike@w3.org, public-html@w3.org, public-
html-a11y@w3.org
As the scrollIntoView([top]) method is all about giving focus it is important
that the needs of non-visual users are covered in a more explicit way.
The spec currently states that:
"Non-visual user agents may ignore the argument, or may treat it in some
media-specific manner most useful to the user."
This seems very vague.
Should the spec not offer more concrete advice? Such as:
"Non-visual user agents may provide focus to the top most relevant element
within the window view, for example by giving focus to the most relevant
heading when the method is called. This will help users of Assistive Technology
such as a screen reader, orientate themselves.
Where there are no relevant elements, then non-visual user agents may ignore
the argument, or may treat it in some other media-specific manner that would be
most beneficial to the user".
--
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Monday, 11 January 2010 19:55:45 UTC