Add ng-aria binding

[Downchuck]

ARIA is a firm W3C standard for rich internet applications. An ng-aria binding would both encourage app authors to use ARIA when suitable and make it easy. Because of the role of ARIA with UI, it is appropriate to have this as a core AngularJS directive.

Example: ng-aria="{expanded: isOpen}"

This would toggle the attribute aria-expanded to the string true/false on the element.

[caitp]

sounds like a use-case for #4269

But that sounds like it would make a great third party module

[albell]

+1

[nosideeffects]

+1

[pkozlowski-opensource]

One thing we could (easily?) do, thought, is to toggle aria visible attributes inside ng-show / ng-hide.

[arbus]

I have an implementation of this as a separate module that covers most of the common aria bindings here.

I can create a PR for this if there is an interest having aria bindings as part of the core.

[btford]

I am interested in this.

[arbus]

@btford, should this be something that is automatically hooked into directives like ngShow and ngHide and then configured or maybe developed as a separate module the way ngRoute and ngAnimate are?

[marcysutton]

+3. one for me, and two for my homies.

[btford]

@arbus Implementation-wise, I'm kind of torn.

• I think anyone using Angular should have sane a11y by default.
• I think modules should be separated, so someone who wants more fine-grained control over a11y can use their own implementation and not have the bytes for Angular's default sitting around.

I think we're better off having a separate repo/module for this so that ARIA support doesn't block the 1.3 release, and so that we can iterate on and release better ARIA support independently of Angular's release cycle. I do think this is important enough to be maintained by angular-core.

[Downchuck]

JQuery-UI went the accessible by default route. It worked out well, but
jQuery did not pick up on adding a .aria() method helper, and I think in
the long run that's meant that most module developers are unaware of it.

-Charles

On Thursday, July 24, 2014, Brian Ford notifications@github.com wrote:

@arbus https://github.com/arbus Implementation-wise, I'm kind of torn.

• I think anyone using Angular should have sane a11y by default.
• I think modules should be separated, so someone who wants more
  fine-grained control over a11y can use their own implementation and not
  have the bytes for Angular's default sitting around.

I think we're better off having a separate repo/module for this so that
ARIA support doesn't block the 1.3 release, and so that we can iterate on
and release better ARIA support independently of Angular's release cycle. I
do think this is important enough to be maintained by angular-core.

—
Reply to this email directly or view it on GitHub
#5486 (comment).