Consider changing the default macOS focus behaviour to include links and form controls
Categories
(Core :: DOM: UI Events & Focus Handling, task)
Tracking
()
People
(Reporter: morgan, Unassigned)
References
Details
STR:
- Load
data:text/html,<select><option>hello</select><button>world</button><a href="mozilla.org">link</a> - In macOS system preferences > keyboard > ensure the Keyboard Navigation toggle is off, and the same checkbox in about:preferences is unchecked
- Attempt to tab the loaded page
Currently:
the select and button are focusable but the link is not
With either the macOS or firefox setting enabled, links and controls are focusable.
On non-mac platforms, links and controls are focusable by default. Should we default this new firefox setting to "on" to standardise?
|
||
Updated•2 years ago
|
|
Reporter | |
Comment 1•2 years ago
|
||
Based on dbolter's comment here I'm inclined to turn this on -- are there any objections? Anyone we should consult who I didn't NI?
|
||
Comment 2•2 years ago
|
||
We should probably track this in a single place, this has been proposed a number of times: bug 1036966, bug 396534, bug 1231014, plus other dupes of bug 1036966.
Since bug 1036966 has more discussion, I propose to move this discussion there (duping this bug) and making the call in there, wdyt?
In general, I'm supportive of this, but historically Neil Deakin has had strong opinions about it. I'd recommend checking with him and also with Spohl, Markus Stange and the other Widget :: Cocoa peers, and probably Olli (smaug) too. For reference, there's precedent of changing the default for web content to deviate from macOS's behavior (in bug 1614658).
Might be worth sending a PSA (Intent to prototype or something) to dev-platform@, just in case I've missed someone?
|
|
Reporter | |
Updated•2 years ago
|
Also supportive of this change -- can't think of any downsides, only upsides from a product perspective.
|
|
Reporter | |
Comment 5•2 years ago
|
||
(In reply to Emilio Cobos Álvarez (:emilio) from comment #2)
We should probably track this in a single place, this has been proposed a number of times: bug 1036966, bug 396534, bug 1231014, plus other dupes of bug 1036966.
Since bug 1036966 has more discussion, I propose to move this discussion there (duping this bug) and making the call in there, wdyt?
In general, I'm supportive of this, but historically Neil Deakin has had strong opinions about it. I'd recommend checking with him and also with Spohl, Markus Stange and the other Widget :: Cocoa peers, and probably Olli (smaug) too. For reference, there's precedent of changing the default for web content to deviate from macOS's behavior (in bug 1614658).
Might be worth sending a PSA (Intent to prototype or something) to dev-platform@, just in case I've missed someone?
Sounds good, I'll send something out and ping those folks on slack :) Thank you!
|
||
Comment 6•2 years ago
|
||
(In reply to kbryant from comment #4)
Also supportive of this change -- can't think of any downsides, only upsides from a product perspective.
+1, I think all the users who are relying on a keyboard already have this pref on or would love to have it on or are using addons or extra software, but the users who are just starting using the keyboard and/or new to Fx users and/or engineers starting testing accessibility of their websites on macOS would be affected in a positive way. After all, it is expected to get to controls with a keyboard and this is what most if not all of the instructions would recommend (i.e. "check if you can Tab to all buttons" or similar).
My vote is to turn it on by default. Thank you, Morgan, for advocating for it!
|
|
||
Comment 7•2 years ago
|
||
Okay, let's track this in bug 1036966.
|
|
||
Comment 8•2 years ago
|
||
Description
•