Skip to content
This repository has been archived by the owner on Sep 5, 2024. It is now read-only.

Invalid color is a little too orange #6982

Closed
jestelle opened this issue Feb 2, 2016 · 2 comments
Closed

Invalid color is a little too orange #6982

jestelle opened this issue Feb 2, 2016 · 2 comments
Assignees
Labels
g3: reported The issue was reported by an internal or external product team. needs: feedback The issue creator or community need to respond to questions in this issue P4: minor Minor issues. May not be fixed without community contributions.
Milestone

Comments

@jestelle
Copy link

jestelle commented Feb 2, 2016

It appears in
https://material.angularjs.org/latest/demo/input
that Deep Orange A700 is used as the default 'invalid' color, used to style text indicating an input is invalid.

I'm assuming this was chosen because it meets accessibility contrast guidelines. However, the Material team has new recommendations on defaults here.

The Material Design team recommends replacing the default with:
Google Red a700 (#D50000) on light backgrounds and

ff6e6e on dark backgrounds.

FF6E6E is a value outside of the Material palette but its the closest to Red A700 that passes accessibility.

These colors will match the Material spec, but shouldn't be considered cast in stone.

Developers and designers are welcome to override these defaults, but should take care in meeting accessibility requirements within their own applications.

@naomiblack naomiblack added g3: reported The issue was reported by an internal or external product team. - Easy fix labels Feb 2, 2016
@ThomasBurleson ThomasBurleson added the P4: minor Minor issues. May not be fixed without community contributions. label Feb 2, 2016
@ThomasBurleson ThomasBurleson added this to the 1.0.6 milestone Feb 2, 2016
@EladBezalel
Copy link
Member

@jestelle please take a look at #3973 and #5992

@EladBezalel EladBezalel added the needs: feedback The issue creator or community need to respond to questions in this issue label Feb 10, 2016
@EladBezalel EladBezalel modified the milestones: 1.0.7, 1.0.6 Feb 10, 2016
@EladBezalel
Copy link
Member

@jestelle closing due to inactivity, if you found anything that i missed please ping me and i will reopen this issue

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
g3: reported The issue was reported by an internal or external product team. needs: feedback The issue creator or community need to respond to questions in this issue P4: minor Minor issues. May not be fixed without community contributions.
Projects
None yet
Development

No branches or pull requests

4 participants