- From: Ryosuke Niwa <notifications@github.com>
- Date: Wed, 16 Oct 2019 01:42:40 -0700
- To: w3c/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 16 October 2019 08:42:42 UTC
> Do you think that if an author marked a custom element as "UA decides", that the UA could use the element's role, or any other data, as a signal to make that distinction? I thought we didn't want to make decisions about non-AT related behavior based on ARIA? Like I stated previously, 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. If someone somewhere introduced a brand new platform with a new set of exotic rules about which element is mouse & keyboard focusable, and which elements can be focused via sequential navigation, then existing custom elements ideally should adopt to those new exotic rules to a reasonable degree without manual updates / rewrites. -- 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-542593820
Received on Wednesday, 16 October 2019 08:42:42 UTC