Technology moves fast! ⚡ Don't get left behind.🚶 Subscribe to our mailing list to keep up with latest and greatest in open source projects! 🏆


Subscribe to our mailing list

wcag-em-report-tool

Interactive Guide to Assist Managing Web Accessibility Evaluations

Subscribe to updates I use wcag-em-report-tool


Statistics on wcag-em-report-tool

Number of watchers on Github 36
Number of open issues 66
Average time to close an issue 3 months
Main language JavaScript
Average time to merge a PR about 5 hours
Open pull requests 2+
Closed pull requests 0+
Last commit about 2 years ago
Repo Created about 5 years ago
Repo Last Updated over 1 year ago
Size 3.21 MB
Homepage http://www.w3.org...
Organization / Authorw3c
Latest Release1.0
Contributors3
Page Updated
Do you use wcag-em-report-tool? Leave a review!
View open issues (66)
View wcag-em-report-tool activity
View on github
Fresh, new opensource launches 🚀🚀🚀
Trendy new open source projects in your inbox! View examples

Subscribe to our mailing list

Evaluating wcag-em-report-tool for your project? Score Explanation
Commits Score (?)
Issues & PR Score (?)

WCAG-EM Report tool is an assistant that takes the user through the process of evaluating the accessibility of a website, using the WCAG-EM Evaluation Methodology. The Report Tool runs entirely on the client and so it can be used offline and in any server configuration available to you.

The Report Tool does not save files to a server or in local storage. Rather, load and save functions are available for storing an evaluation to your local file system.

Important references:

The official released version of the Report Tool can be found at http://www.w3.org/WAI/eval/report-tool/. An example of the latest (unapproved by EO) version is available at http://w3c.github.io/wcag-em-report-tool/dist/.

See Change log for details about the latest version of the WCAG-EM Report Tool.

Install

Before you can install the WCAG-EM Report Tool you will need to install a few components:

  • NodeJS https://nodejs.org/en/
  • Ruby https://www.ruby-lang.org/en/documentation/installation/

In addition to these, you will need to install grunt cli. To do so run the following command. This will install the grunt command line interface in a global space on your machine.

npm install grunt-cli -g

Now with all global dependencies installed, the following commands will install the app and its dependencies

git clone git://github.com/w3c/wcag-em-report-tool.git
gem install compass
npm install
bower install

Usage

You can launch a development version by running:

grunt serve

To create a build in the /dist folder run:

grunt build

The build version can be hosted in on any server that available on http(s). WCAG-EM Report Tool runs in your local browser, so it only loads static files from the server.

Translations

The WCAG-EM Report Tool aims to be available for a wide audience. Much effort has been put into making translations as easy as possible. To learn about how to create your own translations read the translation documentation

Get Involved

Did you find a bug, or are you interested in working with us to create new features for the Report Tool, then get involved with the project!

Data Format

Data in the WCAG-EM Report Tool is saved and can again be loaded in a JSON format. The data format is JSON Linked Data, and uses EARL to store the test results.

Custom fields are based on WCAG-EM and are documented in EARL+JSON-LD format definition.

wcag-em-report-tool open issues Ask a question     (View All Issues)
  • almost 3 years Unable to save in Safari
  • about 3 years Website name is not filled in in the report
  • about 3 years Step 3: Better definition of "10%" sample
  • about 3 years Abbreviations: expansions and ECMA to JS
  • over 3 years translation.md - path
  • over 3 years Notify the user about missing permissions
  • over 3 years Terse accessibility statement to be added to the tool
  • over 3 years Improve wording on the Start page
  • over 3 years Move bootstrap row/col definitions from classes to stylesheets
  • almost 4 years Have import be asynch
  • almost 4 years Switch to node 4
  • almost 4 years Properly configure JShint and JSCS
  • almost 4 years Switch from Grunt to Gulp
  • about 4 years Error handling for unparsable load input
  • about 4 years Step 4 or Step 5: consider "other evaluation observation" field
  • about 4 years Step 4: consider separate field to record improvement suggestions
  • about 4 years Improve the speed of entering audit data
  • about 4 years Prepopulate short names based on explore step
  • about 4 years Add a 'scope' widget
  • about 4 years Restructure "Explore"
  • about 4 years Make labels more meaningful
  • about 4 years Create an introduction for first time users
  • about 4 years Rename the tool
  • about 4 years Allow grouping of success criteria by related topics
  • about 4 years auto-complete short name
  • about 4 years Support sub-requirements
  • about 4 years Support multiple results per assertion
  • about 4 years Remove hasPart from assertions
  • over 4 years Allow for multiple reports
  • over 4 years Add support for Responsibility Breakdown in report
wcag-em-report-tool open pull requests (View All Pulls)
  • Update broken URLs for Translate and Developer links
  • Fix extremely thin font on Retina Mac Screens
wcag-em-report-tool list of languages used
Other projects in JavaScript