Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add guidance for disabled buttons #215

Closed
wants to merge 1 commit into from

Conversation

sanjaypoyzer
Copy link

Clarification for the usage issues outlined in #201 (although not the core issue of contrast).

Clarification for the usage issues outlined in alphagov#201 (although not the core issue of contrast).
@gemmaleigh
Copy link
Contributor

I think we should open this one up for discussion.

I'd like to say something along these lines:

Don’t disable buttons, unless there’s a good reason to.

** Describe suitable reason to disable buttons here **

If you have to disable buttons, make sure they look like this...

Any thoughts on a bettter example?

cc. @edwardhorsford, @joelanman, @timpaul.

@gemmaleigh
Copy link
Contributor

I'm summarising from #201:

If you have to disable buttons, make sure they look like you can't click them.

An example of a useful disabled option is a calendar with greyed out days where no bookings are available.

Provide another way for the user to continue, add an error message or text to explain why the button is disabled.

@gemmaleigh
Copy link
Contributor

Closing in favour of #304.

@gemmaleigh gemmaleigh closed this Sep 7, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants