Overview

This web editor helps evaluators build Accessibility Conformance Reports in the OpenACR format (opens in a new window or tab). It is designed to help accessibility subject matter experts create machine-readable OpenACR documents. Authors will be guided in creating an accessible report for the digital product or service that they are documenting. Conformance for each requirement can be documented as required to generate a Section 508 report.

Tips for using this tool:

  • This editor saves the information you enter locally in your browser (not on our servers). To save or share your OpenACR report, you will need to save it to your computer. You will need the YAML file to submit your OpenACR and to edit this report in the future.
  • As you use the editor, the Report page lists the success criteria that you have checked and not checked.
  • You can export your report as YAML (structured data) but also as HTML (web page). Note: You will not be able to edit the report the future without the YAML file.
  • You can add limited formatting to your report with Markdown (opens in a new window or tab). This allows you to add lists, links and code examples.

About OpenACR Anchor link

OpenACR is a digital native Accessibility Conformance Report (ACR). The initial development is based on Section 508 requirements. There are many advantages in moving to a machine-readable format, but one of the biggest is that it allows accessibility claims of digital products and services to be compared. Moving to a highligh structured, self-validated document format will make this much simpler.

Many organizations face challenges in delivering accessible services to people with disabilities. Software vendors currently submit ACRs for their offerings. These ACRs document conformance of these products and services. These claims are generally provided in a PDF format which is often inaccessible, not consistently structured, and difficult to search. A modern ACR will be validated to see it matches a baseline format.

Responsible organizations both review vendor conformance claims and do independent testing. Documenting these findings in a consistent format will make it easier to provide feedback to vendors. Comparisons will make it easier to update reports.

For more information, see OpenACR (opens in a new window or tab).

Structure of this tool Anchor link

Following the structure of OpenACR, this tool takes you through 7 tables/chapters. Each table/chapter has a number of criteria, which are further divided into components. For each, you can select a level and type in a note about conformance.

A, AA, AAA are for the WCAG 2 guidelines.

FPC, Hardware, Software, Docs is the Section 508 standards.

Links in this editor will open a new window that lead you to the relevant sections of the guidelines.

Terms Anchor link

As you go through and enter conformance for your software, you will select a "term" for each component. Here is the legend of what those selections mean:

Supports
The functionality of the product has at least one method that meets the criterion without known defects or meets with equivalent facilitation.
Partially Supports
Some functionality of the product does not meet the criterion.
Does Not Support
The majority of product functionality does not meet the criterion.
Not Applicable
The criterion is not relevant to the product.
Not Evaluated
The product has not been evaluated against the criterion. This can be used only in WCAG 2.x Level AAA.

Your report

No report started.