mui / mui/material-ui

[docs] MUI Snackbar Accessibility

Open
#45,243 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

accessibility docs scope: toast support: docs-feedback
Dominant language
JavaScript
Stars
99.1k
Forks
32.5k
Avg merge
2d 17h
Merged PRs (30d)
106

Description

Related page

https://mui.com/material-ui/react-snackbar/

Kind of issue

Other

Issue description

The demo on https://v5.mui.com/material-ui/react-snackbar/#introduction does not talk about how to make the Snackbar accessible for tabbing into it when it's dynamically created, and I can't find much information about this issue.

Context

I am trying to make our Snackbar accessible via keyboard navigation - it is somewhat accessible, however, not fully. Basically, we have a notification service which triggers the Snackbar to appear which has a "X" button to close it and sometimes another nested link. I cannot tab into that Snackbar notification unless I tab through the entire page, which is not feasible. Our desired outcome would be to have that Snackbar be next in the tab order, like how the "Open Snackbar" demo on https://v5.mui.com/material-ui/react-snackbar/#introduction works, however I could not get that to work with dynamic Snackbars.

Search keywords: Snackbar Keyboard Navigation Tab Order / Focus

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the related Material UI Snackbar page and its Introduction demo, then compare their documented focus behavior with dynamically created Snackbars containing a close button or nested link. Done means the documentation explains how keyboard users can reach dynamic Snackbar content and clarifies the expected tab order or focus approach.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, react
Domain
accessibility, documentation, frontend
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.