Refactor design to align with WCAG 2.2 accessibility standards
As a developer,
I would like to refactor and align the existing Figma design
with WCAG 2.2 standards
to ensure consistent accessibility compliance across all applications.Background:
The current design in Figma needs some adjustments to fully meet the WCAG 2.2 guidelines. Specifically, issues such as the use of heading elements (e.g., the sequence of header tags and missing h1 on each page) have been noted. This creates discrepancies between accessibility requirements and the visual design.
In the recent merge request, it was found that each page must contain an h1 header, and headers should follow a hierarchical structure (h1, h2, h3, etc.). Currently, there is a deviation in the heading structure and overall design.
Acceptance Criteria:
-
Review Figma design for compliance with WCAG 2.2 standards, focusing on header structure and semantic HTML elements. -
Ensure that each page includes exactly one h1 header as required by WCAG 2.2. -
Ensure that headers should follow a hierarchical structure (h1, h2, h3, etc.). -
Make a decision on whether to update the Figma design to reflect accessibility changes or introduce alternative approaches (e.g., styling non-header elements).
Edited by Eugene E.