Why do EPiServer sample templates use JavaScript that do not comply with WAI standards?

According to WAI guidelines, JavaScript should either be avoided or corresponding functionality should be available in an alternative way that does not use JavaScript. EPiServer's sample template set currently contains some JavaScript, which means that full template functionality cannot be attained with JavaScript disabled.
 
EPiServer customers have varying  needs and have their own individual requirements for a Web site's accessibility and functionality. This means that the customer's implementation partner determines how the customer's template set should be formed, how much of the sample template set can be used and how much must be customized. EPiServer could have two sample template sets; one set with full accessibility and another set that includes functionality that is requested by partners and customers even though it is not fully accessible, but this is not currently the case. EPiServer only has one sample template set, which results in a varying degree of accessibility.
 
EPiServer's sample template set is just that, a sample template set, and cannot currently be seen as "best practice" for accessibility. ElektroPost aspires to follow applicable standards in new product development and also gradually attend to other existing faults and weaknesses. EPiServer templates are based on ASP.NET, which means that it is often difficult to totally avoid JavaScript and other things that can cause accessibility problems, e.g. layout tables, as these form the basis of ASP.NET controls. ElektroPost will however continue to work with accessibility and hopefully the .NET platform will also be improved in the future in this respect.