Ko tenda hembiapoite sa’ivéta oñemba’apokuévo hese hembiapo porãve hag̃ua. Peteĩ jehaipyre nomoĩporãiramo ne apañuái ha eporanduséramo, roguerekohína ore nepytyvõ rekoha ikatútava ndeykeko @FirefoxSupport Twitter-pe ha avei /r/firefox Reddit-pe.

Avatar for Username

Eheka Pytyvõha

Emboyke pytyvõha apovai. Ndorojeruremo’ãi ehenói térã eñe’ẽmondóvo pumbyrýpe ha emoherakuãvo marandu nemba’etéva. Emombe’u tembiapo imarãkuaáva ko “Marandu iñañáva” rupive.

Kuaave

Ko téma oñeñongatúma. Ejapo porandu pyahu eikotevẽramo pytyvõ.

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

  • 1 Mbohovái
  • 2 oguereko ko apañuãi
  • 1 Hecha
  • Mbohovái ipaháva cor-el

MichaelWalker14
MichaelWalker14
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?

Ñemoĩporã poravopyre

Try to ask advice at the Stack Overflow forum site.

Emoñe’ẽ ko mbohavái ejeregua reheve 👍 0

Opaite Mbohovái (1)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

Ñemoĩporã poravopyre

Try to ask advice at the Stack Overflow forum site.