• The content dilemma
• Traditional accessibility
• SWAP
• SWAP process
• SWAP process
• What type of annotations?
• For example: knowledge V accesskeys
• More work for the author?
• Abbreviations and concept zoom
• For example: XML to XML relationships
• Examples of interactivity library
• Current project - Interactivity
• Key advantages
• SWAP API
• Thank you

---

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

• Write good Mark Up
• With options for alternatives for which is useful for some scenarios

• Understand what is in a page
• Save as meta data
• Use knowledge to adapt content to any scenario

d

For example:

• Roles of content/li>
• Meaning behind non text – text equivalences/li>
• Relationship to service – no frames/li>
• Relationships between text nodes and form elements- accessible forms and labels/li>
• Structural identification of page elements – orientation/li>
• Resolving ambiguities and relative importance – simplifications/li>

Plus interpretation = communication of knowledge

d

• 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

d

d

• Classes of content types
• Datatypes
• Date
• Email…
• Action types
• Submit
• Validate…
• Hierarchal
• Heading
• Label
• Table relationship…
• Event
• Focus
• Mouse click….

API of function calls

• Predefined library of types (extendable)
• Predefined library of equivalents
• RDF / “roles” box

(Used in our authoring tool)

www.ubaccess.com

lisa@ubaccess.com