Ken Lassesen
Top achievements
Rank 2
Rank 2
Ken Lassesen
asked on 20 Feb 2010, 06:07 PM
This skin would do the best practises for color contrast etc for WCAG 2, Section 508 accessibility.
If possible, assigning to this skin would also disable any and all features that are questionable about passing a rigorouse 508 review by some one that got up on the wrong side of the bed after a horrible night.
For example:
If possible, assigning to this skin would also disable any and all features that are questionable about passing a rigorouse 508 review by some one that got up on the wrong side of the bed after a horrible night.
For example:
- Disables most if not all of Javascript functionality, animations, etc
The big win is simple: if someone develops a site and give the user the option to declare themself needing accessibility, the site is now skinned for accessibility and everything auto-adjusts. This would be a major win for cost-reduction in government and education sites, etc...
1 Answer, 1 is accepted
0
Hello Ken,
Creating skins that adhere to the WCAG rules about color contrast certainly is a good idea - and we highly value the readability of the skins - the Sitefinity skin has a great contrast (black on white).
Changing control properties based on the skin name, however, is not intuitive, and could be considered a bug if one were to create a skin with the same name, not to say if there are such skins already. There are properties like the AccessibilityMode property of RadComboBox that serve this purpose. And while at this topic - the ASP.NET WebForms has a big problem with disabled JavaScript - namely because all postbacks stop working.
All the best,
Alex Gyoshev
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.
Creating skins that adhere to the WCAG rules about color contrast certainly is a good idea - and we highly value the readability of the skins - the Sitefinity skin has a great contrast (black on white).
Changing control properties based on the skin name, however, is not intuitive, and could be considered a bug if one were to create a skin with the same name, not to say if there are such skins already. There are properties like the AccessibilityMode property of RadComboBox that serve this purpose. And while at this topic - the ASP.NET WebForms has a big problem with disabled JavaScript - namely because all postbacks stop working.
All the best,
Alex Gyoshev
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.