1 / 20

Sakai and Accessibility

Sakai and Accessibility. Mike Elledge Accessibility Team Lead University of Michigan June 9, 2005. Topics. Where We Want To Be Where We Are How to Get There. Where We Want to Be. Achieve Sakai’s Accessibility Mission

hamilton-haley
Download Presentation

Sakai and Accessibility

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Sakai and Accessibility Mike Elledge Accessibility Team Lead University of Michigan June 9, 2005

  2. Topics • Where We Want To Be • Where We Are • How to Get There

  3. Where We Want to Be • Achieve Sakai’s Accessibility Mission • The Sakai Accessibility Team is responsible for ensuring that the Sakai framework and its tools are accessible to persons with disabilities… • “access to and use of information and data that is comparable to…members of the public who are not individuals with disabilities.”1 1Section 508 of the Rehabilitation Act of 1973

  4. Where We Want To Be • Full implementation of Sakai’s Accessibility Style Guide • Based on Core and SEPP requirements • Built on WCAG 1.0 • A, AA, and selected AAA compliance • Section 508 Plus

  5. Where We Want To Be • Provide a tool that enables: • Heading-based scanning of content and functional areas • Link-based navigation among tools • Efficient intrasite navigation via accesskeys • Extended descriptions via Title tags • Tips for Adaptive Technology (AT) users

  6. Where We Are • Refactored Sakai Tools • Completed: • Announcements, assignments, chat, email archive, discussions, home, membership, news, preferences, schedule, web content, page wrapper • Informed by Accessibility Style Guide: • Alt tags, table headers, headings, form labels, title tags • Tools linearalize, are CSS-based • Reviewed by JAWS user for usability

  7. Where We Are • Eliminated Refresh Problem • Continuous refresh precluded AT user access • Made refresh transparent to browsers • Will be event based in future, alerting user to new content

  8. Where We Are • The Portal Challenge • Does not include common access elements: • Skip links, accesskeys • Headings, link titles • Tabindexes • Result: Navigation not integrated with tools

  9. Where We Are • The iFrame Challenge • iFrames in Sakai don’t have self-awareness • Don’t know about the content they contain • Makes unique page and frame titling difficult • Some navigation components don’t cross frames well • Accesskeys, skip links, headings

  10. Bottom Line • Where we are: • Not Section 508 Compliant • Where we want to be: • Meet Section 508 requirements by next major release • Exceed Section 508 in future

  11. How To Get There • Goal: Become Section 508 compliant by fall • Plan: • Resolve portal problems • Finish tool refactoring • Screen tools for Section 508 compliance • Test and tweak tools for usability* *May be outside of 2005 scope

  12. How To Get There • Resources • Indiana University AT Lab • University of Michigan Usability Lab • University of Toronto • AT units at other core institutions • MIT • Stanford • UC Berkeley • Foothill-DeAnza

  13. How To Get There • Resolve Portal Problems • Revise existing portal? • Develop new, non-frame portal?

  14. How To Get There • Finish Tool Refactoring • Extend refactoring across all tools • Heuristic review for Section 508 compliance

  15. How To Get There • Formal Tool Evaluation • Usability Testing • AT user subjects • Test refactored tools and revised portal • Renovate tools based on results • May not (realistically speaking) be completed by end of 2005

  16. How To Get There • Beyond 2005 • Learner Preference-based content delivery • ATutor/TILE approach • Mitigates accessibility issues • Addresses multiple device requirements • Promote and facilitate accessible course materials • Support accessible tool development by SEPP

  17. Sakai Accessibility Documents • Documents related to Sakai Accessibility: • Core/SEPP Requirements • Sakai Accessibility Mission Statement • Sakai Accessibility Style Guide • Indiana University Sakai 1.5 Accessibility Testing • Accessibility Team Analysis of CTNG (Sakai 1.0) • All can be found in the Accessibility section in confluence: http://bugs.sakaiproject.org/confluence/display/2ACC/Home

  18. Questions For Attendees • What is your reaction to the plan? • What issues do you see? • Have you had any similar experiences that you’d like to share? • Have we overlooked anything?

  19. Questions for Sakai?

  20. Contact Information Mike Elledge Software Accessibility/Usability Specialist 2281 Bonisteel Blvd. University of Michigan Ann Arbor, MI 48109 Phone: 734-764-3593 Email: melledge@umich.edu

More Related