In Development
Last Updated:
05 Sep 2023 10:34
by ADMIN
Scheduled for R3 2023
Hudson
Created on:
28 Aug 2023 08:33
Category:
MultiSelect
Type:
Bug Report
RadMultiSelect WCAG 4.1.1 Parsing Error - Duplicate DOM Control with the same Id.
The RadMultiSelect implementation has one error that WCAG 4.1.1 parsing is catching. There is a duplicate span with the same id.
Found in the page source of the demo page (similar to how I implemented as well):
https://demos.telerik.com/aspnet-ajax/multiselect/virtualization/defaultcs.aspx
<select name="ctl00$ContentPlaceholder1$RadMultiSelect1" multiple="" id="ctl00_ContentPlaceholder1_RadMultiSelect1" class="RadMultiSelect RadMultiSelect_Silk" style="width:400px;">
<span id="ctl00_ContentPlaceholder1_RadMultiSelect1_WebServiceCDS" style="display:none;"></span><input id="ctl00_ContentPlaceholder1_RadMultiSelect1_ClientState" name="ctl00_ContentPlaceholder1_RadMultiSelect1_ClientState" type="hidden" />
</select><span id='ctl00_ContentPlaceholder1_RadMultiSelect1_WebServiceCDS' style='display:none'></span>
Found in the page source of the demo page (similar to how I implemented as well):
https://demos.telerik.com/aspnet-ajax/multiselect/virtualization/defaultcs.aspx
<select name="ctl00$ContentPlaceholder1$RadMultiSelect1" multiple="" id="ctl00_ContentPlaceholder1_RadMultiSelect1" class="RadMultiSelect RadMultiSelect_Silk" style="width:400px;">
<span id="ctl00_ContentPlaceholder1_RadMultiSelect1_WebServiceCDS" style="display:none;"></span><input id="ctl00_ContentPlaceholder1_RadMultiSelect1_ClientState" name="ctl00_ContentPlaceholder1_RadMultiSelect1_ClientState" type="hidden" />
</select><span id='ctl00_ContentPlaceholder1_RadMultiSelect1_WebServiceCDS' style='display:none'></span>
1 comment
ADMIN
Rumen
Posted on:
05 Sep 2023 10:34
Hi Hudson,
Can you please share what tool you used to verify this issue? If you check the produced DOM in DevTools source view you will find out that the browser has already stripped the duplicate span (since it is not allowed inside a select element) and only the external one continues to be available. Since there are no duplicate span elements, the content is validated fine with an accessibility checker like AXE, and the screen readers work fine with the produced content:
Regards,
Rumen
Progress Telerik
Stay tuned by visiting our public roadmap and feedback portal pages! Or perhaps, if you are new to our Telerik family, check out our getting started resources!