[WG: Accessibility] Sakai Accessibility Teleconference this week

[Sean Keegan]

> Perhaps the way to proceed is to target
> Sakai 3 as a locus for aria enabled semantics, where they will be crucial
> given it’s ajaxy ways,  and leave the 2.x  as is, which is generally fairly
> accessible in old school ways. Does that sound right?

That sounds fine.  From my experience, 2.x works in terms of
accessibility and if integrating ARIA attributes into the 3.x code is
a more effective workplan, than I can support that option.  I suppose
the big question that comes to mind is then what are the timelines
surrounding 2.7 implementation as well as 3.x target dates?

Based on the meeting notes, it seems that the inclusion of these
roles/attributes in the accessibility checklist is one option to
pursue (as was outlined in the meeting notes from 7/30).  How much
information do you think is necessary to include in the accessibility
checklist - in other words, should there be information specific to
ARIA with examples?

Also - is there a specific accessibility criteria (e.g., WCAG 2, etc.)
that we are attempting to meet with either the 2.x or 3.x releases -
or at least specify to provide direction to developers as to the
conformance level?  I was poking around but did not see anything
specific on the Sakai site.

> I wanted to
> introduce  Scott Williams, the newly appointed head accessibility
> coordinator for the University of Michigan, who will be joining us.

Welcome, Scott.  Glad to have you participating.

Take care and hope to "see" everyone tomorrow,
sean