Skip to content

Possible Walk through for the editor interface: Proposed 2021 Interface

Mike Gifford edited this page Nov 16, 2021 · 7 revisions

This is a draft of the OpenACR editor (previously this was called the OPAT Editor) based on the work of the proposed new 2021 WCAG-EM design. It is simpler and has less text.

Proposed image based on this example.

Overview

This is the OpenACR Generator. It turns your accessibility evaluation findings into a machine readable report. The report produced is in a YAML format.

Tips for using this tool

  • Under “View Report”, you can download your report as HTML (web page) or as YAML (structured data).
  • Any long text box will allow Markdown formatting, to add lists, links and code examples and more.
  • This tool does not automatically save the information that you enter. To save your data in a file locally on your computer, use Windows shortcut keys ctrl+s or Mac shortcut keys cmd+s to open the Save dialog. (Or the ‘Save’ link at the top of the page will open the Save Evaluation Report page and from there the 'Save data file locally to your computer' link will open the Save dialog.)

About this tool

The OpenACR editor can be used to create a structured report of accessibility evaluation findings. It does not perform (automated) checks.

This tool is for experienced accessibility evaluators. You will need knowledge of Section 508, WCAG, accessible web design, assistive technologies, and how people with different disabilities use the Web.

How this tool works

  • All functionality provided by this tool is now loaded. It runs locally in your web browser. You don’t need an Internet connection beyond this point. When you close your web browser window, any unsaved data is lost.
  • All input is recorded as YAML data in the background (in your web browser, not on any server). You can download your report periodically as you work to avoid losing data if your web browser closes.
  • There are many tools that will allow a clean transition between YAML and JSON, if you would like to convert it.
  • You can save partially-complete reports and work on them later. To reload a saved file, use the ‘Open’ link at the top and find the file that you previously saved.

1. Define Scope

Define the overall parameters and scope of the evaluation. Ideally, this is done with the person who commissioned the evaluation (who may or may not be the website owner), to ensure common expectations about the scope of the evaluation.

  • OpenACR Version: [Section 508, WCAG, EU, All]
  • Requirements: [Web 2.0, 2.1, 2.2, Hardware, Software, Documentation]
  • Product/service name:
  • Product Description:
  • Name of Product/Version:
  • Date:
  • Vendor name:
  • Author name (optional):
  • Related OpenACR (optional):
  • Legal disclaimer (optional):
  • Notes:
  • Evaluation Methods Used:

2. WCAG Success Criteria, Level A, AA & AAA

Screen shot of WCAG page

Record the outcome from evaluating the website according to WCAG best practices.

3. Section 508 Refresh

Chapter 3: Functional Performance Criteria (FPC)

Chapter 4: Hardware

Chapter 5: Software

Chapter 6: Support Documentation and Services

4. European Union (EN 301 549)

Coming soon.

ACR View

  • Download Report (YAML)