angular / angular/components

bug(mat-button-toggle-group): Accessibility issue of WCAG non-text contrast and WCAG use of color

Aperta
#27,748 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub
area: material/button-toggle P3
Lingua principale
TypeScript
Stelle
25k
Fork
6.8k
Merge medio
1g 8h
PR unite (30g)
91

Descrizione

### Is this a regression?

- [ ] Yes, this behavior used to work in the previous version

### The previous version in which this bug was not present was

_No response_

### Description

This component fails color contrast in its selected state, and also fails the requirement that color should not be the only visual indicator to convey that an item is in a selected state.

This issue is applicable specifically to mat-button-toggle-group where multiple options are exposed. Single toggle button instances are meeting accessibility requirements because they have a change in text or icon in addition to color.

See WCAG context below:

WCAG [Non-text contrast](https://www.w3.org/WAI/WCAG21/Understanding/non-text-contrast): “This success criterion does not require that controls have a visual boundary indicating the hit area, but if the visual indicator of the control is the only way to identify the control, then that indicator must have sufficient contrast.”
This success criterion is met, but is only applicable to the default (un-selected) state.

WCAG [Non-text contrast](https://www.w3.org/WAI/WCAG21/Understanding/non-text-contrast): Also, any visual information necessary to indicate state, such as whether a component is selected or focused must also ensure that the information used to identify the control in that state has a minimum 3:1 contrast ratio.
This is not being met.

WCAG [Use of color](https://www.w3.org/WAI/WCAG21/Understanding/use-of-color): If content is conveyed through the use of colors that differ not only in their hue, but that also have a significant difference in lightness, then this counts as an additional visual distinction, as long as the difference in relative luminance between the colors leads to a contrast ratio of 3:1 or greater.
This implies that a design solution that meets 3:1 contrast is sufficient in meeting the “Use of Color” success criterion.

### Reproduction

This issue can be reproduced in the component demo and does not require StackBlitz: https://material.angular.io/components/button-toggle/overview

### Expected Behavior

The contrast ratio of the selected state must meet at least 3:1 to fulfill WCAG success criterion for non-text contrast and use of color.

### Actual Behavior

Currently the selected state of mat-button-toggle-group uses a fill color of #E0E0E0. On an #FFFFFF background, the contrast ratio is only 1.32:1.

### Environment

Angular/Material 16.2.1

Guida per i contributori

Apri la guida per i contributori

Direzione di ricerca

Inizia con la demo del componente mat-button-toggle-group all’indirizzo https://material.angular.io/components/button-toggle/overview e verifica lo stato selezionato rispetto ai colori segnalati, #E0E0E0 su #FFFFFF. Il payload non indica alcun file sorgente né alcun test; il lavoro è completato quando lo stato selezionato offre un rapporto di contrasto di almeno 3:1 e non si affida più solo al colore per comunicare la selezione.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Valutazione

Stack tecnologico
angular, typescript
Ambito
accessibility, frontend
Tipo di issue
Bug
Difficoltà
3/5
Tempo stimato
1-2 giorni
Stato di attività
Ferma
Chiarezza
Abbastanza chiara
Idoneità per principianti
42/100

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.