Embed Size (px)
DESCRIPTION
SWAP Technology. Lisa Seeman 2004. The content dilemma. Getting your content to everyone: Disabilities Visual disabilities Hearing disabilities Physical disabilities Cognitive or neurological disabilities Scenarios that need solutions Mobile Different operating systems - PowerPoint PPT Presentation
Citation preview
SWAP Technology
Lisa Seeman 2004
© - UB Access, 2004
The content dilemma
Getting your content to everyone:• Disabilities
• Visual disabilities• Hearing disabilities• Physical disabilities• Cognitive or neurological disabilities
• Scenarios that need solutions• Mobile• Different operating systems• Noisy environment• Many more…
• Cultural• Non English speakers (language translation)• Knowledge system integration
• Keep costs at bay
© - UB Access, 2004
Traditional Accessibility
• Write good Mark Up (XHTML)• With options for alternatives for which is useful for
some scenarios
© - UB Access, 2004
SWAP
• Understand what is in a page• Save as meta data• Use knowledge to adapt content to any scenario
© - UB Access, 2004
General Public (on the Web)
Web Users withDisabilities
(with SWAP)
Your Current Website
Your Current Website
SWAP/Semantic Annotations, Automatic Fixes, Database
SWAPviews Engine
Layer of Meaning
PresentationalLayer
Alternativeversions
Untouchedoriginal
Web Content Accessibility Guidelines
© - UB Access, 2004
Different UsersDifferent scenarios
Application 2
SWAP/Semantic Annotations, Automatic Fixes, Database
SWAPviews Engine
Layer of Meaning
PresentationalLayer
Alternativeversions
Application 1
© - UB Access, 2004
What type of annotations?
For example:• Roles of content
• Meaning behind non text – text equivalences
• Relationship to service – no frames
• Relationships between text nodes and form elements- accessible forms and labels
• Structural identification of page elements – orientation
• Resolving ambiguities and relative importance – Simplifications
Plus interpretation = communication of knowledge
© - UB Access, 2004
For example: knowledge V accesskeys
Site link Page(x) is content type sitemap
Therefore this link links to a site map
knowledge processing
[S] site link
K site link
Site
map
Non sighted user
Russian non sighted user User with
LD
© - UB Access, 2004
Work for the author ?
• Assigning an access key each instance of the link across the site
• Avoid access key conflicts• Decide which links are important
OR• One line metadata
© - UB Access, 2004
Abbreviations and Concept Zoom
WCAG
WCAG expands Web Content Accessibility Guidelines
Web Content Accessibility Guidelines has more help at...
Knowledge Processing
WCAG WCAG (Web Content Accessibility Guidelines)
WCAG Web Content Accessibility Guidelines
WCAG :Web Content Accessibility Guidelines
Web Accessibility is......
© - UB Access, 2004
For example: XML to XML relationships
XML 1
<Meta/><chunk>
<section><text> Joe Bloggs <text> </section><section><text> 22 Cheri <text> </Section>
</chunk>
XML 2<myfile><My Meta/>
<entry name =“Joe bloggs” ><address> 22
Cheri</address><comments>No additional comments<comments>
</entry></myfile>
© - UB Access, 2004
Examples of interactivity library
Classes of content types
DatatypesDateEmail…
Action typesSubmitValidate…
HierarchalHeadingLabelTable relationship…
EventFocusMouse click….
© - UB Access, 2004
Current project Interactivity
Element
Has State
Datatypes
Hierarchal
Longdesc.html
Relationship
contentType
help
class
Presetation
State/ Condition Condition / event
action
createState
Action types
Condition
)listener(
Event Instance
TimeContition
Target
event
observer
TimeCondition
Rendering Condition
ConditionAction
© - UB Access, 2004
Key Advantages
• Better accessibility • Enable new user agent• Address XAG accessibility on schema level
• Without more work for the Author
© - UB Access, 2004
SWAP API
• API of function calls• Predefined library of types (extendable)• Predefined library of equivalents• RDF / “roles” box
(Used in our authoring tool)
