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

Buttons should not be hidden in certain states; need another pattern to offer better accessibility #53

Open
megoth opened this issue Nov 12, 2018 · 1 comment

Comments

@megoth
Copy link
Contributor

megoth commented Nov 12, 2018

The pattern of hiding/showing buttons according to state is problematic in terms of accessibility. It might also not offer the best UX for users. I think toggling availability by changing color and using other cues are a better approach (and mark it semantically, using the disabled-attribute).

Some examples of this pattern:

  • When offering controls for a resource: Is hidden until you hover with a mouse
  • Save-button for sourcePane: I hidden until there are changes to be saved
@timbl
Copy link
Contributor

timbl commented Nov 16, 2018

Good point. Though I think that hiding the optional pane icons at each level made a huge improvement in legibility. With them in, it looks very geeky and off putting to a normal user, and quite distracting even to a power user. Maybe some without hide them behind a "..." 'more stuff' logo.

Agree about disabled start buttons. Something like making them 80% transparent would be better.
The disabled flag on the control may not be what we need either ...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

No branches or pull requests

2 participants