- Issue created by @rkoller
For a few accent colors the button labels have a too low color contrast against the background of primary buttons to meet SC1.4.3.
Secondary buttons instead consist of just a button border and a button label, they don’t have any background color. In consequence, the border color has to meet SC1.4.11 while the button label has to meet SC1.4.3 instead. In addition to accent colors the secondary buttons also use --gin-color-danger in a few contexts.
There are several occasions in light and dark mode where the accent and or the danger color don’t meet SC1.4.3 for secondary buttons (See the table in https://docs.google.com/spreadsheets/d/1won35PxhRFexJYE8FmZ4DCNTo7xEAxC8... or primary_secondary_button.xlsx.zip for more details). In Forced Colors mode there is also no way to distinguish between a primary and a secondary button, the two look identical - both are input elements.
In some contexts secondary buttons are link elements, in this case they have a higher visual affordance than the primary save button.
That illustrates the point that ideally buttons should be buttons, which would simplify things for Force Colors mode - probably worth a follow up issue for Core in general.
Discussed and iterated on the issue with @mgifford, @the_g_bomb, @katannshaw, and @drupa11y
admin/structure/views/view/content. For testing the issue in Forced Colors mode make sure that you’ve switched to dark mode before.admin/content for micro copy like author names and node titles.--gin-color-button-text.Active
4.0
User interface
It affects the ability of people with disabilities or special needs (such as blindness or color-blindness) to use Drupal.