Improving aria-label warnings

[marcysutton]

When a button, checkbox, radio button or slider is missing alternative text, warnings are logged to the developer telling them about the problem and directing them to the live node requiring a fix.

Closes #342

[ThomasBurleson]

@marcysutton - as part of #340 [Refactor to use ngAria], we need to move these service methods to Utils and not use a custom $aria material service (since it conflicts). This also impacts #314.

[marcysutton]

Ok. I figured the service would just be renamed.

[ThomasBurleson]

If we want to use $log, then we need a service. So perhaps just renaming it $materialAria is a good start.

We could even inject the $aria service (from ngAria) and then extend() our own service with ngAria's features.

[marcysutton]

@ThomasBurleson any input on the timing issue mentioned above?

[ThomasBurleson]

@marcysutton - can I voip with you tomorrow AM after 11:00 AM CST?
We can discuss the timing issue and solution(s).

[marcysutton]

Adding TestUtil.mockRaf here causes the existing tests to fail. But without it, $materialAria.expect does not run.

[marcysutton]

@ajoslin @ThomasBurleson This causes an issue when there is more than one component of the same type on a page: $materialAria.expect only executes for the last instance. Need to figure out a way to delay expectAttribute from running but still execute for every component that needs it.

[ajoslin]

Ah. right.

Just do:

function expectAttribute() {
  $$rAF(function() {
    //expectAttribute logic
  });
}

[marcysutton]

Passing false for copyElementText will accommodate components requiring a warning for aria-label if the developer forgot, such as material-slider. Passing true will try to copy the element's text (or use the optional defaultValue, like in the case of material-dialog). I'm open to renaming this parameter to something that sounds more boolean (or refactoring).

[ajoslin]

We include ngAria as a dependency of ngMaterial itself now, so this is extraneous.

[ajoslin]

Merged via 3368c93.