Re: SayAll not auto reading in Chrome


 

Hi,

Chrome support is divided into several parts, of these the important parts are virtual buffers and IAccessible2. Virtual buffer requires NVDA to inject part of itself to Chrome to find out what's going on with the document and to consume the virtual buffer (browse mode) content, and IAccessible2 (IA2) is used to handle accessibility information provided by Chrome (obviously that depends on how web authors and frameworks coded their documents). NVDA would wait for the web document to be ready completely before starting say all, but it looks like with the change to Chrome 100, NV Access might be a taking a different approach to restore automatic say all on page load (we can go on for days talking about the basics of browse mode/virtual buffer internals).

Cheers,

Joseph

Join nvda@nvda.groups.io to automatically receive all group messages.