[AriaNotify] Naming for the priority property

[alisonmaher]

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.

[alisonmaher]

Adding to the agenda to see if anyone has any objection to the current naming for priority.

[cookiecrook]

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!)

[spectranaut]

Discussed in today's meeting: https://www.w3.org/2024/12/12-aria-minutes#6c78

[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.

[jnurthen]

How about
"high" and "normal"
or
"high" and "default"?

[alisonmaher]

@jnurthen those seem reasonable to me, as well. I kind of like the idea of using normal since I have at least seen that used in other specs, like grid.

@cookiecrook @scottaohara or others, any concerns with high and normal instead of high and low?