Accessibility issue when a Screen Reader/assistant calls out a button control which has Keyboard shortcut key
Hi, For a button control we have configured a keyboard shortcut as part of accessibility, shortcut is working as expected but when user uses voice assistant then the "Add" button is announced as "A dd", which is incorrect and confuses VoiceOver users. here we need both shortcut and also voice assistant should clearly call it out as "Add". Can you please suggest the solutions? Eg: &Add (this is how Pega recommended (Localization consideration) to use) in UI it displays as Add.
Current Code:
<button data-test-id="201707260528580280148864" data-ctl="" name="SearchHeader_pyWorkPage_44" accesskey="A" class="pzhc pzbutton" type="button" ><u data-keyboard="." data-click=".">A</u>dd</button>
Expected Code:
<button data-test-id="201707260528580280148864" data-ctl="" name="SearchHeader_pyWorkPage_44" accesskey="A" class="pzhc pzbutton" type="button">Add</button> Note: with tittle attribute that is by providing "helper text" is not accepted
Pegasystems Inc.
US
Hi @SOHIT
Pega no longer recommends introducing Accesskeys within the product. The function often introduces a variety of challenges, such as:
- Conflicts between accesskey shortcuts and the keyboard shortcuts of browsers, operating systems, assistive technologies, and browser extensions.
- Accesskeys overriding the keyboard shortcuts of some screen readers. In other cases they are rendered disabled.
- Accesskeys not working with devices such as tablets and phones, thus not satisfying WCAG POUR criteria.
State of New Jersey Courts
US
@PowerJillHello Jill, I appreciate that information, thank you. So, what does Pega suggest? thanks