Skip to main content

Hello all!  I am a front-end developer, currently working with a partner to remediate the commerce cloud OOTB SFRA to comply with WCAG 2.1 AA and provide a better experience for all users.  Does anyone have any experience with this?  If so, how did go?  Any major pain points?

 

#Accessibility #WCAG Standards  #A11y

2 件の回答
  1. 2021年8月6日 18:44

    Thank you for following up!  

     

    At a glance, there are a few top level concerns that I would love to see align more with the WAI best practices and WCAG techniques:

     

    Main Navigation - this currently uses the role="menu" and role="menuitem" pattern, however, this is typically used for web application menus.  WAI recommends the Disclosure for Navigation pattern. 

     

    PDP Carousel - carousel controls are anchors instead of button controls and do not communicate state or feedback. The WAI carousel pattern would ideal. I submitted this one the IdeaExhange this morning - thinking that might be the best route for proposing changes. :) 

     

    Mobile Refinements - collapsable content is not communicating state. WAI accordion would work in this case. 

     

    Focus Management - noticing areas where the focus is lost after certain user initiated behaviors.  For example, clicking "more results" on the category listing page ideally should send focus to the first new product anchor added to the grid.  Headline hierarchy - also seeing a few pages that don't follow the recommended consecutive headline order.  For example, the bonus product screen displays an h1, followed by an h2, then a series of h1s.

     

    Let me know if I should add these others to the IdeaExchange.  Thanks again!

0/9000