Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

QASP: Add Accessibility standard #14

Closed
jpmckinney opened this issue Dec 14, 2020 · 1 comment
Closed

QASP: Add Accessibility standard #14

jpmckinney opened this issue Dec 14, 2020 · 1 comment
Labels
implementation Relating to policy implementation

Comments

@jpmckinney
Copy link
Member

jpmckinney commented Dec 14, 2020

The question to resolve is how to operationalize the policy, not whether to have a policy about accessibility as such.

From https://derisking-guide.18f.gov/qasp/:

Deliverable Performance Standard(s) Acceptable Quality Level Method of Assessment
Accessibility Web Content Accessibility Guidelines 2.1 AA standards 0 errors reported using an automated scanner, and 0 errors reported in manual testing Pa11y
@jpmckinney jpmckinney changed the title Decide whether to add Accessibility to QASP QASP: Decide whether to add Accessibility Dec 15, 2020
@jpmckinney jpmckinney changed the title QASP: Decide whether to add Accessibility QASP: Add Accessibility Mar 15, 2021
@jpmckinney jpmckinney added implementation Relating to policy implementation and removed discussion labels Mar 15, 2021
@jpmckinney jpmckinney changed the title QASP: Add Accessibility QASP: Add Accessibility standard Mar 15, 2021
@jpmckinney jpmckinney changed the title QASP: Add Accessibility standard QASP: Add Accessibility and Performance standards Mar 17, 2021
jpmckinney added a commit that referenced this issue Dec 12, 2023
@jpmckinney jpmckinney changed the title QASP: Add Accessibility and Performance standards QASP: Add Accessibility standard Dec 12, 2023
@jpmckinney
Copy link
Member Author

Added Accessibility row to QASP.

I tested pa11y and it works.

One approach is to add a sitemap to public websites, which pa11y can use. pa11y is Node.js, so we'd either have to run it manually, or start up e.g. Django's runserver in CI, and then run pa11y against it.

I've configured CI for the data registry: open-contracting/data-registry#317

I added a page to the docs and opened issues in relevant repositories.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
implementation Relating to policy implementation
Projects
None yet
Development

No branches or pull requests

1 participant