Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

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

Hierdie gesprek is in die argief. Vra asseblief 'n nuwe vraag as jy hulp nodig het.

Firefox with Voice Over on Mac OS

  • 1 antwoord
  • 0 hierdie probleem
  • 8 views
  • Laaste antwoord deur 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.