I'm using a UltraWebTree inside a UltraWebListBar and want them to score 100% what concerns to accessibility. All images have their respective 'alts', but when i see the source generated by the browser, i notice that the UltraWebTree as an "img tag" inserted by their own, that doesn't have the 'alt' attribute. Not having the 'alt' attribute, this fails the accessibility test:
<!--
Have you set Section508Compliant=True for the WebTree? This property is defaulted to false to minimize the HTML footprint of the control. Setting it to true should render an alt=" " for the images in question.
-Tony
Yes i have Section508Compliant = True, but still it render that img tag.
Any other ideia?
(thanks for answer)
I would file this one as "bug". I've spoken briefly to the development team and it looks like this is a bug. You'll need to contact our support group so that they can take your information and set you up to be automatically notified as the bug report makes its way through its lifecycle.
A workaround would be difficult. Your only option would be to use JavaScript to manually add the "Alt" attribute to each node. This can be done by walking the DOM tree, but I can't guarantee the screen readers will pick up the changes.
On a side note, the image in question is for display and positioning purposes only, and has no informational value. Accessibility validators obviously can't infer intent of an image so they flag any missing alt attribute, though this image really doesn't require any alternate text. The fix here will be to set the alt property of the image to "" on our side so that validators don't flag the image, and also screen readers know to skip the image as well.
Thanks!
This apparently is still an issue in 2008 volume 3 when the tree control has WebTreeTarget=Heirarchical
-Andrew Douglas
Hello Andrew,
I am trying to reproduce the issue (alt tags missing for 2008.3 UltraWebTree when WebTreeTarget = Hierarchical and Section508Compliant = True), but unfortunately without much success. As far as I can tell, all images have their corresponding alt property set (either to "(Expanded)" / "Collapsed") for expand / collapse image to alt = "" for node images.
Am I missing something? Can you please paste your ASPX tree declaration so I can reproduce that?
Thanks for looking into it. This was from a page that was converted from an old version of infragistics/.net so that might be a contributing factor but I don't know what other settings would be needed to get 508 compliant output. Hope this helps!
<ignav:ultrawebtree id="tvwRecruitment" tabIndex="11" Width="163px" runat="server" AutoPostBack="False"
Font-Names="Arial" Font-Size="10pt" Section508Compliant="True" BrowserTarget="DownLevel" SingleBranchExpand="True"
WebTreeTarget="HierarchicalTree" Indentation="10" FileFlags="StylesOnly" Visible="False">
<autopostbackflags nodechanged="True" />
<Nodes>
<ignav:Node TargetUrl="" TagString="/Staffing/Vacancy/Vacancy.aspx" Text="Position Information"></ignav:Node>
<ignav:Node TagString="/Staffing/Vacancy/VacancyAssessment.aspx" Text="Assessment Information"></ignav:Node>
<ignav:Node TargetUrl="" TagString="/Staffing/Vacancy/Documentation.aspx" Text="Supporting Documents"></ignav:Node>
<ignav:Node TargetUrl="" TagString="/Staffing/Vacancy/VacancyCategory.aspx" Text="Categories"></ignav:Node>
</Nodes>
<SelectedNodeStyle ForeColor="White" BackColor="Navy"></SelectedNodeStyle>
<NodePaddings Bottom="1px" Top="1px"></NodePaddings>
<Padding Top="1px"></Padding>
<Levels>
<ignav:Level Index="0"></ignav:Level>
</Levels>
<ClientSideEvents NodeClick="ValidatedNodeClick" BeforeNodeSelectionChange="BeforeNodeClick"></ClientSideEvents>
</ignav:ultrawebtree>
Hello,
I started from your treeview ASPX setup and changed only the Visible property to True so that the treeview is displayed - then I ran the treeview output through Section 508 validator and the check passed successfully: Here is the validator I used and the HTML I got from your ASPX declaration (I am using version 2008.3):
http://www.section508.info/
Maybe the best way is to isolate a small subset of your project reproducing the issue and sent it directly to our official Developer Support department -
http://ko.infragistics.com/Support/#Overview