Table 1. List of features for the example tools
described.
Category |
Feature |
Tool A |
Tool B |
Tool C |
Test subjects and their environment |
Content-types |
HTML, CSS and JavaScript |
HTML, CSS and JavaScript |
HTML, CSS and JavaScript |
Content encoding and content language |
ISO-8859-1, UTF-8, UTF-16; any language supported by these encodings |
ISO-8859-1, UTF-8, UTF-16; any language supported by these encodings |
yes |
DOM Document fragments |
no |
no |
no |
Dynamic content |
Relies on browser capabilities. |
yes |
yes |
Content negotiation |
Relies on browser capabilities. |
yes |
yes |
Cookies |
Relies on browser capabilities.[See note 1] |
yes |
yes |
Authentication |
Relies on browser capabilities. |
HTTP-basic, HTTP-digest, OpenID, HTML-form-based. |
yes |
Session tracking |
Relies on browser capabilities. |
URL rewriting, cookie-based, TLS session tickets. |
yes |
Crawling |
no |
Yes, filters can be specified. |
no |
Testing functionality |
Selection of evaluation tests |
Per WCAG conformance level |
Per WCAG conformance level; individual tests. |
no |
Automatic, semiautomatic and manual testing |
Only automatic. |
Automatic, semiautomatic and manual. |
yes |
Development of own tests and test extensions |
no |
no |
no |
Test automation |
no |
no |
yes |
Reporting and monitoring |
Standard reporting languages |
EARL [See note 2] |
EARL |
no |
Persistence of results |
no |
yes |
no |
Import/export functionality |
yes? [See note 3] |
yes |
no |
Report customization |
no |
Comments added by evaluator. |
no |
Results aggregation |
no |
Table, timeline. |
no |
Conformance |
no |
yes |
no |
Error repair |
Inline hints. |
yes |
yes |
Tool usage |
Workflow integration |
In browser. |
no |
no |
Localization and internationalization |
en |
User interface available in 18 languages. Tests tailored to en-US,
jp, zh-hans and ko. |
no |
Functionality customization to different audiences |
no |
yes [to whom?] |
no |
Policy environments |
no |
no |
no |
Tool accessibility |
Not accessible from screen readers. |
UI accessible through Operating System APIs. Reports conform to WCAG 2.0 Level A. |
no |