Implement Accessibility features in Frontend of Registration app

[andrea-williams]

Description of the Tech Debt

The frontend of the Registration app has so far been built without any consideration for accessibility needs. For example, we don't have labels for screen readers, we might not be using the correct font (BC Sans), etc.

Ideally we should address all these before the Registration app goes live.

Developers will likely need assistance from UX to identify all the existing accessibility issues in the app, learn best practices, etc.

Tech Debt Triage

The purpose of our technical debt triage process is to analyze technical debt to determine risk level of the technical debt and the value in tackling that technical debt.

Risk Value Scoring:

Level	Value
High	3
Medium	2
Low	1

Technical Debt - Risk Types	Level	Value
Business Area Risk - Risk of business area visibility / damage to user experience		3
Developer Fault Risk - How likely will this tech debt cause a future error related to coding on top of it		1
System Fault Risk - Risk of system errors or application downtime		1
Time Scale Risk - Compound risk effect if left alone. How much more difficult to fix or dangerous will this become over time?		2
Time Sink Risk - How much will this tech debt slow the development process down		1
TOTAL SCORE:		8

[BCerki]

@andrea-williams , do we still need this card? We've added a check to the industry user playwright tests, and have a card for the cas roles one here: https://github.com/orgs/bcgov/projects/122/views/2?filterQuery=access&pane=issue&itemId=61039448