**Executive Summary**

</th> </tr> </table>

The WAI-Tools project work is defined by the following work packages:

  * **WP1:** Development of High-Quality Authoritative Conformance Test Rules 

  

  * **WP2:** Deployment and Demonstration of Accurate Decision Support Tools 

  

  * **WP3:** Integration of Open Tools for Large-Scale Compliance Assessments 

  

  * **WP4:** Engaging, Involving, and Disseminating Results to Key Stakeholders 

  

  * **WP5:** Project Management, Administration, and Technical Coordination 

  

Much of the project work builds on the test rules developed through Work
Package 1, which is the primary contribution of the project. Work Package 3
develops proof-of-concept tools and resources to support demonstrators of
real-life monitoring observatories in Portugal and Norway. These will be
developed through Work Package 2. The operation of these observatories is not
part of the project.

Given the nature of the project work, it does not collect or generate data in
the formal sense. This includes data about people, organisations, finances,
literature, or other entities, including clinical and experimental data. Most
importantly, the project does not collect or generate data that is considered
sensitive to privacy, security, or other ethical aspects. Yet the project does
generate resources, which can be considered data in a less formal sense.
Specifically, the testing rules and associated test cases can be considered as
a data set that is generated through the development activities of the
project.

This report describes the data management considerations and procedures
established in the project plans. This includes the development, publication,
and long-term sustainability of the project data.

These considerations and procedures are built directly into the project work
and financial plans, and ensure fully open data built on open standards from
the on-set of the project. That is, all data is open by default and published
using open licenses to ensure maximum implementation and reuse. This is
achieved by building on existing W3C development procedures and licensing,
which ensure open and royalty-free results. The W3C process and licensing is
widely recognised among the target audience.  
  
<table>  
<tr>  
<th>

**2**

</th>  
<th>

**Data Summary**

</th> </tr> </table>

The WAI-Tools Project develops several resources, most of which are typically
not considered data:

  * Documentation of accessibility testing procedures 

  

  * Test cases for testing procedure implementations 

  

  * Specification for a format for results from testing 

  

  * Software implementation of the above resources 

  

  * Educational materials and other documentations 

  

  * Scientific publications including reviewed articles 

  

All these outcomes of the project will be provided publicly using open
licensing. This may include:

  * W3C Document License: _https://www.w3.org/Consortium/Legal/2015/doc-license_

  

  * W3C Software and Document Notice and License: _https://www.w3.org/Consortium/Legal/2015/copyright-software-and-document_

  

  * W3C Community Contributor License Agreement: _https://www.w3.org/community/about/agreements/cla/_

  

  * Other comparable open license ensuring royalty-free use 

  

Scientific publications will be available under Open Access, typically Gold
Open Access unless there is specific justification to do otherwise. This would
be agreed upon with the Project Officer in advance.

For the purpose of this report, we do not consider the development of
specifications, software code, educational and outreach materials, and
scientific publications as data. We can consider the testing rules and the
associated test cases to be some form of ‘data’ that will be generated by the
project.

We expect to develop a total of 70 such testing rules over the 3-years
duration of the project. Each of the rules will, on average, have about 8 test
cases (at least 2 for ‘pass’ condition, 2 for ‘fail’ condition, and 2 for ‘not
applicable’ condition). This results in a data set of about 630 items (70 plus
560 items).

The testing rules and associated test cases are developed according to the W3C
ACT Rules Format 1.0 specification, which defines the format of these data
items:

  * _https://www.w3.org/TR/act-rules-format/_

  

The testing rules and associated test cases are developed by project staff
through a W3C Community Group called Auto-WCAG. In the earlier stages of the
project some of the testing rules and associated test cases may reuse existing
materials. This may be testing rules that project partners or others have
provided publicly for reuse, or brought into W3C through the Contributor
License Agreement (CLA):

  * _https://auto-wcag.github.io/auto-wcag/_

  

The target audience of these testing rules and associated test cases are
developers of accessibility testing tools and methodologies. Many of the key
vendors in this space are either participating in this effort directly, or
monitoring the development closely. The WAI-Tools Project includes activities
for further coordination, outreach, dissemination, and exploitation of these
primary project results.

In the process of developing the testing rules, selected samples of publicly
available websites will be used to validate the accuracy of the testing rules.
Results from these validations will not be shared or stored beyond the
involved project partners, and for the sole purpose of validation of the
rules.  
  
<table>  
<tr>  
<th>

**3**

</th>  
<th>

**FAIR Data**

</th> </tr> </table>

The following describes the findability, accessibility, interoperability, and
reusability of project data.  
  
<table>  
<tr>  
<th>

**3.1**

</th>  
<th>

**Findable**

</th> </tr> </table>

The testing rules and associated test cases are intended to become W3C
resources, and integrated as part of wealth of resources provided by the W3C
Web Accessibility Initiative (WAI):

  * _https://www.w3.org/WAI/_

  

The exact final location of this data set on the W3C/WAI website is yet to be
determined. However, we expect that this data set will be incorporated into or
linked from key WAI resources, such as:

  * Understanding WCAG 2.1: _https://www.w3.org/WAI/WCAG21/Understanding/_

  

  * Techniques for WCAG 2.1: _https://www.w3.org/WAI/WCAG21/Techniques/_

  

  * How to Meet WCAG 2.1: _https://www.w3.org/WAI/WCAG21/quickref/_

  

These resources are the primary and authoritative references for the target
audience of this data set, which will ensure maximum findability. Further
cross-linking may be considered later, if needed.

#  3.2 Accessible

The testing rules and associated test cases will be maintained on a W3C GitHub
repository:

• _https://w3c.github.io/wcag-act-rules/_

This repository will manage the testing rules and test cases developed through
the W3C Auto-WCAG Community Group, and that are considered to be sufficiently
mature and authoritative by W3C. That is, this repository will ensure a
certain threshold of quality, to ensure reliability for users of the data.

This will also ensure transparency, change control, and open accessibility of
the data. The data itself follows the publicly documented ACT Rules Format 1.0
specification, to ensure openness of the data.

#  3.3 Interoperable

Interoperability is a key criteria for completion of W3C standards. By
following theW3C ACT Rules Format 1.0 specification for the development of the
testing rules and associated test cases we ensure interoperability of the
data. The WAI-Tools Project include specific deliverables to demonstrate this
through documenting open source tools built by independent organisations that
employ this data.

#  3.4 Reuse

The testing rules and associated test cases developed by the project are
openly reusable by default. They are developed under the W3C Contributor
License Agreement (CLA), which allows royalty-free reuse by any entity,
commercially or non-commercially, including for the development of derivative
work. The finalised test rules and associated test cases will, in addition, be
published under the W3C Document License. This is more restrictive regarding
derivative work, to ensure interoperability. That is, developers who want to
refer to an authoritative data set endorsed by W3C can do so by referring to
the W3C repository using the W3C license. Developers who want to extend,
modify, or otherwise reuse the same data set can do so by referring to the
Auto-WCAG repository using the CLA license.  
  
<table>  
<tr>  
<th>

**4**

</th>  
<th>

**Resource Allocation**

</th> </tr> </table>

The costs for ensuring open data is built directly into the project work and
financial plan. Specifically, the work plan ensures development through the
open W3C community process. There are hardly any additional costs for this
work mode, yet the result are ensured to be open. The financial plan includes
a budget for Open Access should it be needed. However, the project does not
generate research data but rather scientific publications, which will be
equally provided through Open Access licensing.  
  
<table>  
<tr>  
<th>

**5**

</th>  
<th>

**Data Security**

</th> </tr> </table>

The testing rules and associated test cases developed by the project do not
include sensitive data. In turn, there is no need for particular security
measures in the project. The data is stored using one of the most widely known
developer platforms, GitHub. This has been recently acquired by Microsoft,
which may support the long-term availability of the platform. In addition, W3C
GitHub repositories are regularly backed-up in W3C space, to ensure long-term
preservation of the data. The data itself will continue to be maintained and
curated by responsible W3C groups beyond the project duration.  
  
<table>  
<tr>  
<th>

**6**

</th>  
<th>

**Ethical Aspects**

</th> </tr> </table>

There are no ethical aspects applicable to the project development of testing
rules and test cases.  
  
<table>  
<tr>  
<th>

**7**

</th>  
<th>

**Other Issues**

</th> </tr> </table>

There are no other issues applicable to the project development of testing
rules and test cases.