Additional Accessibilty enhancements

[nschonni]

Related to gh-706
Fixes gh-230

• ARIA-Invalid works and is cleared properly on the resetForm() call
• Add aria-required tags to any of the data, static or class required elements.

---

@jzaefferer I'm not sure where I should be hooking in to have rules defined in code be hooked in before the first validation call. Ex:

    form.validate({
        rules: {
            ariaRequiredDynamic: "required"
        }
    });

[jzaefferer]

I've changed this since I primarly run tests (and demos for manual testing) in the browser, and I want the concat task to run asap.

[nschonni]

I can revert that, but I found it useful for the immediate feedback from the watch task as I was developing.

[jzaefferer]

I can see it being useful when you have more of a CLI focus while developing.

Maybe we can have multiple watch targets? For example, I could run "grunt watch:concat" to only get the concatenation?

[jzaefferer]

Thanks for this. It's great to finally have some progress in this area. I've left a few comments above.

[jzaefferer]

This seems to have been lost in another comment, I wrote: "The problem is then any elements that are added later, which the plugin supports thanks to event delegation. Back when it didn't have that, there was a refresh method. I hope we can avoid having to add that back..."

Any ideas how to address that?

[nschonni]

I've fixed the commenting and quoting lines.

---

This seems to have been lost in another comment, I wrote: "The problem is then any elements that are added later, which the plugin supports thanks to event delegation. Back when it didn't have that, there was a refresh method. I hope we can avoid having to add that back..."

Any ideas how to address that?

Nope, that one stumped me. I tried plugging in the aria-required, but I couldn't find the correct spot to leverage the rules defined in settings. Reading http://www.w3.org/TR/WCAG-TECHS/ARIA2.html again, I think that flagging them required after the fact is still "OK", just less than ideal.
/cc @pjackson28 @LaurentGoderre

[nschonni]

@jzaefferer should this get landed now and address the dynamic element issues later?

[fagerli]

@jzaefferer Any chance of the aria-invalid part being included any time soon? Would be much appreciated!

[jzaefferer]

I've landed this in master, after a rebase. Unit tests look good in Chrome. After the rebase, the same 14 tests failed in IE8 as on master, so that should be fine as well. I'm not too happy about including something that isn't quite done, yet, but since I can't spend any time on this plugin these days, I hope its better to land as-is.

Thanks again @nschonni for your contributions. I appreciate those a lot!

[nschonni]

No problem @jzaefferer I still owe you a Skype 😄