mdn / mdn/browser-compat-data

api.Document.ariaNotify - Firefox should also be marked as partial

Open
#29,610 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

acd browser:multiple data:api p3 platform limitation
Dominant language
JSON
Stars
5.8k
Forks
2.6k
Avg merge
1d 21h
Merged PRs (30d)
186

Description

What type of issue is this?

Incorrect support data (example: BrowserX says "86" but support was added in "40")

What information was incorrect, unhelpful, or incomplete?

Chromium browsers are marked as partially supporting the document.ariaNotify (and element.ariaNotify) methods on macOS.
See https://github.com/mdn/browser-compat-data/blob/7bb620de9bd19120cdd7dfa87b56b8b3a6347bed/api/Document.json#L778

From our testing, Voice Over had trouble reliably reading these notifications, and could get interrupted by user actions.

Firefox is marked as fully supporting the APIs, even though, under the hood, it very likely uses the same macOS API.

So, it would seem fair to:

  • Either have both Chromium and Firefox be marked as partial, for the same reasons.
  • Or, have them both marked as fully supported, if we decide that the current support is "good enough".

@janewman said he was doing some testing here. Please let us know if you find something that could help make a decision.

What browsers does this problem apply to, if applicable?

No response

What did you expect to see?

Similar support data, if both browser engines indeed use the same underlying APIs.

Did you test this? If so, how?

Not yet. To be updated when/if we find relevant test results.

Can you link to any release notes, bugs, pull requests, or MDN pages related to this?

No response

Do you have anything more you want to share?

No response

MDN URL

https://developer.mozilla.org/en-US/docs/Web/API/Document/ariaNotify

MDN metadata
MDN page report details
  • Query: api.Document.ariaNotify
  • Report started: 2026-05-05T21:31:18.785Z

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with api/Document.json around line 778 and compare the Chromium and Firefox entries for Document.ariaNotify; also inspect the related element.ariaNotify data mentioned in the issue. Resolve whether the macOS VoiceOver behavior warrants partial support for both engines or full support for both, then update the support data to match the agreed evidence.

Written by the indexing model from the issue text.

Assessment

Tech stack
json
Domain
documentation, web-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.