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.

Sign up for GitHub

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

Jump to bottom

Consider ariaNotify being named a more general accessibility notification in HTML/DOM rather than an ARIA-specific mixin in the ARIA spec #2399

Open
cookiecrook opened this issue Dec 12, 2024 · 2 comments
Open

Consider ariaNotify being named a more general accessibility notification in HTML/DOM rather than an ARIA-specific mixin in the ARIA spec #2399

cookiecrook opened this issue Dec 12, 2024 · 2 comments
Assignees
@smockle

Comments

@cookiecrook
Copy link
Contributor

cookiecrook commented Dec 12, 2024 •
edited
Loading

I've mentioned this elsewhere, but I have two related naming/location concerns for ariaNotify

IMO, the concept of accessibility announcements is not limited to ARIA... So

  1. It should not be named "aria". I recall we suggested accessibilityNotify in various meetings.
  2. It should land in one of the mainstream specs, probably HTML.
@cookiecrook
Copy link
Contributor Author

Related

@cookiecrook cookiecrook changed the title Consider ariaNotify being a general accessibility notification in HTML/DOM rather than a mixin in the ARIA spec Consider ariaNotify being named a more general accessibility notification in HTML/DOM rather than an ARIA-specific mixin in the ARIA spec Dec 12, 2024
@smockle
Copy link
Contributor

smockle commented Dec 19, 2024

It should not be named "aria". I recall we suggested accessibilityNotify in various meetings.

#2332 is a related issue; it links to—and includes excerpts from—previous discussions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@smockle smockle

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@cookiecrook @smockle