Avoid inappropriate use of ARIA roles, states, and properties - Announcements

Description

Throughout the environment controls that either expand or collapse content do not inform screen reader users of their purpose. The <aria-expanded> attribute is utilized however it is injected into the DOM once the control has been activated, and is not present when the page loads. As screen-reader users rely on the <aria-expanded="false"> attribute on page load to discern that the control expands a section of content, they will have difficulty discerning which elements in the environment have an expanded state.Below is a particular instance of <aria-expanded="true"> being injected into the DOM via JavaScript that can be found in Resources as SAK-31548.

http://qa03-sakai.marist.edu:8080/portal/site/e72d72d4-f582-4dce-8261-6b923060787c/tool/24bf98be-5fe0-4b16-aca7-0f464c7ba312#A0b648a8b01ffe1b7e431525edf50c7b-HTML

Attachments

1

Activity

Show:

Matt Clare January 30, 2017 at 2:03 PM

I agree that there appears to be no issue with the reorder, as it's both functional and based on the known accessible Fluid project.

I just reviewed the marist hosted version that was evaluated and trunk. Some of the list items were better interpreted by Chromevox (always a lesser test than JAWS), but what's more is the keyboard related instructions were not read in the Marist version because of the improper skip class related to SAK-31549.

With the keyboard instructions read by a screenreader, I think this now resolved.

My comparison is recorded here https://www.screencast.com/t/xwwkBwk77dB

Sam Ottenhoff January 25, 2017 at 6:32 PM

Okay I see no ues of "aria" in all of announcements. Reorder functionality uses Fluid project reorder component. Any ideas what this refers to?

Matt Clare July 22, 2016 at 3:01 PM

It's somewhere on this page (I don't expect this to help much)

Incorporated

Details

Priority

Affects versions

Fix versions

Components

Assignee

Reporter

Created July 22, 2016 at 2:23 PM
Updated February 1, 2017 at 12:25 PM
Resolved January 30, 2017 at 2:06 PM