160 likes | 193 Views
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
E N D
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 • Noisy environment • Many more… • Cultural • Non English speakers (language translation) • Knowledge system integration • Keep costs at bay
Traditional Accessibility • Write good Mark Up (XHTML) • With options for alternatives for which is useful for some scenarios
SWAP • Understand what is in a page • Save as meta data • Use knowledge to adapt content to any scenario
General Public (on the Web) Web Users with Disabilities (with SWAP) Web Content Accessibility Guidelines Your Current Website Alternative versions SWAPviews Engine Presentational Layer SWAP/Semantic Annotations, Automatic Fixes, Database Layer of Meaning Untouched original Your Current Website
Different Users Different scenarios Alternative versions SWAPviews Engine Presentational Layer SWAP/Semantic Annotations, Automatic Fixes, Database Layer of Meaning Application 1 Application 2
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
For example: knowledge V accesskeys Page(x) is content type sitemap Site link Therefore this link links to a site map knowledge processing • Site • map [S] site link K site link Russian non sighted user Non sighted user User with LD
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
Abbreviations and Concept Zoom WCAG :Web Content Accessibility Guidelines Web Accessibility is...... WCAG WCAG expands Web Content Accessibility Guidelines Web Content Accessibility Guidelines has more help at... Knowledge Processing • WCAG WCAG WCAG (Web Content Accessibility Guidelines) Web Content Accessibility Guidelines
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> For example: XML to XML relationships
Examples of interactivity library • Classes of content types • Datatypes • Date • Email… • Action types • Submit • Validate… • Hierarchal • Heading • Label • Table relationship… • Event • Focus • Mouse click….
Event Instance observer TimeContition Current project Interactivity event TimeCondition Condition (listener) Element Target Rendering Condition Has State State/ Condition Condition / event Relationship Hierarchal contentType help Action types Datatypes Condition Action createState Presetation Longdesc.html action class ContentType
Key Advantages • Better accessibility • Enable new user agent • Address XAG accessibility on schema level • Without more work for the Author
SWAP API • API of function calls • Predefined library of types (extendable) • Predefined library of equivalents • RDF / “roles” box (Used in our authoring tool)
Thank you www.ubaccess.com lisa@ubaccess.com