Use TAB or TAB + SHIFT to navigate to the kebab menu and close buttons.
Notice the lack of meaningful name announced by NVDA.
Current Behavior
The kebab menu buttons and close buttons rely on svgs to visually convey their purpose. They lack informative alternative text or inline button labels. The purpose of the buttons is not conveyed to screen reader users.
Expected behavior/code
Ensure that all operable controls have accessible names. In the case of the button elements, inline text will suffice. This text can be visually hidden with CSS, although authors should not use display:none.
Note that the svgs should also be hidden from assistive technology with aria-hidden="true" and `focusable="false".
Environment
Chrome 92, Windows 10, NVDA 2020.4
AEM Core Components v. 2.17
Affected Users
Screen reader users, users of speech input
Steps to Reproduce
Current Behavior The kebab menu buttons and close buttons rely on
svg
s to visually convey their purpose. They lack informative alternative text or inline button labels. The purpose of the buttons is not conveyed to screen reader users.Expected behavior/code Ensure that all operable controls have accessible names. In the case of the
button
elements, inline text will suffice. This text can be visually hidden with CSS, although authors should not usedisplay:none
.Note that the svgs should also be hidden from assistive technology with
aria-hidden="true"
and `focusable="false".Environment Chrome 92, Windows 10, NVDA 2020.4 AEM Core Components v. 2.17
Affected Users Screen reader users, users of speech input
WCAG SC 4.1.2 Name, Role, Value