Address Case Details Non-critical Accessibility Issues (Part 2)

[governmentSponsored]

This ticket handles the accessibility issues that are not mandated by WCAG.

Case Overview

• [ ] When a case is unassigned, the Assigned Staff List field gets in a state where an unordered list has a direct child that is a span, which threw an error in Axe DevTools.

Court Docket View

• [ ] Change Document Number field to simple text entry, and use real-time validation to inform the user that only numbers are acceptable. [input="number"] should generally be avoided, because it poses accessibility issues in terms of informing the user that certain inputs are valid or not.
• [ ] When there is a blank docket entry number (e.g. two entries on the same day), Axe DevTools throws an error, stating that a div has an aria-label attribute, but no valid role attribute.

[fmaddenflx]

Definition of Done:

• [ ] Acceptance criteria met - The system meets all acceptance criteria
• [ ] Feature toggles created - Features that are deployed but not released have toggles
• [ ] Design QA passed - All visual UI looks and works the way it’s supposed to
• [ ] Usability validated - Team ensures the working code is easy to use
• [ ] Accessibility tests passed - System passes automated and manual accessibility tests and supports applicable devices
• [ ] Code refactored for clarity - Developers can understand the work simply by reviewing the code
• [ ] Dependency Rule followed - More important code doesn’t directly depend on less important code
• [ ] Development debt eliminated - UX and code aligns to the team’s latest understanding of the domain
• [ ] Source code merged - Code has been merged into the main branch
• [ ] 90% unit test coverage achieved - Automated test coverage tools indicate coverage of >= 90%
• [ ] Code reviewed - Code is reviewed by at least two other team members before being merged
• [ ] Code quality checks passed - Code passes all automated quality checks
• [ ] Security scans passed - Code passes expected scans for vulnerabilities and compliance issues
• [ ] Threat model updated - The threat model incorporates new threats and remediations
• [ ] Build process updated - Automated build process include code supporting the user story
• [ ] Load/performance tests passed - Performance tests include the functionality of the user story
• [ ] Documents are updated - All required documentation is up to date and version controlled
• [ ] Code is deployed - Code is deployed to the highest production like environment