-
Notifications
You must be signed in to change notification settings - Fork 27.5k
bug(ngAria): update aria-valuemin/max
when min
/max
change
#11770
Comments
As a result of thi fix, `ngMin/Max` also set `aria-valuemin/max` on "range"-shaped elements. Fixes angular#11770
@gkalpak ngAria already binds It's worth noting that ARIA generally isn't necessary on native inputs, only custom controls like Here is a sandbox where you can see ngAria in action, see the first "Test Slider" component, which has I don't necessarily think there is an action item right now, I just wanted you to be aware of what ngAria currently does and what it should/shouldn't do. :) |
@marcysutton, thx for the insight. Note, though, that my 2 points above are still valid (aka action items), since:
I just realized there is another issue (which #11774 does not address): |
Oh yes, you're totally right. Although your last point about To clear up what needs to happen (at least for me):
|
My item (1) was that
It seems that
Just to be clear, it should watch (rather observe) |
As a result of thi fix, `ngMin/Max` also set `aria-valuemin/max` on "range"-shaped elements. Fixes angular#11770
As a result of thi fix, `ngMin/Max` also set `aria-valuemin/max` on "range"-shaped elements. Fixes angular#11770 Closes angular#11774
Currently,
ngAria
checksattr.min/max
in a 200-priority directive's post-linking function and setsaria-valuemin
/aria-valuemax
accordingly.There are 2 issues with this approach:
ngMin
/ngMax
will also result inattr.min/max
being updated, but only afterngAria
has setaria-valuemin/max
. As a result,ngAria
is effectively not taking into accountngMin
/ngMax
(while I think it should).min
/max
change later on,aria-valuemin/max
are not updated, resulting in misleading info (accessibility loses 😢).Luckily, solving (2) will automatically fix (1) as well.
So, I believe that
ngAria
shouldattr.$observe
certain attributes and update aria values accordingly.This is probably true for other attributes besides
min
/max
(@marcy should know better).The text was updated successfully, but these errors were encountered: