We have non-visual team members who are unable to fully participate in the process. Although an accessible navigable version has been released, it currently reads only “links” and does not allow adjustments to specify elements as buttons, for example.

To ensure a fully accessible experience, our components should include a dedicated area in their original specifications for defining the correct accessibility roles and attributes. This allows screen readers to navigate the entire screen — not just elements anchored in the HTML.