[low] consider more specific that "accessibility information" (1. accessibility info landing page, 2. reports (ATAG, VPAT, other), 3. "accessibility statement")

[shawna-slh]

Suggestion: Include field for them to provide a link to their ATAG Report, generated from https://www.w3.org/WAI/atag/report-tool/

Rationale: provides consistency of reports. promotes the tool

Level of importance: Low importance for first iteration or later

For example, in the Evaluation Tools List, we provide field for them to include a link to their Accessibility Statement and their ACT Rules Implementation Report.

[shawna-slh]

Since so few will have a formal ATAG Report, perhaps if that field is left blank, it is not displayed in the list -- as opposed to most of the fields where the label shows up and then "not provided".

[shawna-slh]

MVP:

• add to submission form
• get it into the JSON

MVP+2:

• add it to the List view details

[shawna-slh]

I also see that :

• many have an accessibility landing page, though it's not an "accessibility statement"
• some have a VPAT

How to we want to capture and provide these different types of information for list users?

[shawna-slh]

For now, we changed it to just "Accessibility information" in the listing. And the submission form says "Link to accessibility information (such as the tool's accessibility statement)"

I guess many will have an accessibility landing page that links to any additional information such as an accessibility statement, a VPAT, an ATAG Report, etc.