[Bug 24201] New: Allow data table navigation using the tab key by setting keyboard focus on the rows (columns).

https://www.w3.org/Bugs/Public/show_bug.cgi?id=24201

            Bug ID: 24201
           Summary: Allow data table navigation using the tab key by
                    setting keyboard focus on the rows (columns).
           Product: HTML.next
           Version: unspecified
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: default
          Assignee: dave.null@w3.org
          Reporter: devarshipant@gmail.com
        QA Contact: public-html-bugzilla@w3.org
                CC: mike@w3.org, robin@w3.org

Allow users to navigate table rows (columns) using the keyboard tab, which in
turn conveys to a screen reader user the following information when the
keyboard focus is on a specific row (column):
1. Associate the header information with every data cell. This would make
navigating tables easier as a user only needs to tab, rather than use table
reading keys. 
2. Tables with form fields would be easier to navigate as well. A user would
tab in order to navigate to a row (column) and while the screen reader
announces the cells and its header(s), the user hits the enter key to enter
into the forms mode (PC cursor) to fill out the form field.
3. The announcements with a screen reader for a typical data table that uses
this paradigm would be as follows:
3.1. When the virtual cursor is on the table, the user would hear how to
navigate, like “Table uses tab key to navigate to row (column).” – Something
that is currently done while navigating tree views, as in "tree view, n items:
To move through or expand / collapse, use arrow keys,” etc.
3.2. The tab key navigation will first go over the column headers followed by
rows, all the while following the rule listed in 2. 
It’s something I feel could be useful. And honestly, am not even sure if an
aria role or an attribute would be able to accomplish it.

-Devarshi

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Friday, 3 January 2014 21:06:26 UTC