Closed Bug 2022592 Opened 1 month ago Closed 29 days ago

Dialog opened with a dialog-button is missing accessible name for the container

Categories

(Firefox :: Settings UI, defect)

defect

Tracking

()

RESOLVED INVALID
Accessibility Severity s3

People

(Reporter: ayeddi, Unassigned)

References

Details

(Keywords: access, good-first-bug)

Attachments

(1 file)

Steps to reproduce (STR):

  1. Have a screen reader running (i.e. NVDA on Windows OS).
  2. Using keyboard navigation, navigate to an instance of the <dialog-button> element and activate the button that triggers this dialog
    1. For instance, on the Storybook example for Domain-specific UI Widgets > Settings > Dialog Button > Default, activate Manage certificates... button
  3. Confirm that the dialog is opened and observe the screen reader's announcement of this dialog's content.

Expected results:

  1. The dialog container should include accessible name that is set on it explicitly, i.e. a screen reader would announce this name of the dialog once the dialog is opened and keyboard focus is moved into it.

Actual results:

  1. The dialog container is not communicating its accessible name

Recommendation:

  1. Set an on-screen string for the dialog to have a unique id
  2. Update the dialog container to have aria-labelledby attribute that is set to the on-screen string's id

Thanks for going through Storybook and auditing this! I am going to mark this as INVALID though since we're not using this dialog-button anywhere in the Settings code. We ended up using moz-box-button for this case. See Bug 2023625 for more details about removing the dialog-button in the preferences/ folder.

Status: NEW → RESOLVED
Closed: 29 days ago
Resolution: --- → INVALID
See Also: → 2023625
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: