W3C home > Mailing lists > Public > public-html-a11y@w3.org > February 2010

[Bug 8715] Scrolling elements into view

From: <bugzilla@wiggum.w3.org>
Date: Mon, 08 Feb 2010 11:54:09 +0000
To: public-html-a11y@w3.org
Message-Id: <E1NeSBt-0006Ta-SQ@wiggum.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8715


Joshue O Connor <joshue.oconnor@cfit.ie> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |joshue.oconnor@cfit.ie




--- Comment #2 from Joshue O Connor <joshue.oconnor@cfit.ie>  2010-02-08 11:54:08 ---
Ian said:
>I don't understand. "Non-visual user agents may provide focus to the
>top most relevant element" doesn't make sense to me. How can there be a
>top-most anything if it's not a visual UA?

The notion of a 'view' is relative in different modalities. Some users are
sighted, some not. A sighted person may glance at a page and quickly understand
context etc, a non-sighted person may need to be able to easily navigate to an
area of the page, or quickly tab to various elements to be given this sense of
context. Do you follow?

If so, there should be a way of supporting a non-visual mode of access (the
spec currently refers to it as "media-specific manner most useful to the
user"). I suggest the text needs to be more specific in /how/ to do this. In
its simplest terms - this could be for example, a parent element in the DOM
etc.


-- 
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, 8 February 2010 11:54:12 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 04:42:01 GMT