CAMS-428: case detail accessibility

[fmaddenflx]

Purpose

Fixed non-critical Accessibility Issues

resolved the following issues:

• Look at H1 with name of page. Page is not titled, Perhaps should be Case Details
• Correct the Back to case list link. Could we know where the user came from to go back? Could be coming from My Cases, Staff Assignment, or Case Search.
• Rename Basic Information to Case Details Overview?
• Rename Audit History (Audit has baggage)
• Display the division code somewhere
• fix the space between labels and data.
• Change History empty state alert (no changes made) should say "No changes have been made to this case."

In regards to the backlink. We looked into various ways to accomplish this and each one opened up a large can of worms causing disorienting effects for the users. It was decided in the end that it would be better to not have a backlink. Backlink removed and all associated code dealing with localstorage and/or broadcast channel removed.

Testing/Validation

Testing is not yet complete.

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