WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Meaningful Sequende Question

for

From: Steve Green
Date: Dec 7, 2022 10:35AM

According to the MDN website, the aria-modal="true" attribute is not supposed to do that. They say "Setting aria-modal="true" on dialog and alertdialog role containers indicates the presence of a "modal" element to users of assistive technology, but does not actually make the element modal. The features that make the element actually modal must be implemented by the developer."

https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Attributes/aria-modal

Steve Green
Managing Director
Test Partners Ltd


-----Original Message-----
From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of Brooks Newton
Sent: 07 December 2022 17:28
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: Re: [WebAIM] Meaningful Sequende Question

Hi All,

Does anyone have a list of browsers and versions that correctly parse aria-modal="true" so that the user's Tab sequence is properly constrained within the container marked up with aria-modal="true" with no additional custom focus management?

The reason why I ask has everything to do with user outcomes. I understand that SC 1.3.2 Meaningful Sequence in WCAG 2.x is passed if the Tab sequence "can be programmatically determined." But just because it "can" doesn't mean that the proper Tab sequence "will" be set if the browser/user agent doesn't render the modal content using the content author's intended interaction pattern.

Do content authors have any assurance that if they use the right page code to pass SC 1.3.2 the Tab sequence will achieve an accessible result for users with disabilities who use a keyboard or similar input approach?

Brooks

On Tue, Dec 6, 2022 at 7:22 PM Birkir R. Gunnarsson < <EMAIL REMOVED> > wrote:

> If the content is visually presented as a dialog, it should have a
> dialog role. If it doesn't I'd fail it under WCAG 4.1.2 for not
> presenting its role.
> Also, if it isn't a dialog, what happens when you press tab with focus
> on the last interactive element in the dialog, where does the focus
> end up? Based on that it's possible that I might fail it under 2.4.3,
> but failing it under 1.3.2 would be a bit creative.
> I think there's a 95%+ chance the content is visually presented a a
> dialog/overlay/popover, what have you, and then it needs the dialog
> role (+ accessible name and aria-modal="true" if it is modal) for a
> screen reader user.
>
>
>
> On 12/6/22, Jim Homme < <EMAIL REMOVED> > wrote:
> > Hi,
> > In the page under consideration, there is a link. When the user
> > clicks
> the
> > link, content appears. Focus jumps to the content. In the HTML
> > order, though, the content is below the footer of the page. When the
> > user hits a Close button, focus jumps back to the link the user originally clicked.
> The
> > content below the page footer disappears. Question: would you fail
> > the content below the page footer for logical reading order?
> >
> > Jim
> >
> > =========> > Jim Homme
> > Senior Digital Accessibility Consultant Bender Consulting Services
> > 412-787-8567
> > https://www.benderconsult.com/
> > Support the dreams of independence through employment for students
> > with disabilities with your Amazon purchases.
> > https://smile.amazon.com/ch/83-0988251
> >
> > > > > > archives at http://webaim.org/discussion/archives
> > > >
>
>
> --
> Work hard. Have fun. Make history.
> > > archives at http://webaim.org/discussion/archives
> >