Contrast themes – Buttons appear differently depending on whether they use `a` or `button` element
See original GitHub issueIssue Summary
Our styled buttons are meant to look the same whether they use an a
element or a button
element (normal mode screenshot on left). However, when using a forced-colors mode (like Windows High Contrast Mode), they appear differently (Chrome-emulated forced-colors mode screenshot on the right).
normal | high-contrast |
---|---|
Proposed Solution
We should add some styling in forced-colors mode to give all button.button
s the same text and border color that a.button
s get by default.
Issue Analytics
- State:
- Created a year ago
- Comments:12 (12 by maintainers)
Top Results From Across the Web
The Button element - HTML: HyperText Markup Language
The <button> HTML element is an interactive element activated by a user with a mouse, keyboard, finger, voice command, or other assistive ...
Read more >A Complete Guide to Links and Buttons
Our complete guide to links, buttons, and button-like inputs in HTML, CSS, and JavaScript.
Read more >Contrast themes - Windows apps
Contrast themes use a small palette of colors (with a contrast ratio of at least 7:1) to help make elements in the UI...
Read more >CSS Button Style – Hover, Color, and Background
Another thing to make sure of is that there is enough contrast between the button's background color and text color. This helps make...
Read more >Building a button component - web.dev
In this post I want to share my thoughts on how to build a color-adaptive, responsive, and accessible <button> element.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@albinazs you can go for this without checking with anyone else – but note since you’ve also claimed #8659, it’d be nice for you to either finish that one, or comment there that you no longer intend to work on it. We can’t let people claim all the issues 😛
@albinazs let’s go with ButtonTexr - great solution. Let’s get a PR up and we can move ahead with this.