mdn / mdn/browser-compat-data

html.elements.optgroup - Incorrect `<optgroup>` support

Open
#21,663 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

acd browser:multiple data:html
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?

Neither Chromium, Firefox, nor WebKit support <optgroup> fully and have not for many years and all versions.

What browsers does this problem apply to, if applicable?

Chromium (Chrome, Edge 79+, Opera, Samsung Internet), Firefox, Safari

What did you expect to see?

Partial support for all browsers.

Except maybe Firefox on desktop which can keep "full support". Though care should be taken to identify when Firefox started supporting <optgroup> since I am wary it did so on day 1.

Did you test this? If so, how?

Yes, using https://adrianroselli.com/demos/splitting-within-selects/index.html.

Chrome 120 / Windows 11:

  • does not expose the <optgroup> within the accessibility tree.

Safari 17 / macOS 14.0:

  • does not expose the <optgroup> within the accessibility tree;
  • announces the <optgroup> as “dimmed” when using VoiceOver (likely a result of prior bullet);
  • has insufficient contrast (1.4:1), making the text essentially useless to low vision users.

Firefox 118 / Android 13:

  • announces the <optgroup> as “disabled” when using TalkBack (may be an issue in Firefox accessibility tree, but cannot inspect it);
  • has insufficient text contrast (2.9:1).

Safari 17 / iPadOS 17.0.3:

  • has insufficient text contrast.
Can you link to any release notes, bugs, pull requests, or MDN pages related to this?

Webkit:

Chromium:

Do you have anything more you want to share?

No response

MDN URL

https://developer.mozilla.org/en-US/docs/Web/HTML/Element/optgroup

MDN metadata
MDN page report details
  • Query: html.elements.optgroup
  • Report started: 2023-12-18T17:28:34.010Z

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 the MDN optgroup page and the linked WebKit and Chromium accessibility issues. Determine the appropriate partial-support ranges for Chromium, Firefox, and WebKit, including whether Firefox desktop should remain full support. Done means the browser-compatibility data reflects the documented behavior and historical support evidence.

Written by the indexing model from the issue text.

Assessment

Tech stack
html
Domain
accessibility, web-dev
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.