E-mail List Archives
Thread: Accessibility of a date picker?
Number of posts in this thread: 5 (In chronological order)
From: Moore,Michael (Accessibility) (HHSC)
Date: Thu, May 26 2016 7:41AM
Subject: Accessibility of a date picker?
No previous message | Next message →
Deque has a very good example of how to properly implement a date picker.
https://dequeuniversity.com/library/aria/date-pickers/sf-date-picker
Mike Moore
Accessibility Coordinator
Texas Health and Human Services Commission
Civil Rights Office
(512) 438-3431 (Office)
From: Bryan Garaventa
Date: Thu, May 26 2016 9:12AM
Subject: Re: Accessibility of a date picker?
← Previous message | Next message →
Actually the behavior that aria-readonly="true" on a grid as not going into Forms Mode is a screen reader bug.
A grid is an interactive construct according to the spec, regardless whether it is readonly or not, and it is meant to be interacted with using the keyboard.
If the intent is to build a data table instead, then the developer should be using role=table and it's associated roles in accordance with the table mappings at
http://whatsock.com/training/matrices/#table
This is why the table role was added to the spec, to provide an accessible construct for non-interactive tables.
Since aria-readonly is supported on role="gridcell, role=columnheader, and role=rowheader cells for example, you could easily have a table where some cells marked as column or row header cells are meant to be readonly but others are not, and if you are not allowed to enter Forms Mode on some but not others or if Forms Mode gets booted out when you arrow to a readonly cell, it will impair intuitive navigation.
Please file this behavior as a bug if you notice this happening.
Bryan Garaventa
Accessibility Fellow
SSB BART Group, Inc.
= EMAIL ADDRESS REMOVED =
415.624.2709 (o)
www.SSBBartGroup.com
From: Birkir R. Gunnarsson
Date: Thu, May 26 2016 11:20AM
Subject: Re: Accessibility of a date picker?
← Previous message | Next message →
True.
But the table role is new and, in my most recent testing, is not
supported anywhere (well, IE/FF with Jaws/NVDA).
I have had to recommend building a read-only grid once or twice where
there was no way of implementing an HTML table.
That being said, I totally agree with you Bryan, that a grid is an
interactice construct and should cause a.t. to go into forms mode.
Unfortuantely the is a discontted in that the ARIA spec makes no user
agent recommendation for different roles.
I know people are working on supporting documentation to address this
gp, though I am not well versed in the details. But I know it is
needed.
-B
On 5/26/16, Bryan Garaventa < = EMAIL ADDRESS REMOVED = > wrote:
> Actually the behavior that aria-readonly="true" on a grid as not going into
> Forms Mode is a screen reader bug.
>
> A grid is an interactive construct according to the spec, regardless whether
> it is readonly or not, and it is meant to be interacted with using the
> keyboard.
>
> If the intent is to build a data table instead, then the developer should be
> using role=table and it's associated roles in accordance with the table
> mappings at
> http://whatsock.com/training/matrices/#table
> This is why the table role was added to the spec, to provide an accessible
> construct for non-interactive tables.
>
> Since aria-readonly is supported on role="gridcell, role=columnheader, and
> role=rowheader cells for example, you could easily have a table where some
> cells marked as column or row header cells are meant to be readonly but
> others are not, and if you are not allowed to enter Forms Mode on some but
> not others or if Forms Mode gets booted out when you arrow to a readonly
> cell, it will impair intuitive navigation.
>
> Please file this behavior as a bug if you notice this happening.
>
> Bryan Garaventa
> Accessibility Fellow
> SSB BART Group, Inc.
> = EMAIL ADDRESS REMOVED =
> 415.624.2709 (o)
> www.SSBBartGroup.com
>
>
From: Bryan Garaventa
Date: Thu, May 26 2016 11:53AM
Subject: Re: Accessibility of a date picker?
← Previous message | Next message →
In recent tests, role=table is now supported in IE11 using JAWS17 plus in Firefox and Chrome, plus in NVDA in Chrome. This should also now work in Safari via webkit.
The only variable that still needs to be worked out by JAWS and NVDA is the proper support of aria-owns as reflected in the accessibility tree, or in the case of IE11 as the attribute is meant to be used with multiple ID refs and how this affects the reading order.
Bryan Garaventa
Accessibility Fellow
SSB BART Group, Inc.
= EMAIL ADDRESS REMOVED =
415.624.2709 (o)
www.SSBBartGroup.com
From: Birkir R. Gunnarsson
Date: Thu, May 26 2016 3:15PM
Subject: Re: Accessibility of a date picker?
← Previous message | No next message
Whoops, I guess it is time to upgrade my Jaws to 17 *grin*.
Thanks for the info.
On 5/26/16, Bryan Garaventa < = EMAIL ADDRESS REMOVED = > wrote:
> In recent tests, role=table is now supported in IE11 using JAWS17 plus in
> Firefox and Chrome, plus in NVDA in Chrome. This should also now work in
> Safari via webkit.
>
> The only variable that still needs to be worked out by JAWS and NVDA is the
> proper support of aria-owns as reflected in the accessibility tree, or in
> the case of IE11 as the attribute is meant to be used with multiple ID refs
> and how this affects the reading order.
>
> Bryan Garaventa
> Accessibility Fellow
> SSB BART Group, Inc.
> = EMAIL ADDRESS REMOVED =
> 415.624.2709 (o)
> www.SSBBartGroup.com
>
>
>