X hits on this document

537 views

0 shares

0 downloads

0 comments

38 / 134

Nicholas C. Romano, Jr.

Website Accessibility Research:

Disabled Users Still Locked Out

© Copyright 2007 All Rights Reserved

Slide #38

Faculty Research Excellence Series

Sponsored by the OSU-Tulsa Library

Thursday, March 29, 2007 6:00 pm North Hall Room 150

Checkpoints:10.1, 10.2,…etc.

Checkpoints:10.1, 10.2,…etc.

Checkpoints: 9.1, 9.2,…etc.

Checkpoints: 8.1, 8.2,…etc.

Checkpoints: 7.1, 7.2,…etc.

Checkpoints: 6.1, 6.2,…etc.

Checkpoints: 51, 5.2,…etc.

Checkpoints: 4.1, 4.2,…etc.

Checkpoints: 3.1, 3.2,…etc.

Checkpoints: 2.1, 2.2,…etc.

Checkpoints: 1.1, 1.2,…etc.

Checkpoints: 14.1, 14.2,…etc.

Checkpoints: 13.1, 13.2,…etc.

Checkpoints: 12.1, 12.2,…etc.

Needs

Experience

Cognitive

Psychomotor

Affective

Styles

Content

Representations

Universal Design

for Learning

Principles

Control

Mechanisms

Expression

Mechanisms

Engagement

Mechanisms

Motivation

Mechanisms

Learning

Communication

Manipulation

Interests

Skill Level

Preferences

Individual User

Characteristics

Knowledge

Axioms: users

Have these differences

Web Sites: can provide

different methods

Design Themes

Graceful

Transformation

Understandable,

Navigable

Content

Guidelines/Checkpoints

#12. Provide context and

orientation information.

# 13. Provide clear

navigation mechanisms

# 14. Ensure that documents

are clear and simple.

#1. Provide equivalent alternatives

to auditory & visual content.

#2. Don't rely on

color alone.

#3. Use markup and style

sheets and do so properly.

#4. Clarify natural

language usage.

#5. Create tables that transform

gracefully.

#6. Ensure pages featuring new

technologies transform gracefully.  

#7. Ensure user control of time-

sensitive content changes.

#8. Ensure direct accessibility of

embedded user interfaces.

#9. Design for

device-independence.

#10. Use interim solutions. .

#11. Use W3C technologies

and Guidelines.

Underlying Rationale

#12. Provide context and

orientation information.

# 13. Provide clear

navigation mechanisms

# 14. Ensure that documents

are clear and simple.

Audio screen readers read

all characters literally

#2. Don't rely on

color alone.

Semantic Information helps

specialized software understand

page organization.

Enables use of language-

appropriate pronunciation rules

#5. Create tables that transform

gracefully.

#6. Ensure pages featuring new

technologies transform gracefully.  

#7. Ensure user control of time-

sensitive content changes.

#8. Ensure direct accessibility of

embedded user interfaces.

#9. Design for

device-independence.

Scripted pop-up windows can

surprise or disorient

Some pages cannot be made

directly accessible.

Document info
Document views537
Page views537
Page last viewedThu Dec 08 04:50:46 UTC 2016
Pages134
Paragraphs2313
Words11671

Comments