2008186 - Dialog lacks role (Settings dialog > Topics dialog)

Status: RESOLVED WORKSFORME

(Firefox :: New Tab Page, defect)

Description

[John Northup]

Steps to Reproduce

Open DevTools. Activate the Customize button. Within the Settings dialog, activate the Manage topics button. The Topics dialog opens. Inspect the dialog container.

Expected Behavior

Dialog container is a <dialog> (preferred) or has role="dialog".

Actual Behavior

Dialog is implemented using a generic container without a programmatically determinable dialog role.

User Impact

AT cannot identify the content as a dialog.

WCAG 2.2 References

• WCAG 4.1.2 - Name, Role, Value

Recommendations

Change dialog container to a <dialog> (preferred) or apply role="dialog" to the existing container.

Testing Environment

Any

Assistive Technology Used

Any or None

Code Pointers

<div class="sections-mgmt-panel sections-mgmt-panel-enter-done">

Further Reference

• W3C WAI APG: Modal Dialog Example

Comment 1

[John Northup]

Attachment: Topics dialog open

Comment 2

[Ina Popescu, Desktop QA]

The issue can be seen as described by the reporter in Nightly 149.0a1. Marking as NEW.

Comment 3

[❌ Anna Yeddi [:ayeddi] ❌ On leave until 2027-01-04]

Attachment: NVDA output showing the "Topics button" is focused and announced after the view within a "settings" dialog was changed, A11y DevTools are showing this is the view within that dialog

This is a change in a view within existing "Settings" dialog and the focus is placed on the header (first focusable element of the new content), thus user is notified of the change by the announcement of the focused element ("{Topic} button").

That's being said, when the bug 2008117 the structure of the "< Topics" button would be resolved, this bug should be re-evaluated to ensure the change in the content of the dialog is being communicated to assistive technology users appropriately.