E-mail List Archives
Re: aria-label issue with JAWS
From: Maxability A11Y
Date: Jul 18, 2018 8:31AM
- Next message: Maxability A11Y: "Re: Confirmation of actions - violation or feature?"
- Previous message: Peter Quale: "Interpretation of WCAG 1.4.13"
- Next message in Thread: Mallory: "Re: aria-label issue with JAWS"
- Previous message in Thread: Birkir R. Gunnarsson: "Re: aria-label issue with JAWS"
- View all messages in this Thread
Here is a working example of treeview, if it helps.
https://w3c.github.io/aria-practices/examples/treeview/treeview-2/treeview-2a.html
I have checked with NVDA 2018.2 Firefox61 and JAWS 2018 on Chrome. The only
difference I could observe is that NVDA says expand and collapse while JAWS
says Open and close.
Hope it helps.
Thanks & Regards
Rakesh
On Wed, Jul 18, 2018 at 4:46 PM, Birkir R. Gunnarsson <
<EMAIL REMOVED> > wrote:
> As for Jaws not reading aria-label on a <ul> element, that's simply a
> bug. aria-label is valid with any role, including implicit roles (a
> <ul> has an implicit role of list).
> You could try to add role="list" to the <ul> element to see if it
> makes a difference. I know you are not supposed to duplicate the
> implicit role but sometimes it helps with assistive technology
> behavior.
> As for the demo, can you post a link to it?
> Have you tried any of the tree examples from the ARIA Authoring Practices?
>
>
>
> On 7/18/18, Kakarla Meharoon < <EMAIL REMOVED> > wrote:
> > Hi,
> >
> > The issue is related to tree structure we are using ul and li for the
> tree
> > items and tree elements or nodes having check boxes also so thats the
> > reason if we add role="tree" for the ul wrapper and aria-label the labels
> > are not read out by the screen reader.
> > So we have done custom approach here
> >
> > Because JAWS is preventing the preferred arrow key navigation from
> working
> > (as noted below, it is fine when the screen reader is not active).
> >
> > This is why we are deliberately changing to tabstop triangular icons and
> > enter to expand/collapse. It also improves the visibility of the tree
> when
> > scrolling with arrow keys, as the visibility now follows the tab focus
> > (previously it could be lost/scrolled offscreen).
> >
> > The issue of JAWS interfering with the arrow key navigation occurs for
> > example in the official Kendo UI Tree keyboard navigation demo (fine
> > without JAWS, broken when screenreader is active):
> > > > > > > > > >
>
>
> --
> Work hard. Have fun. Make history.
> > > > >
- Next message: Maxability A11Y: "Re: Confirmation of actions - violation or feature?"
- Previous message: Peter Quale: "Interpretation of WCAG 1.4.13"
- Next message in Thread: Mallory: "Re: aria-label issue with JAWS"
- Previous message in Thread: Birkir R. Gunnarsson: "Re: aria-label issue with JAWS"
- View all messages in this Thread