Skip to content

A11Y : fix issues due to 4.1.0 (Multiple Select2)#24833

Draft
f2cmb wants to merge 4 commits into
glpi-project:mainfrom
f2cmb:a11y/dropdowns/select2-4.1-baseline
Draft

A11Y : fix issues due to 4.1.0 (Multiple Select2)#24833
f2cmb wants to merge 4 commits into
glpi-project:mainfrom
f2cmb:a11y/dropdowns/select2-4.1-baseline

Conversation

@f2cmb

@f2cmb f2cmb commented Jul 10, 2026

Copy link
Copy Markdown
Contributor
  • I have read the CONTRIBUTING document.
  • I have performed a self-review of my code.
  • I have added tests that prove my fix is effective or that my feature works.

Description

Finishes the 4.1.0 bump from #24438. Kept because the chip's remove control is now a real <button aria-label="Remove item"> (keyboard/screen-reader reachable) instead of a decorative <span>. The raw bump broke our overrides, so I adapted the SCSS to the new chip layout: padding-left to stop the × overlapping the text, margin-left restored so the first chip isn't glued to the left edge, styled the search field (now a <textarea>), and renamed the removed containerCssClass option to selectionCssClass.

It's one global rule, no per-screen special-casing. Checked live on Forms, ITIL, Assets and Config: renders as before, minus the overlap. New dropdown_a11y.spec.ts locks the accessible button (fails on 4.0.13, passes on 4.1.0).

Screenshots :

Capture d’écran 2026-07-10 à 13 19 14 Capture d’écran 2026-07-10 à 13 19 36

@f2cmb f2cmb changed the title A11Y : fix issues due to 4.1.0 A11Y : fix issues due to 4.1.0 (Multiple Select2) Jul 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant