User stories

Transparency

1) As the developer of an accessibility test tool, I want to test my tool for accuracy in a way that can be compared to other tools, so that accuracy is a quality aspect I can use to position my product in the market.

2) As an accessibility auditor, I want to know exactly what the tools I use do and do not test, so that when I'm doing an audit I know what parts I can leave to a tool and what I should test myself.

3) As a developer of an open source accessibility tool, I want to document the way my tool tests for accessibility issues in a clear and understandable way, so that users who can't code can still contribute to the design of the tool.

Harmonization

4) As the product manager of a website, I want to know that the interpretation of WCAG used during testing internally is consistent with that of the accessibility community at large, so that I can be confident that test results are in line with my customer's expectation

5) As the product manager of a web application, I want the accessibility tools used internally to follow an interpretation of WCAG consistent with that of accessibility auditors I might hire for additional accessibility auditing, so that issues that have been resolved do not get reopened due to differing interpretations of accessibility requirements.

6) As the manager of a digital library, I want to automatically get a measure of the accessibility of eBooks, in a way that well understood and accepted by accessibility experts, so that I can provide accessibility information to my users, without having to constantly answer and argue questions by publishers about interpretations of the accessibility tests.

7) As a QA lead, following a web accessibility policy for an organization, I want to write test instructions (rules) that can be used by developers and QA testers, so that internal accessibility policies can be tested with the same ease as those of WCAG.

Measurability

8) As a developer of web applications, I want to configure my accessibility test tool in such a way that it only runs the most accurate rules, so that my integration tests only fail when there are real accessibility conformance issues.

9) As a Chief accessibility officer, I want to compare different accessibility tools based on test coverage and accuracy, so that I can empirically determine which accessibility tool best fits those requirements, without having to ask an accessibility expert.

10) As the developer of a new (web) technology, I want to write rules on how to test the accessibility of this technology, in a way that is understood and implementable by various accessibility test tools, so that developers of accessibility test tools can easily add basic accessibility testing of this new technology to their tool

11) As the product manager of a website, I want to provide my development and my QA team with products to help them avoid accessibility issues, so that I can minimize remediation costs of issues found by the accessibility team of my organization.