Completed
Last Updated: 13 Sep 2021 05:08 by ADMIN
Release 2.27.0
Scott
Created on: 05 May 2021 11:15
Category: DropDownList
Type: Bug Report
1
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
When I use the Chrome Lighthouse (based on the axe accessibility testing tool) to assess the accessibility of the TelerikDropDownList I am getting several issues.
2 comments
ADMIN
Marin Bratanov
Posted on: 10 May 2021 18:22

Hi Scott,

The DropDownList does not have an <input> element, and if you set its Id parameter it will render as the id attribute of its topmost <span> element. The DefaultText renders in a span that is denoted by the aria-described-by attribute and so setting a default text should provide a description even if there is no item selected. The issue here is that there is a trailing space at the end of the value and that will be fixed.

That said, we have these reports on our radar and we will be investigating them.

Regards,
Marin Bratanov
Progress Telerik

Love the Telerik and Kendo UI products and believe more people should try them? Invite a fellow developer to become a Progress customer and each of you can get a $50 Amazon gift voucher.

Scott
Posted on: 06 May 2021 13:53

Here are all the aria issues i found on drop down lists.

ARIA input fields do not have accessible names

When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers.

 

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions.

[aria-*] attributes do not have valid values

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values.