[WG: Accessibility] Accessibility improvements that could be seen in Sakai 3 over Sakai 2

[Mary Stores]

Brian,

It looks good to me so far based on our discussions. If I think of 
anything else, I'll let you know.

Quoting "Richwine, Brian L" <brichwin at indiana.edu>:

> I am making a list of accessibility improvement that could be
> achieved in Sakai 3 over the Sakai 2.x code base. I'm especially
> interested in including issues that go beyond the "low hanging fruit"
> and in having a list that addresses issues that are critical to get
> into the ground floor of Sakai 3's development.
>
> Please email the list with comments and suggestions. Here is what I
> have so far:
>
> Accessibility improvements that could be seen in Sakai 3 over Sakai 2
>
> *         Explicitly labeling every form element (ARIA can be helpful here)
>
> *         Make all controls keyboard accessible (ARIA and accessible
> JavaScript techniques can be helpful here)
>
> *         Use accessible content authoring tools. Make sure the
> content authoring tools allow the user to create accessible content
> (alt text for images, accessible table markup (headers, summary,
> etc.), appropriate structural elements (headings, paragraphs, etc.),
> etc.)
>
> *         Allow users to specify their default WYSIWYG editor preference
>
> *         Make all link text/titles to unique destinations distinct.
> Make sure the purpose/destination of each link is clear.
>
> *         Use of appropriate semantic markup (good heading structure,
> lists for lists, paragraphs for paragraphs, well marked up data
> tables with summaries and appropriate headers, etc.)
>
> *         The use of CSS for layout instead of tables, or have each
> table's role marked appropriately
>
> o   Using ARIA: Adding role="presentation" to the table tag causes it
> to always be treated as a layout table
>
> o   Using ARIA: Adding role="grid" to the table tag causes any table
> to be treated as a data table
>
> *         Eliminating cases where the use of color is the sole means
> of communicating pieces of information
>
> *         Better announcement of pop-ups and completed actions (ARIA
> can be helpful here)
>
> *         Uniform and logical use of ARIA Landmarks to improve page
> navigation and purpose discovery by the user
>
> *         Use of ARIA features as needed to provide necessary
> contextual information for adaptive technologies (roles, states,
> change notification, etc.)
>
> *         Don't use frames/iFrames. If frames are necessary, make
> sure they are named appropriately to provide necessary contextual
> information.
>
>
> Brian Richwine
> Adaptive Technology Support Specialist
> Adaptive Technology and Accessibility Centers
> Indiana University - Bloomington/Indianapolis
> http://iuadapts.indiana.edu
> (812) 856-4112
>
>