mdn/content

Popover API needs Accessibility Info

Open

#37,465 opened on Jan 1, 2025

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Markdown (22,427 forks)batch import
Content:WebAPIhelp wanted

Repository metrics

Stars
 (8,900 stars)
PR merge metrics
 (Avg merge 7d 3h) (147 merged PRs in 30d)

Description

MDN URL

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

What specific section or headline is this issue about?

No response

What information was incorrect, unhelpful, or incomplete?

There was no mention of accessibility semantics or how popovers are exposed to screen readers

What did you expect to see?

  1. How popovertarget / popover are exposed to screen readers
  2. Do developers still need to use aria-controls/aria-haspopup on the marked button
  3. Do developers still need to apply an aria-role to the element with the popup attribute

Do you have any supporting links, references, or citations?

No response

Do you have anything more you want to share?

No response

MDN metadata

Contributor guide

Research direction
Research the accessibility semantics of the Popover API and document how screen readers expose popover targets and popover elements, including whether ARIA attributes like aria controls, aria haspopup, and roles are needed.
Tech stack
html
Domain
frontend
Issue type
Documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
HTMLaccessibility
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80