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

Re: [Clarifications] Content focus, Visual Text

From: Ian B. Jacobs <ij@w3.org>
Date: Fri, 26 Jul 2002 22:33:04 -0400
Message-ID: <3D420660.2080005@w3.org>
To: Jim Ley <jim@jibbering.com>
CC: w3c-wai-ua@w3.org

Jim Ley wrote:
> "Ian B. Jacobs" <ij@w3.org>
> 
>>[1] http://www.w3.org/WAI/UA/WD-UAAG10-20020708/
>>
>>1) Checkpoint 9.1 starts:
>>
>>    "1. Provide at least one content focus for each viewport
>>    (including frames) where enabled elements are part of the
>>    rendered content."
> 
> 
> Tom Gilder raised in wai-ig the fact that the above also needs to cover
> elements with CSS overflow property set to produce scrollbars - the
> element with the scrollbars needs to be able to recieve focus - Mozilla
> currently does not make these elements accessible, and IE requires the use
> of the proprietary tabindex extension as an author.
> 
> I propose changing "including frames" to "including frames, and any
> element which can be scrolled" (or similar)

I suspect that what you are asking for is already covered:

  * You must be able to move the content focus to any
    enabled element. Whether you consider the scrolled
    element as part of the same or different viewport,
    checkpoint 9.1 as written covers what you're asking
    for.

  * If you are talking about operating the scrollbars
    themselves through the keyboard, that's covered
    by checkpoint 1.1.

Does this sound correct?

  _ Ian

-- 
Ian Jacobs (ij@w3.org)   http://www.w3.org/People/Jacobs
Tel:                     +1 718 260-9447
Received on Friday, 26 July 2002 22:36:18 GMT

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