Developers' Guide to Features of Web Accessibility Evaluation Tools

Abstract

This document describes features that web authoring and quality assurance tools can incorporate, so that they support the evaluation of accessibility requirements, such as those defined by the Web Content Accessibility Guidelines (WCAG) 2.0. The main purpose of this document is to promote awareness of such tool features and to provide introductory guidance for tool developers on what kind of features they could provide in future implementations of their tools. This listing of features could also be used to help compare different types of evaluation tools, for example during the procurement of such tools.

The features in scope of this document include capabilities to help specify, manage, carry out and report the results from web accessibility evaluations. For example, some of the described features relate to crawling of websites, interacting with tool users to carry out semi-automated evaluation, and providing evaluation results in a machine-readable format. This document does not describe the evaluation of web content features, which is addressed by WCAG 2.0 and its supporting documents.

This document encourages the incorporation of accessibility evaluation features in all web authoring and quality assurance tools, and the continued development and creation of different types of web accessibility evaluation tools. The document does not prioritize nor require any particular accessibility evaluation feature or specific type of evaluation tools. It describes features that can be provided by tools that support fully-automated, semi-automated, and manual web accessibility evaluation. Following this document can help tool developers to meet accessibility checking requirements defined by the Authoring Tool Accessibility Guidelines (ATAG).

1 Introduction

Designing, developing, monitoring, and managing a website typically involves a variety of tasks and people who use different types of tools. For example, a web developer might use an integrated development environment (IDE) to create templates for a content management system (CMS), while a web content author will typically use the content-editing facility provided by the CMS to create and edit the web pages. Ideally all these tools provide features to support everyone involved throughout the process in evaluating accessibility. For example, an IDE could provide functionality to check document fragments so that the developer can check individual web page components during their development, and a CMS could provide functionality to customize the accessibility checks that are automatically carried out to help monitor the quality of the website. This document lists and describes these types of features that can be provided by tools to support accessibility evaluation in a variety of situations and contexts.

1.1 Evaluation Tools

In the context of this document, an evaluation tool is a (web-based or non-web-based) software application that enables its users to evaluate web content according to specific quality criteria, such as web accessibility requirements. This includes but is not limited to the following (non-mutually-exclusive) types of tools:

• Web authoring tool - Any web-based or non-web-based application(s) that can be used by authors (alone or collaboratively) to create or modify web content for use by other people (other authors or end users); from the Authoring Tool Accessibility Guidelines (ATAG) 2.0;
• Web quality assurance tool - Any (web-based or non-web-based) software application that is specifically designed to evaluate web content according to quality criteria (that are usually broader than accessibility requirements alone);
• Web accessibility evaluation tool - Any (web-based or non-web-based) software application that is specifically designed to evaluate web content according to accessibility requirements, such as the Web Content Accessibility Guidelines (WCAG) 2.0.

Note that these terms are not mutually exclusive. A web accessibility evaluation tool is a particular type of web quality assurance tool. In some cases it can be part of a web authoring tool, or considered to be a web authoring tool depending on the functionality that it provides (see the ATAG 2.0 definition for authoring tool). Also, a web quality assurance tool might not check for accessibility criteria but might provide other functionality, such as for managing quality assurance processes and reporting evaluation results, that may be useful for web accessibility evaluation. This document refers to any of these tools collectively as evaluation tools.

W3C Web Accessibility Initiative (WAI) provides a list of web accessibility evaluation tools that can be searched according to different criteria such as the features listed in this document.

2 Features of an accessibility evaluation tool

[Review Note: Feedback on this section is particularly welcome, specifically with suggestions for accessibility evaluation features that are not listed below and with comments to refine listed accessibility evaluation features.]

The features of an accessibility evaluation tool are presented in this section from different perspectives: the resource to be evaluated (i.e., web content and its linked resources, which enable its rendering to the user agent and end user), the testing requirements, the reporting customization capabilities of the tool and other tool usage characteristics like the integration into the development and editing workflow of the user.

The accessibility evaluation features listed and described below is not exhaustive. It may not be possible nor desired for a single tool to implement all of the listed features either. For example, tools that are specifically designed to assist designers in creating web page layouts would likely not incorporate features for evaluating the code of web applications. Developers can use this list to identify features that are relevant to their tools to plan their implementation. Also others interested in acquiring and using evaluation tools can use this document to learn about relevant features to look for.

2.1 Retrieving and rendering web content

This category includes features that help to retrieve and render different types of web content. There are tools that may retrieve the content to be analyzed from the file system or from a database. However, the majority of them do it via a network connection through the HTTP(S) protocol. This section focuses mostly on this latter scenario.

Due to the characteristics of the HTTP(S) protocol, the rendering of a web resource implies the manipulation and storage of many other components associated with it, like request and response headers, session information, cookies, authentication information, etc. These associated components are also considered in the following.

2.1.1 Content types

Although the majority of web resources are HTML documents, there are many other types of resources that need to be considered when analyzing web accessibility. For example, resources like CSS stylesheets or JavaScript scripts allow the modification of markup documents in the user agent when they are loaded or via user interaction. Many accessibility tests are the result of the interpretation of those resources and are therefore important for an accessibility evaluation. Accessibility evaluation tools should state which types of formats they support.

Some types of content formats include:

• Markup documents. These are normally HTML [HTML4, HTML5] or XML documents. Processing these resources typically requires the ability to build a Document Object Model (DOM) [DOM] according to the different specifications, which can then be parsed and analyzed.
• Style resources. These are presentation modifiers, which conform to the different CSS specifications [CSS2, CSS3]. The interpretation of stylesheets is relevant for many accessibility techniques.
• Script resources. These are components that modify the content or the presentation of web resources and web applications, be it because of user interaction or because of other functional requirements (e.g., notifications, dynamic updates, etc.). These resources play a critical role in Rich Internet Applications. Ignoring these resources may lead to missing accessibility problems or to report non-existing errors. The scripting language commonly used on the web is JavaScript, based upon ECMAScript [ECMAScript] standardized by the Ecma International standards organization.
• Media resources. These are images (static or animated), movies or audio tracks, which are standalone or embedded in a web resource. From the accessibility standpoint, the evaluation of these resources is relevant for issues like colour contrast, colour blindness or media alternatives, for instance.
• Other document formats. Many reports and administrative information are available in other document formats, typically in government websites. The format most commonly found is PDF, initially developed by Adobe [PDF] and later on standardised by ISO. Although not very frequent on the web, it is possible to encounter as well other formats like Apache OpenOffice [ODF] or Microsoft Office [OOXML].
• Resources with other formats. Examples of these could be Adobe Flash, Java applets, Microsoft Silverlight, etc. These resources are normally found embedded within HTML pages as applications.

2.1.2 Content encoding and content language

This feature identifies which content languages and encodings are supported by the evaluation tool. The web is a multilingual and multicultural space in which information can be presented in different languages, thus evaluation tools should be in the position to address this issue. Furthermore, web content can be transmitted using different character encodings and sets (like ISO-8859-1, UTF-8, UTF-16, etc.), which demands from the evaluation tools the capacity to handle them.

More information about this topic can be found in the W3C Internationalization Activity [W3Ci18n].

2.1.3 DOM document fragments

Many websites are generated dynamically by combining code templates with HTML snippets that are created by website editors. Evaluation tools may be integrated into Content Management Systems (CMS) and Integrated Development Environments (IDE) to test these snippets as developers and/or editors create them.

Usually this is implemented in the evaluation tools by creating DOM document fragments [DOM] from these snippets. Evaluation tools may filter as well the accessibility tests according to their relevance to the document fragment.

2.1.4 Dynamic content

Web and cloud applications are becoming very frequent on the web. These applications present similar interaction patterns as those of desktop applications and contain dynamic content and interface updates. Tools that evaluate such applications should emulate and record different user actions (e.g., activating interface components by clicking with the mouse, swiping with the fingers on a touch-screen or using the keyboard) that modify the status of the current page or load new resources. The evaluation tool needs to define and record these intermediate steps that can be later on interpreted by the tool (see section on web testing APIs).

2.1.5 Content negotiation

Content negotiation is a characteristic of the HTTP(S) protocol that enables web servers to customize the representation of the requested resources according to the demands of the client user agent. Because of this, the identification of resources on the web by a Uniform Resource Identifier (URI) alone may not be sufficient. To support content negotiation, the testing tool customizes and stores the HTTP headers according to different criteria (see discussion in

• to fetch a particular variant of the content, such as a mobile website;
• to fetch a specific language version of a website;
• to control session and authentication information;
• etc.

2.1.6 Cookies

A cookie is a name-value pair that it is stored by the user-agent [HTTPCOOKIES]. Cookies contain information relevant to the website that is being rendered and often include authentication and session information exchanged between the client and the server, which as seen before may be relevant for content negotiation.

A tool that supports cookies may store the cookie information provided by the server in an HTTP response an reuse it in subsequent requests. It may also allow the user to manually set cookie information to be used with the HTTP requests.

2.1.7 Authentication

Websites may require authentication (e.g., HTTP authentication, OpenID, etc.) to control access to given parts of the website or to present customized content to authenticated users.

A tool that supports authentication allows the user to provide their credentials beforehand, so that they are used when accessing protected resources, or it prompts the user to enter her credentials upon the server request. The tool may also support the use of different credentials for different parts of a web site.

2.1.8 Session tracking

Within HTTP, session information can be used for different purposes like, e.g., implementation of security mechanisms (login information, logout a user after a long inactivity period) or track the interaction paths of the users.

2.1.9 Crawling

Some evaluation tools incorporate a web crawler [WEBCRAWLER] able to extract hyperlinks out of web resources. There are many types of resources on the web that contain hyperlinks. The misconception that only HTML documents contain links may lead to wrong results in the evaluation process.

A web crawler defines an starting point and a set of options. The most common features of a web crawler (configuration capabilities) are:

• Types of content-types crawled (see section 2.1.1).
• Capability to define inclusion and exclusion filters. Customers may require analysis of concrete parts of the website or may not want to include others. Filters can be defined in different ways. For example, the user could define regular expressions against which URLs are matched, the maximum number resources to be crawled or a maximum recursion level in the crawling process.
• Multithreaded crawling. For a large site, it may be important to optimize performance by having a tool able to crawl in parallel threads.
• Avoidance of duplicate downloads. It is typical from web resources to link many times to the same resource (for example, stylesheets, main navigation pages, images, etc.). If the crawler is not able to identify such issues, it may lead to a great performance loss or to other runtime problems.
• Capabilities related to features described in previous sections like: content negotiation, authentication support or session tracking.

2.2 Testing functionality

This category includes features targeted to the configuration of the tests to be performed.

2.2.1 Selection of evaluation tests

Accessibility evaluation tools may offer the possibility to select a given subset of evaluation tests or even a single one. A typical example could be performing tests to the different conformance levels (A, AA or AAA) of the Web Content Accessibility Guidelines 2.0 or selecting individual tests for a single technique or common failure.

This feature shall not be confused with the fact that some tools are focused on testing a single characteristic of the web page, like for example, a tool to test color contrast.

2.2.2 Test modes: automatic, semiautomatic and manual

According to the Evaluation and Report Language (EARL) specification [EARL10], there are three types of modes to perform accessibility tests:

• Automatic - where the test was carried out automatically by the software tool without any human intervention.
• Manual - where the test was carried out by human evaluators. This includes the case where the evaluators are aided by instructions or guidance provided by software tools, but where the evaluators carried out the actual test procedure.
• Semi-Automatic - where the test was partially carried out by software tools, but human input or judgment was still required to decide or help decide the outcome of the test.

There are some evaluation tools that support accessibility experts by performing semiautomatic or manual tests. This support is normally introduced by highlighting in the source code or in the rendered document areas which could be originating accessibility problems or where human intervention is needed (for instance, to judge the adequacy of a given alternative text to an image).

Tools may keep provenance information (i.e., which part of the report was automatically generated by the tool and which was manually modified).

Some tools do not declare that they only perform automatic testing. Since it is a known fact that automatic tests only cover a small set of accessibility issues, full accessibility conformance can only be ensured by supporting developers and accessibility experts while testing in manual and semiautomatic mode.

2.2.3 Development of own tests and test extensions

Developers and quality assurance engineers need sometimes to implement their own tests. For that purpose, some tools define an API that helps developers to create their own tests, which respond to internal demands within their organization.

2.2.4 Test automation

When evaluating accessibility of web sites and applications, it is sometimes desirable to create scripts that emulate user interaction. With the growing complexity of web applications, there is an effort to standardize such interfaces. One of them is, for instance, the WebDriver API [WebDriver]. Tools that support this API enable developers to write tests that automate the application's and the end-users' behaviour.

2.3 Reporting and monitoring

This category includes features related to the ability of the tool to present, store, import, export and compare the testing results in different ways. In this section the term report must be interpreted in its widest sense. It could be a set of computer screens presenting different tables and graphics, a set of icons superimposed on top of the content displayed to the user indicating different types of errors/warnings, a HTML document or a word processor document summarizing the evaluation results, etc.

2.3.1 Standard reporting languages

Support for standard reporting languages like EARL [EARL10] is a requirement for many users. There are cases where tool users want to exchange results, compare evaluation results with other tools, import/export results (for instance, when tool A does not test a given problem, but tool B does it), filter results, etc. The support for a standardized language facilitates those tasks.

Although they may not be considered standardized, some tools support exporting test results in other common formats like Comma-Separated Values (CSV) [CSV, TABDATA].

2.3.2 Persistence of results

The implementation of monitoring features requires that the tool has a persistence layer (a database, for example) where results could be stored and retrieved at a later stage to compare different evaluation rounds.

2.3.3 Import/export functionality

In many evaluation methodologies, accessibility experts and quality assurance engineers use different tools. If the evaluation tool supports import and export of test results (for instance, in EARL format [EARL10], as JSON [JSON], in a CSV [CSV, TABDATA] file, etc.), the tool may be easily integrated in such environments.

2.3.4 Report customization

This feature allows the customization of the resulting report according to different criteria, such as the target audience, the type of results, the part of the site being analyzed, the type of content, etc. This feature may also allow the developer or the accessibility expert to add additional comments in the report.

2.3.5 Results aggregation

The presentation of evaluation results is influenced by the underlying hierarchy of the accessibility techniques with guidelines and success criteria. Aggregation is also related to the structure of the page. For instance, accessibility errors may be listed for a whole web resource or presented for concrete components like images, videos, tables, forms, links, etc.

2.3.6 Conformance

Conformance statements are demanded by many customers to assess quickly the status of their website. When issuing such conformance statements it is thus necessary to tackle the different types of accessibility techniques (i.e., common failures, sufficient techniques, etc.) and aggregate results as described in the previous section.

As described in Section 2.2.2, full accessibility compliance can only be achieved when manual testing has been implemented.

2.3.7 Error repair

The majority of web developers have little or no knowledge about web accessibility. Tools may provide together with their reporting capabilities additional information to support developers and accessibility experts to correct the accessibility problems detected. This information may include examples, tutorials, screencasts, pointers to online resources, links to the W3C recommendations, etc. If the evaluation tool is part of an authoring tool as described in the Authoring Tool Accessibility Guidelines 2.0 [ATAG], then the tool will meet its success criterion B.3.2.1.

This feature may include, for example, a guided step-by-step wizard which guides the evaluator to correct the problems found. Automatic repair of accessibility problems is discouraged, as it may originate non-desirable side-effects.

2.4 Tool usage

This section includes characteristics that describe the integration into the development and edition workflow of the user or are targeted to the customization of different aspects of the tool depending on its audience, like for instance, user interface language, user interface functionality, user interface accessibility, etc.

2.4.1 Workflow integration

Accessibility evaluation tools present different interfaces, which allow their integration into the standard development workflow of the user. The typical ones that can be highlighted are the following:

• Plug-ins or extensions in web browsers. Tools that integrate in web browsers may delegate on it the retrieval and rendering of the evaluated web content, effectively having as test subject the content the user is browsing at that moment. These tools may also present the evaluation results on the web browser's viewport or in a separate window.
• Plug-ins for Integrated Development Environments (IDEs) or for Content Management Systems (CMS). Tools that integrate with IDEs extend their typical capabilities to report accessibility errors. The communication possibilities range from direct integration into the API of the tool to access via a REST interface, for example.
• Stand-alone tools: desktop, mobile apps, online tools, etc.
• Integration into bug tracking systems, where developers and experts can monitor and trace accessibility problems.
• etc.

2.4.2 Localization and internationalization

Localization and internationalization are important to address worldwide markets. Tool users may not be able to speak English and it is necessary to present the user interface (e.g., icons, text directionality, UI layout, units, etc.) and the reports customized to other languages and cultures. As pointed out earlier, more information about this topic can be found in the W3C Internationalization Activity [W3Ci18n] and in [I18N].

From the accessibility standpoint, it is recommended to use the authorized translations of the Web Content Accessibility Guidelines. It must be considered as well that some accessibility tests need to be customized to other languages, like for instance, such as those related to readability.

2.4.3 Functionality customization to different audiences

Typically, evaluation tools are targeted to web accessibility experts with a deep knowledge of the topic. However, there are also tools that allow the customization of the evaluation results or even the user interface functionality to other audiences like, for instance:

• web developers with no or little knowledge of accessibility, who need detailed information on how to correct the problems found to implement appropriate solutions; or
• web commissioners, who need an aggregated view of the evaluation results and tools to support the monitoring of their own websites.

The availability of such characteristics must be declared explicitly and presented in an adequate way to these target user groups.

2.4.4 Policy environments

Although there is an international effort to harmonize web accessibility standards, there are still minor differences in accessibility requirements in different countries. The tool should specify in its documentation which policy environments are supported. Most of the tools are focused on the implementation of the Web Content Accessibility Guidelines 2.0 [WCAG20], because it is the accessibility standard most commonly referenced in policies worldwide.

2.4.5 Tool accessibility

Accessibility evaluation teams may include people with disabilities. To that end, it is relevant that the tool itself can be used with different assistive technologies and it is integrated with the accessibility APIs of the running operating system. In such cases, compliance with the Authoring Tool Accessibility Guidelines 2.0 [ATAG] becomes an important feature to support both from the perspective of the user interface of the tool and the access to its results.

Additionally, when producing reports (for instance, in HTML format), it is important that they are accessible as well and in compliance with the Web Content Accessibility Guidelines 2.0 [WCAG20].

3 Example profiles of evaluation tools

This section presents 3 examples of accessibility evaluation tools. They are provided for illustration purposes and do not represent an existing product. In every subsection, we will highlight some of the key features of the tool. The table at the end of the chapter summarizes and complements these textual descriptions.

3.1 Example Tool A: Browser plug-in evaluating a rendered HTML page

Tool A is a browser plug-in, which can perform a quick automatic accessibility evaluation on a rendered HTML page. The main features of the tool are:

• Testing of the Web Content Accessibility Guidelines 2.0 techniques that can be automatically analyzed. The configuration options of the tool are limited to perform one of the three conformance levels of WCAG: A, AA or AAA.
• Graphical presentation of accessibility issues by means of icons that represent different types of problems. By selecting any of the icons, the user receives hints on ways to solve the error.
• The tool relies on the capabilities of the browser to support cookies, authentication and content negotiation, but it does not offer configuration capabilities for these items.
• Since the tool works directly on the browser, it is not integrated in the workflow of users who utilize IDEs in their development process.
• The tool allows to export the evaluation results as an EARL report or as a CSV file.

Table 1 presents an overview of the matching features as described in section 2.

3.2 Example Tool B: Large-scale accessibility evaluation tool

Tool B is a large-scale accessibility evaluation tool used to analyze web sites with large volumens of content. The main features of the tool are:

• It offers its users the possibility to crawl and evaluate complete websites. It also offers the possibility to customize which parts of the website are analyzed by defining or excluding different areas of the site to be crawled.
• Evaluation results are retained in a relational database and there is a dashboard to compare results at different dates. Users can select a subset of the crawled pages and complete the automatic and semiautomatic tests by inspecting the selected pages and store the results in the database.
• The tool analyzes HTML, CSS and JavaScript, being able to interpret it dynamically with a rendering engine.
• The tool supports authentication, sessions, cookies and content negotiation by customizing the HTTP headers and other parameters used in the crawling process.
• The tool performs autonomously the WCAG automatic tests.
• The reports of the tool can be exported as an EARL report (serialized as RDF/XML), as a spreadsheet and as a PDF document.
• The tool implements the corresponding interfaces to the accessibility APIs of the operating system, being accessible to users with disabilities.

Table 1 presents an overview of the matching features as described in section 2.

3.3 Example Tool C: Accessibility evaluation tool for mobile applications

Tool C is an accessibility evaluation tool for web-based mobile applications. The tool does not support native applications, but it provides a simulation environment based upon a virtual machine environment that emulates the accessibility API of some devices. The main features of the tool are:

• The tool can emulate different user agents running on given mobile operating systems. Like tool A, it relies on the capabilities of the browser to support cookies, authentication and content negotiation, but it does not offer configuration capabilities for these items.
• It shows typical display sizes corresponding to predefined smartphones and tablets.
• It supports HTML, CSS and JavaScript, providing to the users an implementation of the Web Driver API, supporting automatic and manual evaluation.
• It detects only accessibility issues related to the implementation of the accessibility API of the given mobile operating systems.

Table 1 presents an overview of the matching features as described in section 2.

3.4 Side-by-Side Comparison of the Example Tools

This section presents a tabular comparison the tool features described previously. They are provided for illustration purposes and do not represent an existing product.

4 References

ATAG

Authoring Tool Accessibility Guidelines (ATAG) 2.0. W3C Candidate Recommendation 7 November 2013. Jan Richards, Jeanne Spellman, Jutta Treviranus (editors). Available at: https://www.w3.org/TR/ATAG20/

CSS2

Cascading Style Sheets Level 2 Revision 1 (CSS 2.1) Specification. W3C Recommendation 07 June 2011. Bert Bos, Tantek Çelik, Ian Hickson, Håkon Wium Lie (editors). Available at: https://www.w3.org/TR/CSS2/

CSS3

CSS Current Status is available at: https://www.w3.org/standards/techs/css

CSV

Common Format and MIME Type for Comma-Separated Values (CSV) Files. Y. Shafranovich. Internet Engineering Task Force (IETF). Request for Comments: 4180, 2005. Available at: https://tools.ietf.org/rfc/rfc4180.txt

DOM

W3C DOM4. W3C Last Call Working Draft 04 February 2014. Anne van Kesteren, Aryeh Gregor, Ms2ger, Alex Russell, Robin Berjon (editors). Available at: http://www.w3.org/TR/dom/

EARL10

Evaluation and Report Language (EARL) 1.0 Schema. W3C Working Draft 10 May 2011. Shadi Abou-Zahra (editor). Available at: https://www.w3.org/TR/EARL10-Schema/

ECMAScript

ECMAScript® Language Specification. Standard ECMA-262 5.1 Edition / June 2011. Available at: http://www.ecma-international.org/ecma-262/5.1/

HTML4

HTML 4.01 Specification. W3C Recommendation 24 December 1999. Dave Raggett, Arnaud Le Hors, Ian Jacobs (editors). Available at: https://www.w3.org/TR/html4/

HTML5

HTML5. A vocabulary and associated APIs for HTML and XHTML. W3C Candidate Recommendation 04 February 2014. Robin Berjon, Steve Faulkner, Travis Leithead, Erika Doyle Navara, Theresa O'Connor, Silvia Pfeiffer, Ian Hickson (editors). Available at: http://www.w3.org/TR/html5/

HTTPCOOKIES

HTTP State Management Mechanism. A. Barth. Internet Engineering Task Force (IETF). Request for Comments: 6265, 2011. Available at: https://tools.ietf.org/rfc/rfc6265.txt

I18N

Internationalization and localization. Wikipedia. Available at: https://en.wikipedia.org/wiki/Internationalization_and_localization

JSON

The JSON Data Interchange Format. Standard ECMA-404 1^st Edition / October 2013. Available at: http://www.ecma-international.org/publications/standards/Ecma-404.htm

ODF

Open Document Format for Office Applications (OpenDocument) Version 1.2. OASIS Standard 29 September 2011. Patrick Durusau, Michael Brauer (editors). Available at: http://docs.oasis-open.org/office/v1.2/OpenDocument-v1.2.html

OOXML

Ecma international. TC45 - Office Open XML Formats. Ecma International. Available at: http://www.ecma-international.org/memento/TC45.htm

PDF

PDF Reference, sixth edition. Adobe® Portable Document Format, Version 1.7, November 2006. Adobe Systems Incorporated. Available at: http://www.adobe.com/devnet/pdf/pdf_reference_archive.html

RFC2119

Key words for use in RFCs to Indicate Requirement Levels. IETF RFC, March 1997. Available at: http://www.ietf.org/rfc/rfc2119.txt

TABDATA

Model for Tabular Data and Metadata on the Web. W3C First Public Working Draft 27 March 2014. Jeni Tennison, Gregg Kellogg (editors). Available at: https://www.w3.org/TR/tabular-data-model/

W3Ci18n

W3C Internationalization (I18n) Activity. Available at: https://www.w3.org/International/

WAI-ARIA

Accessible Rich Internet Applications (WAI-ARIA) 1.0. W3C Recommendation 20 March 2014. James Craig, Michael Cooper (editors). Available at: https://www.w3.org/TR/wai-aria/

WCAG20

Web Content Accessibility Guidelines (WCAG) 2.0. W3C Recommendation 11 December 2008. Ben Caldwell, Michael Cooper, Loretta Guarino Reid, Gregg Vanderheiden (editors). Available at: https://www.w3.org/TR/WCAG20/

WCAG20-TECHS

Techniques for WCAG 2.0. Techniques and Failures for Web Content Accessibility Guidelines 2.0. W3C Working Group Note 8 April 2014. Michael Cooper, Andrew Kirkpatrick, Joshue O Connor (editors). Available at: https://www.w3.org/TR/WCAG20-TECHS/

WEBCRAWLER

Web crawler. Wikipedia. https://en.wikipedia.org/wiki/Web_crawler

WebDriver

WebDriver. W3C Working Draft 12 March 2013. Simon Stewart, David Burns (editors). Available at: http://www.w3.org/TR/webdriver/

Acknowledgements

The editors would like to thank the contributions from the Evaluation and Repair Tools Working Group (ERT WG), and especially from Yod Samuel Martín, Philip Ackermann, Evangelos Vlachogiannis, Christophe Strobbe, Emmanuelle Gutiérrez y Restrepo and Konstantinos Votis.

This publication was developed with support from the WAI-ACT project, co-funded by the European Commission IST Programme.