POLICY: A non-javascript fallback is not required for new features provided that WCAG 2 AAA is met

The policy under discussion is this:

When developing new features for Moodle (core or plugins):

1. Use progressive enhancement wherever you can, with well-marked-up HTML structures and Javascript and AJAX that enhances this.
2. However, if you have no choice but to make an interface that only works with Javascript enabled, then you must be able to prove that your interface conforms to WCAG 2.0 AAA (ARIA etc). There is no need to craft an alternative interface for those not using JS.