Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • B bootstrap
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 263
    • Issues 263
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 114
    • Merge requests 114
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Bootstrap
  • bootstrap
  • Issues
  • #33715
Closed
Open
Issue created Apr 22, 2021 by Administrator@rootContributor

"Dialog" is not announced for modals

Created by: Malvoz

Repro steps:

  1. Start NVDA (or perhaps the screen reader of your choice)
  2. Visit https://getbootstrap.com/docs/5.0/components/modal/#live-demo
  3. Open the modal dialog

Expected: "Dialog" should be announced (along with the content of the modal).

Result: "Dialog" is not announced.

I noticed that manually moving role="dialog" (although moving tabindex="-1" instead may also work) from its current <div class="modal"> element to the child <div class="modal-dialog"> the result is that "dialog" is announced.

This may be an NVDA bug (I'll probably wait with reporting until I get feedback here). It could be that this has to do with the fact that the standard <dialog> element must not have a tabindex attribute, and therefore for some reason NVDA fails to announce the ARIA role, but perhaps that's totally unrelated.

If others can confirm that this does not work as expected (in NVDA and/or another screen reader) that'd be much appreciated.

Environment:

  • Windows 10.0.19042
  • Chrome 90.0.4430.85
  • NVDA 2020.4

/cc @patrickhlauke

Assignee
Assign to
Time tracking