CAMS-426: header critical accessibility issues

[fmaddenflx]

Purpose

A number of issues were found with the last merge.

Major Changes

While fixing issues with Accessibility of the Header, a number of other Axe errors were flagged which required a major fix on a number of issues. All issues should now be resolved and working better than ever. There are likely a few issues on other tickets that were solved in this update. It was difficult to avoid updating them here, since the app wouldn't run due to a11y linting accessibility issues.

Testing/Validation

Test coverage is above 95%

Notes

Please see the ensemble notes document for a list of things to watch out for.

Definition of Done:

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