Hello,
I've been trying to implement a treeview with checkboxes for a SharePoint 2010 custom web part. Just by using the built-in node template, this works without a hitch.
However, a core requirement of this web part is that it is to be fully compliant with the WCAG 2.0 AA standard. Out of the box, the only issue that appears is that the checkboxes do not have a label associated with them; a requirement for WCAG 2.0 A compliance. i've read all over the site that the treeview is WCAG A compliant, but whether that's version 1.0 or 2.0 of the WCAG standard varies based on the source.
I stumbled across a forum post from 2009 which mentions using a custom NodeTemplate to fix the compliancy issue (link is here). The issue is indeed resolved. However, the fix then breaks any client-side checkbox functionality (CheckChildNodes, OnClientNodeCheck, etc). The current solution that I'm using is server-side code; this also has the unfortunate side-effect of causing a postback upon ANY node being selected.
Has anyone been able to find a solution to this problem by using any form of client-side navigation that does not require a postback to function properly?
Thanks
I've been trying to implement a treeview with checkboxes for a SharePoint 2010 custom web part. Just by using the built-in node template, this works without a hitch.
However, a core requirement of this web part is that it is to be fully compliant with the WCAG 2.0 AA standard. Out of the box, the only issue that appears is that the checkboxes do not have a label associated with them; a requirement for WCAG 2.0 A compliance. i've read all over the site that the treeview is WCAG A compliant, but whether that's version 1.0 or 2.0 of the WCAG standard varies based on the source.
I stumbled across a forum post from 2009 which mentions using a custom NodeTemplate to fix the compliancy issue (link is here). The issue is indeed resolved. However, the fix then breaks any client-side checkbox functionality (CheckChildNodes, OnClientNodeCheck, etc). The current solution that I'm using is server-side code; this also has the unfortunate side-effect of causing a postback upon ANY node being selected.
Has anyone been able to find a solution to this problem by using any form of client-side navigation that does not require a postback to function properly?
Thanks
4 Answers, 1 is accepted
0
Ryan
Top achievements
Rank 1
Rank 1
answered on 09 Nov 2011, 09:01 PM
Since it's been 5 days since I posted this (and the reply that appears to be posted from the main view isn't actually visible to me), I'm going to go ahead and bump this thread.
0
Ryan
Top achievements
Rank 1
Rank 1
answered on 21 Nov 2011, 08:40 PM
I'm going to bump this again to see if anyone has a solution to this. I'm assuming that the hidden (to me) responses are just automatically generated...
0
Hi Ryan,
I am sending you a sample project that shows a way to handle these events using jQuery.
Hope this will be helpful.
Greetings,
Plamen Zdravkov
the Telerik team
I am sending you a sample project that shows a way to handle these events using jQuery.
Hope this will be helpful.
Greetings,
Plamen Zdravkov
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
Ryan
Top achievements
Rank 1
Rank 1
answered on 23 Nov 2011, 07:28 PM
That code checks all nodes, regardless of what node was checked by the user. If a user selects a child node, all of its siblings and all of the nodes higher in the hierarchy (and their child nodes) are also selected. It also does not unselect a node when it is already selected. It definitely puts me on the right track, so I'll see if I can get it working a bit better.