afternoon session – day 1

of 27/27
Afternoon Session – Day 1 Afternoon Session – Day 1 Towards Full Accessibility in LMS Towards Full Accessibility in LMS OpenACS/.LRN Fall Confenrece 2006

Post on 22-Jan-2016




0 download

Embed Size (px)


Towards Full Accessibility in LMS. Afternoon Session – Day 1. OpenACS/.LRN Fall Confenrece 2006. Objectives of the Session. On-going developments and research works on accessibility compliance in LMS - PowerPoint PPT Presentation


  • Afternoon Session Day 1

    Towards Full Accessibility in LMSOpenACS/.LRN Fall Confenrece 2006

    Objectives of the SessionOn-going developments and research works on accessibility compliance in LMSAnalyze the accessibility status of .LRN/OpenACS and discuss the existing main problems and the way to solve them.Educate .LRN community in the importance of developing with accessibility requirements in mindDefine some guidelines to help .LRN developments reach the accessibility requirements

  • OpenACS/.LRN Fall Conference 2006Artificial Intelligence Dpt.Day 1 - Afternoon Session

    Towards Full Accessibility in LMSAccessibility Requirements in dotLRN Olga C. Santos R&D Technical Manager of aDeNu Research Group UNED (Spain)

    OverviewIntroduction to AccessiblityObjectivesWAI guidelines: WCAG 1.0 & 2.0Accessibility in .LRNPrevious effortsCurrent statusReported bugsPractical GuidelinesAJAX and accessibilityValidation

  • Introduction to Accessibility


    To allow different strategies for web accessTo facilitate the integration of technical aidsRemove accessibility barriers and Guarantee access for all

    Checkpoints for WCAG 1.0

    WCAG 2.0Still a DRAFT version!!! WCAG 2.0 Quick Reference Several changes Success Criteria and Conformance Levels Instead of Checkpoints and PrioritiesBaseline concept: technologies with accessibility supportDoes not prohibit the use of any specific technologyAs long as they are supported by accessible user agents, including assistive technologies. Comparison: WCAG 1.0 checkpoints to WCAG 2.0 Success Criteria

    [Off Topic]: Web Design World 2006Boston: Dec 11-13, 2006"Accessibility in a Web 2.0 World" by Shawn HenryWAI Outreach Coordinator at the W3Cholds a research appointment at the MIT Computer Science and Artificial Intelligence Laboratory (CSAIL)

  • Accessibility in .LRN

    Accessibility Status in .LRN efforts:Tristan Kalnins-Cole's under Dorian Peter's supervision2.1.3 was unofficially WCAG 1.0 level A compliantSelva theme: Designed to improve navigation and usability and based on CSSCurrent version: .LRN 2.2.0Tried to comply with WCAG 1.0 level AAnalysis based on the checkpoints from WCAG 1.0 Problems reported to the Bug tracker

    Requirements for accessibility in .LRN 2.2.0Selva ThemeAccessible forms (instead of standard.adp)openacs-4/packages/acs-templating/resources/forms/accessible-forms.adpMinor changes in some files (some already in CVS)openacs-4/www/blank-master.adpopenacs-4/packages/acs-subsite/lib/login.tclopenacs-4/packages/acs-templating/tcl/widget-procs.tclopenacs-4/packages/dotlrn/www/admin/term-new.tcl

    Bug Tracker: open accessibility bugsWCAG 1.0 level A: 6 open bugs#3024: WCAG - Checkpoint 5.2 #2940: LORS frames need a title #2939: LORS requires Javascript #2931: Specify language with lang attribute #2822: alt and title description in Calendar images #2816: alt description in dotLRN logo is not sufficientWCAG 1.0 level AA: 9 open bugs#2841: WCAG - Checkpoint 3.6 #2840: WCAG - Checkpoint 3.5 #2839: WCAG - Checkpoint 3.2 #2837: WCAG - Checkpoint 13.3 #2836: WCAG - Checkpoint 13.2 #2835: WCAG - Checkpoint 13.1 #2834: WCAG - Checkpoint 12.4 #2833: WCAG - Checkpoint 5.3 #2832: WCAG - Checkpoint 3.3WCAG 1.0 level AAA: 2 open bugs#3022: WCAG - Checkpoint 2.2 #3021: WCAG - Checkpoint 13.5

    Main reported problems (1/3)Skip menu missing (select where to go from top of the page)Site map or table of contents missingColour combinations used are not optimal Foreground and background of top menus (white vs. greenish/bluish)Critical problems in Calendar, ForumsDefault size of the text used in some pages is too smallFolder names, learning material, assessment, learning units, Specify language with lang attribute Proper descriptions in ALT and TITLE tagsExplicitly associate the form controls and their labels with the LABEL elementForums, Assessment

    Main reported problems (2/3)ForumsAn iframe is used and does not have a titleAlt text for expanding the thread (upside down orange triangle) is "+Table should have a table header (TH), summary and caption for the table, while layout should be controlled by css E.g. table under "members does notFrames Need to be avoided, or properly commentedTITLE attributes for the frames are emptyReconsidering the way LORS and IMS-LD packages are displayedAppletsUsed in LORSMetadata to give semanticskeywords, author, date, ...

    Main reported problems (3/3)Mark up lists and list items properly. UL elements can only include LI elements, but not P, BR or B, which are format elements and should be applied from the CSS.Use header elements to convey document structureh1 and h2 tags are used to give format to the titles!!!Documents have to validate to published formal grammarsThe same ID attribute is used several times in many pagesABSMIDDLE or BASELINE are not valid values for the attribute align.Attributes that do not exist are used: e.g. REMEMBERDeprecated attributes are used: e.g. BORDERStyle element can only be used in the head, not in the body. in the forums: div style="clear: both;Use style sheets to control layout and presentation

  • Practical Guidelines

    GuidelinesGuidelines for accessible and usable web sites: Observing Users Who Work With Screen Readers - Theofanos and Redish (2003) testing with people with disabilitiesUnderstand the relationship between accessibility and usability Understand how blind and low-vision users work with Web sites Develop research-based guidelines for accessibility and usability Assess the usability of specific Web sites for blind and low-vision users 32 guidelines grouped by:Using a Screen Reader Navigating through Web Sites Filling Out Forms

    Other referencesBooks, Sites, and Guidelines on Accessible Web Design aimed at developers who already have some experience coding web pages and project managers and administrators who need to be informed about accessibility, solid usability principles, and web standards. Web Accessibility Center at Ohio State University

  • AJAX

    AjaxAsynchronous Javascript and XMLmix of old technologies and new ideasincremental update of portions of a Web page without reloading the entire page. On the fly reloading of pagesspeeds up the Web, avoiding the need to reload the page how users and assisstive technologies identify slight page changes?Screen readers have to read the page from the beginningPartially sighted work on subpgesIf javascript is off, do it in the old way

    10 "Must Read" articles on AJAX, Accessibility and Web 2 technology Accessibility Overview Accessibility of AJAX Applications AJAX and Screenreaders: When Can it Work? Accessible Javascript guidelines Why Ajax Sucks (Most of the Time) Making AJAX work with screen readers

    Some recommendations from the user that the page is updated dynamicallyscreen reader users can decide when to trigger a re-read of the pageSend alerts when information is updatedalert boxes are read by screen readers and usually displayed with a soundHighlight recently updated areas for a short period of timeDont let the user fill in forms that cannot submitInform the user at the top or detect javascript automatically and warn

  • Validation

    ValidationTechnical guidelines can be automatically managed and validatedBut others require the manual (human) involvementThe ALT and TITLE tags are filled, but the content is good?Accessibility content guidelinesStructuring the contents: key idea paragraphs, main point at the beginning, Terminology: standard names, pronunciation by screen readers, Additional information about the contents: descriptions, acronyms, headings,

    ValidationMeeting just the accessibility guidelines defined by the WAI standards (or the national implementations such as the American Section 508, the UK SENDA, the Italian Stanca, or the German BITV) does not necessarily mean that the contents are accessible for allBut it is a BIG step forward

    ValidationEnd-user evaluations are neededUser evaluation (real users using assitive devices)Expert evaluation Important feedback for .LRN will be gathered by aDeNu Group from the following projects:FAA (Open and Flexible Training)EU4ALL (European Unified Approach for Accessible Life Long Learning)ALPE (Accessible Learning Platform for Europe)

  • Thanks for your attentionAny Questions?