Date   

locked Re: History with Jarte and NVDA

 

This topic is now locked, as I think anything and everything about Jarte that can be covered in reference to accessibility with NVDA has.

It's also now unsupported software that one uses at one's own risk.  And I'm not trying to imply that there is any security risk, just that if something occurs with Windows that breaks Jarte it will remain broken.
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

I do not understand why some seek to separate a person from their actions.  The self is composed of an individual’s thoughts, actions, and expression, which are contained in and actuated by the body.  What you do and say is the clearest indicator of who you are.

      ~ Brian Vogel

 


locked Re: History with Jarte and NVDA

 

On Tue, May 25, 2021 at 11:36 PM, Sarah k Alawami wrote:
Actually jarte just came out with a new update a few months ago.
-
Sarah, their own website, https://www.jarte.com/, specifically, https://www.jarte.com/store.html , states:  Jarte Plus is now free and can be downloaded from the download page

Their support page reads, in its entirety:  Support is no longer provided for Jarte. No further development of the Jarte program is expected.

If you are a Jarte Plus customer who needs a new download link for Jarte Plus then please note that Jarte Plus is now freely available to everyone and can be downloaded from the Download page.

See the Jarte Help document for any other help you may need.

--------------
If you've got something newer than Version 6.2 then it's not the Jarte that most of us think of when Jarte is mentioned.  And that terminal (as in final) version came out in early 2018.
 
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

I do not understand why some seek to separate a person from their actions.  The self is composed of an individual’s thoughts, actions, and expression, which are contained in and actuated by the body.  What you do and say is the clearest indicator of who you are.

      ~ Brian Vogel

 


locked Re: History with Jarte and NVDA

Sarah k Alawami
 

Actually you can still buy jarte to auto correct stuff when you type or spell check. I have not bought it as of yet, but I have edited the ini file to heavily customize the heck out of the program to make it fit my needs. You can even make it sound like a typewriter which helps me actually.

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of David Russell
Sent: Tuesday, May 25, 2021 6:27 AM
To: nvda@nvda.groups.io
Subject: [nvda] RE History with Jarte and NVDA

Hello NVDA Group,

To Gene, David, and others interested.

Gene, Jarte was a 'nimble' word processor said to be basic and not have all the bells and whistles found on MS Word. I believe only
Jarte+ is available for free, or at its cost of under twenty-five US
dollars. Also, the plus version offers spelling error features via the screen reader mode, and again mimics WordPad. That answers your question of what I ant it to do for a significant savings: act like MS Word for a savings of over 50 percent.

The issue of the product no longer being supported is concerning.
Should this raise 'flags' and what might those be?

To David, a friend suggested LibreOffice, too. I note from doing a Google search, there were issues in 2019 with this program repeating words, skipping text, and perhaps spellcheck. I did pick up on the producers being passionate from what I read by them. As a writer, I am reliant on software working well and together. These past issues were said to occur between LibreOffice and either Jaws or NVDA. If you can allay my concerns to their existence, I will give LibreOffice strong consideration as it is still active!
I have files on a thumb drive produced in the 2013 version of MS Word.
Jarte will read those. Can one expect the same from LibreOffice?

Excuse me for my wordiness, but I have found that two or more heads on a matter may be better than one.. Thanks!

--
David C. Russell, Author


On using NVDA development snapshots (alpha), beta, or release candidates #adminnotice

 

Given what's going on now, and will almost certainly go on again, I feel that this message is really necessary at the moment.  Although focused on NVDA, the principles apply to any use of alpha, beta, or release candidate software from anyone.

Joseph Lee eloquently wrote:  Another huge reminder: betas are meant to gather feedback before software goes live. Things can break, including add-ons not working properly or not even running at all, so please don’t panic.

The part of this that I wish to emphasize:  Users of alpha, beta, and release candidate software are expected to report issues as part of the deal.  This software is not made available so that random users can "get a sneak peek," but in an effort to actually test it and see what does and does not work.  The earlier you are in the process, the more issues you should expect, and the more work you should expect to undertake to report them.

Alpha and development snapshot software is a work in progress.  Your feedback and bug reports when you hit a bump are a part of both the work and the ability to make progress.  Almost anyone using alpha software knows this, and proceeds accordingly, providing feedback for virtually every bump they encounter, even if that feedback is only adding a comment to an existing report of a sort of "me too" nature so that the extent of the issue can be framed.

But the above really seems to get lost when it comes to beta and release candidate software, and it can't and shouldn't.  Using pre-release software puts obligations on those that use it to make reports of issues to "iron out the kinks" and further development.  That's the very reason you are being invited to use it.

With what's going on right now, it's pretty much a foregone conclusion that there are going to be some breakages, particularly in relationship to add-on compatibility, most of which can be easily fixed once identified.  And that's where Joseph's "don't panic" comes into play.

If you hit an add-on incompatibility, and it's not resolved within 24-48 hours, then I'd report it.  I suspect that there are going to be a number of these "quick fix" type compatibility issues so this is one of the rare occasions where having tons of reports about the same issue likely wouldn't be helpful.  If you're hitting other issues with NVDA itself, or an add-on that is compatible with 2021.1 but not working correctly, then those should be reported immediately.  Remember that NVDA issues are reported via GitHub while Add-On issues are reported to their respective developers (some of whom are using GitHub to manage their add-on projects, some of whom are not, so dropping an e-mail is a good first step).

But if you are using pre-production software, part of the deal is that you're a tester and you have an obligation to report issues as you find them.
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

I do not understand why some seek to separate a person from their actions.  The self is composed of an individual’s thoughts, actions, and expression, which are contained in and actuated by the body.  What you do and say is the clearest indicator of who you are.

      ~ Brian Vogel

 


Re: checklist to perform web accessibility test with NVDA

 

On Wed, May 26, 2021 at 04:16 AM, Sascha Cowley wrote:
Again, I know and agree with all of this; I was just responding to the question asked.
-
Sometimes, going beyond "responding to the question asked" is a value-added service when you have background the questioners don't.  I think that this is what we're all trying to do, in one way or another, at this point.

The original question is really ill-posed.  And mentioning why, which you, I, and several others have done, serves a bigger purpose than just trying to answer it as posed.
 
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

I do not understand why some seek to separate a person from their actions.  The self is composed of an individual’s thoughts, actions, and expression, which are contained in and actuated by the body.  What you do and say is the clearest indicator of who you are.

      ~ Brian Vogel

 


locked Re: Does turning-on "BitLocker" cause any accessibility issues?

 

On Wed, May 26, 2021 at 07:32 AM, JM Casey wrote:
the OP stated that his employer leaves him no choice in that matter.
-
I read that as meaning that encryption is required, and nothing more.  I could be wrong.  But were I in this position, I would be pushing back against the need for drive encryption in general and BitLocker in particular.  It's gross overkill if it's strictly client data that you're seeking to encrypt.

There are other alternatives.  And the one I mentioned has now been confirmed as fully accessible and does not require full drive encryption.  There are others, too.
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

I do not understand why some seek to separate a person from their actions.  The self is composed of an individual’s thoughts, actions, and expression, which are contained in and actuated by the body.  What you do and say is the clearest indicator of who you are.

      ~ Brian Vogel

 


Re: Microsoft Excel and NVDA

 

How interesting! I just went to check if the cell coordinates are
checked and they were checked so I entered okay. Then I opened an
excel document and found out the arrows work moving from cell to cell.

On 5/26/21, Nevzat Adil via groups.io <nevzatadil=gmail.com@groups.io> wrote:
I had the same issue yesterday when I tried to create an invoice. I
use Office 2010. I did not have that issue before. Good thing I also
have JAWS as a backup.

On 5/26/21, Rui Fontes <rui.fontes@tiflotecnia.com> wrote:
Have you checked, in the NVDA configurations, Document formating, to
announce cell coordinates?


Rui Fontes

NVDA portuguese team


Às 05:30 de 26/05/2021, Eilana Benish escreveu:

Good morning

I have a serious problem with Microsoft Excel

When using the arrow keys or the tab key, to move between cells in
Microsoft Excel, even on the gnu document, NVDA announces the word
cell instead of the cell coordinates.

I`M USING THE LAST VERSION OF nvda AND I DID NOT MADE ENNY CHANGES –
SO THIS IS WEIRD.

I HOPE MICROSOFT DID NOT MADE UPDATE TO THE MICROSOFT 365 OFFICE THAT
COSSES THIS PROBLEM.




--


*ובכבוד רב,***

*אילנה בניש מורשה נגישות שירות 2200*

*ייעוץ, ליווי והערכת נגישות ושמישות אינטרנט וטכנולוגיות
מידע*<https://adn-accesstime.com>**

*טלפון ישיר 📱+972-50-7100367| דוא"ל 📧**benish.ilana@gmail.com*
<mailto:benish.ilana@gmail.com>*
*





--
Nevzat Adil
Library of Congress Certified
Literary Braille Proofreader
C: 512 502 4403
e-mail: nevzatadil@gmail.com
Facebook: m.facebook.com/LiteraryBrailleProofreader





--
Nevzat Adil
Library of Congress Certified
Literary Braille Proofreader
C: 512 502 4403
e-mail: nevzatadil@gmail.com
Facebook: m.facebook.com/LiteraryBrailleProofreader


Re: Microsoft Excel and NVDA

 

I had the same issue yesterday when I tried to create an invoice. I
use Office 2010. I did not have that issue before. Good thing I also
have JAWS as a backup.

On 5/26/21, Rui Fontes <rui.fontes@tiflotecnia.com> wrote:
Have you checked, in the NVDA configurations, Document formating, to
announce cell coordinates?


Rui Fontes

NVDA portuguese team


Às 05:30 de 26/05/2021, Eilana Benish escreveu:

Good morning

I have a serious problem with Microsoft Excel

When using the arrow keys or the tab key, to move between cells in
Microsoft Excel, even on the gnu document, NVDA announces the word
cell instead of the cell coordinates.

I`M USING THE LAST VERSION OF nvda AND I DID NOT MADE ENNY CHANGES –
SO THIS IS WEIRD.

I HOPE MICROSOFT DID NOT MADE UPDATE TO THE MICROSOFT 365 OFFICE THAT
COSSES THIS PROBLEM.




--


*ובכבוד רב,***

*אילנה בניש מורשה נגישות שירות 2200*

*ייעוץ, ליווי והערכת נגישות ושמישות אינטרנט וטכנולוגיות
מידע*<https://adn-accesstime.com>**

*טלפון ישיר 📱+972-50-7100367| דוא"ל 📧**benish.ilana@gmail.com*
<mailto:benish.ilana@gmail.com>*
*




--
Nevzat Adil
Library of Congress Certified
Literary Braille Proofreader
C: 512 502 4403
e-mail: nevzatadil@gmail.com
Facebook: m.facebook.com/LiteraryBrailleProofreader


locked Re: Does turning-on "BitLocker" cause any accessibility issues?

JM Casey
 

Yeah...I suppose so. That's just remote sighted assistance...*grins*...but oh well. You gotta do what you gotta do. And while people have been recommending other encryptions in this thread, the OP stated that his employer leaves him no choice in that matter.

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Luke Davis
Sent: May 25, 2021 11:09 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Does turning-on "BitLocker" cause any accessibility issues?

JM Casey wrote:

I mean, if the opening dialogue is the same every time, you shouldn’t
really need speech feedback – but it would e a matter of estimating
when that dialogue appears, and of course if something unpredictable happens, you wouldn’t neceeessarily know about it. Someone else said they needed sighted help aboug 50% of the time (I think) which is crazy.
You could also use something like Be My Eyes's Microsoft support option, to contact Microsoft each time you boot. Assuming you have a smartphone.
I wonder how many of those calls people would have to make before MS would devote some time to making that interface somewhat more accessible.
Likely wishful thinking.

You wouldn't have to show them the password, just get them to tell you when the prompt is on screen, put down the phone to type it in, and if it fails they can tell you that.

Luke


Re: Microsoft Excel and NVDA

Rui Fontes
 

Have you checked, in the NVDA configurations, Document formating, to announce cell coordinates?


Rui Fontes

NVDA portuguese team


Às 05:30 de 26/05/2021, Eilana Benish escreveu:

Good morning

I have a serious problem with Microsoft Excel

When using the arrow keys or the tab key, to move between cells in Microsoft Excel, even on the gnu document, NVDA announces the word cell instead of the cell coordinates.

I`M USING THE LAST VERSION OF nvda AND I DID NOT MADE ENNY CHANGES – SO THIS IS WEIRD.

I HOPE MICROSOFT DID NOT MADE UPDATE TO THE MICROSOFT 365 OFFICE THAT COSSES THIS PROBLEM.

 




--


ובכבוד רב,

אילנה בניש מורשה נגישות שירות 2200

ייעוץ, ליווי והערכת נגישות ושמישות אינטרנט וטכנולוגיות מידע

טלפון ישיר 📱 +972-50-7100367 | דוא"ל 📧 benish.ilana@...


locked Re: Does turning-on "BitLocker" cause any accessibility issues?

Michael Micallef at FITA
 

I confirm that veracrypt is fully accessivble, just don’t forget the master password.

 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Brian Vogel via groups.io
Sent: Tuesday, 25 May 2021 20:43
To: nvda@nvda.groups.io
Subject: Re: [nvda] Does turning-on "BitLocker" cause any accessibility issues?

 

CAUTION: This email originated from OUTSIDE the Government Email Infrastructure. DO NOT CLICK LINKS or OPEN attachments unless you recognise the sender and know the content is safe.

 

Unless you need drive encryption, as opposed to file and folder encryption where your HIPAA data is stored, you need not use BitLocker.

There are other options, and a very popular one is VeraCrypt  (See Beginner's Tutorial).  It allows you to create what they call a VeraCrypt container, which is just a special type of folder where anything copied into it or saved into it is encrypted, and anything taken out of it or opened from it by the person who created it will be decrypted for their use.  I seem to recall VeraCrypt being discussed on one of the screen-reader-centric groups and its being accessible, but I can't recall for certain.  If it is accessible, it could be far easier to deal with than BitLocker if what has been reported here remains true, and I cannot say whether it does or does not.

Note from me as moderator:  The only reason I'm allowing this topic to continue is because, so far, it's focused on whether or not BitLocker is accessible with NVDA, and details regarding issues with same.  If it takes a turn toward how to use BitLocker (or even VeraCrypt) then that needs to occur on the Chat Subgroup or elsewhere, as neither of those topics is screen reader dependent once it's established that basic accessibility exists.
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

I do not understand why some seek to separate a person from their actions.  The self is composed of an individual’s thoughts, actions, and expression, which are contained in and actuated by the body.  What you do and say is the clearest indicator of who you are.

      ~ Brian Vogel

 


Re: checklist to perform web accessibility test with NVDA

 

Having been a tester for both government and other organisations there is little to be accessible about.


Nvda will support firefox and chromium brousers in their pure form.

So chrome, edtge, firefox and waterfox up to 2020.08 will work.

Versions afterwards may have issues but yeah access wize thats not a problem.

Make sure you have latest updates to everything which is stable.

If you are testing a site on your beta copy of whatever, mmaybe you should revert or use a stable copy of everything unless you need to test a site with a beta of course.

Site wize, most things unless their have weird configurations will be probably ok.

From time to time you will encounter weird issues with databases but its not like they aren't hard to handle depending on the friendlyness of the owners.

It also depends how receptive the owners are to inaccessibility of things.

If anything nvda should be more accessible as far as sites go because you don't have to be concerned in most cases with scripts, drivers, graphics intercepts, extra display controler drivers, and everything else.

That doesn't mean you won't have a certain profile loaded for testing but its easier than jaws for example.

Generally jaws will work as long as the program you are working with has scripts for jaws else it just won't work because jaws needs scripts to function at all.

Nvda itself is 1 huge script run inside a python instance so its just there.

So most access depends on the site in question and shouldn't depend on the brouser generally or reader at least as far as nvda is concerned.

If you do use jaws with testing, then if it works with jaws its going to work with nvda.

Of course if your program you are testing uses things like universal speech or tolque then its just going to work with most readers by default supposedly.

Most things should work with firefox and chromium ports and since most stuff is written of those that should be fine.

If people don't want this to be a jaws bashing thing, we can call nvda windows 10 and jaws windows 98.

Windows 98 needed drivers for everything else it wouldn't work so jaws scripts are drivers in this case.

No drivers no work.

On 26/05/2021 8:02 pm, Luke Davis wrote:
Sascha Cowley via groups.io wrote:

      Can you explain how accessible with NVDA is different than just regular accessible?
I should have said "just regular screen reader accessible".

For one, there are many other accessibility issues than those encountered by screen-reader users, and screen-readers are not the only assistive technology
in use.
All of that is true. But the OP asked for a checklist specific to NVDA website accessibility.

You are starting at the very broad end of the question. The OP started at the extremely specific and narrow end of the question.

My contention is, that if you follow accessibility guidelines as a whole, and screen reader specific ones if you want, you will end up with a site that is accessible to NVDA, without ever having to have a checklist for specifically making it accessible for NVDA.

I doubt there is any NVDA specific accessibility checklist for websites, because there shouldn't be.
A site should be designed for accessibility. Screen reader accessibility, to be sure, but if you design it to be accessible to NVDA without making it generally screen reader accessible, you run the risk of overlooking general accessibility guidelines.
I don't think NVDA promotes that direction.

Second, as I'm sure you know, different screen-reader and browser combinations perform differently together on the same website.
Of course they do. But again, you should not design a website with that goal in mind, but with general accessibility to all screen readers in mind.
It can be done. The site might not perform ideally in all screen readers, but it can be made to perform adequately in all of them.

Luke




Re: checklist to perform web accessibility test with NVDA

Sascha Cowley
 

Again, I know and agree with all of this; I was just responding to the question asked.

On 2021-05-26 18:02, Luke Davis wrote:
Sascha Cowley via groups.io wrote:

      Can you explain how accessible with NVDA is different than just regular accessible?
I should have said "just regular screen reader accessible".

For one, there are many other accessibility issues than those encountered by screen-reader users, and screen-readers are not the only assistive technology
in use.
All of that is true. But the OP asked for a checklist specific to NVDA website accessibility.

You are starting at the very broad end of the question. The OP started at the extremely specific and narrow end of the question.

My contention is, that if you follow accessibility guidelines as a whole, and screen reader specific ones if you want, you will end up with a site that is accessible to NVDA, without ever having to have a checklist for specifically making it accessible for NVDA.

I doubt there is any NVDA specific accessibility checklist for websites, because there shouldn't be.
A site should be designed for accessibility. Screen reader accessibility, to be sure, but if you design it to be accessible to NVDA without making it generally screen reader accessible, you run the risk of overlooking general accessibility guidelines.
I don't think NVDA promotes that direction.

Second, as I'm sure you know, different screen-reader and browser combinations perform differently together on the same website.
Of course they do. But again, you should not design a website with that goal in mind, but with general accessibility to all screen readers in mind.
It can be done. The site might not perform ideally in all screen readers, but it can be made to perform adequately in all of them.

Luke




Welcome to the NVDA Community Add-ons website - Proxy support for NVDA #nvdaaddonsfeed

nvda@nvda.groups.io Integration <nvda@...>
 

Proxy support for NVDA

  • Author: Jose Manuel Delicado
  • NVDA compatibility: 2019.3 to 2020.4
  • Download stable version

This add-on allows the NVDA screen reader to connect to the Internet through one or more proxy servers. To make it possible, it applies various patches to the standard Python library or modifies certain environment variables, depending on the chosen configuration. You will be able to update NVDA and their add-ons automatically from your corporate environment and even perform remote sessions, provided that your organization proxy server allows it.

Features

  • Support for various proxy server types: http, socks4 and socks5.
  • Ability to redirect all traffic through the proxy server or only specific traffic (http, https, ftp).
  • Ability to redirect all traffic through a proxy server and, after that, redirect specific traffic through other servers (nested proxies).
  • Profile switch and config reset aware: if you usually work with a portable copy of NVDA, you can create various profiles for different environments (home, work, office1, office2) and manually activate them.

Usage

This add-on adds a new category to the NVDA settings dialog called "Proxy". In this category, you will find four settings groups. The first one allows you to configure a general proxy for all traffic. The other groups allow you to configure proxy servers only for specific protocols. All groups have the following fields:

  • Host: hostname or ip address of the proxy server. Leave empty to disable that particular proxy.
  • Port: server port.
  • Username: optional. User name for server autentication.
  • Password: optional. Password for server autentication. Note that password is not required for socks4 servers.

In addition to the previous fields, the following options are available in the first settings group:

  • SOCKS proxy type: socks4, socks5 or http can be selected.
  • Use proxy for dns requests if possible: when this checkbox is checked, hostnames or domain names will be directly sent to and resolved on the proxy server. When it is unchecked, names will be resolved locally and the server will receive only the destination ip address. Note that not all socks4 proxy servers support this option.

Tipically, most users will only have to configure the first settings group. If you don't know your proxy details, ask your organization network administrator for more information.

Limitations

  • Very limited IPV6 support.
  • UDP traffic is not supported on all proxy servers.
  • External DLL libraries won't respect the settings configured in this add-on.
  • Only basic autentication is supported for http proxy servers. Digest autentication is not supported.
  • In order to redirect all traffic (including https connections) through an http proxy, the server must support the CONNECT http method.
  • A "direct connection" mode can't be configured. If you disable a specific proxy, the system default will be used instead.

Changelog

Version 1.0

  • Initial release.


Welcome to the NVDA Community Add-ons website - NVDAUpdate Channel Selector #nvdaaddonsfeed

nvda@nvda.groups.io Integration <nvda@...>
 

NVDAUpdate Channel Selector

  • Author: Jose Manuel Delicado
  • NVDA compatibility: 2019.1 to 2020.4
  • Download stable version

This add-on allows you to download and install the latest NVDA version of the chosen type without visiting any webpage nor using your web browser. It is useful when, for example, you want to test new features in a NVDA snapshot and then return back to the most recent stable release. If you test regularly NVDA snapshots and you usually install them in your computer, you will save a lot of time with this add-on. If you prefer testing snapshots in portable mode keeping your installed copy of NVDA unchanged, this add-on is for you as well.

Usage

You can change the NVDA update channel by going to NVDA menu, Preferences, Settings, Update channel category. Once you choose the desired channel and press OK, wait until the next automatic update check or go to NVDA help menu and choose "Check for updates" option. For now, these are the available channels:

  • Default: this is the default channel used by your NVDA version. Choosing this option means the same as disabling the add-on.
  • Stable: force update channel to stable. Useful when you want to return to a stable version from a snapshot.
  • Stable, rc and beta: this is the channel for beta releases. You will receive the first beta version once it is released. This channel allows you to update through betas and release candidates until you reach the next stable version.
  • Alpha (snapshots): choose this option to update to the latest alpha. Alpha snapshots allows you to test new features, but they are quite unstable. Please, be careful.
  • Beta (snapshots): choose this option to update to the latest beta snapshot built from the beta branch. Beta code has been more tested than Alpha. However, until the official beta version is released, it may not be stable enough for most users.
  • RC (snapshots): choose this option to update to the latest release candidate snapshot built from the rc branch. RC code has been more tested than Beta. However, until the official rc version is released, it may not be stable enough for most users.
  • Disable updates (not recommended): this option disables the update channel. If you check for updates an error message will be displayed. Remember that you can disable automatic updates from the General settings category. Use this option only with testing purposes.

Changelog

Version 1.0

  • Initial version.


Re: checklist to perform web accessibility test with NVDA

Luke Davis
 

Sascha Cowley via groups.io wrote:

Can you explain how accessible with NVDA is different than just regular accessible?
I should have said "just regular screen reader accessible".

For one, there are many other accessibility issues than those encountered by screen-reader users, and screen-readers are not the only assistive technology
in use.
All of that is true. But the OP asked for a checklist specific to NVDA website accessibility.

You are starting at the very broad end of the question. The OP started at the extremely specific and narrow end of the question.

My contention is, that if you follow accessibility guidelines as a whole, and screen reader specific ones if you want, you will end up with a site that is accessible to NVDA, without ever having to have a checklist for specifically making it accessible for NVDA.

I doubt there is any NVDA specific accessibility checklist for websites, because there shouldn't be.
A site should be designed for accessibility. Screen reader accessibility, to be sure, but if you design it to be accessible to NVDA without making it generally screen reader accessible, you run the risk of overlooking general accessibility guidelines.
I don't think NVDA promotes that direction.

Second, as I'm sure you know, different screen-reader and browser combinations perform differently together on the same website.
Of course they do. But again, you should not design a website with that goal in mind, but with general accessibility to all screen readers in mind.
It can be done. The site might not perform ideally in all screen readers, but it can be made to perform adequately in all of them.

Luke


Re: Add-on Updater 21.05.1 #addonrelease

 

Hi all,

Another huge reminder: betas are meant to gather feedback before software goes live. Things can break, including add-ons not working properly or not even running at all, so please don’t panic. I and other members of the add-ons world can assure you that we are working around the clock to test and release add-ons that are ready for NVDA 2021.1.

P.S. Originally, I thought 2021.1 betas wouldn’t be as stressful as 2019.3 betas, but I was wrong: it will take a while before everyone is on board, especially because changes were made that caused several speech synthesizer add-ons to fail; editing add-on manifests will not work. The add-ons community have informed synth add-on makers about this, and synth driver add-on authors are working hard on preparing their add-ons. Also, due to changes to GUI toolkit NvDA is using, potentially any add-on that comes with a dialog (such as Systray List, StationPlaylist, and others) will not work properly with 2021.1 beta 1; developers of affected add-ons (I included) are working hard to make sure our add-ons are fully ready by the time 2021.1 stable version is released to the world.

I (as an add-on author and NVDA code contributor) am saying all this to reassure you: users are not forgotten. When it comes to add-ons, your pain is my pain, and I and the add-ons community members are doing everything we can to improve your lives and productivity through our add-ons, including making them ready by the time you meet NVDA 2021.1. At this time, on behalf of NVDA add-ons community and mailing list members (I am the head admin of NVDA Add-ons mailing list), I would like to kindly request that you wait for add-on developers to update their add-ons and wait for announcements, and if you don’t see your favorite add-on not working after 2021.1 stable version is released, then please send a love letter to add-on authors.

Thank you.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee via groups.io
Sent: Wednesday, May 26, 2021 12:02 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Add-on Updater 21.05.1 #AddonRelease

 

Hi all,

Update: If you are using Add-on Updater 21.05 with NVDA versions earlier than 2021.1 beta 1 or alpha-22877, you can now download Add-on Updater 21.05.1 via Add-on Updater. After that, you can enable update checks.

Specifically, follow the below steps as exactly as shown:

If you are not using NVDA alpha.22877 or 2021.1 beta 1 or later and would like to use one of these:

  1. Check if automatic add-on updates setting is on (NVDA menu/Preferences/Settings/Add-on Updater), and if not, enable it.
  2. Install Add-on Updater 21.05.1 when offered. You MUST install Add-on Updater 21.05.1 BEFORE you can use alpha.22877 or 2021.1 beta 1 or later because without that, you won't receive new add-on updates through this add-on because Add-on Updater will be flagged as incompatible and will not work.
  3. Install whatever NvDA version you would like to use AFTER installing Add-on Updater 21.05.1 and restarting NVDA once.

If you are using NVDA alpha.22877 or 2021.1 beta 1 or later and happen to be using Add-on Updater 21.05: you must download Add-on Updater 21.05.1 manually (see the earlier message for download link).

If you are using Add-on Updater 21.05.1: you can ignore this as you are using latest release.

Expect more messages from add-on authors as add-on updates declaring support for NvDA 2021.1 beta 1 are released (some of them include mine).

Cheers,

Joseph


Re: Add-on Updater 21.05.1 #addonrelease

 

Hi all,

Update: If you are using Add-on Updater 21.05 with NVDA versions earlier than 2021.1 beta 1 or alpha-22877, you can now download Add-on Updater 21.05.1 via Add-on Updater. After that, you can enable update checks.

Specifically, follow the below steps as exactly as shown:

If you are not using NVDA alpha.22877 or 2021.1 beta 1 or later and would like to use one of these:

  1. Check if automatic add-on updates setting is on (NVDA menu/Preferences/Settings/Add-on Updater), and if not, enable it.
  2. Install Add-on Updater 21.05.1 when offered. You MUST install Add-on Updater 21.05.1 BEFORE you can use alpha.22877 or 2021.1 beta 1 or later because without that, you won't receive new add-on updates through this add-on because Add-on Updater will be flagged as incompatible and will not work.
  3. Install whatever NvDA version you would like to use AFTER installing Add-on Updater 21.05.1 and restarting NVDA once.

If you are using NVDA alpha.22877 or 2021.1 beta 1 or later and happen to be using Add-on Updater 21.05: you must download Add-on Updater 21.05.1 manually (see the earlier message for download link).

If you are using Add-on Updater 21.05.1: you can ignore this as you are using latest release.

Expect more messages from add-on authors as add-on updates declaring support for NvDA 2021.1 beta 1 are released (some of them include mine).

Cheers,

Joseph


Re: checklist to perform web accessibility test with NVDA

Sascha Cowley
 

"Yes, and" I was responding to Luke Davis' question. I am aware of everything you stated.


Re: checklist to perform web accessibility test with NVDA

 

On Wed, May 26, 2021 at 12:34 AM, Sascha Cowley wrote:
For one, there are many other accessibility issues than those encountered by screen-reader users, and screen-readers are not the only assistive technology in use.
Second, as I'm sure you know, different screen-reader and browser combinations perform differently together on the same website.
-
Yes, and?

There is no grand unified checklist that handles varieties of accessibility technologies that don't target the same demographics.

And the second is a given so, yes, one could do the typical screen reader checks with any given screen reader, using everything else the same, and have slightly different results.

There is no "NVDA accessible," per se, just like there's no JAWS accessible, Narrator accessible, etc.  There are times when one screen reader or another may work better than another.

You're talking about field test results with a specific screen reader, which is all that can be determined with a single screen reader.  General accessibility standards, previously referenced, are screen-reader agnostic.
 
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

I do not understand why some seek to separate a person from their actions.  The self is composed of an individual’s thoughts, actions, and expression, which are contained in and actuated by the body.  What you do and say is the clearest indicator of who you are.

      ~ Brian Vogel

 

6261 - 6280 of 90522