Skip to content

Conversation

@njpanderson
Copy link
Contributor

Have checked the new contrast meets WCAG AA using the following tool:

http://webaim.org/resources/contrastchecker/

If there’s a better checker you guys all use, do let me know in the comments!

Have checked the new contrast meets WCAG AA using the following tool:

http://webaim.org/resources/contrastchecker/

If there’s a better checker you guys all use, do let me know in the comments!
@youknowriad youknowriad requested a review from jasmussen June 1, 2017 17:48
@aduth aduth added [Focus] Accessibility (a11y) Changes that impact accessibility and need corresponding review (e.g. markup changes). Design labels Jun 1, 2017
@jasmussen
Copy link
Contributor

This is what I see:

screen shot 2017-06-02 at 10 05 35

Nice, looks good, thanks for working on this!

I did notice that the dark gray hover color doesn't actually work — it's replaced by a $medium-blue-500 color. Which frankly is probably better as it matches the hover color for similar buttons. So that hover rule can probably be removed. Otherwise 🚢

The button already inherits the hover colour from .components-icon-button.
@njpanderson
Copy link
Contributor Author

Have removed the redundant hover. This might be my smallest PR ever, now ;)

@jasmussen
Copy link
Contributor

Not sure why travis failed on that one. But the change looks good now!

@njpanderson
Copy link
Contributor Author

I don't know if you fixed something @jasmussen but it seems to be passing here now.

@jasmussen
Copy link
Contributor

I guess the test ran again. Ship it!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

[Focus] Accessibility (a11y) Changes that impact accessibility and need corresponding review (e.g. markup changes).

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants