search

w3c / aria

Accessible Rich Internet Applications (WAI-ARIA)
https://w3c.github.io/aria/
Other
654 stars 125 forks source link

[AriaNotify] Is ariaNotify the best name for the new notification API? #2332

Closed alisonmaher closed 1 week ago

alisonmaher commented 2 months ago

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 commented 1 month ago

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 commented 1 month ago

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.

alisonmaher commented 1 week ago

As per today's meeting https://www.w3.org/2024/11/14-aria-minutes.html

alisonmaher: this revisits TPAC discussion. … we had discussed the name. … jamie and aaron had good points on keeping the name … now would like to move this forward

spectranaut_: there do not seem to be objections, so this seems to be a go.

alisonmaher: great!

closing this out issue out as no fix!