Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Site Site
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 24
    • Issues 24
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Indienet
  • SiteSite
  • Issues
  • #18

Closed
Open
Created Mar 14, 2018 by Aral Balkan@aralOwner

Minor: Disabled buttons should give feedback if accidentally pressed

Via @laura:

https://axesslab.com/disabled-buttons-suck/

(That disabled buttons do not give feedback.)


Aral: Interestingly, however, for people with screenreaders, the state of the button is read and it does constitute good usability.

Keeping this open so we can have a think about it.

Ideally, you would be able to both disable the button and react if it is pressed. That will have the correct semantics as well as guiding behaviour without violating (albeit my own) “prevent, don’t scold” principle when designing interactions. Some relevant discussion of how this can be achieved technically: https://stackoverflow.com/questions/3100319/event-on-a-disabled-input#comment52017136_3100395

Assignee
Assign to
Time tracking

Like this? Fund us! Your patronage helps keep us independent and going.