- From: <seeman@netvision.net.il>
- Date: Wed, 11 Aug 2004 13:31:00 +0300
- To: wai-xtech@w3.org
- Message-id: <01c601c47f8e$4eb4eca0$340aa8c0@lisaibm>
I am sure I have missed out usages , but it is hard to encapsulate the full paradigm in a few bullet points . In the RDF Techniques document I identify a few areas where RDF can enhance accessibility: * Media Equivalents including: Providing text equivalents for resources attached to any resource by anybody, mapping to webservice that provides the equivalent (such as our no frames transcoder, or high contrast rendering) * Structured Textual Markup - enhancing stucture of the markup of a document, including Data Tables outside a document, or translating the structure of an XML document to a markup structure that AT's are used to dealing with (e.g. myXML to XHTML) Binding sections of a document to a common role. Mapping different content sections as a block with common task/role, * Role and associations of elements and formats (pink implies feminine, bold is important, this is a field for the date, this page is a site map) * Clarifying Text (such as lexical references, resolving ambiguities such as pronouns (which "he" did you mean?), implied meanings, that type of thing) * Simplifying Text (such as symbols, summaries, to sections of content including section annotated with a role or as a block, marking sections of content as important for a given profile. Etc) * Forms and Interactivity -using RDF to map to the accessible interactivity model, and accessible form information , building and binding functional equivalents * Robustness and cross technology solutions including, a, using RDF to map accessibility and content model on non W3C technologies and non WCAG supported markup languages (see XAG) b, use of user profiling for different interpretations and rendering of web content General benefits Why RDF - Taken from the RDF Techniques document * Key benefits of annotation based solutions * Annotation base accessibility usage could solve accessibility problems in the following situations: * Simplified, annotated or multimedia content required for accessibility for some, is inappropriate for other audiences. 2 For example: annotations can provide, titles, headers, summaries (non normative) , glossary references and links to background information * The original rendering is incapable of change, such as when web authors are unable to use simplified language. * There are a large amount of pages to be made accessible including legacy pages - Annotations work generically on a site and are constructed to apply to the whole site. A single annotation can address a violation that occurs on multiple pages, and will fix each occurrence of the accessibility violation. The site does not have to be pulled down and retrofitted, and many pages can be automatically repaired. Annotations can also be constructed to apply generically to any content that is based on the same template. The same annotation repairs multiple pages that are created by the same application and template. * XML schema can be annotated to increase accessibility usage, which could have an effect of an immeasurable number of documents based on that schema. * alternatives / conditional content in different media's can be provided. For instance, an auditory rendering of a visual aid might be more appropriate in some contexts than text. * User profiles can be attached to Web content and alternatives, so renderings can be optimized to the individual user. As a secondary benefit, RDF Improves compatibility Knowledge-Based Services and the Semantic Web. In integrating accessibility and the semantic web, accessibility can be moved forward, paving the way for customized accessible searches and intelligent user agents with additional applications. Keep well and all the best, Lisa Lisa Seeman UB Access Tel: +972-2-648-3782 (please note our new number) Website: <http://www.ubaccess.com/> www.ubaccess.com THIS E-MAIL CONTAINS CONFIDENTIAL INFORMATION AND IS INTENDED FOR THE RECIPIENT OF THIS E-MAIL ONLY.
Received on Wednesday, 11 August 2004 10:30:47 UTC