swagger-api / swagger-api/swagger-ui

Correct accessibility issues with Authorization dialog

Open
#10,706 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

backlog cat: a11y
Dominant language
JavaScript
Stars
29k
Forks
9.3k
Avg merge
2d 23h
Merged PRs (30d)
25

Description

  • provide indication that the dialog was opened

  • prevent keyboard navigation from moving outside of the dialog

  • focus the dialog when opening it on operation-level

  • do not focus a random input inside of the dialog

  • provide ability to focus, interact with and check the state of checkboxes

  • select all/none should not be links and should not be nested inside of a heading

  • provide ability to close the dialog with Esc key

  • do not move the focus to the top of the page after closing the dialog

This task covers issues originally reported in:

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 by locating the Authorization dialog entry point in swagger-ui and read the linked issues #7350 and #5290 for the original context. Use the unchecked checklist as the acceptance criteria: address dialog announcement, focus containment and restoration, checkbox interaction, and correct select all/none semantics while preserving the completed Esc behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
accessibility, frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.