W3C home > Mailing lists > Public > public-html@w3.org > July 2014

Re: HTML focusable areas feedback

From: Steve Faulkner <faulkner.steve@gmail.com>
Date: Sat, 26 Jul 2014 21:34:05 +0200
Message-Id: <554BC586-6B04-42A6-B78F-1632103DABA6@gmail.com>
Cc: "public-html@w3.org" <public-html@w3.org>
To: "james.nurthen@oracle.com" <james.nurthen@oracle.com>
Hi James

Sent from my Chorizone 

> On 26 Jul 2014, at 20:38, "james.nurthen@oracle.com" <james.nurthen@oracle.com> wrote:
> 
> 
> 
>> On Jul 26, 2014, at 10:43, Steve Faulkner <faulkner.steve@gmail.com> wrote:
>> 
>> Hi James 
>> 
>> Sent from my iPhone
>> 
>>> On 26 Jul 2014, at 18:59, James Nurthen <james.nurthen@oracle.com> wrote:
>>> 
>>> If these are focusable by default (as is currently the case in FF) then 2 additional things need to happen
>>> 1) it MUST be possible for a web developer to reverse this behaviour. The current FF behaviour is causing us issues in some combobox implementations and needs to be resolved. I would suggest allowing tabindex=-1 to ensure the area is never focusable. This does not work in the current FF implementation
>> 
>> Does using tabindex=-1 resolve the issue in FF?
> 
> No. FF still focuses it. 

Suggest that is a bug, best to file one against FF

>> 
>>> 2) An accessible name and role needs to be provided for this region so AT can determine what to speak when it gets focus.
>> 
>> Being scrollable, I would suggest, is a property not a role.
> 
> What role would you give it then?

If the element already has a role there is no need. 
<section> for example has a default role of region.
If not would depend on what the element content was, I think.

> 
>> 
>> 
>>> 
>>> Regards,
>>> James
>>> 
Received on Saturday, 26 July 2014 19:34:43 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:16:39 UTC