[WG: Accessibility] Accessibility Jira Tickets to consider closing

Richwine, Brian L brichwin at indiana.edu
Wed Jul 14 09:49:54 PDT 2010


Hi,

On the Outstanding Sakai 2.x Jira Ticket Discussion page there is a section for Jira tickets we are considering closing with a resolution of "Won't Fix". (This page is located here:  http://confluence.sakaiproject.org/display/2ACC/Outstanding+Sakai+2.x+Accessibility+Jira+Tickets+Discussion#OutstandingSakai2.xAccessibilityJiraTicketsDiscussion-ConsiderClosingWon%27tFix )

I would like to discuss these Jira tickets in the Accessibility WG teleconference on July 28th (two weeks from now). Mary Stores, Joe Humbert, and I have looked at these Jiras and believe they can be closed. Before closing them, we want to give the group opportunity to provide input. Below is a list of these issues, and our comments as to why we think they can simply be closed with a resolution of "Won't fix".


1.       http://jira.sakaiproject.org/browse/SAK-12821 - Enable users to select items in list by typing letter

Recommend closing this because the ability to perform "first-letter" navigation is a feature provided by most adaptive technologies that work with Web pages. Navigation by typing is also a feature that can be enabled in some browsers (Firefox / Opera).


2.       http://jira.sakaiproject.org/browse/SAK-8068 - Extend heading tags to include form labels and table cells; caption tags to data tables

Recommend closing this because most adaptive technologies have tools to easily discover and navigate to form elements (such as the Forms List dialog box in JAWS). Appropriate mark-up for data tables using the summary attribute, table headers, and related attributes is well known and effective. Recommend closing this JIRA ticket in favor of writing JIRA tickets for specific issues to improve headings, form control labels, data table mark-up, etc.


3.       http://jira.sakaiproject.org/browse/SAK-5068 - Allow users to turn off accesskeys

Recommend closing this as the comments in the JIRA ticket point out that the option to turn access keys on or off doesn't really fulfill a purpose. Improvements in how Web browsers handle access keys has made this less of an issue. Browser configuration can reduce/eliminate browser + accesskey conflicts and screen reader hot key combinations take precedence over browser hotkeys/accesskeys. IE 7+ and Firefox 3+ now require Alt+Shift to activate an accesskey. Opera requires Shift+Esc to activate an accesskey and allows that key combination to be configured.


Brian Richwine
Adaptive Technology Support Specialist
Adaptive Technology and Accessibility Centers
Indiana University - Bloomington/Indianapolis
http://iuadapts.indiana.edu
(812) 856-4112

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/accessibility/attachments/20100714/49f5486e/attachment.html 


More information about the accessibility mailing list