W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > April to June 2012

Fw: [NVDA] #2390: NVDA doesn't handle role=dialog with supporting ARIA attributes according to spec

From: Bryan Garaventa <bryan.garaventa@whatsock.com>
Date: Wed, 30 May 2012 09:36:28 -0700
Message-ID: <5F388EDD058E42C5B9E6EF2FCAB89B4A@WAMPAS>
To: <w3c-wai-ig@w3.org>
Is this correct?

----- Original Message ----- 
From: "NVDA Trac" <noreply+nvdaTrac@nvaccess.org>
Cc: <nvda-dev@lists.nvaccess.org>
Sent: Tuesday, May 29, 2012 4:09 PM
Subject: Re: [NVDA] #2390: NVDA doesn't handle role=dialog with supporting 
ARIA attributes according to spec


> #2390: NVDA doesn't handle role=dialog with supporting ARIA attributes 
> according
> to spec
> -------------------------------+------------------------
>        Reporter:  bgaraventa  |       Owner:
>            Type:  defect      |      Status:  new
>        Priority:  minor       |   Milestone:
>       Component:  Core        |     Version:  2012.2rc1
>      Resolution:              |    Keywords:  ARIA
> Operating system:  Windows XP  |  Blocked by:
>        Blocking:              |
> -------------------------------+------------------------
>
> Comment (by jteh):
>
> Replying to [comment:6 bgaraventa]:
> > Can you help me out? I've been reading the spec, but I can't find where
> it says that user agents must parse both an aria-describedby attribute and
> an aria-label/aria-labelledby at the same time. Can you point me to where
> it says this?
> As I said, see my quote above from the spec regarding alertdialog.
>
> > Now, since NVDA ignores role=presentation (which should cause NVDA to
> ignore all of this content when parsing alternative text according to the
> user agent specification),
> From the roles spec:
> > However, the user agent MUST expose content and descendant elements that
> do not have an explicit or inherited role of presentation. Thus, the
> presentation role causes a given element to be treated as having no role
> or to be removed from the accessibility tree, but does not cause the
> content contained within the element to be removed from the accessible
> tree.
> This suggests we should ignore the element, but not its descendants.
>
> > and NVDA will announce all of the content regardless what the label is
> explicitly set to,
> First, we don't announce all the content. We try to determine what content
> would constitute the caption/description of the dialog. This algorithm is
> necessarily complex and is not perfect, but we've done our best to ensure
> it only reads labels and text nodes. Second, you're still confusing label
> and description. Dialogs (even before ARIA) have always had a label and an
> optional caption/description/message. The presence of a label doesn't
> necessarily mean there is no caption/description/message.
>
> -- 
> Ticket URL: <http://www.nvda-project.org/ticket/2390#comment:7>
> NVDA <http://www.nvda-project.org/>
> A free and open-source screen reader for Windows
> 
Received on Wednesday, 30 May 2012 16:37:05 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 30 May 2012 16:37:08 GMT