12 reviewed
Commit | Summary | Notes |
---|---|---|
7ce0b474 | Further tabIndex getter tweaks |
[OK] These default values seem reasonable (noted that, at least currently, SVG elements only get a default tabIndex of 0 if they've an href, which matches HTML). SVG links still need correctly labelling, as would objects. |
7952ba43 | Make the default tabIndex for <frame> 0 |
[OK] |
f5ae47e5 | Make autofocus="" a global attribute |
[OK] Normal accessibility considerations apply - this only widens the scope of the attribute as opposed to changing behaviour. Note: Firefox does not support it, and Chrome/Edge only apply it to focusable elements, as per the referenced TPAC consensus and that seems most sensible. |
2d783dbb | Update autofocus processing algorithm |
[OK] Could check with devs? |
d19d9632 | Update sequential focus navigation to include shadow trees |
[OK] This and related commits (below) implemented the feature as specced by W3C, though there were some concerns within W3C, e.g.: https://github.com/w3c/webcomponents/issues/554 - ultimately however the issue was closed with the status quo. |
1ab7c860 | Define different types of focusability |
[OK] This both reflects real-world behaviour and clarifies it. |
133607f1 | Handle delegates focus in the focusing steps |
[OK] Relates to d19d9632 |
3bbb8701 | Tweak shadow host focus delegation |
[OK] Relates to d19d9632 |
b48bb223 | Prevent double-focusing with autofocus="" inside <dialog> |
[OK] |
bcd5d619 | Make autofocus="" work with delegatesFocus and <area> |
[OK] Supported in Chrome/Edge; not Firefox |
a1a503a0 | Add Accessibility considerations to element definitions |
[OK] Most helpful :-) |
6bbf2258 | Add "Accessibility considerations" for custom elements |
[OK] Most helpful :-) |