Accessibility Page Improvements

[amandadupell]

Is this issue related to the design system core library or design system website?

Design System website

Suggestions to the Design System Accessibility page

Small changes

• Update Developer and Designer Guidance links #1833
• Add Relevant Links from Product Accessibility Office to Resources Section #1858
• Add Government Resources to Accessibility Page #1918
• Accessibility page - Content Changes Based on Figma Comments #2214

Component page-level changes

• Privide Direct Links to Guides Specific to Components #2117

Section changes

• Add New Designer and Software Developer Guides Section #1971
• Add New Designer and Developer Videos Section to Accessibility Page #2008
• Add Video to Accessibility Page #2453

Larger changes

• provide a form section where users can submit feedback regarding the content of the accessibility page, the videos and the guides; this would mostly be used by the Product Accessibility Office to know what kind of information people would like to see in the future
• Restructure Accessibility Page #2118

"Accessibility" page will be a hub, presenting spoke pages as cards. The spokes would be:

• Designer and Software Developer Guides
• Accessible Product Design Videos
• Accessibility in Design & Development
• Testing for Accessibility
• Government Standards and Regulations
• External Resources

Additional Section

• Add "How to Best Test"/"Testing" Section to Accessibility Page #1932
• Create accessibility considerations checklist #2191
• Add Visual Elements for HPE Core Principles in Introduction #2238

Analytic Tracking

• confirm links to accessibility resources are tracked properly in Google Analytics

This data will be used by the Product Accessibility Office to see how much traffic we get from the Design System site. Helps us to answer the question of how valuable this page is to Design System users.

Open-ended Questions for Consideration

• Should we consider breaking down the page into multiple pages based on the sections?
• How can we indicate an "onboarding" section or have a place to point to for new developers at HPE?
• Should we have our own "checklist" for WCAG compliance, similar to this one for WebAIM and others found here?
• Most guides are written at a broad level without much technical language. Is there a way we could provide code snippets or examples through Grommet for developers?

Design

#2281