sticky Community Message, Screen Reader Compatibility, Subject Lines, Email Threads #AdminNotice
First, I hope this message finds all of you well. The past year has been tough on many. Please know that, whatever it is that you may be experiencing, you are not alone. Please reach out to firstname.lastname@example.org if there is anything you might need, or if you need to talk. Please also utilize the resources in your region, and reach out to your friends and family for support. Also, at the risk of politicizing what I know to be a controversial issue, if you have not been vaccinated, I would urge you to consider doing so. If you have questions about that, please do some research from reputable sources. If you need help finding those, please get in touch at email@example.com. As a community, I'd like to think that we are all here to not only learn about, and discuss Windows accessibility, but also to support one another, to help lift one another up, and to be aware that, as a community, we are not alone. While I cannot pretend to walk in many of your shoes, I can say that struggles are real, what you feel is valid, and I, as the incoming forum owner/representative, am here to help in whatever way I can.
I have found myself reflecting on a particular thread on this list that has seen over 30 messages, and has also seen a number of spun off threads. I would like to request each of you to consider the following:
If you have any questions regarding any of the above, please reach out to firstname.lastname@example.org so that we can have an off-list discussion regarding the matter.
The message above is intended for the recipient to whom it was
addressed. If you believe that you are not the intended recipient,
please notify me via reply email and destroy all copies of this
correspondence. Action taken as a result of this email or its contents
by anyone other than the intended recipient(s) may result in civil or
criminal charges. I have checked this email and all corresponding
attachments for security threats.
Registered Linux User 529141.
To find out about a free, open-source, and versatile screen reader for Windows, visit nvaccess.org
You can follow @nimerjaber on Twitter for the latest technology news.
To contact me, you can reply to this email or you may call me at (970) (393-4481) and I will do my best to respond to you promptly.
Thank you, and have a great day!
Note to archive readers: these messages are marked as “sticky”.
To follow-up on Nimer’s post: whenever information about screen reader compatibility comes up, the best source of information comes from vendors themselves. Although we do have Windows Insiders who can provide early information, we are limited when it comes to providing information such as which version of JAWS will be compatible with Windows 11, under the hood changes to Narrator, when the next version of NVDA will be released, and related discussions. When in doubt, do ask vendors such as Microsoft, Vispero, NV Access, and others who can give you up to date information – for this reason, when it comes to screen reader advisories, whatever vendors say overrides advisories sent here.
In coming days I will be publishing a preliminary screen reader advisory for Windows 10 21H2 (build 19044), Windows Server 2022 (build 20348), and Windows 11 21H2 preview (build 22000), and to some extent, other ecosystem devices such as Xbox OS (version 2108), HoloLens, and Surface Hub. The upcoming advisory is preliminary and is based on observations and reports from users, as well as what’s going on with Windows development. Although the upcoming advisory is based on latest available information, you should still look for official word from vendors, especially concerning support for Windows 11 from their screen readers. For example, it was reported that JAWS 2022 will support Windows 11 (according to Eric Damery as quoted by a member), and I can say that the next version of NVDA includes foundations to support Windows 11 (based on latest source code commits); even then, I expect Vispero and NV Access will release official comments on Windows 11 support as it nears public release later this year.
Hope this helps. And to echo Nimer, please stay safe and healthy.
Joseph (the current and about to retire owner/head list rep)