W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > October to December 2013

Fw: [NVDA] #3023: Browsing down the page using the arrow keys is non-intuitive when an ARIA Tree control is present

From: Bryan Garaventa <bryan.garaventa@whatsock.com>
Date: Sun, 13 Oct 2013 23:26:45 -0700
Message-ID: <175DB328708E4D66A0F8B56B15F89A8C@WAMPAS>
To: <w3c-wai-ig@w3.org>
Can anyone here please confirm whether my assessment on this is correct or 
not?
http://community.nvda-project.org/ticket/3023

----- Original Message ----- 
From: "NVDA Trac" <noreply+nvdaTrac@nvaccess.org>
Cc: <nvda-commits@lists.sourceforge.net>
Sent: Sunday, October 13, 2013 11:22 PM
Subject: Re: [NVDA] #3023: Browsing down the page using the arrow keys is 
non-intuitive when an ARIA Tree control is present


> #3023: Browsing down the page using the arrow keys is non-intuitive when 
> an ARIA
> Tree control is present
> --------------------------------+------------------------
>        Reporter:  bgaraventa   |       Owner:  jteh
>            Type:  defect       |      Status:  closed
>        Priority:  minor        |   Milestone:  2013.2
>       Component:  Browse mode  |     Version:  2013.2rc2
>      Resolution:  fixed        |    Keywords:  ARIA
> Operating system:  Windows 7    |  Blocked by:
>        Blocking:               |
> --------------------------------+------------------------
> What's New entry:
>
>
> --------------------------------+------------------------
>
> Comment (by bgaraventa):
>
> I'm sorry, but that's not true.
>
> Please read the ARIA spec at
> http://www.w3.org/TR/wai-aria/roles#tree
>
> Where it states:
>
> "To be  keyboard accessible, authors SHOULD manage focus of descendants
> for all instances of this  role, as described in Managing Focus."
>
> There are only two ways to make an ARIA Tree accessible, and yes, one of
> these ways is by setting focus on the container with role=tree. This
> requires the use of the aria-activedescendant attribute and a completely
> different keyboard handling model.
>
> The second way, which is also totally valid, is to set focus on the
> individual nodes that include role=treeitem, which is how the ARIA Tree
> that I referenced is programmed.
>
> The benefit of using the method of setting focus on the treeitem nodes
> individually instead of setting focus on the container with role=tree in
> combination with aria-activedescendant, is that doing so works accessibly
> going as far back as JAWS 11 in IE8.
>
> This method also works well in NVDA using both IE and Firefox when focus
> is set on the selected tree node, as you've already seen.
>
> The problem is that, when you are arrowing down the page in Browse Mode,
> you have no way of knowing that you are looking at an ARIA Tree.
>
> --
> Ticket URL: <http://community.nvda-project.org/ticket/3023#comment:11>
> NVDA Community <http://community.nvda-project.org/>
> A free and open-source screen reader for Windows 
Received on Monday, 14 October 2013 06:27:30 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 13 October 2015 16:21:50 UTC