Open tdonohue opened 5 months ago
@tdonohue @hostle83
4science is interested in working on this task. In order to resolve the problem we're going to add an e2e test where required. Where not going to add any validation test in the new e2e created expect for the accessibility scanning.
Estimation is about 50h including any possible fixes for accessibility issues detected when the e2e test is created
@atarix83 : I think it's perfectly OK to only create the accessibility validation for the new e2e tests. That also has the benefit of creating a "basic scaffolding" for all pages to have more thorough e2e tests in the future (as part of a future effort).
Assigned to you and adding estimate details as a label.
Description
As of #2711, the following User Interface pages have automated accessibility scanning (via Deque's Axe tool) enabled:
The following pages are believed to be missing accessibility scanning:
Proposed solution
All DSpace user interface pages / modals should have an automatic accessibility scan enabled.
testA11y()
function on the page similar to the examples in #2711testA11y()
script fails (because accessibility issues exist on the page), then either the issues should be fixed or a temporary exclusion can be added to thetestA11y()
script until those issues can be fixed. For examples of exclusions see `submission.cy.ts`This ticket need not be solved by a single PR. In fact, it may be easier to implement these improvements over several PRs. Therefore, multiple people can claim this ticket provided they are clear about which pages they are working on.
Related work
Related to the work in #2711, which builds on some earlier automatic accessibility scanning.