This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Firefox with Voice Over on Mac OS

  • 1 svar
  • 0 har dette problemet
  • 7 views
  • Siste svar av Dropa

more options

I'm using Firefox on a Mac with the built-in screen reader Voice Over. When I need to log in to a web page, with a User Name & password stored in Apple's Key Chain utility, I typically press Command-Shift-A & the User name & Password fields are automatically populated. Unfortunately, with my new installation of Firefox, I've found that the key combination in question is used to launch the "Add Ons" window. Is there a work-around for this? The Command-Shift-A is the only way that a blind user can populate those fields from Key Chain. The buttons, usually visible in or around those fields for a sighted user are inaccessible.

Thanks so much,

CJ

I'm using Firefox on a Mac with the built-in screen reader Voice Over. When I need to log in to a web page, with a User Name & password stored in Apple's Key Chain utility, I typically press Command-Shift-A & the User name & Password fields are automatically populated. Unfortunately, with my new installation of Firefox, I've found that the key combination in question is used to launch the "Add Ons" window. Is there a work-around for this? The Command-Shift-A is the only way that a blind user can populate those fields from Key Chain. The buttons, usually visible in or around those fields for a sighted user are inaccessible. Thanks so much, CJ

All Replies (1)

more options

Beyond the default Browser keyboard hotkeys those most likely are standard settings and the only way that I read was either a 3rd party software to override those hotkeys or a userChrome.css edit to change those from standard keyboard hotkeys.