1 / 16

Sakai Accessibility: 2.2 and Beyond

Sakai Accessibility: 2.2 and Beyond. Mike Elledge, Michigan State University Gonzalo Silverio, University of Michigan with special guest Colin Clark, University of Toronto. Sakai Accessibility. What is Sakai Accessibility? Enhancements to 2.2 Key Projects for 2.3 Next Steps Other Issues

rinah-roth
Télécharger la présentation

Sakai Accessibility: 2.2 and Beyond

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 Accessibility: 2.2 and Beyond Mike Elledge, Michigan State University Gonzalo Silverio, University of Michigan with special guest Colin Clark, University of Toronto

  2. Sakai Accessibility • What is Sakai Accessibility? • Enhancements to 2.2 • Key Projects for 2.3 • Next Steps • Other Issues • JAWS Demonstration

  3. What is Sakai Accessibility? • An objective, an approach, a work in progress • Beyond the guidelines and standards

  4. Enhancements to 2.2 • Addition of accesskeys to common functions • Save, Cancel, Options, Permissions, Edit, Delete • Enhanced title tags to include tool names • Options, Permissions, Edit, etc. top bar tool functions • Extension of heading tags to include • Table subjects, hierarchies, and semantic blocks • Addition of alternates to event handlers • Provide “onclick” alternative for screen reader users • Addition of caption/summary tags to data tables

  5. 2.2 Enhancement Challenges • Templating Languages • Velocity: freedom (but no accountability) + Anything is possible - Each “view” in each tool is sui generis - There is no “validation” • JSF: structure (but restrictions) + Each tool uses the same “widget” in the same way - Not all widgets produce the best accessible mrkup - Core JSF and Sakai widget toolkit is sparse • Some examples

  6. Key Projects for 2.3 • Reducing or eliminating frames • Customizing JSF widgets • Portlet and portal communication • Breadcrumbs • Page-specific titles • CSS alternatives for persons with disabilities

  7. An invitation for 2.3: portal • Portal has always been a placeholder • Tool agnostic • iFrame dependent • Rigid • 2.3 - what should it “look” like from an accessibility POV? • Need input…some possible directions: • The OSPI model • The desktop model • The interface-less model

  8. An invitation for 2.3: tools • Humdrum workaday: velocity based tools - last chance at an overall edit • Need community to suggest a plan, get involved in setting tools in stone from an accessibility POV • JSF tools (and any new tool) • Core widgets: identify gaps, deficits • Sakai widgets: flesh out tlds, correct rendering • New Sakai widgets to address needs not met by Core and old Sakai

  9. Next Steps • Adoption of projects by community • Review of 2.2 accessibility • Prioritization of known issues • Formalizing Sakai Accessibility

  10. Sakai in the Future • AJAX and dynamic content • U Toronto TransformAble tool, based on IMS “AccessForAll” specifications • An information appliance?

  11. Developer’s Checklist (handout) • Accesskey Element • Form Structure • Heading Tags • Page Content and Structure • Skip Links • Table Structure • Title Tag and Title Element

  12. Community Interest (handout) • Assistance with evaluation • Assistance with 2.3 projects

  13. JAWS Demonstration

  14. Questions? Discussion?

  15. Handouts • Developer quick tips • Sign-up sheet for Accessibility WG • Sign-up for project interest

More Related