E-mail List Archives
Re: expectations role=group / role=region
From: Birkir R. Gunnarsson
Date: Apr 4, 2022 11:23AM
- Next message: glen walker: "Re: expectations role=group / role=region"
- Previous message: Bryan Garaventa: "Re: expectations role=group / role=region"
- Next message in Thread: glen walker: "Re: expectations role=group / role=region"
- Previous message in Thread: Bryan Garaventa: "Re: expectations role=group / role=region"
- View all messages in this Thread
I couldn't agree more!
I also find it weird that navigation landmarks are exposed with
default settings but regions are not. I'm fine with regions without an
accessible name not being exposed (after all a region without an
accessible name is technically speaking not a landmark), but a legit
region with an accessible name is there for a reason, to describe a
section of content and communicate its boundaries. Without screen
reader support this important info does not get communicated.
It's no wonder that screen reader user reliance on ARIA landmarks is
dwindling (see the WebAIM screen reader user surveys).
As for the question, use the group role if it achieves the intended
purpose, to communicate carousel name and boundaries to a screen
reader user. I'm all for theoretical clarity but if assistive
technologies do not support the ideal approach we have to find a
practical approach that works.
On 4/4/22, Bryan Garaventa via WebAIM-Forum
< <EMAIL REMOVED> > wrote:
> " I'm finding that screen reader announcements for the region role are
> disappearing, especially in Jaws, even if the region has an accessible
> name."
>
> I forget when this was introduced in JAWS, but I filed a bug against this a
> long time ago. Basically, named regions are not reliably announced unless
> "Virtual Cursor Verbosity" is set to "High", which is "Medium" by default.
> Personally I find this extremely annoying.
>
> You can see this by visiting:
> https://whatsock.com/Templates/Accordions/Internal/index.htm
>
> On the page in FF or Chrome with JAWS running:
> 1. Press Insert+V to open the Verbosity dialog.
> 2. On the option "Virtual Cursor Verbosity", press Spacebar to toggle this
> to "High" and press Enter.
>
> Now you will hear named regions.
>
> I still think this is a major issue for accessible intuitive navigation that
> you have to enable accessibility because it is not provided by default.
>
>
>
> Bryan Garaventa
> Principal Accessibility Architect
> Level Access, Inc.
> <EMAIL REMOVED>
> 415.624.2709 (o)
> www.LevelAccess.com
>
>
- Next message: glen walker: "Re: expectations role=group / role=region"
- Previous message: Bryan Garaventa: "Re: expectations role=group / role=region"
- Next message in Thread: glen walker: "Re: expectations role=group / role=region"
- Previous message in Thread: Bryan Garaventa: "Re: expectations role=group / role=region"
- View all messages in this Thread