#focusgroup
Here's what actually moves the needle:

The Browser Features That Could Actually Move Accessibility Forward

`focusgroup` and `ariaNotify()` Address Structural Barriers

#Accessibility #ADA #WebStandards #BrowserInteroperability
The Browser Features That Could Actually Move Accessibility Forward
Sara Soueidan's Interop 2027 picks represent a shift in how the web platform handles accessibility. Two proposals — focusgroup and ariaNotify() — could reduce barriers for screen reader and keyboard users.
accessibility.chat
November 9, 2026 at 7:02 PM
This is a good list. (I’m looking forward to see how devs and “AI” tools break sites with focusgroup, but I have not been able to make my concerns heard.)
For your amusement, my Interop 2027 picks: https://adrianroselli.com/2026/11/my-interop-2027-picks.html I link to others who are smarter than I. If I didn’t link yours, it’s not because I think you’re not smarter, I just don’t know you made a list. So link it here?
toot.cafe
November 11, 2026 at 6:22 AM
Interest invokers mainly, but now I’m suspect of any feature that makes it into stable before it lands in a spec (e.g. focusgroup). Shipping to stable signals that authors can start using it with a polyfill.
October 30, 2026 at 5:54 PM
Updates on CRAN: accessibility (1.6.0), aniSNA (1.2.1), ast2ast (1.1.2), autograph (1.2.8), BayesianQDM (1.0.0), BIOdry (0.9.6), cdcanthro (0.5.0), CERFIT (0.2.1), contdid (0.1.2), DSIR (0.13.0), fido (1.1.5), FocusGroup (0.5.6), frailtyEM (1.0.2), GaussSuppression (1.3.2), GeoModels (2.3.0)
October 30, 2026 at 9:17 PM
Updates on CRAN: accessibility (1.6.0), aniSNA (1.2.1), ast2ast (1.1.2), BayesianQDM (1.0.0), CERFIT (0.2.1), DSIR (0.13.0), FocusGroup (0.5.6), frailtyEM (1.0.2), geozarr (0.3.0), glyparse (1.0.0), golfastr (0.3.0)
October 30, 2026 at 3:29 PM
Interest invokers mainly, but now I’m suspect of any feature that makes it into stable before it lands in a spec (e.g. focusgroup). Shipping to stable signals that authors can start using it with a polyfill.
October 30, 2026 at 5:54 PM
Making a custom toolbar accessible with keyboard navigation usually requires a lot of JavaScript code.

The experimental `focusgroup` HTML attribute aims to make this much easier by letting the browser handle arrow-key navigation for you. 👇

#WebDev #a11y #HTML

1/4
October 26, 2026 at 9:00 PM
A basic implementation looks like this:
<div focusgroup="toolbar">
<button>Cut</button>
<button>Copy</button>
</div>

How do you currently handle arrow-key navigation in your projects? Let me know!

You can find more detail and a link to the proposal on my profile blog.

4/4
October 26, 2026 at 9:00 PM
Here is what `focusgroup` does:

1. Native arrow-key navigation:
- Users can use arrow keys to move between buttons or menu items automatically.

2. Less custom JavaScript:
- You do not need to write complex keyboard event listeners. The browser manages the active focus state.

2/4
October 26, 2026 at 9:00 PM
🎉
October 12, 2026 at 3:09 PM
focusgroup and referenceTarget are huge for accessibility!
October 11, 2026 at 9:00 PM
Safari’s “Listen to page” feature pronouncing the HTML `focusgroup` attribute:

“foc-us-group”
October 11, 2026 at 11:28 AM
Even though I did rank focusgroup as my number two, since the functionality previously required JS, it’s quite easy to start using today and just use a polyfill (despite some hiccups with focusgroup + popover).
October 11, 2026 at 10:48 AM
For the polyfill, this has a workaround (setting tabindex=0 on the buttons): github.com/microsoft/po...

Also a since fixed bug where popover semantics would clobber the focusgroup semantics: issues.chromium.org/issues/56467...
focusgroup: visibility check is unfortunate for focusgroup=menu in a popover · Issue #74 · microsoft/polyfills
It is very difficult to get the focusgroup polyfill to work when a focusgroup=menu is a popover or is within a popover. <div focusgroup=menu popover> <button>Save</button> <button>Fork</button> <bu...
github.com
October 11, 2026 at 12:06 PM
Going through the Interop list of features interop-rank.fxdx.dev and selecting and ranking the ones I want to see across browsers in 2027.

I chose 15 features.

At the top of my list are #HTML #a11y features `focusgroup`, ariaNotify(), `headingoffset` and `headingreset`.
2027 Web Platform Feature Ranking
Rank the Interop 2027 features you care most about
interop-rank.fxdx.dev
October 11, 2026 at 9:31 AM
I agree with pretty much all of these 🙂

Also you're the first (out of the ones you linked) that includes HTML focusgroup in their picks. This is my top ask also. I worry that the fact that the spec PR is still open will preclude this from being considered for Interop 2027... but fingers crossed.
October 11, 2026 at 11:39 AM
My top 9 / 34 prioritized features :

1. HTML `focusgroup`
2. JS `Temporal`
3. CSS transition with `display`
4. CSS `calc-size()` function
5. HTML `headingoffset` to works with components
6. CSS `var()` in sizes Containers Queries
7. HTML Responsive iframe to avoid double scroll
8. CSS […]
Original post on mamot.fr
mamot.fr
October 11, 2026 at 11:11 AM
> despite some hiccups with focusgroup + popover

I'm using the polyfill and make heavy use of popover. Haven't hit any hiccups yet, but if you have some pointers maybe it will save me some headache in the future?
October 11, 2026 at 12:01 PM
Heh I was just talking about exactly that with someone last night. I think it'd work really well in combination with a whole bunch of the interactive list examples in the post.

Interactive list + focusgroup + link/clickDelegation could make a no-JS single-tab-stop nav or set of cards really easy.
October 9, 2026 at 10:41 PM
Done! Here are my top five. Can't wait for `Temporal`!
October 8, 2026 at 4:49 PM
Feels like lists with buttons and (urgh) focusgroup covers most of the use cases in a backwards-compatible way?

(Grids are already a pattern that people implement terribly, and devs interfering in tab order/arrowing is almost always going bad.)
October 8, 2026 at 9:15 PM
That wouldn't address the mode-switching issue, since the semantics of lists +buttons wouldn't support arrowing (actually have a line about that in there because it's come up before 😅).

Using focusgroup also requires choosing a token, likely `toolbar`, which doesn't really cover the use cases.
October 8, 2026 at 9:21 PM
Chioke Dmachi as Tyler Durden in a Fight Club reimagining 🎬

www.youtube.com/shorts/lUJsk...

#chiokedmachi #chioke #Dmachi #heartlessreign
Fight Club Reimagined Chioke Dmachi - Topic Dmachi as Tyler Durden
YouTube video by FocusGroup Entertainment
www.youtube.com
October 7, 2026 at 3:29 PM