WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Regarding expected functionality for an ARIA editable data grid control

for

From: Bryan Garaventa
Date: Nov 11, 2013 2:00PM

I'll be happy to share it when complete.

In the meantime, I've discovered a few NVDA bugs that I'll need to report
later when I have the demos ready to go.

E.G

NVDA won't enter Applications Mode when encountering focusable Gridcell
elements within an ARIA Grid, not when Tabbing through active elements, nor
by pressing Enter on a focusable Gridcell, nor when the focus() method is
used to manually set focus to a Gridcell.

When in Browse Mode, you cannot use the table navigation commands such as
control+alt+Left/Up/Right/Down to navigate the cells within the ARIA Grid
table, even though the underlying markup is a standard data table with
correctly implemented headers .

When Applications Mode is manually invoked using Insert+Space, you can then
use the standard arrow keys and other commands to navigate the ARIA Grid,
however column header cells identified using the 'headers' attribute on the
Gridcell element are not announced when navigating left and right between
cells on the same row,
and when arrowing up and down between rows, adjacent cell content is
announced even though these extra cells do not have focus.

Confirmed using the latest public version of NVDA in Firefox.

----- Original Message -----
From: "Don Mauck" < <EMAIL REMOVED> >
To: "WebAIM Discussion List" < <EMAIL REMOVED> >
Sent: Monday, November 11, 2013 8:53 AM
Subject: Re: [WebAIM] Regarding expected functionality for an ARIA editable
data grid control


> Bryan --
> I agree that the focus should be on the first column of the last row, this
> sounds good, I'd be interested in the final results.
> -----Original Message-----
> From: Bryan Garaventa [mailto: <EMAIL REMOVED> ]
> Sent: Sunday, November 10, 2013 4:09 PM
> To: WebAIM Discussion List
> Subject: Re: [WebAIM] Regarding expected functionality for an ARIA
> editable data grid control
>
> Thanks, that makes sense to me as well.
>
> Unfortunately I'm coming up against browser/AT key interception issues,
> so
> the choices are somewhat limited.
>
> For example, ctrl+PageUp/PageDown won't work. It works fine from the
> keyboard, but if you have JAWS running and Applications Mode is active,
> the
> screen reader intercepts this combination and it never gets passed to the
> grid. The same is true for ctrl+Up/Down as well.
>
> Similarly, alt+Home can't be used because the browser intercepts this and
> opens the home page, and alt+Left/Right will activate the Back and Forward
> buttons respectively.
>
> So here are the keyboard combinations that appear to work best in a
> focusable grid:
>
> Up/Down = Navigate by row
> alt+Up/Down = Navigate to the first or last row on the current page
> Left/Right = Navigate by column
> Home/End = Navigate to the first or last column on the current row
> ctrl+Home/End = Navigate to the first row on the first page or the last
> row
> on the last page
> PageUp/PageDown = Navigate by page
> alt+PageUp/PageDown = Navigate to the first row on the first or last page
>
> These key combinations appear to have the least amount of browser and AT
> conflicts.
>
> ----- Original Message -----
> From: "Birkir R. Gunnarsson" < <EMAIL REMOVED> >
> To: "WebAIM Discussion List" < <EMAIL REMOVED> >
> Sent: Sunday, November 10, 2013 12:44 PM
> Subject: Re: [WebAIM] Regarding expected functionality for an ARIA
> editable
> data grid control
>
>
>>I would say that ctrl-end puts focus on the last row of the last page.
>> As long as ctrl-page up will move to the first row of that page.
>> This is more in line with the expected functionality of this key
>> combination in other situations, such as in a text editor.
>> Keep up the good work.
>> Cheers
>> -Birkir
>> Birkir Gunnarsson
>> Accessibility SME | Deque Systems
>>
>>
>> On 11/9/13, Bryan Garaventa < <EMAIL REMOVED> > wrote:
>>> Hi, I'm currently designing an ARIA Data Grid control, which is going to
>>> do
>>> all sorts of stuff. The intent is to make this as scalable and as
>>> accessible
>>> as absolutely possible for desktop and mobile platforms for keyboard and
>>> screen reader users. It will also normalize equally across jQuery, Dojo,
>>> and
>>> MooTools.
>>>
>>> I have a question though about the expected functionality of pagination.
>>>
>>> Pagination is handled automatically, where you can arrow down or up past
>>> the
>>> bounds of the rendered grid rows and cause the previous or next page to
>>> load
>>> automatically for infinite scrolling, and the same is true by pressing
>>> PageUp or PageDown to navigate by page.
>>>
>>> Pressing Control+Home and Control+End though will render the first and
>>> last
>>> pages respectively.
>>>
>>> So if you press Control+Home, the row that receives focus is row 1 on
>>> the
>>> first page.
>>>
>>> When Control+End is pressed though, would it make more sense to set
>>> focus
>>> to
>>> row1 on the last page, or on the last row on the last page?
>>>
>>> It's mostly done, but more details about what the grid is supposed to do
>>> are
>>> available at
>>> http://lnkd.in/bj465ZD
>>>
>>> Thanks,
>>> Bryan
>>> >>> >>> >>>
>> >> >> >
> > > > > >