RE: Operable Grid Cell

The problem here though isn't the mode of interaction, but rather, how to convey differing types of gridcell types to the user.

Take the following example.

There is an interactive grid, with one row from left to right, that contains four gridcell nodes.
The user, in Forms/Application mode using a screen reader, moves focus between gridcell nodes using the arrow keys, and focus is moved between each gridcell node (element with role=gridcell) specifically.
The leftmost gridcell is a toggle button, with a pressed state that needs to be conveyed to the user.
The next gridcell is an editable string that needs to convey that it is editable to the user.
The next gridcell is a listbox control that needs to be stepped into in order to allow selection, and also has a default value that needs to be conveyed to the user while focus is on the gridcell node, and the role of listbox needs to be conveyed at the same time to convey the purpose of this gridcell.
The next gridcell contains embedded content as well as active elements, which is a mixed bag of control types that needs to be stepped into while conveying this purpose to the user while focus is still on the gridcell.

So, how do you do all of these things at the same time without having to resort to offscreen or explicit label strings like "LabelText Toggle Button Pressed" for example?

-----Original Message-----
From: Joseph Scheuhammer [mailto:clown@alum.mit.edu] 
Sent: Monday, September 29, 2014 12:12 PM
To: Matthew King; Alexander Surkov
Cc: Alexander Surkov; Bryan Garaventa; Joseph Scheuhammer; W3C WAI Protocols & Formats; Yura Zenevich
Subject: Re: Operable Grid Cell

What Matt said.


I was going to point out that the APG section on grid, although centred on keyboard access, does hint at how to treat individual gridcells as "actionable" (the APG term) vs. "read-only".

But, Matt beat me to it.

--
;;;;joseph.

'Array(16).join("wat" - 1) + " Batman!"'
            - G. Bernhardt -

Received on Monday, 29 September 2014 20:24:16 UTC