We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Funkcionalnosć tutoho sydła so přez wothladowanske dźěła wobmjezuje, kotrež maja waše dožiwjenje polěpšić. Jeli nastawk waš problem njerozrisuje a chceće prašenje stajić, wobroćće so na naše zhromodźenstwo pomocy, kotrež na to čaka, wam na @FirefoxSupport na Twitter a /r/firefox na Reddit pomhać.

Pomoc přepytać

Hladajće so wobšudstwa pomocy. Njenamołwimy was ženje, telefonowe čisło zawołać, SMS pósłać abo wosobinske informacije přeradźić. Prošu zdźělće podhladnu aktiwitu z pomocu nastajenja „Znjewužiwanje zdźělić“.

Dalše informacije

Where can I find information on using the Firefox debugger with the JAWS or NVDA screen readers? Which debugger tools are recommended?

  • 1 wotmołwa
  • 2 matej tutón problem
  • 1 napohlad
  • Poslednja wotmołwa wot cor-el

more options

When using the built-in debugger, if forms mode kicks on in the JAWS screen reader, the source code will not be read. I can read the code by using the virtual PC cursor, but need to be able to debug JavaScript by doing things like setting breakpoints. In general, which resources should I read for debugging in Firefox with a screen reader, whether that be JAWS or NVDA? Is there an add-on that I should be using, instead of the built-in developer tools?

When using the built-in debugger, if forms mode kicks on in the JAWS screen reader, the source code will not be read. I can read the code by using the virtual PC cursor, but need to be able to debug JavaScript by doing things like setting breakpoints. In general, which resources should I read for debugging in Firefox with a screen reader, whether that be JAWS or NVDA? Is there an add-on that I should be using, instead of the built-in developer tools?

Wšě wotmołwy (1)

more options

Wubrane rozrisanje