WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Meaningful Sequende Question

for

From: Brooks Newton
Date: Dec 7, 2022 11:43AM

Hi Jeremy,

I appreciate your explanation of the role of ARIA markup. I guess that
works out pretty well for browser manufacturers not having to change any of
their wares' behavior based on its presence. How does that work for
developers and users with disabilities? Seems to me like this "not my
problem" approach puts it all back on content owners, who undoubtedly will
interpret what the right thing to do is a number of ways, including many
that don't support access.

Why not make aria-modal into a full-fledged HTML attribute or element
then? Why not handle something as fundamental as focus constraint in modal
content at more centralized source (user agents) for the benefit of
consistency and predictability? Can anyone provide a use case where a
content author marks up a container as modal, but doesn't want focus to be
constrained to that container, unless the user affirmative takes action to
dismiss the modal? If you can think of a case like this, wouldn't that be
the exception and not the rule?

Brooks

On Wed, Dec 7, 2022 at 12:36 PM Jeremy Echols < <EMAIL REMOVED> > wrote:

> And bear in mind this is about how assistive technologies handle the
> attribute, not the user agent. So if assistive tech imposes a limit which
> the unmodified browser doesn't, things can get pretty hairy.
>
>