.jpg "Review: Motorola Moto G Stylus 2026")
If you’ve ever tried navigating a website without a mouse — maybe your trackpad died mid-presentation, or you simply prefer keeping your hands on the keyboard — you already know the frustration. Half the page is off-limits. Buttons don’t respond. Menus mock you from a distance.
Turns out, you’re not alone: roughly 50% of websites skip tabindex entirely, a basic building block for making keyboard navigation work. Microsoft wants to fix that — and it’s not waiting for developers to figure it out on their own.
A simpler way to build keyboard-friendly websites
The Edge team just announced focusgroup, a new HTML attribute that makes keyboard-accessible web design dramatically simpler. Developers add one attribute to their HTML and the browser takes it from there — no convoluted tabindex logic, no third-party libraries fattening up your codebase.
Arrow keys behave the way users actually expect, hidden or disabled elements get quietly skipped over, and it even works inside shadow DOM without throwing a tantrum.
The problem it’s solving has quietly plagued developers for years. Building a fully keyboard-accessible site — one with menus, submenus, toolbars, and tab groups — isn’t simple. It takes significant time, specialized knowledge, and a pile of JavaScript that your users then have to download every time they visit.
More code means slower load times, and slower load times mean frustrated users.
Less code, faster pages, better accessibility
Microsoft first sketched out focusgroup back in 2021, then brought it to the OpenUI community group in 2022 — so this isn’t a weekend project. It’s been baking for years, with input from across the browser ecosystem.
The beneficiaries are wide: people with motor disabilities, power users, enterprise workers navigating complex dashboards — basically anyone who’s ever hit Tab and prayed.
Right now it’s live for early testing in Edge, and Microsoft has pushed the code upstream to the Chromium project — which means Chrome and its many siblings could pick it up too. If the rest of the browser world follows suit, what looks like a quiet developer tool could end up reshaping how accessible the web feels for millions of people who never touch a mouse.
