- From: Patrick H. Lauke <redux@splintered.co.uk>
- Date: Tue, 15 Oct 2019 11:23:23 +0100
- To: w3c-wai-ig@w3.org
And copying some further thoughts here, for archival: you may need to use "focus" in the more generic sense. but preface it with something similar to the current wording of "focus visible": "Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible." i.e. you don't want to necessarily MANDATE that focus be visible as a result of click/tap (as that would then also completely disallow :focus-visible and current browser heuristics) frankensteining something together like "When a keyboard operable User Interface Component receives focus, and the user is operating the interface component with a keyboard, ..." it's admittedly awkward, but need to make sure we don't mandate things we shouldn't by accident... maybe it can then get away with a note in understanding about how "focus" may, depending on the type of interface control, match the element that has the current programmatic focus (in the document.activeElement sense) or the "logical" focus (e.g. the aria-activedescendant) but with a further note that in some very specific cases, there might indeed be two elements that do have focus at the same time (like combobox with listbox), and then there the requirement for the focus indication does apply to both. P -- Patrick H. Lauke www.splintered.co.uk | https://github.com/patrickhlauke http://flickr.com/photos/redux/ | http://redux.deviantart.com twitter: @patrick_h_lauke | skype: patrick_h_lauke
Received on Tuesday, 15 October 2019 10:23:28 UTC