As a quick sense check, ask yourself the following:
- Does the feature include showing and hiding of content? If so, you need JS to at minimum “toggle aria and enable closing on
- Is the natural focus order the most ideal? “If the natural order loses the relationship between a trigger and the element it triggered, or a keyboard user can’t even access the content via natural tab order, then you need JS to assist in focus management”
- Does the effect rely on hover and/or focus? You may need JS to make an alternative solution “for touch screen users and those using desktop zoom of 200%+ or magnification software”
Tooltips should be used as a last resort. Ask yourself why you’re adding this text to the UI, and where else it could go. But if you do use one, make sure it’s dismissable without moving hover or focus, that its contents can be hovered without it disappearing, and that it doesn’t disappear based on a timeout.
Modals, as we’ve covered in previous frequent11y issues, would ideally be implemented with a HTML native
<dialog> element, but it isn’t currently accessible. Custom solutions need JS because it should be dismissable with the
Esc key, and the keyboard focus should be trapped inside. As to what to focus on when opening the modal, Stephanie’s presented a decision tree.
Tabs need to toggle
tabindex="0" and all the others to
Dropdown menus need JS, even though we now have CSS’s
:focus-within property, because we still need to toggle
aria-expanded, be able to close the open menu button with
Esc and implement arrow keys for navigating between menu items.
Prefer longer newsletters? You can subscribe to week11y, fortnight11y or even month11y updates! Every newsletter gets the same content; it is your choice to have short, regular emails or longer, less frequent ones. Curated with ♥ by developer @ChrisBAshton.