Frontend DogmaKeyboard Accessibility: The Clearest Signal of Digital Maturity, by @deconspray:
JectureWCAG 2.2 raised the bar on focus indicators with SC 2.4.11, and a lot of teams haven't caught up. The A11y Collective's guide covers contrast ratio requirements, minimum size, and why removing the default browser outline is still one of the most common accessibility failures in production. Good reference to share with any design team that's still using outline: none.
#accessibility #WCAG #keyboardnavigation
Tab into a data table, press arrow keys to read across a row. Nothing happens. This is one of those silent failures that never shows up in axe scans but completely breaks the experience for keyboard users. The fix is simpler than you'd think: add tabindex="0" to the scrollable container so it can receive focus, and keyboard scrolling works immediately.
#accessibility #keyboardnavigation #CSS
https://css-tricks.com/why-keyboard-users-cant-scroll-your-overflow-containers/
Why Keyboard Users Can't Scroll Your Overflow Containers | CSS-Tricks
When a keyboard user Tabs into the table, its focus lands on a cell. Then they press the arrow keys to read across the row but nothing happens. Your screen reader users never noticed because they navigate the accessibility tree, not the scroll container.
Focus indicators are one of the most commonly botched WCAG requirements, mostly because they get treated as a visual afterthought. This guide covers the actual WCAG 2.2 criteria (2.4.11 and 2.4.12) with practical techniques for building focus styles that actually pass without looking terrible. Good reference to send when a designer says "can we just remove the outline."
#accessibility #WCAG #keyboardnavigation
Why Keyboard Users Can’t Scroll Your Overflow Containers, by @csstricks:
https://css-tricks.com/why-keyboard-users-cant-scroll-your-overflow-containers/
Why Keyboard Users Can't Scroll Your Overflow Containers | CSS-Tricks
When a keyboard user Tabs into the table, its focus lands on a cell. Then they press the arrow keys to read across the row but nothing happens. Your screen reader users never noticed because they navigate the accessibility tree, not the scroll container.
Focus Indicators 101: A Simple Guide for Developers, by @popetech.bsky.social:
https://www.youtube.com/watch?v=uT-MWywxv74
#videos #introductions #guides #focus #keyboardnavigation #accessibility
Focus indicators 101: A simple guide for developers
A Guide to Accessible Focus Indicators, by @popetech.bsky.social:
https://blog.pope.tech/2026/03/04/a-guide-to-accessible-focus-indicators/
Does Your Navigation Need an ARIA Menu? Probably Not, by @popetech.bsky.social:
https://blog.pope.tech/2026/02/10/does-your-navigation-need-an-aria-menu-probably-not/
Accessibility, by @bogdanlazar.com and @mgifford (@httparchive.org):
https://almanac.httparchive.org/en/2025/accessibility
#webalmanac #studies #research #metrics #accessibility #colors #contrast #zooming #scaling #internationalization #keyboardnavigation #skiplinks #forms #labels #placeholders #multimedia #images #aria #overlays #ai
5 Accessibility Checks to Run on Every Component, by @hdv (@zeroheight):
https://zeroheight.com/blog/5-accessibility-checks-to-run-on-every-component/
#accessibility #components #testing #keyboardnavigation #designtokens #microcontent #zooming #screenreaders
