Hi all,
Does anyone know of a solution to the following accessibility issues, all of which are failing the WCAG2.0 AA compliancy standards...?
Examples...
1. RadGrid Pager elements - missing "title" attribute
The PagerStyle "NextPrevNumericAndAdvanced" produces (amongst other stuff!) the following two text input fields...
- GoToPageTextBox
- ChangePageSizeTextbox
These input fields do not have the "title" attribute by default, and it's not possible for me to relate them to separate <LABEL> tags due to design considerations.
Is there any way of specifying a "title" attribute for these fields? I notice all the other links in the Pager enable this with the "xxxToolTip" attributes, but I can't find a similar attribute for the GoToPage and ChangePageSize inputs.
2. RadDatePicker (and others) - presentation tables include "summary" attribute.
Many of the controls produce tables to lay out the various components, but these layout tables include a "summary" attribute which the AA guidelines stipulate must either be not included, or contain a null value.
For example...
- RadDatePicker produces...
- RadComboBox produces...
So, is there any way to easily customise the "summary" attribute?
Also while I'm here... the ComboBox table example above (correctly) uses "style" attribute to control the table's cellspacing and border, whereas the DatePicker uses "cellspacing=0" and "border=0", which are not recommended.
Thanks in advance,
Jon
(Note: Sorry if this has already been answered elsewhere; I've searched the forums but can't find the answer if it exists!)
Does anyone know of a solution to the following accessibility issues, all of which are failing the WCAG2.0 AA compliancy standards...?
Examples...
1. RadGrid Pager elements - missing "title" attribute
The PagerStyle "NextPrevNumericAndAdvanced" produces (amongst other stuff!) the following two text input fields...
- GoToPageTextBox
- ChangePageSizeTextbox
These input fields do not have the "title" attribute by default, and it's not possible for me to relate them to separate <LABEL> tags due to design considerations.
Is there any way of specifying a "title" attribute for these fields? I notice all the other links in the Pager enable this with the "xxxToolTip" attributes, but I can't find a similar attribute for the GoToPage and ChangePageSize inputs.
2. RadDatePicker (and others) - presentation tables include "summary" attribute.
Many of the controls produce tables to lay out the various components, but these layout tables include a "summary" attribute which the AA guidelines stipulate must either be not included, or contain a null value.
For example...
- RadDatePicker produces...
<table cellspacing="0" summary="title and navigation" border="0">
- RadComboBox produces...
<table summary="combobox" style="border-width:0;border-collapse:collapse;">So, is there any way to easily customise the "summary" attribute?
Also while I'm here... the ComboBox table example above (correctly) uses "style" attribute to control the table's cellspacing and border, whereas the DatePicker uses "cellspacing=0" and "border=0", which are not recommended.
Thanks in advance,
Jon
(Note: Sorry if this has already been answered elsewhere; I've searched the forums but can't find the answer if it exists!)
3 Answers, 1 is accepted
0
Jonathan
Top achievements
Rank 1
Rank 1
answered on 24 Aug 2012, 01:29 AM
(bumped...)
Hilarious...
Instead of providing a solution, I notice you've simply removed the "AA-compliant" claims from your DatePicker & Grid controls' accessibility pages, and added the word "mostly" to your claim of AA-compliancy on your home page!
Well I suppose your advertising is now accurate, but of absolutely no use to anyone who purchased the controls when they were being advertised as "AA Compliant". Very professional, Telerik!
Unimpressed.
:-(
Hilarious...
Instead of providing a solution, I notice you've simply removed the "AA-compliant" claims from your DatePicker & Grid controls' accessibility pages, and added the word "mostly" to your claim of AA-compliancy on your home page!
Well I suppose your advertising is now accurate, but of absolutely no use to anyone who purchased the controls when they were being advertised as "AA Compliant". Very professional, Telerik!
Unimpressed.
:-(
0
Hi, Jonathan.
Those are some very interesting questions. Currently, you can't really fix them, apart from hooking into the rendering on the server and overriding the end design.
That of course implies that you may need to provide additional styling and in short is not really a solution.
Another approach is to be not compliant, but add / remove features on the fly with JavaScript. Regarding the RadComboBox <table> "summary" attribute - you can easily remove it. You could follow the approach described in this forum post.
As for the AA compliance as a general, we have not given up on being compliant. However that requires some rewriting of the controls and we are doing it gradually.
For the upcoming Q3 release, the ComboBox will be the first of the input control to have improved rendering so it can be compliant. If that goes well (read received positively and no bug reports), the same approach will be applied to other input control, such as the DatePicker and so on.
The grid is going to be tough to conform if possible at all. But when we know what can be done, rest assure will improve the control and definitely post about it, as it will be huge improvement in terms of accessibility and compliance.
Regards,
Ivan Zhekov
the Telerik team
Those are some very interesting questions. Currently, you can't really fix them, apart from hooking into the rendering on the server and overriding the end design.
That of course implies that you may need to provide additional styling and in short is not really a solution.
Another approach is to be not compliant, but add / remove features on the fly with JavaScript. Regarding the RadComboBox <table> "summary" attribute - you can easily remove it. You could follow the approach described in this forum post.
As for the AA compliance as a general, we have not given up on being compliant. However that requires some rewriting of the controls and we are doing it gradually.
For the upcoming Q3 release, the ComboBox will be the first of the input control to have improved rendering so it can be compliant. If that goes well (read received positively and no bug reports), the same approach will be applied to other input control, such as the DatePicker and so on.
The grid is going to be tough to conform if possible at all. But when we know what can be done, rest assure will improve the control and definitely post about it, as it will be huge improvement in terms of accessibility and compliance.
Regards,
Ivan Zhekov
the Telerik team
If you want to get updates on new releases, tips and tricks and sneak peeks at our product labs directly from the developers working on the RadControls for ASP.NET AJAX, subscribe to their blog feed now.
0
Jonathan
Top achievements
Rank 1
Rank 1
answered on 27 Aug 2012, 12:42 AM
G'day Ivan,
Thanks for the response.
Ok, I can live with the JavaScript solution to all of these problems if there's no other option. I was just thrown after having provided my boss with work estimates on the assumption that all the 3rd-party controls used in our project were already AA-compliant.
By the way, your RadGrid advertising still says: "RadGrid for ASP.NET AJAX is level AA accessible (in compliance with the W3C Web Accessibility Guidelines 2.0)." on the following pages...
http://www.telerik.com/products/aspnet-ajax/getting-started/tech-sheets/accessibility-support.aspx
http://demos.telerik.com/aspnet-ajax/grid/examples/generalfeatures/accessibility/defaultcs.aspx
Jon.
Thanks for the response.
Ok, I can live with the JavaScript solution to all of these problems if there's no other option. I was just thrown after having provided my boss with work estimates on the assumption that all the 3rd-party controls used in our project were already AA-compliant.
By the way, your RadGrid advertising still says: "RadGrid for ASP.NET AJAX is level AA accessible (in compliance with the W3C Web Accessibility Guidelines 2.0)." on the following pages...
http://www.telerik.com/products/aspnet-ajax/getting-started/tech-sheets/accessibility-support.aspx
http://demos.telerik.com/aspnet-ajax/grid/examples/generalfeatures/accessibility/defaultcs.aspx
Jon.