Repository navigation
docs(public-docsite-v9-headless): add Accessibility section - #36968
Open
Victor Genaev (mainframev) wants to merge 2 commits into
Open
Victor Genaev (mainframev) wants to merge 2 commits into
Victor Genaev (mainframev) wants to merge 2 commits into
Conversation
📊 Bundle size report✅ No changes found |
Victor Genaev (mainframev)
force-pushed
the
docs/headless-a11y-section
branch
from
October 21, 2026 10:32
9c7ff71 to
bca7453
Compare
|
Pull request demo site: URL |
Victor Genaev (mainframev)
force-pushed
the
docs/headless-a11y-section
branch
2 times, most recently
from
October 21, 2026 11:12
3d4020e to
c7025e9
Compare
Victor Genaev (mainframev)
marked this pull request as ready for review
October 21, 2026 11:19
Replace the single Overview/Accessibility page with an Accessibility section: Overview, Keyboard navigation (focusgroup), Overlays (<dialog> and Popover API), Focus indicator, and Disabled & native controls, with live Do/Don't examples built from headless components and CSS modules. Move the data-attribute reference to a new Guides/Styling state page.
… components Describe native <dialog> Tab behavior in the Dialog, Drawer, Nav, Popover and TeachingPopover docs and link to the Overlays accessibility page.
Victor Genaev (mainframev)
force-pushed
the
docs/headless-a11y-section
branch
from
October 21, 2026 11:24
c7025e9 to
41fa2e2
Compare
Victor Genaev (mainframev)
added a commit
to mainframev/fluentui
that referenced
this pull request
Oct 21, 2026
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Previous Behavior
The headless docsite had a single
Overview/Accessibilitypage with a generic summary. Parts of it were out of date: it said Accordion headers setaria-controls(they don't) and described a JavaScript focus trap (modal dialogs use native<dialog>). It didn't cover focusgroup, overlays, forced colors or disabled-focusable controls.New Behavior
An
Overview/Accessibilitysection modeled on the v9 Concepts/Developer/Accessibility docs, rewritten for unstyled components:focusgroupworks, loading the polyfill, thefocusgroupvalue, arrow keys, wrapping and Tab re-entry per component, usingfocusgroupin custom components, polyfill limitations.<dialog>+showModal(),popover="auto" | "manual" | "hint"), differences from the styled components, reading order, inert, Tab in modal overlays, focus on open,popover="auto"closing other popovers, Escape and light dismiss, the missing Popover API case.:focus-visible, contrast and size, forced colors,aria-activedescendantoptions, with a live Do/Don't example.aria-pressed),disabledvsdisabledFocusable, keeping native inputs, with live Do/Don't examples.Screenshots
Accessibility / Overview
Accessibility / Keyboard navigation
Accessibility / Overlays
Accessibility / Focus indicator
Accessibility / Disabled & native controls
Guides / Styling state