13.07.2015 Views

EPiServer's Compliance to WCAG and ATAG - EPiServer World

EPiServer's Compliance to WCAG and ATAG - EPiServer World

EPiServer's Compliance to WCAG and ATAG - EPiServer World

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>EPiServer</strong> CMS 5 <strong>Compliance</strong> <strong>to</strong> <strong>WCAG</strong> <strong>and</strong> <strong>ATAG</strong> <strong>EPiServer</strong> CMS 5 <strong>Compliance</strong> <strong>to</strong> <strong>ATAG</strong> 1.0| 113.4 Do not au<strong>to</strong>matically generate equivalent alternatives. Do not reuse previously authored alternatives without author confirmation, except whenthe function is known with certainty.1 Yes3.5 Provide functionality for managing, editing, <strong>and</strong> reusing alternative equivalents for multimedia objects. 3 NoGuideline 4. Provide ways of checking <strong>and</strong> correcting inaccessible content.Checkpoint Priority Conformance4.1 Check for <strong>and</strong> inform the author of accessibility problems. Relative No4.2 Assist authors in correcting accessibility problems. Relative No4.3 Allow the author <strong>to</strong> preserve markup not recognized by the <strong>to</strong>ol. 2 Partial4.4 Provide the author with a summary of the document's accessibility status. 3 No4.5 Allow the author <strong>to</strong> transform presentation markup that is misused <strong>to</strong> convey structure in<strong>to</strong> structural markup, <strong>and</strong> <strong>to</strong> transform presentationmarkup used for style in<strong>to</strong> style sheets.Guideline 5. Integrate accessibility solutions in<strong>to</strong> the overall "look <strong>and</strong> feel".3 NoCheckpoint Priority Conformance5.1 Ensure that functionality related <strong>to</strong> accessible authoring practices is naturally integrated in<strong>to</strong> the overall look <strong>and</strong> feel of the <strong>to</strong>ol. 2 Yes5.2 Ensure that accessible authoring practices supporting Web Content Accessibility Guidelines 1.0 [<strong>WCAG</strong>10] Priority 1 checkpoints are amongthe most obvious <strong>and</strong> easily initiated by the author.Guideline 6. Promote accessibility in help <strong>and</strong> documentation.2 YesCheckpoint Priority Conformance6.1 Document all features that promote the production of accessible content. 1 Yes6.2 Ensure that creating accessible content is a naturally integrated part of the documentation, including examples. 2 Yes6.3 In a dedicated section, document all features of the <strong>to</strong>ol that promote the production of accessible content. 3 YesGuideline 7. Ensure that the authoring <strong>to</strong>ol is accessible <strong>to</strong> authors with disabilities.Checkpoint Priority Conformance7.1 Use all applicable operating system <strong>and</strong> accessibility st<strong>and</strong>ards <strong>and</strong> conventions. Relative No7.2 Allow the author <strong>to</strong> change the presentation within editing views without affecting the document markup. 1 Partial

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!