Re: [w3c/webcomponents] Mechanism for setting the tabindex focus flag without sprouting tabindex attribute? (#762) from Alice on 2019-10-16 (public-webapps-github@w3.org from October 2019)

From: Alice <notifications@github.com>
Date: Wed, 16 Oct 2019 02:13:26 -0700
To: w3c/webcomponents <webcomponents@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <w3c/webcomponents/issues/762/542607331@github.com>

> it's also a bit problematic to hard code exactly the set of behaviors Safari has because we need to design this to be forward compatible. 

I don't follow - I'm suggesting the opposite of that: the developer chooses only "always tabbable" or "UA decides", and then the UA decides based on any set of signals it feels is appropriate.

> I thought we didn't want to make decisions about non-AT related behavior based on ARIA?

I wouldn't want to decide focusability wholesale (i.e. which of the four categories I laid out an element should fall into) based on ARIA; I think that it would be appropriate for a UA using ARIA as a signal as to how it determines the focus behaviour of an element which has already been determined to be user-focusable.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/762#issuecomment-542607331

Received on Wednesday, 16 October 2019 09:13:28 UTC