You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current design of AriaNotify, as outlined in the spec PR and the explainer, includes a priority, which takes on values of none or important.
These map closely to the aria-live values of polite and assertive. Do we want the naming to closely align with these, or do we like that this diverges to help authors in better distinguishing these two features?
My proposal is to keep the naming separate given that polite and assertive may imply certain assumptions surrounding interrupt, which is a separate property in the ariaNotify API.
The text was updated successfully, but these errors were encountered:
I like @scottaohara's suggestion from today's meeting of high and low… because none seems more like the aria-live="off" value than aria-live="polite"... (Thanks for raising this @alisonmaher!)
Thanks @scottaohara and @cookiecrook for raising the potential confusion with aria-live="off". I, too, like the suggestion for high and low.
I'll leave this issue open for a bit longer in case other opinions come through, but in lieu of other comments, I'll get the explainer updated to reflect the updated naming and close this issue out.
The current design of AriaNotify, as outlined in the spec PR and the explainer, includes a
priority
, which takes on values ofnone
orimportant
.These map closely to the
aria-live
values ofpolite
andassertive
. Do we want the naming to closely align with these, or do we like that this diverges to help authors in better distinguishing these two features?My proposal is to keep the naming separate given that
polite
andassertive
may imply certain assumptions surroundinginterrupt
, which is a separate property in theariaNotify
API.The text was updated successfully, but these errors were encountered: