If the accessibility checking functionality of an authoring tool can detect that content does not meet a requirement of clauses 9 (Web content) or 10 (Documents) as applicable, then the authoring tool shall provide repair suggestion(s).

Rationale

The European accessibility standard's requirement to help authors repair inaccessible content can exceed the Section 508 requirement to prompt authors to create accessible content (504.3 Prompts). This checkpoint, Repair Assistance, specifically captures authoring tool abilities to offer repair suggestions, so that conformance with the European standard can be accurately reported.

Refer to Requirement 11.6.4: Repair Assistance for more information (external link to EN 301 549 toolkit).

Note: For authoring tool creators, language regarding possible repairs available can be investigated by examining the draft W3C document Techniques For Accessibility Evaluation And Repair Tools.

Note: The IBM compliance reporting system will be able to convey compliance status with European EN 301 549/Mandate 376: Accessibility requirements suitable for public procurement of ICT products and services in Europe. IBM accessibility checkpoints for the Revised Section 508 standard cover most of the EN 301 549 requirements. However, this is one of a set of additional checkpoints that must be completed to fully report compliance with the European standard.

Development Techniques

Review the General techniques as well as other tabs applicable to your technology.  Prioritize the use of technology-specific techniques, and implement the General techniques as needed. You are always required to find, understand and implement accessible code techniques to meet the checkpoint. The documented techniques and supplements are not exhaustive; they illustrate acceptable ways to achieve the spirit of the checkpoint. If numbered, techniques are in order of preference, with recommended techniques listed first. Where used, IBM information that complements the WCAG techniques is indicated as supplemental.

General techniques

Instructions: The output of authoring tools must meet all WCAG checkpoints. In addition, items in this section represent ATAG techniques deemed sufficient to address particular ATAG 2.0 guidelines which can be used to help meet the additional EN 301 549 requirement to help authors repair accessibility issues.

Web techniques

There are no specific Web techniques for this checkpoint. Refer to the General techniques section.

Mobile Native (iOS) techniques

Instructions: In addition to the General Techniques, the Mobile Native (iOS) techniques in this section represent a technique or combination of techniques that is deemed sufficient for meeting this checkpoint.

Eclipse techniques

Instructions: The Eclipse techniques in this section represent a technique or combination of techniques deemed sufficient for meeting this checkpoint.

Windows-based (MSAA+IA2) techniques

Instructions: The Windows-based (MSAA+IA2) techniques in this section represent a technique or combination of techniques deemed sufficient for meeting this checkpoint.


Most links in this checklist reside outside ibm.com at the Web Content Accessibility Guidelines (WCAG) 2.0. W3C Recommendation 11 December 2008: http://www.w3.org/TR/WCAG20/

Copyright © 1994-2017 World Wide Web Consortium, (Massachusetts Institute of Technology, European Research Consortium for Informatics and Mathematics, Keio University, Beihang University). All Rights Reserved.

Copyright © 2001, 2017 IBM Corporation