WCAG Compliance a little elusive

[Naeem]

hi,

I have a question but first a statement of concern.

There are claims that all feature of the RadGrid are WCAG 1.0 A compliant.  However, the first thing I would like to raise as there have been forum posts that caveat this by saying you can't have Static headers and enableScrolling = true.  Now admittedly, the forum post that caveats this is quite old but I suspect this is still the case.  I am concerned that the claim that all features are compliant is entirely misleading.  Now on to my question:

WCAG 1.0 Checkpoint 6.3 states "Ensure that pages are usable when scripts, applets, or other programmatic objects are turned off or not supported. If this is not possible, provide equivalent information on an alternative accessible page.".  My question is how is this supported by the RadGrid if paging is on?  what also needs to be set to ensure that javascript postbacks are not required?

Thanks

[Dimo]

Hello Naeem,

Can you please specify where do we claim that "all features" are WCAG compliant? Maybe there has been some misunderstanding or we need to correct some texts on our site?

Naturally, some rich (interactive) functionalities cannot be supported with Javascript turned off, i.e. they are not accessible. In such cases it is more important to ensure that the control markup and content are accessible, and they are. For example, a feature such as column resizing is not accessible for screen readers, but it doesn't have to be anyway. The same applies to static headers - a blind user doesn't need static headers.

Here are a couple of demos, which demonstrate paging with no need for Javascript:

http://demos.telerik.com/aspnet-ajax/grid/examples/programming/seopaging/defaultcs.aspx

http://demos.telerik.com/aspnet-ajax/grid/examples/generalfeatures/accessibility/defaultcs.aspx


Best wishes,
Dimo
the Telerik team

Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.

[Naeem]

Hi Dimo,

Thanks for the prompt response.  It was a forum post from a Telerik Admin that claimed the "all" support.  Looking back it was actually for the ASP forum not the AJAX one.  See http://www.telerik.com/community/forums/aspnet/grid/grid-and-accessibility-508.aspx

Thanks for you help and I'll continue with my investigations.

Can I make a suggestion and perhaps request that the table in http://www.telerik.com/products/aspnet-ajax/resources/accessibility-support.aspx is caveated with a statement that all features may not be immemdiately WCAG compliant.

[Naeem]

Dimo,

Thanks for the Demos.  The examples are just the sort of thing I was looking for.  As we have to ensure WCAG AA complicance we have to try and avoid javascript postbacks and that is exactly what PagerStyle.EnableSEOPaging leads us towards.

Thanks again

Naeem

[Dimo]

Hello Naeem,

When you enable SEO paging, the pager buttons are rendered as hyperlinks with URLs with query string parameters. These hyperlinks trigger GET requests to the web server - these are neither postbacks, nor Javascript is involved in any way.

All the best,
Dimo
the Telerik team

Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.