home *** CD-ROM | disk | FTP | other *** search
- <?xml version="1.0" encoding="iso-8859-1"?>
- <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
- <html xmlns="http://www.w3.org/1999/xhtml">
- <head>
- <title>Accessibility in Amaya</title>
- <meta name="GENERATOR" content="amaya V4.2.2" />
- <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
- </head>
-
- <body xml:lang="en" lang="en">
-
- <table border="0" width="100%" summary="toc">
- <tbody>
- <tr>
- <td><p><img border="0" alt="W3C" src="../../Icons/WWW/w3c_home" /> <img
- border="0" alt="Amaya" src="../Icons/amaya.gif" /></p>
- </td>
- <td><p align="right"><a href="Configure.html" accesskey="p"><img
- alt="previous" border="0" src="../Icons/left.gif" /></a> <a
- href="Manual.html" accesskey="t"><img alt="top" border="0"
- src="../Icons/up.gif" /></a></p>
- </td>
- </tr>
- </tbody>
- </table>
-
- <div id="Access">
- <h2>Accessibility and Amaya</h2>
-
- <h3>Producing Accessible content</h3>
-
- <p>Amaya can be used to produce content that conforms to the W3C's <a
- href="http://www.w3.org/TR/WAI-WEBCONTENT">Web Content Accessibility
- Guidelines</a>. Some features, such as the requirement for an alt attribute
- for images and imagemap areas are already built in - it is impossible to add
- an image until it has alternative text. Amaya also automatically produces
- valid W3C compliant markup. Other features, such as appropriate long
- descriptions and captioning must be done by the author through the attributes
- menus or structure menus.</p>
-
- <p>The Amaya help documentation currently describes <a
- href="HTML-elements/infoTypes.html">how to use a few individual HTML
- elements</a> and as that documentation is written it will include help on how
- to ensure that the pages produced are accessible. In the meantime the most
- thorough guidelines are the W3C's <a
- href="http://www.w3.org/TR/WAI-WEBCONTENT">Web Content Accessibility
- Guidelines</a>. The W3C's <a href="http://www.w3.org/WAI">Web Accessibility
- Initiative</a> also publishes "<a
- href="http://www.w3.org/WAI/References/QuickTips/#Introduction">Quick Tips to
- make accessible Web sites</a>", ten handy reminders which are:</p>
- <ul>
- <li><strong>Images & animations.</strong> Use the <code>alt</code>
- attribute to describe the function of each visual.</li>
- <li><strong>Image maps.</strong> Use client-side <code>MAP</code> and text
- for hotspots.</li>
- <li><strong>Multimedia.</strong> Provide captioning and transcripts of
- audio, and descriptions of video.</li>
- <li><strong>Hypertext links.</strong> Use text that makes sense when read
- out of context. For example, avoid <q>click here</q>.</li>
- <li><strong>Page organization.</strong> Use headings, lists, and consistent
- structure. Use <strong>CSS</strong> for layout and style where
- possible.</li>
- <li><strong>Graphs & charts.</strong> Summarize or use the
- <code>longdesc</code> attribute.</li>
- <li><strong>Scripts, applets, & plug-ins.</strong> Provide alternative
- content in case active features are inaccessible or unsupported.</li>
- <li><strong>Frames.</strong> Use <code>NOFRAMES</code> and meaningful
- titles.</li>
- <li><strong>Tables.</strong> Make line by line reading sensible.
- Summarize.</li>
- <li><strong>Check your work.</strong> Validate. Use tools, checklist, and
- guidelines at <a
- href="http://www.w3.org/TR/WAI-WEBCONTENT">http://www.w3.org/TR/WAI-WEBCONTENT</a>.</li>
- </ul>
-
- <p></p>
-
- <h3>Accessibility of Amaya</h3>
-
- <p>Amaya's accessibility for people with disabilities is being improved with
- each release. Currently it is possible to perform most functions in Amaya
- without using a mouse, and to do most editing functions (except entering text)
- without using the keyboard.</p>
-
- <p>Accessibility features in the current version include:</p>
- <ul>
- <li>Alternate, Link, Structure and Table of Contents views that can be
- navigated and edited, and are all synchronized to the Formatted
- view..</li>
- <li>Source editing.</li>
- <li>Adding, removing and editing multiple stylesheets dynamically, including
- a user stylesheet.</li>
- <li>Access keys and Keyboard activation of commands, and links and form
- controls.</li>
- </ul>
- </div>
-
- <p align="right"><a href="Configure.html"><img alt="previous" border="0"
- src="../Icons/left.gif" /></a> <a href="Manual.html"><img alt="top" border="0"
- src="../Icons/up.gif" /></a></p>
- <hr />
- </body>
- </html>
-