Add guidance for handling empty tabpanels - #45233
Merged
Merged
Conversation
Josh-Cena
marked this pull request as ready for review
August 31, 2026 18:08
Contributor
|
Preview URLs (1 page) (comment last updated: 2026-09-12 00:34:37) |
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
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.
Description
Adds guidance to the ARIA
tabpanelrole page on handling panels that have no content to show. It advises against leaving a focusable emptytabpanel(a focus dead-end for keyboard and assistive-technology users), and suggests removing the tab/tabpanel when there is genuinely no content, or giving the panel a placeholder message such as "No data".Motivation
Provides the practical guidance requested in the linked issue so implementers handle empty tabpanels accessibly.
Additional details
Related issues and pull requests
Fixes #30470