2010 Closed Sakai 2.x Accessibility Jira Tickets

Contents

Resolved / Closed Accessibility Jira Tickets for 2010

Closed - Could Not Reproduce

type	key	summary	assignee	reporter	priority	status	resolution	created	updated	due
Unable to locate Jira server for this macro. It may be due to Application Link configuration.

type	key	summary	assignee	reporter	priority	status	resolution	created	updated	due
Unable to locate Jira server for this macro. It may be due to Application Link configuration.

type	key	summary	assignee	reporter	priority	status	resolution	created	updated	due
Unable to locate Jira server for this macro. It may be due to Application Link configuration.

type	key	summary	assignee	reporter	priority	status	resolution	created	updated	due
Unable to locate Jira server for this macro. It may be due to Application Link configuration.

type	key	summary	assignee	reporter	priority	status	resolution	created	updated	due
Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Closed - Non-Issue

type	key	summary	assignee	reporter	priority	status	resolution	created	updated	due
Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Closed - Will Not Fix

type	key	summary	assignee	reporter	priority	status	resolution	created	updated	due
Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Acceptable workaround - user can enter date manually

type	key	summary	assignee	reporter	priority	status	resolution	created	updated	due
Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Acceptable workaround - user can enter date manually

type	key	summary	assignee	reporter	priority	status	resolution	created	updated	due
Unable to locate Jira server for this macro. It may be due to Application Link configuration.

I am going to go with the following heuristic, and close this so that the issue gets the attention it needs:

Reserve headers for delimiting semantic blocks to which screen reader navigation might be needed. Once inside the block, screen reader should be provided with navigation/markers native to that block: labels and inputs, properly constructed tables, text block markup, etc.
Do not double up headers with any other markup that has screen reader meaning on its own.
The maximum depth/number of headers should be constrained to 2 and 5 (at each level) respectively. This is somewhat arbitrary - the aim of a limit here is to provide enough information but no overwhelm.

Generally speaking: This issue is too generic. If the above heuristic is acceptable it should be tested against specific functionality/tools and separate JIRAs opened to deal with them specifically.

Accessibility WG needs to determine if this is an acceptable heuristic (or make any needed changes) and then put the heuristic into the accessibility evaluation protocols.

type	key	summary	assignee	reporter	priority	status	resolution	created	updated	due
Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Closed as a non-issue because it was an erroneously reported issue.

type	key	summary	assignee	reporter	priority	status	resolution	created	updated	due
Unable to locate Jira server for this macro. It may be due to Application Link configuration.

This issue is pretty generic. A Cancel (live a Save or an Edit) is a POST - hence a new page is retrieved. In some cases (like when a validation error happens or when a success message is displayed for high stakes actions) the new page focus should land on the message, but this is not necessarily always the case - I would vote for closing this issue and opening specific issues to deal with specific cases.

type	key	summary	assignee	reporter	priority	status	resolution	created	updated	due
Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Closed 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.

type	key	summary	assignee	reporter	priority	status	resolution	created	updated	due
Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Closed 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.

type	key	summary	assignee	reporter	priority	status	resolution	created	updated	due
Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Closing this as the comments in the JIRA ticket point out that the option to turn them on or off doesn't really fulfill a purpose. 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.