I'm working on some 508 compliance tasks and four of my tasks deal with the UltraWebGrids having three (two are similar, so combined) issues:
1. Not accessible with via the keyboard - You can't tab to the grid unless you have a link in the grid, and even then, you're only on the link, you can't select different cells.
2. Left arrow does not collapse record, Right arrow does not expand record - This is something they wish to have that is like Windows Explorer, how when you click on a folder, using the left and right arrows will collapse and expand the folder.
Now, I'm explained to them that the Left and Right arrow issue may end up being different keys, but I'm unable to find out what keys are used to open a selected row. Left and Right arrows currently, if you've clicked in the grid, move you through the cells, but never to the cell containing the expand/collapse image.
The Section508Complaint flag for the grids are set to true. But there is one thing I did notice.
In Mozilla Firefox 4.0 and Internet Explorer 8 (and probably older versions) when I tab the screen it goes right past the expand/collapse images. However, in Chrome 11, it tabs right to them. When I investigated the source through the browsers, I noticed two differences.
1. Mozilla and Internet Explorer use a <th> cell for it (the rest in the row are <td>) while Chrome uses all <td> for the row.
2. Mozilla and Internet Explorer simply put an onclick in the image while Chrome wraps the image in an anchor tag with the javascript in the href.
We wish Mozilla and Internet Explorer did it like Chrome does, because Chrome still has many issues with the Infragistics controls we use. We don't have the luxury of using another grid as it's too time consuming and we have a deadline coming up. If anyone can give me another option of how to access the table and especially what keys to use to expand/collapse a row, I'd be truly appreciative.
Also, this is one suggestion we have, but we really are trying to not have to go this far. We think we could use Javascript to read the DOM, pull the onclick from the images, wrap the image with an anchor tag (as Chrome does it) and change the <th> to <td> (InFocus reports many errors saying that the headers and cells aren't appropriately associated).
Sorry for the long thread, but this is a major issue. Thanks.
My apologies but I think I placed this thread in the wrong forum. This should be placed in the ASP.Net forum. Could a mod or employee please move this there? Thank you very much.
Hello jbrunkowski, All controls and components are compliant with the accessibility rules. http://es.infragistics.com/resources/accessibility.aspx#AccessibilitySection508 http://help.infragistics.com/NetAdvantage/ASPNET/2011.1/CLR4.0/?page=Web_Accessibility_Overview.html
If you have that something is not working correctly I can open support ticket for you. There you can send me a sample which we can investigate and log a development issue if is needed.
Please let me know If you want to open a support ticket
Hello Jason,
see these links: Accessibility Overview , WebGrid Accessibility Compliance
Hope this helps
Also, and I could be looking in the wrong area, but nowhwere on the chart you provided do I see the UltraWebGrid. I know that in recent times it's been suggested to us that we need to upgrade, but with as deeply rooted and as often as we've used them, it isn't an easy task. Is there a 508 compliance chart for the UltraWebGrid? Thanks.
I have since opened a ticket (with no response to date). I just wanted to put this on the forum to see whom would get back to me first. Technically my 508 compliance tasks need to be completed by this Friday or we'll just chalk them up to "Infragistics issues" which isn't a good thing. Thank you for your response and if you could have them take a look at my ticket (let me know if you need the link) then that'd be awesome. Thanks.