Skip to main content

#WCAG Standards0 人がディスカッション中

We noticed a voiceover reader does not work well with our traditional end-user quote template.  What have others done? Create a quote template to use with those who are visually impaired so their accessibility tools function properly when reading quotes? Any other options? 

Thanks

Jim

#Usability  #WCAG Standards

3 件の回答
  1. 2022年1月12日 15:38

    @Jim Barrett Do you have an example of a quote which did not seem to be properly read by Voiceover? There can be several things which would make text unavailable to a screen reader, one of the biggest culprits being images of text, rather than text itself. My suggestion would be to work to make the template accessible, rather than creating a 2nd template which is specific to only certain users. If you are able to share an example, I might have some more specific suggestions for why you're encountering this behavior.

0/9000

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

Great to find this community and see all the helpful info shared!

 

We wondered whether anyone has looked into or knows of documentation around accessibility for Salesforce Surveys? It would be great to know whether the product is compliant with WCAG standards or at least compatible with screen readers for example.

 

I assume being built on the standard Salesforce stack the accessibility support is good but just haven't found anything confirming this explicitly.

 

Thanks all!

Lawrence

3 件のコメント
  1. 2020年8月20日 18:23

    @[Lawrence Newcombe

    If you are open to consider other 100% native Salesforce Survey options on AppExchange, check out SurveyVista on AppExchange -

    https://appexchange.salesforce.com/appxListingDetail?listingId=a0N3A00000FYkISUA1

    For SurveyVista, No issues are found by Free WCAG 2.0 checker. Additionally, SurveyVista offers everything you can do with Salesforce Surveys and plus more! Happy to discuss more over phone so if interested, send private message!

0/9000