Web-Facing Change PSA: Minimum size of <option> within <select> dropdown

395 views
Skip to first unread message

Stephanie Zhang

unread,
Jun 4, 2024, 1:22:44 PMJun 4
to blin...@chromium.org
Contact emails
Specification
Design docs
Summary
The WCAG (accessibility guidelines) specify that the size of pointer inputs must be at least 24x24 CSS pixels. The <option> element within the <select> dropdown currently does not meet this height requirement.


Blink component
TAG review
None

TAG review status
Not applicable

Risks


Interoperability and Compatibility
Low risk. This update modifies the height of the <option> elements within the select popup to ensure WCAG standards are met. While this may lead to minor visual changes on websites, the overall impact remains minimal since it only alters the size of the popup and the height of each <option> element, without affecting the in-page controls.


Gecko: Shipped/Shipping The default size of the <option> element within the <select> dropdown exceeds 24x24 CSS pixels.

WebKit: No signal Filed bug https://bugs.webkit.org/show_bug.cgi?id=275079

Web developers: No signals

Other signals:

Ergonomics
None


Activation
None


Security
None


WebView application risks
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
None
(This question autogenerates the response “None” and the answer cannot be modified on Chrome Platform Status. To clarify, this change is considered low risk and carries the same compatibility risk for Android WebView applications as it does for other platforms)

Debuggability
None


Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, ChromeOS, Android, and Android WebView)?
Yes

Is this feature fully tested by web-platform-tests?
Yes


Flag name on chrome://flags
None

Finch feature name
SelectOptionAccessibilityTargetSize

Requires code in //chrome?
False

Tracking bug
Estimated milestones
Shipping on desktop 128
 
Shipping on Android 128
 
Shipping on WebView 128
 


Anticipated spec changes
Open questions about a feature may be a source of future web compat or interop issues. Please list open issues (e.g. links to known github issues in the project for the feature specification) whose resolution may introduce web compat/interop risk (e.g., changing to naming or structure of the API in a non-backward-compatible way).
None

Link to entry on the Chrome Platform Status
This intent message was generated by Chrome Platform Status.
 

Stephanie Zhang

unread,
Jun 10, 2024, 5:02:54 PMJun 10
to blink-dev, Stephanie Zhang
Reply all
Reply to author
Forward
0 new messages