As a contributor to the Chromium project, Microsoft has put forward an implementation for the focusgroup technology. This aims to streamline website navigation using only the keyboard, completely eliminating the need for a mouse or touchscreens.
Microsoft believes there is a pressing demand to refine the methods for building accessible websites, particularly those manageable via keyboard input. Currently, the tool for this is the tabindex HTML attribute, which permits cycling through interactive elements with the TAB key and activating them using ENTER. Developers can specify the order in which elements receive “focus” through sequential TAB presses.
In practical application, however, this existing mechanism proves quite cumbersome. Microsoft notes that contemporary websites feature intricate components like nested menus, toolbars, tabs, and sets of input fields. Implementing keyboard navigation for these structures demands considerable expertise and effort. For developers, this translates into either complicating the site’s underlying code or integrating external JavaScript libraries—both of which degrade site performance because a larger volume of code must execute upon page load.
As an alternative, Microsoft originally proposed the focusgroup technology back in 2022. This concept envisions a two-tiered navigation system: pressing the TAB key shifts focus between predefined groups of elements, and within any selected group, navigation between individual items is handled using the arrow keys. Tagging these element groups within the site’s source code is considerably less complicated.
Microsoft’s vision is now moving beyond mere concept. The company has submitted their focusgroup implementation to the Chromium project and initiated testing within their own Edge browser, which shares the same underlying platform. Its inclusion in Chromium means that developers of other browsers based on the same engine will have the option to adopt this technology if they choose. At this stage, Microsoft is actively soliciting feedback from both end-users and developers concerning the feature’s performance and efficacy.
About the Author
