WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Modal dialogs and page titles

for

From: Geethavani.Shamanna
Date: Apr 24, 2024 9:50AM

Thank you, this is very helpful. I will file a bug on the NVDA GitHub page.

Geetha
-----Original Message-----
From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of Birkir R. Gunnarsson
Sent: Wednesday, April 24, 2024 12:48 PM
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: Re: [WebAIM] Modal dialogs and page titles

External email: if the sender or content looks suspicious, please click the Report Message icon, or forward it to report-phishing

What is announced when you press the title keyboard shortcut in a screen reader is up to the screen reader vendor. The developer cannot force one or the other.

All that the developer can do is to make sure that the page and the dialog have an accessible name (the <title> element for the page,, aria-labelledby referencing an element with the dialog title or aria-label on the dialog element.
Obviously the dialog you tested was fully accessible so the differences you observed come from the screen reader interpretation of title.

Both Jaws and NVDA have GitHub issue pages where you can file an issue if you feel the screen reader is not reading the most useful info for the context. The NVDA GitHub in particular is very responsive and often generates good discussion.
All you need to file an issue is a GitHub account, and then Google NVDA GitHub and click "issues" and "new issue".

Let us know if you end up filing one, I am curious to see where that discussion goes.


On Wed, Apr 24, 2024 at 7:38 AM <EMAIL REMOVED> < <EMAIL REMOVED> > wrote:

> Expected Behavior:
> The ideal behavior is for screen readers to announce the dialog title
> when focus enters the modal. This provides context and helps the user
> understand the purpose of the newly opened content.
> Reasons for Inconsistency:
> * Browser/Screen Reader Differences: How screen readers and browsers
> interact with dialogs can vary, leading to inconsistent reading of titles.
> * Implementation Issues: Even with proper ARIA roles (role="dialog")
> and labeling (aria-labelledby or aria-label), errors in the code can
> prevent screen readers from announcing the title correctly.
> Developer Argument:
> While technically correct that a modal is part of the original page,
> focusing on the page title when a modal is open is unhelpful for
> screen reader users. It disrupts the user's flow and doesn't convey
> the change in context.
> Recommendations:
> * Prioritize Dialog Title: Ensure that the dialog title
> (aria-labelledby or aria-label) is announced when focus enters the modal.
> * Test Thoroughly: Use a combination of screen readers and browsers
> to verify that the titles are read as expected.
> * Educate Developers: Explain to your developer colleagues why
> reading the dialog title is crucial for screen reader users. Reference
> W3C accessibility guidelines for support.
> Resources:
> * ARIA Dialog Role:
> https://deve/
> loper.mozilla.org%2Fen-US%2Fdocs%2FWeb%2FAccessibility%2FARIA%2FRoles%
> 2Fdialog_role&data%7C02%7Cgeethavani.shamanna%40open.ac.uk%7C0ad47b
> ee80e64f861cf708dc64548211%7C0e2ed45596af4100bed3a8e5fd981685%7C0%7C0%
> 7C638495561348039186%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQI
> joiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=Wh6SB5Skf
> 9%2B6Vo8vaVTNO3tOwMTWzzXAy%2BuSHvjAXmw%3D&reserved=0
> Let me know if you'd like more clarification!
> *
> https://gith/
> ub.com%2Fjessarcher%2Fjessarcher.com&data%7C02%7Cgeethavani.shamann
> a%40open.ac.uk%7C0ad47bee80e64f861cf708dc64548211%7C0e2ed45596af4100be
> d3a8e5fd981685%7C0%7C0%7C638495561348053532%7CUnknown%7CTWFpbGZsb3d8ey
> JWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7
> C%7C%7C&sdata=txe%2Fuqu9PgiXGp%2F2IR2clw1%2Fhm5JbXG4%2FIf9zwXY1K4%3D&r
> eserved=0
>
> Dean Vasile
>
>
> 617-799-1162
>
> > On Apr 24, 2024, at 4:58 AM, Geethavani.Shamanna <
> <EMAIL REMOVED> > wrote:
> >
> > Hi all,
> >
> > I noticed some inconsistent screen reader behaviour when reading the
> titles of modal dialogs. On accessing the Add Delivery Address dialog
> on
> > https://ww/
> > w.w3.org%2FWAI%2FARIA%2Fapg%2Fpatterns%2Fdialog-modal%2Fexamples%2Fd
> > ialog%2F&data%7C02%7Cgeethavani.shamanna%40open.ac.uk%7C0ad47bee8
> > 0e64f861cf708dc64548211%7C0e2ed45596af4100bed3a8e5fd981685%7C0%7C0%7
> > C638495561348065744%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQ
> > IjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=dZ%2FW
> > rapoVIlaNwnXEXdlXeI03zCGdOW7LRW6HcptjKo%3D&reserved=0
> > On pressing insert-t, Jaws says 'add delivery address Dialog'. NVDA
> however reads the page title 'Modal Dialog Example|APG|WAI|W3C' whilst
> within the dialog.
> >
> > What is the standard behaviour expected here? Since modals are part
> > of
> the original page, the developers I am working with argue that the
> page title should be read out, even when the focus is within the dialog.
> However, as a screen reader user, I would find it useful if the dialog
> title is read out whilst the focus is within the dialog.
> >
> > Insights appreciated.
> >
> > Many thanks.
> > Geetha
> > > http://list/.
> webaim.org%2F&data%7C02%7Cgeethavani.shamanna%40open.ac.uk%7C0ad47b
> ee80e64f861cf708dc64548211%7C0e2ed45596af4100bed3a8e5fd981685%7C0%7C0%
> 7C638495561348074139%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQI
> joiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=6wsHfI5Zw
> Uxe7ZtKvOEcisvE23a17CiFqn8mV%2BtzfNo%3D&reserved=0
> List archives at
> http://webai/
> m.org%2Fdiscussion%2Farchives&data%7C02%7Cgeethavani.shamanna%40ope
> n.ac.uk%7C0ad47bee80e64f861cf708dc64548211%7C0e2ed45596af4100bed3a8e5f
> d981685%7C0%7C0%7C638495561348079817%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiM
> C4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C
> &sdata=yQJU9%2BuxuGwy1S4%2BQ6GUn0iPw2ISWAS%2FHQzaPr1DnMw%3D&reserved=0
> >


--
Work hard. Have fun. Make history.