Top Banner
Accessibility Issues Liddy Nevile QuickTime™ and a TIFF (Uncompressed) decompressor are needed to see this picture.
31

Accessibility Issues

Dec 07, 2014

Download

Technology

liddy

 
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Accessibility Issues

Accessibility IssuesLiddy Nevile

QuickTime™ and aTIFF (Uncompressed) decompressor

are needed to see this picture.

Page 2: Accessibility Issues

Overview

• Accessibility definitions• Current work to minimise problems• IMS accessibility activities• Matching content to people’s needs• Implementations• References

Page 3: Accessibility Issues

Overview

• Accessibility definitionsNot …• Telecommunications …. Or is it?• Economic equity … or is it?

Page 4: Accessibility Issues

Typical problems

• Can’t see screen• Can’t see colours• Can’t read text• Can’t hear• Can’t control cursor• Can’t type

Page 5: Accessibility Issues

OS supportAdd this to Favorites folderAdd this to startup itemsApple channel…..

Page 6: Accessibility Issues

Browser support (?)

• Lynx• IE• Netscape/Mozilla• iCab• Opera• Amaya• There are about 35 browsers in common

use…• (Note W3C UAAG - includes LMS)

Page 7: Accessibility Issues

ATs for people with vision disabilities

Page 8: Accessibility Issues

Jason White

QuickTime™ and aCinepak decompressor

are needed to see this picture.

Page 9: Accessibility Issues

Other assistive technologies

QuickTime™ and aTIFF (Uncompressed) decompressorare needed to see this picture.

QuickTime™ and aTIFF (Uncompressed) decompressorare needed to see this picture.

QuickTime™ and aTIFF (Uncompressed) decompressor

are needed to see this picture.

Page 10: Accessibility Issues

Other accessibility problems

QuickTime™ and aTIFF (Uncompressed) decompressorare needed to see this picture.

QuickTime™ and aTIFF (Uncompressed) decompressor

are needed to see this picture.

QuickTime™ and aTIFF (Uncompressed) decompressor

are needed to see this picture.

QuickTime™ and aTIFF (Uncompressed) decompressor

are needed to see this picture.

QuickTime™ and aTIFF (Uncompressed) decompressor

are needed to see this picture.

Page 11: Accessibility Issues

Accessibility definitions

• W3C - device independence, separation of content from presentation

• U.S. - s. 508 for Federal Govt. contracts• Australia - common law system with

regulations• UK, European Commission …• IMS/MMI-DC Working definition:

mismatch between user needs and content

Page 12: Accessibility Issues

W3C Guidelines

• Accessibility guidelines• Techniques• Checkpoints• Checkpoint techniques• QA and Certification- for authors, authoring tools, user

agents

Page 13: Accessibility Issues

Localisation of W3C guidelines

• University, system, organisational guidelines

• Controlling systems and templates• EuroAccessibility efforts• CEN MMI-DC Workshop• IMS Accessibility Guidelines• ( -> maths interest)

Page 14: Accessibility Issues

W3C Technologies that work

• Cascading style sheets (CSS1)• eXtensible Markup Language and CSS2• Scalable Vector Graphics (SVG)• Synchronised Multimedia Integration

Language (SMIL) • eXtensible Stylesheet Language (XSLT)• ChemML, MathML, MusicML, ...

Page 15: Accessibility Issues

SVG example

Page 16: Accessibility Issues

SVG example

• Image is represented as vectors in text• Sub-images can be identified• Metadata can be added• Rights management can be used• Behaviours can be controlled

– Eg an interactive knee dissection linked to external resources

Page 17: Accessibility Issues

Technologies that work (contd.)

• XML => MathML, ChemML, etc• MathML as an example

– The equation x2 + 4x + 4 =0

Page 18: Accessibility Issues

Separate presentation from content

• Presentational markup to ensure display can be controlled - with style sheets to define the display characteristics

• Content markup to provide machine readable version of content so it could be read into content manipulators

Page 19: Accessibility Issues

• <mrow>• <mrow>• <msup> <mi>x</MI> <mn>2</mn> </msup> <mo>+</MO>• <mrow>• <mn>4</mn>• <MO>&InvisibleTimes;</MO>• <MI>x</MI>• </mrow>• <MO>+</MO>• <mn>4</mn>• </mrow>• <MO>=</MO>• <mn>0</mn>• </mrow>

MathML is like HTML…

Page 20: Accessibility Issues

Screen presentation

• It can be read aloud by screen readers

• It can be used in maths applications

• It can be programmed for interactivity

• It can be programmed for feedback

• But it can’t yet be used in Braille.

Page 21: Accessibility Issues

Technologies that work (contd.)

• XML and RDF and EARL ….• XML - human readable, schemas etc …..• RDF - this ‘object’ has property ‘this’• EARL - this ’agent’ said this ‘object’ has this

‘property’ on this ‘date’• Eg “The application ‘Lift’ evaluated this

page as accessible (didn’t fail) on 3/9/2002”.

Page 22: Accessibility Issues

Author support

• W3C described what to do, how to do it, when and why,…

• Automatic support is required ->• W3C Authoring Tools Accessibility

Guidelines - note s. 508

Page 23: Accessibility Issues

Accessibility tools• Accessible tools• Tools for accessible authoring• Validators ie code validators • Evaluators ie compliance with

guidelines producing metadata (EARL)• Digital repositories for descriptive

metadata• (re-usable metadata??)• On-the-fly repair tools (SWAP, TILE, ..)

Page 24: Accessibility Issues

New IMS/DC/…approach

• Think of the user and work towards user needs and preferences

• Provide a good, easy way to record user needs and preferences

• Describe content in terms of needs and preferences

• Avoid all issues to do with disabilities and to do with legal liability

Page 25: Accessibility Issues

Accessibility issues

• Direct accessibility• Compatible accessibility• Alternative modality• Equivalent content• User choice

Page 26: Accessibility Issues

User profiles

• Control• Display (presentation)• Content• A special element to add to the LIP

because this info is usually managed by a different person from the teacher (and sometimes the student)

• Multiple, cascading profiles

Page 27: Accessibility Issues

AccLIP (User profile)

• AccessForAll:http://www.imsproject.org/accessibility/

Page 28: Accessibility Issues

Content profiles

• Control• Display (presentation)• Content• A separate element as the information

is usually an EARL statement• Same schema for exact matching and

easy maintenance

Page 29: Accessibility Issues

AccMD (Content profile)

• An EARL statement … so a URI:http://www.imsproject.org/accessibility

Page 30: Accessibility Issues

Implementation

• The Inclusive Learning Exchange at http://inclusivelearning.ca/

QuickTime™ and aTIFF (Uncompressed) decompressor

are needed to see this picture.