approximately 73.2553% of #accesibility issues i've seen recently come from "we decided to keep our UI nice and clean by hiding shit in a tooltip!", followed by the crushing realisation of what it means to have an accessible tooltip #wcag#a11y
what then follows is usually a long series of "bargaining" efforts to justify why the tooltip doesn't need to be keyboard-triggerable, or that it doesn't need to be hoverable with the mouse, or that it's ok that it also contains interactive controls inside it but doesn't receive logical focus, or... when in the end, the simplest answer is "just don't use a bloody tooltip and have the stuff there for all to see/use. at a stretch, use a disclosure widget" #a11y#accessibility
@wtrmt best answer: you don't. less good answer: add extra intermediate step to a tap, even on an interactive control, always first triggers the tooltip, and only THEN the actual action. so now you made each tap take twice as much effort :)
Add comment