You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I seem to be unable to install an app without using the mouse. Am I doing something wrong or is it not possible?
What I've tried
When opening the installation pop-up and searching for an app, I can navigate to the 'Install' anchor element, but pressing enter does nothing. Neither does pressing space.
Probable cause
My guess is that this is because the element is rendered as an anchor tag with an href value of #. Because it does not take the user anywhere, would it make more sense to use button elements instead? There is already a task on making the links look like buttons, but I still don't think this would solve the keyboard accessibility issue. I also think that a button would be more semantically correct here, but I may very well be wrong.
The text was updated successfully, but these errors were encountered:
thomasheartman
changed the title
How do I install an app using only the keyboard?
Unable to install an app using only the keyboard
Apr 8, 2021
A little update on this: in Firefox, I was able to trigger it by pressing shift+enter, which is bound to "open link in new window". ctrl+enter ("open link in new tab") also seems to work. So at least there's a workaround for it for now. However, this is still surprising from a user's perspective, and I think it would still be preferable to make them actual buttons.
Problem
I seem to be unable to install an app without using the mouse. Am I doing something wrong or is it not possible?
What I've tried
When opening the installation pop-up and searching for an app, I can navigate to the 'Install' anchor element, but pressing enter does nothing. Neither does pressing space.
Probable cause
My guess is that this is because the element is rendered as an anchor tag with an href value of
#
. Because it does not take the user anywhere, would it make more sense to use button elements instead? There is already a task on making the links look like buttons, but I still don't think this would solve the keyboard accessibility issue. I also think that a button would be more semantically correct here, but I may very well be wrong.The text was updated successfully, but these errors were encountered: