CAMS-418 accessibility stuff

[fmaddenflx]

Purpose

Made updates to comply with Accessibility findings

Major Changes

• Ensure that pagination controls can be focused via keyboard. This included changing the links (a tags) to unstyled buttons. Use of "a" tag with a click event an no href is improper from an accessibility standpoint. We need to avoid this practice.
• Gave staff assignment page a Main landmark -- consisted of simply changing main screen component outermost div to a "main" element.
• Added tooltips to Information button (did this on both the Staff Assignment page and My Cases page)
• Created a convenient ScreenInfoButton component for less boilerplate code. Just pass it a modal ref and be done.
• Updated head title for every screen.
• Fixed title for scroll-to-top button.
• Fixed colors for links in banner.
• Fixed issues with Screen Info Button and related modal.
• Added alert role to Alert component
• Added presentation role to table in Staff Assignment Modal
• Added Skip-to-main-content link in Banner and MainContent component
• Escaping out of modal returns focus to toggle button

• Added focusability to toggleModalButton

  You must supply a ref to the toggleModalButton, and if you do, it will be passed to the Modal, then the Modal will call focus() on the toggle button when the modal is closed.

Testing/Validation

Test coverage was not affected by changes.

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

[amorrow-flexion]

Make Sure The E2E tests are run on this branch. I have a feeling they have been impacted:

Succeeded: https://github.com/US-Trustee-Program/Bankruptcy-Oversight-Support-Systems/actions/runs/10599343291