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] Is ariaNotify the best name for the new notification API? #2332

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

Comments

@alisonmaher
Copy link

alisonmaher commented Sep 17, 2024

The topic around naming of the ariaNoify API, as noted in the spec PR and the explainer, has been raised in the past. The reasoning with the push back is that the API is not really an ARIA property, so should the name be tied to ARIA or something else?

Opening this issue to discuss if there are other ideas for naming, or if the group is happy to stick with ariaNoify.

@alisonmaher
Copy link
Author

This was discussed at TPAC with the relevant minutes quoted below:

keithamus: the other thing is naming, I think we discussed notificationId, we can change. I think everyone is happy with the name ariaNotify, should we litigate priority?

jcraig: I don't think this needs to have aria, maybe accessibilityNotify

Jamie: accNotify?

aaronlev: I like ariaNotify, everyone knows it's related to accessibility. No one knows what AT is

jcraig: I like accessibilityNotify, it's longer to type

smockle: is it an accessibiltiy only feature, I coudl see someone who wants to use ear-cons who's not an AT user

Jamie: I think it should be aria, by virtue of it being a prefix like everything else. It's just simpler

Matt_King: no matter how broad the use is, it's still accessibility

cyns: and if I were making a setting in the OS, I'd put it in the a11y settings

jcraig: I think Leonie mentioned a feature where having air pods in and getting a text message, you get it spoken to you. I can see a point to having a broader use case

00:42:07 [jcraig]
s/Leonie mentioned a feature/Leonie mentioned she'd just learned of the feature/

jamesn: WE ARE DONE

sarah: risk with making the use case broader is that it stops working as well , better to keep it accessibility specific

Given the above, I think we had converged on keeping the name accessibility specific. There were some suggestions around potentially accessibilityNotify or ATNotify. However, given the arguments for the name ariaNotify by @aleventhal and @jcsteh, my proposal will be to keep the name the same, and close this issue as no change.

@aleventhal
Copy link
Contributor

I prefer the current name. ARIA doesn't only have to mean aria-foo attributes. ARIA stands for Accessible Rich Internet Applications, which is where authors will want to use this. ARIA is like a brand for authors implementing that.

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

No branches or pull requests

2 participants