Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[AriaNotify] Naming for the priority property #2333

Open
alisonmaher opened this issue Sep 17, 2024 · 4 comments
Open

[AriaNotify] Naming for the priority property #2333

alisonmaher opened this issue Sep 17, 2024 · 4 comments
Labels

Comments

@alisonmaher
Copy link

alisonmaher commented Sep 17, 2024

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
Copy link
Author

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

@cookiecrook
Copy link
Contributor

cookiecrook commented Dec 12, 2024

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
Copy link
Contributor

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

@alisonmaher
Copy link
Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants