Per WAI-ARIA 1.2, the "aria-level" attribute, if present, "is an integer greater than or equal to 1".
However, Blazor TreeView uses 0-indexing for the attribute which means that the root item has an invalid (and ignored) aria-level property. This is problematic because the browser will infer the level from the DOM nesting for the root item, but then use aria-level for all other sub-trees, leading to inconsistent levels (in the demo, the level goes 2 > 1 > 2).
Hi Winston,
I confirm that this is an actual accessibility bug. As a result, we will use the public item you opened as a place for reporting different TreeView accessibility issues.
All TreeView accessibility bugs at once are planned for a fix in our 3.4.0 release that will be live in mid-June.
I hope this time frame suits you. If anything else related appears, please let me know.
Regards,
Hristian Stefanov
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.
Hi Winston,
I'm currently performing some more tests on the described issue. I will come back here with more details as soon as possible (at the latest, the next week).
If anything else related appears, please keep me updated.
Thank you for your patience and understanding.
Regards,
Hristian Stefanov
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.