lang/en_utf8/help/accessibility.html

   1 <!--
   2 TODO:  Update as accessibility status changes.
   3 FILE:  lang/en_utf8/docs/accessibility.html
   4 NOTES: Hard-coded links need to be edited/ scripted.
   5        May need editing for local Moodle sites.
   6 -->
   7
   8
   9 <h1>Accessibility</h1>
  10
  11 <h2>Accessibility Statement</h2>
  12
  13 <p>This site has been tested in a range of browsers and with screen reader software.</p>
  14
  15 <p>Moodle uses semantic markup to assist screen reader users among others &mdash; site, page
  16  and block headings use &lt;h1&gt;, &lt;h2&gt;, navigation blocks are lists &lt;ul&gt; and so on.
  17 </p>
  18
  19 <p>Moodle complies with the World Wide Web Consortium's [<a href="http://www.w3.org/TR/WCAG10/" title="Web Content Accessibility Guidelines 1.0">Web
  20  Content Accessibility Guidelines 1.0</a>] level 1, most of level 2
  21  [<a href="http://www.w3.org/WAI/WCAG1AA-Conformance"  title="About Double-A WCAG conformance">about Double-A conformance</a>]
  22  and some level 3. Through these guidelines we aim to comply with local laws regarding access to those with disabilities.
  23  We are currently working to improve the accessibility and usability of Moodle.
  24  At present there are still some tables used for layout, but in general presentation (using style sheets) is separated from content.
  25 </p>
  26
  27 <p>We welcome feedback, particularly reports of any inaccessible content.
  28  Please [<a href="./message/discussion.php?id=2">message the administrator</a>].
  29 </p>
  30
  31
  32 <h2>Access keys</h2>
  33
  34 <p>At present we don't specify access keys, but we intend implementing them for a future release of Moodle.</p>
  35
  36
  37 <h2>Links</h2>
  38
  39 <p>There is a link before each side block, which allows screen reader users to skip the block.
  40  Note, the link is hidden from graphical browsers.</p>
  41
  42 <p>Many links have title attributes
  43 that describe the link in greater detail, unless the text of the link already
  44 fully describes the target (such as the headline of an article). If a link has
  45 an access key this will be announced in the link title.</p>
  46
  47 <p>Whenever possible, links are written to make sense out of context.
  48  There are no javascript: pseudo-links. </p>
  49
  50
  51 <h2>Images</h2>
  52
  53 <p>All images use the alt attribute to
  54 provide alternate text where appropriate; images that are purely decorative
  55 contain a null alt attribute. Images, such as maps, that present complex
  56 information have a longdesc attribute linking them to a text description of the
  57 image content.</p>
  58
  59
  60 <h2>Standards compliance</h2>
  61
  62 <p>This site is built using valid
  63  <acronym title="Extensible Hyper-Text Markup Language">XHTML</acronym>
  64  for markup and uses CSS for presentation.</p>
  65
  66 <p style="text-align:center">
  67   <a href="http://validator.w3.org/check?verbose=1&amp;ss=1&amp;uri=<?php echo $CFG->wwwroot; ?>" title="Use the W3C validator">Validate HTML</a>
  68 | <a href="http://www.contentquality.com/mynewtester/cynthia.exe?rptmode=-1&amp;url1=<?php echo $CFG->wwwroot; ?>" title="Test with Cynthia">Section 508 Check</a>
  69 | <a href="http://www.contentquality.com/mynewtester/cynthia.exe?rptmode=0&amp;warnp2n3e=1&amp;url1=<?php echo $CFG->wwwroot; ?>" title="Test with Cynthia">WCAG 1 (2,3) Check</a>
  70 </p>