1. nvda@nvda.groups.io

Re: Read-all problem with a website

CARLOS-ESTEBAN <carlosestebanpianista@...>
 

Hello.
The solution is the reader mode of the browser.
In chrome, go to the page chrome://flags. In edit box search write reader mode. In the option reader mode, select enabled in the combo box and press the button relaunch.
Regards.

Carlos Esteban Martínez Macías.
Músico (pianista) y también ayuda a usuarios con discapacidad visual en el
uso de lectores de pantalla y tecnología.
Experto certificado en el lector de pantalla NVDA.

Musicien (pianist) and also help to users with a visual disability in the use of screen readers and technology.
Certified expert in screen reader NVDA.



El mié., 8 de jul. de 2020 a la(s) 11:53, Joseph Lee (joseph.lee22590@...) escribió:
Hi,
Report dynamic content changes setting is most effective in terminals, but
that's about to change to include web applications (not in a distant
future).
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Luke Davis
Sent: Wednesday, July 8, 2020 9:53 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Read-all problem with a website

On Wed, 8 Jul 2020, Brian Vogel wrote:

> personal accounts of illness and healing? There is a single "ticker
> box" (I have no idea what these things are actually called in web
> design speak) at the

They used to be called marquees. Generated by the marquee element.

Now I think their just called live regions, and I believe there are a few
ways to implement them.
I don't have access to an NVDA machine right now to find out if "Report
dynamic content changes" (NVDA+5) has any effect on this.

Luke
Join nvda@nvda.groups.io to automatically receive all group messages.
More
Home Messages Hashtags Subgroups About Features Pricing Updates Terms Help Twitter