Re: Are web applications that accessible?
If the web app you are using is independent of a browser. In other word is self-contained browser like skype, Visual Code Editor and others. Then what is available to you is very restrictive. As the screen reader is fully dependent on what is revealed by this style of app via the accessibility framework like UIA, MSAA or iaccess2. If you cannot write a plugin, then you will have very limited access to available information.toggle quoted messageShow quoted text
A general overview how web pages regardless if they are stand-alone apps or uses any web browser work:
* the web page is loaded.
* The DOM is populated (Document Object Model).
* the accessibility tree of the browser is populated which has the required information for a assistive technology product.
* The accessibility API (framework) like UIA is populated by the browser.
* the screen reader then interrogates the accessibility API or the browser directly.
There is more complexity to what I have outlined above. But this gives a general overview how information flows.
NVDA might be able to get more information but you need to learn python, the accessibility API and possibly a bunch of other API information to get the information you want. A major learning curve for yourself. Where it would be far cost effective for your energy and time to reach out to the owner of the product to make the require changes.
From: firstname.lastname@example.org <email@example.com> On Behalf Of Damien Garwood
Sent: Sunday, 13 October 2019 7:16 AM
Subject: Re: [nvda] Are web applications that accessible?
Those are actually very interesting questions. I have theories, but that's all they are. I'm sure someone who is more expert on this topic will correct me if it turns out I'm wrong, which I'm sure I probably am.
The simple answer first. Announcements for several document elements (table headers, clickable items, links, headings etc) can be enabled or disabled through the document formatting section of the settings dialog.
Other than that, the only way to really customise what is spoken by NVDA (such as changing control type text, changing spoken order etc) is through scripting.
Now for my theories. Scripting web app enhancements with NVDA wouldn't be as simple as making an app module for several reasons.
1. NVDA has its own internal stuff that allows it to do its browse/focus mode thing. This could interfere with web apps that you might think can be scripted as app modules (those packaged as executables like Skype and so on).
2. The web browser is just a host for the app, and so I'm guessing NVDA can't get to it the same way it gets to a standard desktop control. Even apps packaged as their own executables like Skype are actually using Chrome/Chromium/whatever it's called these days.
3. Bear in mind that different browsers have different rules for rendering controls and information, and so unfortunately it wouldn't be a uniform process.
Having said that. There are several accessibility API's that NVDA has, over the years, managed to smack under one umbrella. So I'm guessing that's only a matter of time before the same can be done for web browsers, and eventually, web apps.
As for profiles. My guess is that those can be used in the normal way for web apps that come as executables, but would be difficult to set up for external websites, for similar reasons. The profile would be triggered by the browser, not the app itself.
On 12/10/2019 07:21 pm, Robert Logue wrote:
1: Is it difficult for users to script NVDA for web applications?