WebAIM - Web Accessibility In Mind

E-mail List Archives

Thread: aria-haspopup="dialog"

for

Number of posts in this thread: 7 (In chronological order)

From: Kakarla Meharoon
Date: Fri, May 04 2018 3:37AM
Subject: aria-haspopup="dialog"
No previous message | Next message →

Hi

I tried to use aria 1.1 updates, aria-haspopup= "dialog" for the link which
will open as a popup, but in JAWS it is announced as a dialog but NVDA it
is reading as a submenu.

Did anyone try this one?

Is it necessary to give advance warning to the link/button which opens as a
dialog?

From: Mallory
Date: Fri, May 04 2018 4:42AM
Subject: Re: aria-haspopup="dialog"
← Previous message | Next message →

I thought the default for an unknown (or simply "true") value of aria-haspopup was "menu" so maybe [your version of] NVDA doesn't recognise that value?

cheers,
_mallory

On Fri, May 4, 2018, at 11:37 AM, Kakarla Meharoon wrote:
> Hi
>
> I tried to use aria 1.1 updates, aria-haspopup= "dialog" for the link which
> will open as a popup, but in JAWS it is announced as a dialog but NVDA it
> is reading as a submenu.
>
> Did anyone try this one?
>
> Is it necessary to give advance warning to the link/button which opens as a
> dialog?
> > > >

From: glen walker
Date: Fri, May 04 2018 7:47AM
Subject: Re: aria-haspopup="dialog"
← Previous message | Next message →

Actually, unknown values are supposed to be treated as "false", according
to https://www.w3.org/TR/wai-aria/#aria-haspopup

User agents *MUST* treat any value of aria-haspopup that is not included in
> the list of allowed values...as if the value false had been provided.
>

Both firefox and chrome, with the latest NVDA, say 'submenu' instead of
'dialog'. Internet Explorer doesn't say anything other than "link". JAWS
works fine, as you mentioned.

I looked at the NVDA bug list and I don't see anything regarding
aria-haspopup values. You may want to file a bug for them.

https://github.com/nvaccess/nvda/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+aria-haspopup


On Fri, May 4, 2018 at 4:42 AM, Mallory < = EMAIL ADDRESS REMOVED = > wrote:

> I thought the default for an unknown (or simply "true") value of
> aria-haspopup was "menu" so maybe [your version of] NVDA doesn't recognise
> that value?
>
> cheers,
> _mallory
>
> On Fri, May 4, 2018, at 11:37 AM, Kakarla Meharoon wrote:
> > Hi
> >
> > I tried to use aria 1.1 updates, aria-haspopup= "dialog" for the link
> which
> > will open as a popup, but in JAWS it is announced as a dialog but NVDA it
> > is reading as a submenu.
> >
> > Did anyone try this one?
> >
> > Is it necessary to give advance warning to the link/button which opens
> as a
> > dialog?
> > > > > > > > > > > > >

From: Birkir R. Gunnarsson
Date: Fri, May 04 2018 8:30AM
Subject: Re: aria-haspopup="dialog"
← Previous message | Next message →

I filed a Jaws bug for this in December
https://github.com/FreedomScientific/VFO-standards-support/issues/33
(yes, my GitHub username is wildebrew, long story).
This issue has a fairly detailed description of the problem and points
to a Codepen I created to demonstrate the problem.
I could go and file it with NVDA, or anybody who is filing this with
NVDA is free to point to this issue.
If you do open an NVDA issue about this, please reply to this thread.
If nobody has by Sunday I will try to find the time to open it and
will also reply to this thread.
Thanks
-Birkir



On 5/4/18, glen walker < = EMAIL ADDRESS REMOVED = > wrote:
> Actually, unknown values are supposed to be treated as "false", according
> to https://www.w3.org/TR/wai-aria/#aria-haspopup
>
> User agents *MUST* treat any value of aria-haspopup that is not included in
>> the list of allowed values...as if the value false had been provided.
>>
>
> Both firefox and chrome, with the latest NVDA, say 'submenu' instead of
> 'dialog'. Internet Explorer doesn't say anything other than "link". JAWS
> works fine, as you mentioned.
>
> I looked at the NVDA bug list and I don't see anything regarding
> aria-haspopup values. You may want to file a bug for them.
>
> https://github.com/nvaccess/nvda/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+aria-haspopup
>
>
> On Fri, May 4, 2018 at 4:42 AM, Mallory < = EMAIL ADDRESS REMOVED = > wrote:
>
>> I thought the default for an unknown (or simply "true") value of
>> aria-haspopup was "menu" so maybe [your version of] NVDA doesn't recognise
>> that value?
>>
>> cheers,
>> _mallory
>>
>> On Fri, May 4, 2018, at 11:37 AM, Kakarla Meharoon wrote:
>> > Hi
>> >
>> > I tried to use aria 1.1 updates, aria-haspopup= "dialog" for the link
>> which
>> > will open as a popup, but in JAWS it is announced as a dialog but NVDA
>> > it
>> > is reading as a submenu.
>> >
>> > Did anyone try this one?
>> >
>> > Is it necessary to give advance warning to the link/button which opens
>> as a
>> > dialog?
>> > >> > >> > >> > >> >> >> >> >>
> > > > >


--
Work hard. Have fun. Make history.

From: Steve Faulkner
Date: Fri, May 04 2018 9:03AM
Subject: Re: aria-haspopup="dialog"
← Previous message | Next message →

>
> I filed a Jaws bug for this in December
>
https://github.com/FreedomScientific/VFO-standards-support/issues/33


Thanks for the reminder Birkir, have gone in to the JAWS internal bug
tracker and given it a bump.

--

Regards

SteveF
Current Standards Work @W3C
<http://www.paciellogroup.com/blog/2015/03/current-standards-work-at-w3c/>;

On 4 May 2018 at 15:30, Birkir R. Gunnarsson < = EMAIL ADDRESS REMOVED = >
wrote:

> I filed a Jaws bug for this in December
> https://github.com/FreedomScientific/VFO-standards-support/issues/33
> (yes, my GitHub username is wildebrew, long story).
> This issue has a fairly detailed description of the problem and points
> to a Codepen I created to demonstrate the problem.
> I could go and file it with NVDA, or anybody who is filing this with
> NVDA is free to point to this issue.
> If you do open an NVDA issue about this, please reply to this thread.
> If nobody has by Sunday I will try to find the time to open it and
> will also reply to this thread.
> Thanks
> -Birkir
>
>
>
> On 5/4/18, glen walker < = EMAIL ADDRESS REMOVED = > wrote:
> > Actually, unknown values are supposed to be treated as "false", according
> > to https://www.w3.org/TR/wai-aria/#aria-haspopup
> >
> > User agents *MUST* treat any value of aria-haspopup that is not included
> in
> >> the list of allowed values...as if the value false had been provided.
> >>
> >
> > Both firefox and chrome, with the latest NVDA, say 'submenu' instead of
> > 'dialog'. Internet Explorer doesn't say anything other than "link".
> JAWS
> > works fine, as you mentioned.
> >
> > I looked at the NVDA bug list and I don't see anything regarding
> > aria-haspopup values. You may want to file a bug for them.
> >
> > https://github.com/nvaccess/nvda/issues?utf8=%E2%9C%93&q> is%3Aissue+is%3Aopen+aria-haspopup
> >
> >
> > On Fri, May 4, 2018 at 4:42 AM, Mallory < = EMAIL ADDRESS REMOVED = >
> wrote:
> >
> >> I thought the default for an unknown (or simply "true") value of
> >> aria-haspopup was "menu" so maybe [your version of] NVDA doesn't
> recognise
> >> that value?
> >>
> >> cheers,
> >> _mallory
> >>
> >> On Fri, May 4, 2018, at 11:37 AM, Kakarla Meharoon wrote:
> >> > Hi
> >> >
> >> > I tried to use aria 1.1 updates, aria-haspopup= "dialog" for the link
> >> which
> >> > will open as a popup, but in JAWS it is announced as a dialog but NVDA
> >> > it
> >> > is reading as a submenu.
> >> >
> >> > Did anyone try this one?
> >> >
> >> > Is it necessary to give advance warning to the link/button which opens
> >> as a
> >> > dialog?
> >> > > >> > > >> > > >> > > >> > >> > >> > >> > >>
> > > > > > > > > >
>
>
> --
> Work hard. Have fun. Make history.
> > > > >

From: Birkir R. Gunnarsson
Date: Fri, May 04 2018 9:43AM
Subject: Re: aria-haspopup="dialog"
← Previous message | Next message →

I went ahead and opened a new issue for NVDA,
https://github.com/nvaccess/nvda/issues/8235
(who needs lunch, it's a Friday).
Feel free to comment or watch the issue.

Cheers
-B


On 5/4/18, Steve Faulkner < = EMAIL ADDRESS REMOVED = > wrote:
>>
>> I filed a Jaws bug for this in December
>>
> https://github.com/FreedomScientific/VFO-standards-support/issues/33
>
>
> Thanks for the reminder Birkir, have gone in to the JAWS internal bug
> tracker and given it a bump.
>
> --
>
> Regards
>
> SteveF
> Current Standards Work @W3C
> <http://www.paciellogroup.com/blog/2015/03/current-standards-work-at-w3c/>;
>
> On 4 May 2018 at 15:30, Birkir R. Gunnarsson < = EMAIL ADDRESS REMOVED = >
> wrote:
>
>> I filed a Jaws bug for this in December
>> https://github.com/FreedomScientific/VFO-standards-support/issues/33
>> (yes, my GitHub username is wildebrew, long story).
>> This issue has a fairly detailed description of the problem and points
>> to a Codepen I created to demonstrate the problem.
>> I could go and file it with NVDA, or anybody who is filing this with
>> NVDA is free to point to this issue.
>> If you do open an NVDA issue about this, please reply to this thread.
>> If nobody has by Sunday I will try to find the time to open it and
>> will also reply to this thread.
>> Thanks
>> -Birkir
>>
>>
>>
>> On 5/4/18, glen walker < = EMAIL ADDRESS REMOVED = > wrote:
>> > Actually, unknown values are supposed to be treated as "false",
>> > according
>> > to https://www.w3.org/TR/wai-aria/#aria-haspopup
>> >
>> > User agents *MUST* treat any value of aria-haspopup that is not included
>> in
>> >> the list of allowed values...as if the value false had been provided.
>> >>
>> >
>> > Both firefox and chrome, with the latest NVDA, say 'submenu' instead of
>> > 'dialog'. Internet Explorer doesn't say anything other than "link".
>> JAWS
>> > works fine, as you mentioned.
>> >
>> > I looked at the NVDA bug list and I don't see anything regarding
>> > aria-haspopup values. You may want to file a bug for them.
>> >
>> > https://github.com/nvaccess/nvda/issues?utf8=%E2%9C%93&q>> is%3Aissue+is%3Aopen+aria-haspopup
>> >
>> >
>> > On Fri, May 4, 2018 at 4:42 AM, Mallory < = EMAIL ADDRESS REMOVED = >
>> wrote:
>> >
>> >> I thought the default for an unknown (or simply "true") value of
>> >> aria-haspopup was "menu" so maybe [your version of] NVDA doesn't
>> recognise
>> >> that value?
>> >>
>> >> cheers,
>> >> _mallory
>> >>
>> >> On Fri, May 4, 2018, at 11:37 AM, Kakarla Meharoon wrote:
>> >> > Hi
>> >> >
>> >> > I tried to use aria 1.1 updates, aria-haspopup= "dialog" for the link
>> >> which
>> >> > will open as a popup, but in JAWS it is announced as a dialog but
>> >> > NVDA
>> >> > it
>> >> > is reading as a submenu.
>> >> >
>> >> > Did anyone try this one?
>> >> >
>> >> > Is it necessary to give advance warning to the link/button which
>> >> > opens
>> >> as a
>> >> > dialog?
>> >> > >> >> > >> >> > >> >> > >> >> >> >> >> >> >> >> >> >>
>> > >> > >> > >> > >> >
>>
>>
>> --
>> Work hard. Have fun. Make history.
>> >> >> >> >>
> > > > >


--
Work hard. Have fun. Make history.

From: chagnon@pubcom.com
Date: Fri, May 04 2018 9:50AM
Subject: Re: aria-haspopup="dialog"
← Previous message | No next message

Dear Wildebrew,
Wow. You just never know about people's alter-lives, eh?
Do tell! The list is waiting for the details.

— — —
Bevi Chagnon, founder/CEO | = EMAIL ADDRESS REMOVED =
— — —
PubCom: Technologists for Accessible Design + Publishing
consulting ' training ' development ' design ' sec. 508 services
Upcoming classes at www.PubCom.com/classes
— — —


-----Original Message-----
From: WebAIM-Forum < = EMAIL ADDRESS REMOVED = > On Behalf Of Birkir R. Gunnarsson
Sent: Friday, May 4, 2018 10:31 AM
To: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = >
Subject: Re: [WebAIM] aria-haspopup="dialog"

I filed a Jaws bug for this in December
https://github.com/FreedomScientific/VFO-standards-support/issues/33
(yes, my GitHub username is wildebrew, long story).
This issue has a fairly detailed description of the problem and points to a Codepen I created to demonstrate the problem.
I could go and file it with NVDA, or anybody who is filing this with NVDA is free to point to this issue.
If you do open an NVDA issue about this, please reply to this thread.
If nobody has by Sunday I will try to find the time to open it and will also reply to this thread.
Thanks
-Birkir



On 5/4/18, glen walker < = EMAIL ADDRESS REMOVED = > wrote:
> Actually, unknown values are supposed to be treated as "false",
> according to https://www.w3.org/TR/wai-aria/#aria-haspopup
>
> User agents *MUST* treat any value of aria-haspopup that is not
> included in
>> the list of allowed values...as if the value false had been provided.
>>
>
> Both firefox and chrome, with the latest NVDA, say 'submenu' instead
> of 'dialog'. Internet Explorer doesn't say anything other than
> "link". JAWS works fine, as you mentioned.
>
> I looked at the NVDA bug list and I don't see anything regarding
> aria-haspopup values. You may want to file a bug for them.
>
> https://github.com/nvaccess/nvda/issues?utf8=%E2%9C%93&q=is%3Aissue+is
> %3Aopen+aria-haspopup
>
>
> On Fri, May 4, 2018 at 4:42 AM, Mallory < = EMAIL ADDRESS REMOVED = > wrote:
>
>> I thought the default for an unknown (or simply "true") value of
>> aria-haspopup was "menu" so maybe [your version of] NVDA doesn't
>> recognise that value?
>>
>> cheers,
>> _mallory
>>
>> On Fri, May 4, 2018, at 11:37 AM, Kakarla Meharoon wrote:
>> > Hi
>> >
>> > I tried to use aria 1.1 updates, aria-haspopup= "dialog" for the
>> > link
>> which
>> > will open as a popup, but in JAWS it is announced as a dialog but
>> > NVDA it is reading as a submenu.
>> >
>> > Did anyone try this one?
>> >
>> > Is it necessary to give advance warning to the link/button which
>> > opens
>> as a
>> > dialog?
>> > >> > >> > archives at http://webaim.org/discussion/archives
>> > >> >> >> archives at http://webaim.org/discussion/archives
>> >>
> > > archives at http://webaim.org/discussion/archives
> >


--
Work hard. Have fun. Make history.