[Athen] Salesforce Issues

[Vaughn, Michael]

Hi Emily,

I don’t have ready access to a Salesforce instance to verify your findings, but we usually don’t fuss much about errors reported by automated tools that don’t have much or any impact on users. WAVE does report errors in hidden content which is often not actually an issue. Presumably, the system would not expose the hidden content without first populating it with the missing child elements.

Also, a `tabindex=-1` attribute on a div does not cause the content to be skipped. It allows the element to be programmatically focused. If WAVE is reporting no heading structure, there must be some other reason for it.

Thanks,
Mike

_____
Michael Vaughn (he/him/his)
Associate Director of Digital Accessibility
Yale University, Information Technology Services

From: athen-list <athen-list-bounces at mailman12.u.washington.edu> on behalf of Emily Singer Lucio <eslucio at umd.edu>
Date: Monday, April 17, 2023 at 2:29 PM
To: Access Technology Higher Education Network <athen-list at u.washington.edu>
Subject: [Athen] Salesforce Issues
Hello all.

We are working with the Salesforce team and their accessibility people.  We continue to have two issues that are worrisome.


  *   an error exposed by the WAVE tool<https://wave.webaim.org/> - Broken ARIA menu. This error<https://docs.google.com/document/d/1wwhIinSurogPZqPHJAASzMMuBdSoUpUnJ8fGYfyN3uY/edit#bookmark=id.f3gwpm6bm9ni> presents in the WAVE tool but not with a screen reader. Stub code is included by Salesforce for potential future use with the top level menu so that additional menu items can overflow into a dropdown menu. The unnecessary 'menu' placeholder is in the Salesforce-generated code without any menu items, which breaks the ARIA rules. The Marketing and Communications team's assessment is that all WAVE errors should be removed. This error isn't identified by the screen reader because the parent element is hidden but a future update could expose the error.


"Upon further review, the ARIA menu issue is accessible and working as designed. Page navigation is using the standard out-of-box Jepson theme navigation header. I have attached a screen recording demonstrating the accessibility of page navigation using the JAWS 2023 screen reader." - Salesforce



  *   An alert exposed by the WAVE tool - No heading structure. The alert presents in the WAVE tool but not with a screen reader.  The H1 tag is on the 'My Cases' heading. A div six levels up from this H1 heading has tabindex="-1" which indicates that this div should be skipped, thereby signaling to WAVE/screen readers that the div that contains the H1 should be skipped.


I would like to get collective input from this group.  Have any of you had these issues?

Respectfully,

Emily Singer Lucio She/Her/Hers
ADA/504 Coordinator
University of Maryland, College Park
Office of Diversity & Inclusion
3123 Susquehanna Hall
4200 Leigh Road
College Park MD 20742
Tel:301 405-2841 | Fax:301 314-9992
Email: eslucio at umd.edu<mailto:eslucio at umd.edu>
Website: accessibility.umd.edu<http://accessibility.umd.edu/>

“Just because a man lacks the use of his eyes doesn’t mean he lacks vision.” — Stevie Wonder
Source: WeCapable
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman12.u.washington.edu/pipermail/athen-list/attachments/20230417/acbbd079/attachment.html>