EPIC: Accessibility improvements for Venia (Lighthouse)

[ericerway]

From pwa-studio created by ericerway : magento-research/pwa-studio#594

This issue is for the following packages:

[X] venia-concept [ ] pwa-buildpack [X] peregrine [ ] pwa-devdocs [ ] upward-js [ ] upward-spec

This issue is a:

[ ] Bug [X] Feature suggestion [ ] Documentation issue [ ] Other (Please Specify)

Environment

Question	Answer
Magento version
Operating System + version
node.js version (node -v)
npm version (npm -v)

Description

As a shopper, I want to experience a fully accessible Venia storefront regardless of my abilities so that I can achieve WCAG 2.0 recommendations and Google Lighthouse recommendations.

https://www.w3.org/WAI/standards-guidelines/wcag/

Expected result:

Updates to elements, colors, and language on key Venia experiences to improve accessibility as defined Google Lighthouse.

Categories: (affected)

• Elements Have Discernible Names
• Color Contrast is Satisfactory
• Page Specifies Valid Language

Pages: (affected)

• Homepage
• Category
• Product Details

Tasks

• [ ] Update Venia home, category, and PD pages with recommended fixes from Lighthouse
• [ ] Review Google Lighthouse scores for Accessibility to verify (Lighthouse 4.0.0-alpha.1)
• [ ] Update documentation (as appropriate)

Possible solutions:

Updates to Venia and UI components (peregrine) as appropriate.

[dmtrkad]

@ericerway , Are there any PBIs in "Ready for development" status that could be picked by us into this epic?

[ericerway]

Not yet, we have determined that this needs to be further groomed and associated with the core Peregrine (components) work first.

[ericerway]

@awilcoxa do we need both epics for accessibility or can we consolidate? (reference: #623)

[awilcoxa]

closing as duplicate