|
Today's newsletter is sponsored by ConfigCat — the feature flag service that helps you release features faster and with less risk. More on them at the end of today's newsletter. For accessibility reasons, I sometimes need to programmatically focus on elements that would not normally be focusable. Two noteable examples…
In both examples, you need to add a By default, when the content in question receives focus, it gets a big blue focus ring around it. That ring is an important visual indicator about what has focus for people who navigate by keyboard. But it can look "off" for focus who navigate with a mouse. (This is generally a bigger issue with SPAs and heading focus than a skip nav link, which is typically only used by keyboard users.) To "fix" this without breaking accessibility for people who navigate with a keyboard, you can hide the This pseudo-class gets applied to an element when the browser/User Agent determines (based on user heuristics or behavior) that they would benefit from visible focus indicators. In my experience, if the behavior that triggered the focus event was triggered by a mouse, Are you looking for a service to support dynamic feature flags? ConfigCat is a cross-platform LaunchDarkly alternative that's easy to learn and quick to set up. With SDKs for 19 platforms — including JavaScript, Python, Ruby, Java, and even Rust — you can toggle features on or off without redeploying. ConfigCat subscriptions are the same price regardless of your team size. Get 25% off any paid plan with code Cheers, Want to share this with others or read it later? View it in a browser. |
0 Komentar untuk "[Go Make Things] Tabindex, programmatic focus, and outline styles"