mirror of
https://github.com/moodle/moodle.git
synced 2025-01-19 14:27:22 +01:00
71 lines
3.0 KiB
HTML
71 lines
3.0 KiB
HTML
<!--
|
|
TODO: Update as accessibility status changes.
|
|
FILE: lang/en_utf8/docs/accessibility.html
|
|
NOTES: Hard-coded links need to be edited/ scripted.
|
|
May need editing for local Moodle sites.
|
|
-->
|
|
|
|
|
|
<h1>Accessibility</h1>
|
|
|
|
<h2>Accessibility Statement</h2>
|
|
|
|
<p>This site has been tested in a range of browsers and with screen reader software.</p>
|
|
|
|
<p>Moodle uses semantic markup to assist screen reader users among others — site, page
|
|
and block headings use <h1>, <h2>, navigation blocks are lists <ul> and so on.
|
|
</p>
|
|
|
|
<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
|
|
Content Accessibility Guidelines 1.0</a>] level 1, most of level 2
|
|
[<a href="http://www.w3.org/WAI/WCAG1AA-Conformance" title="About Double-A WCAG conformance">about Double-A conformance</a>]
|
|
and some level 3. Through these guidelines we aim to comply with local laws regarding access to those with disabilities.
|
|
We are currently working to improve the accessibility and usability of Moodle.
|
|
At present there are still some tables used for layout, but in general presentation (using style sheets) is separated from content.
|
|
</p>
|
|
|
|
<p>We welcome feedback, particularly reports of any inaccessible content.
|
|
Please [<a href="./message/discussion.php?id=2">message the administrator</a>].
|
|
</p>
|
|
|
|
|
|
<h2>Access keys</h2>
|
|
|
|
<p>At present we don't specify access keys, but we intend implementing them for a future release of Moodle.</p>
|
|
|
|
|
|
<h2>Links</h2>
|
|
|
|
<p>There is a link before each side block, which allows screen reader users to skip the block.
|
|
Note, the link is hidden from graphical browsers.</p>
|
|
|
|
<p>Many links have title attributes
|
|
that describe the link in greater detail, unless the text of the link already
|
|
fully describes the target (such as the headline of an article). If a link has
|
|
an access key this will be announced in the link title.</p>
|
|
|
|
<p>Whenever possible, links are written to make sense out of context.
|
|
There are no javascript: pseudo-links. </p>
|
|
|
|
|
|
<h2>Images</h2>
|
|
|
|
<p>All images use the alt attribute to
|
|
provide alternate text where appropriate; images that are purely decorative
|
|
contain a null alt attribute. Images, such as maps, that present complex
|
|
information have a longdesc attribute linking them to a text description of the
|
|
image content.</p>
|
|
|
|
|
|
<h2>Standards compliance</h2>
|
|
|
|
<p>This site is built using valid
|
|
<acronym title="Extensible Hyper-Text Markup Language">XHTML</acronym>
|
|
for markup and uses CSS for presentation.</p>
|
|
|
|
<p style="text-align:center">
|
|
<a href="http://validator.w3.org/check?verbose=1&ss=1&uri=<?php echo $CFG->wwwroot; ?>" title="Use the W3C validator">Validate HTML</a>
|
|
| <a href="http://www.contentquality.com/mynewtester/cynthia.exe?rptmode=-1&url1=<?php echo $CFG->wwwroot; ?>" title="Test with Cynthia">Section 508 Check</a>
|
|
| <a href="http://www.contentquality.com/mynewtester/cynthia.exe?rptmode=0&warnp2n3e=1&url1=<?php echo $CFG->wwwroot; ?>" title="Test with Cynthia">WCAG 1 (2,3) Check</a>
|
|
</p>
|