Date   

Re: Help using Notepad and text files

 

Grant,

            I'll try to give some quick answers so you can spend some time playing with and exploring NVDA yourself, which is really the best way to eventually get the hang of it.

            I will presume that you are using the desktop keyboard format, meaning that INSERT is what will be your NVDA key, and this is the default layout.  If you happen to be using the laptop layout, which is not the default, even on laptops since most have number pads these days, then NVDA would be CAPS LOCK.  Some commands change slightly depending on the keyboard layout you are using, but I'm going to presume the desktop layout.

            NVDA has multiple help files, all of which can be accessed via the NVDA Main Menu, Help Option.  That would be NVDA+N,H.  The "two biggies" are at the top of the list that's the User Guide, and Commands Quick Reference.   I cannot tell you how often I end up hitting NVDA+N,H,Q to bring up the Commands Quick Reference in my web browser to find one of the commands I don't use often.

            NVDA also has an Input Help Mode, that can be toggled on/off by using NVDA+Number Row 1.  When it's on, pressing any key or key combination will cause NVDA to report what that would do, but not do it.  You have to toggle it off again to go back to normal mode.

            Say all, which is what I think you mean by read screen, is NVDA+Down Arrow.

            Reporting the status bar, if there is one, is NVDA+End

--

Brian - Windows 10 Pro, 64-Bit, Version 1909, Build 18363  

Power is being told you're not loved and not being destroyed by it.

       ~ Madonna

 

 


Help using Notepad and text files

Grant Metcalf
 

I am trying to learn how to use NVDA. However, I do not use Wordpad  but Notepad and primarily work only with text files. I also am having to switch from my Win7 PC to a Win10 PC on which I have installed Classic Shell from SERO. 
Here are a few questions:
1. How do I access the help file and its information?
2. What is the read the screen command?
3. How do I read the “status Bar” or bottom of the screen?
4. How can I review keyboard commands without changing a document or accidently deleting an item from my PC?
 
If anybody is willing to discuss this via the telephone, I am in California and currently available most of the day.
 
Listening for His shout!
Grant Metcalf – a.k.a. Grandpa DOS
Email: the.gems@...
 
 


Re: strange behavior with NVDA 2019.3

 

If the cut-outs are always at the beginning of words, and he's using Bluetooth audio, it's the Bluetooth Audio that is the problem.  There is an NVDA Add-on, BluetoothAudio, that is meant to remedy this issue.  If it doesn't work, there is another alternative in a program called Silenzio, but it makes sense to try the add-on first.
--

Brian - Windows 10 Pro, 64-Bit, Version 1909, Build 18363  

Power is being told you're not loved and not being destroyed by it.

       ~ Madonna

 

 


Re: strange behavior with NVDA 2019.3

Tyler Spivey
 

Audio enhancements. See if you can turn them off. Just go to Run and type mmsys.cpl, then select your playback device, properties, and see if it has an enhancements tab. There should be a disable checkbox there.

On 4/11/2020 9:18 AM, Tony Ballou wrote:
Hi,


I'm trying to help a friend who has both the latest versions of windows 10 pro, and NVDA.  For some reason, NVDA is partially reading the text.  An example of what's going on is that instead of saying the word information, it's only saying formation. Syllables of words are being cut.  I've never seen this happen before, hopefully somebody can give me an idea of what's going on.  Thanks.


Tony



strange behavior with NVDA 2019.3

Tony Ballou
 

Hi,


I'm trying to help a friend who has both the latest versions of windows 10 pro, and NVDA.  For some reason, NVDA is partially reading the text.  An example of what's going on is that instead of saying the word information, it's only saying formation. Syllables of words are being cut.  I've never seen this happen before, hopefully somebody can give me an idea of what's going on.  Thanks.


Tony


Re: google chrome version 81

 

Cordelia,

             If you're willing to be the "accessibility guinea pig" and wouldn't mind trying out the replacement for PDF-XChange Viewer, which is PDF-XChange Editor, would you?

            There was a major change to the look and feel of the interface, going to the now-all-the-rage flat look, which I hate, so I didn't go to it.  But they very well could have improved accessibility as part of that move.  It can be downloaded here:  https://www.tracker-software.com/product/downloads
You do not need the "Plus" version.  I just do not have the time (nor interest, to be honest) to play with this as far as determining its accessibility or the lack thereof.  I suspect if nothing else that the OCR function will remain the same even if the rest is completely inaccessible.

--

Brian - Windows 10 Pro, 64-Bit, Version 1909, Build 18363  

Power is being told you're not loved and not being destroyed by it.

       ~ Madonna

 

 


Re: google chrome version 81

Cordelia Scharpf
 

OK, I could live with this until I find something more readily accessible and compatible with screen readers. Thanks a lot for your caution, Brian, and for pointing out that it can actually read a number of languages, something I do need for work.

 

Cordelia

 

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Brian Vogel
Sent: Saturday, April 11, 2020 5:53 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] google chrome version 81

 

Cordelia,

              The message in which I posted that tutorial dates from January 2018, and the actual content was written well before that, as I got in to the whole OCR processing with saving the text layer for PDFs for two of my clients who were graduate students at the time and were constantly getting old image scanned PDFs of articles that had no text layer associated with them, just the image.

              PDF-Xchange Viewer is discontinued software, according to Tracker Software, but it is still available for download and there have been patches since it went to discontinued status.  It is actually my preferred PDF viewer and it's what I use, but I can't recommend it for general use for screen reader users because it is nowhere near to accessible overall.  It's OCR function, however, is, and it works beautifully.  When you add in that you can download somewhere around 20 different languages in addition to English for OCR-ing it really can't be beat.  I had a client once whose first language is Swedish and that was one of the languages in the language add-on collection.

              The download page for PDF-XChange Viewer and several other archived discontinued products is:  https://www.tracker-software.com/product/downloads/discontinued
The date on the last stable version of the software is December 16, 2018.
  
--

Brian - Windows 10 Pro, 64-Bit, Version 1909, Build 18363  

Power is being told you're not loved and not being destroyed by it.

       ~ Madonna

 

 


Re: google chrome version 81

 

Cordelia,

              The message in which I posted that tutorial dates from January 2018, and the actual content was written well before that, as I got in to the whole OCR processing with saving the text layer for PDFs for two of my clients who were graduate students at the time and were constantly getting old image scanned PDFs of articles that had no text layer associated with them, just the image.

              PDF-Xchange Viewer is discontinued software, according to Tracker Software, but it is still available for download and there have been patches since it went to discontinued status.  It is actually my preferred PDF viewer and it's what I use, but I can't recommend it for general use for screen reader users because it is nowhere near to accessible overall.  It's OCR function, however, is, and it works beautifully.  When you add in that you can download somewhere around 20 different languages in addition to English for OCR-ing it really can't be beat.  I had a client once whose first language is Swedish and that was one of the languages in the language add-on collection.

              The download page for PDF-XChange Viewer and several other archived discontinued products is:  https://www.tracker-software.com/product/downloads/discontinued
The date on the last stable version of the software is December 16, 2018.
  
--

Brian - Windows 10 Pro, 64-Bit, Version 1909, Build 18363  

Power is being told you're not loved and not being destroyed by it.

       ~ Madonna

 

 


Re: google chrome version 81

Cordelia Scharpf
 

Brian,

 

Thank you for this tutorial. I will try this software as I often get seemingly blank PDFs to read. Might you recall, by chance, when you wrote this tutorial and whether the software has been updated since?

 

Cordelia  

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Brian Vogel
Sent: Saturday, April 11, 2020 4:44 PM
To: nvda
@nvda.groups.io
Subject: Re: [nvda] google chrome version 81

 

On Sat, Apr 11, 2020 at 03:43 AM, Shaun Everiss wrote:

A properly designed pdf should just work.

And something created as PDF from the get go generally will.  A huge number of commercial documents are generated initially as PDFs, not much unlike one uses Word, and when the document is text-based to begin with, it reads.

The problem is, and you identified it, is that there are millions upon millions of image scanned PDFs that were created as such before the age of OCR being an automatic part of that process.  Unless you (and it's generally the individual you) run OCR processing on them they won't be accessible regardless of what is being used in an attempt to read them.  This is what it is, and in the case of image PDFs that are images of text, running OCR processing generally resolves the problem if the original image is even just decent.

But you've hit the nail on the head in that something generated as a PDF from scratch, that is, designed from the ground up in PDF format, is an entirely different animal than an old image scanned PDF.  Given how long electronic documents circulate in their original forms it's likely that image scanned PDFs, and the need to post-process them with OCR when the image is an image of things like a magazine article, letter, book page, or the like will be with us long past the time I'll be dead.

I wrote a brief tutorial on a specific piece of software I like for doing this because its OCR is really, really good and you can save the text layer it generates along with the file so it's there when you need to open it again in the future or send it along to someone else.  https://nvda.groups.io/g/nvda/message/33512 
 
--

Brian - Windows 10 Pro, 64-Bit, Version 1909, Build 18363  

Power is being told you're not loved and not being destroyed by it.

       ~ Madonna

 

 


Re: NVDA Audio Themes Add On

 

Documentation for the add-ons (or at least most of them) comes packaged with and can be accessed via the NVDA main menu.

NVDA+N,H,D   (NVDA Main, Help, Run Add-ons Documentation) after pressing which you will be presented with a list of your installed add-ons for which a documentation package was included.  Since the GitHub page for that add-on mentions updating the documentation as part of this latest version, the Audio Themes add-on should be somewhere in that list.  I can't know where as I can't know what add-ons any given person might be using.  Navigate to it, hit Enter, and the documentation will open in the web browser you have set as default on your system for your reading pleasure.

--

Brian - Windows 10 Pro, 64-Bit, Version 1909, Build 18363  

Power is being told you're not loved and not being destroyed by it.

       ~ Madonna

 

 


A Public Apology to Shaun Everiss Plus Bugzilla vs. GitHub

 

I want to apologize to Shaun, as I have been made aware that Bugzilla now will allow you to log in using your GitHub credentials.   That was not formerly the case, but like many interfaces that have begun doing stuff like "log in with Google," or "log in with Facebook," it appears that Bugzilla will allow you to log in using GitHub credentials.  This apology is sincere.  I based my comments on what had been longstanding practice for years, as well as what I saw on both bug reports, where Shaun is identified by a slightly different user name.  Still, not knowing how Bugzilla might handle user name extraction, I cannot know what credentials were used to log in and it is entirely possible he used his GitHub account credentials to access Bugzilla.

It is critical to recognize that Bugzilla and GitHub are two entirely separate bug reporting systems, each of which is used by different software developers.  There are also other project management systems out there besides those two.  With NVDA being on GitHub it gets discussed quite a bit more here off and on.  No matter what piece of software you might be wanting to file an issue or bug report, or even a formal feature request, for you must determine where it is to be reported.

I would never want to discourage anyone from "getting into the act" of doing bug/issue reporting and, again, thank Shaun Everiss for having taken the time and effort to have filed this one.  We'd never have seen as rapid a response and fix had that not been done.
--

Brian - Windows 10 Pro, 64-Bit, Version 1909, Build 18363  

Power is being told you're not loved and not being destroyed by it.

       ~ Madonna

 

 


Re: google chrome version 81

 

On Sat, Apr 11, 2020 at 03:43 AM, Shaun Everiss wrote:
A properly designed pdf should just work.
And something created as PDF from the get go generally will.  A huge number of commercial documents are generated initially as PDFs, not much unlike one uses Word, and when the document is text-based to begin with, it reads.

The problem is, and you identified it, is that there are millions upon millions of image scanned PDFs that were created as such before the age of OCR being an automatic part of that process.  Unless you (and it's generally the individual you) run OCR processing on them they won't be accessible regardless of what is being used in an attempt to read them.  This is what it is, and in the case of image PDFs that are images of text, running OCR processing generally resolves the problem if the original image is even just decent.

But you've hit the nail on the head in that something generated as a PDF from scratch, that is, designed from the ground up in PDF format, is an entirely different animal than an old image scanned PDF.  Given how long electronic documents circulate in their original forms it's likely that image scanned PDFs, and the need to post-process them with OCR when the image is an image of things like a magazine article, letter, book page, or the like will be with us long past the time I'll be dead.

I wrote a brief tutorial on a specific piece of software I like for doing this because its OCR is really, really good and you can save the text layer it generates along with the file so it's there when you need to open it again in the future or send it along to someone else.  https://nvda.groups.io/g/nvda/message/33512 
 
--

Brian - Windows 10 Pro, 64-Bit, Version 1909, Build 18363  

Power is being told you're not loved and not being destroyed by it.

       ~ Madonna

 

 


Re: check boxes dont' work in sim tool kit pro

mohammad suliman
 

Hello Sarah,

I am not familiar with the app you're asking about, however I'll suggest to do the following:
  •  Set NVDA debugging level to debug. You can do this by hitting NVDA +n for NVDA menu > preferences > settings > general.
  • Restart NVDA with add-ons disabled.
  • Perform the steps which will trigger the issue
  • Copy the log as before and send it here. Please be careful to not send the log with sensitive info.
I will suggest also to try the steps to reproduce (besides trying with brows mode) while in focus mode. If I am not mistaking, the error happens with brows mode according to the log you already sent.
I am interested to see if the error is the one I already seen with Electron apps recently. If not, let's hope I or someone else could identify the reason behind the problem.

Good luck!
Mohammad

On Fri, 10 Apr 2020 at 23:06, Sarah k Alawami <marrie12@...> wrote:

Here you go.

INFO - main (08:07:12.659) - MainThread (7648):
Starting NVDA version 2019.3.1
INFO - core.main (08:07:13.123) - MainThread (7648):
Config dir: C:\Users\Sarah\AppData\Roaming\nvda
INFO - config.ConfigManager._loadConfig (08:07:13.123) - MainThread (7648):
Loading config: C:\Users\Sarah\AppData\Roaming\nvda\nvda.ini
INFO - core.main (08:07:13.369) - MainThread (7648):
Using Windows version 10.0.18363 workstation
INFO - core.main (08:07:13.369) - MainThread (7648):
Using Python version 3.7.5 (tags/v3.7.5:5c02a39a0b, Oct 14 2019, 23:09:19) [MSC v.1916 32 bit (Intel)]
INFO - core.main (08:07:13.370) - MainThread (7648):
Using comtypes version 1.1.7
INFO - core.main (08:07:13.370) - MainThread (7648):
Using configobj version 5.1.0 with validate version 1.0.1
INFO - synthDriverHandler.setSynth (08:07:16.059) - MainThread (7648):
Loaded synthDriver oneCore
INFO - core.main (08:07:16.059) - MainThread (7648):
Using wx version 4.0.3 msw (phoenix) wxWidgets 3.0.5 with six version 1.12.0
INFO - brailleInput.initialize (08:07:16.171) - MainThread (7648):
Braille input initialized
INFO - braille.initialize (08:07:16.172) - MainThread (7648):
Using liblouis version 3.10.0
INFO - braille.initialize (08:07:16.177) - MainThread (7648):
Using pySerial version 3.4
INFO - braille.BrailleHandler.setDisplayByName (08:07:16.186) - MainThread (7648):
Loaded braille display driver noBraille, current display has 0 cells.
INFO - core.main (08:07:16.523) - MainThread (7648):
Java Access Bridge support initialized
INFO - _UIAHandler.UIAHandler.MTAThreadFunc (08:07:16.547) - _UIAHandler.UIAHandler.MTAThread (7160):
UIAutomation: IUIAutomation6
INFO - external:globalPlugins.Weather_Plus.sendlog (08:07:17.311) - MainThread (7648):
Weather_Plus 7.5: <urlopen error [Errno 11001] getaddrinfo failed>
INFO - core.main (08:07:17.570) - MainThread (7648):
NVDA initialized
INFO - updateCheck.AutoUpdateChecker._started (10:22:22.563) - MainThread (7648):
Performing automatic update check
ERROR - scriptHandler.executeScript (12:59:00.440) - MainThread (7648):
error executing script: <bound method BrowseModeDocumentTreeInterceptor.script_tab of <NVDAObjects.IAccessible.chromium.ChromeVBuf object at 0x040730D0>> with gesture 'tab'
Traceback (most recent call last):
File "scriptHandler.pyc", line 205, in executeScript
File "browseMode.pyc", line 1423, in script_tab
File "browseMode.pyc", line 1419, in _tabOverride
AttributeError: 'NoneType' object has no attribute 'setFocus'
INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo (13:03:34.275) - MainThread (7648):
No developer info for navigator object

I didn't know what to include so I included all of it.

Sarah Alawami, owner of TFFP. . For more info go to our website.

to subscribe to the feed click here and you can also follow us on twitter

Our discord is where you will know when we go live on [twitch.](http://twitch.tv/ke7zum] Feel free to give the channel a follow and see what is up there.

For stream archives, products you can buy and more visit my main lbry page and my tffp lbry page YOu will also be able to buy some of my products and eBooks there.

Finally, to become a patron and help support the podcast go here

On 10 Apr 2020, at 11:56, Cohn, Jonathan wrote:

I’m sorry, but I can’t download a application to try and copy your symptoms. We might get a hint at what is going on though with the NVDA-F1 function. Can you paste the last 20 or so lines from that output?

 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io>
Date: Friday, April 10, 2020 at 12:11 PM
To: Nvda List <nvda@nvda.groups.io>
Subject: [nvda] check boxes dont' work in sim tool kit pro

External email alert: Be wary of links & attachments.

An odd subject but not necessarily true. I don't really know how to explain this one.

This is an electron app by the way so I don't really know if this is a chrome thing or not.

steps

  1. download stkp you do not need an account, just put a nick name in the settings if you want.
  1. Go to the add tabs option at. the bottom and click it.
  1. Add a tab such as http://simbrief.net or the active sky. The second one won't work unless you have prepared and active sky (as) running.

results

Notice that links don't work, check boxes can't be checked and edit fields can't be typed into, only in that particular applet. The rest of the links in the app work. The developer is a bit stumped as to why this is not working. If someone can tell me what to say to him, or can contact him on their discord which can be found in the dash board, please let me know. He wants to make the app accessible but does not know what he is doing. He has nvda but has not even I don't think tired to fix this. It is not on his list to fix now, but it will be soon.

Take care

Sarah Alawami, owner of TFFP. . For more info go to our website.

to subscribe to the feed click here and you can also follow us on twitter

Our discord is where you will know when we go live on [twitch.](http://twitch.tv/ke7zum] Feel free to give the channel a follow and see what is up there.

For stream archives, products you can buy and more visit my main lbry page and my tffp lbry page YOu will also be able to buy some of my products and eBooks there.

Finally, to become a patron and help support the podcast go here


Re: google chrome version 81

mohammad suliman
 

Hello guys,

Yes, I agree, I think Google is making nice work in the accessibility field, but one always asks for better and better, especially that there are companies who manage to provide that level of accessibility we are hoping for.
I think that PDF documents can be accessible as other file formats. When I started to use computers with a screen readers, I got the impression that PDF documents aren't accessible, not sure where this idea came from. However, gradually I started to realize that you can read PDFs with a screen reader, I have came to know that by accident in fact. From that moment on, I have became more and more reliant on PDF files for my study and work. Recently, I also was told by a friend of mine who works as an accessibility tester that PDFs can be used exactly as HTML forms to fill out data accessibly  of course, which was kind of surprise for me. What I am trying to say that PDF creators have the means to create accessible documents which are very friendly to use, but maybe rules and laws need to make sure this happens.
Let's hope for a better times with PDF accessibility!

best!
Mohammad

On Sat, 11 Apr 2020 at 10:43, Shaun Everiss <sm.everiss@...> wrote:
The problem is that pdf is more than a file.

Its an image format, a archive, a document.

A lot of manuals come in it.

At home we save archives of photos and scanned images in it.

Many scanners and such use it as it is a commen format.

So its not going away any time soon.

A properly designed pdf should just work.

But if it doesn't you can use something like codex to convert any pdf
into something that can be used freely.

Now it would be nice if all manuals and stuff the blind need to read
from books to everything else were in actual html code.

Pdfs are like a zip file for images and documents.

Now what needs to happen is that if a pdf is supposed to be for us blind
people to read there needs to be something that stops it being compiled
if its not accessible.

But there are pdf documents that we don't need to read as such.

As I said a lot of scanners and such use pdf generally.

Right now adobe controls all this pdf cloud and other things.

I do think there needs to be something for us users to edit, and view
pdfs, handle forms etc and make things accessible and working.

Most of the time I am converting a pdf into something else though an
accessibly done pdf can be read and its fine.

To be honest if pdfs did go, it would be back to image files.

The good news is that a lot of pdfs for a lot of things like manuals and
the like were created from word documents.

As for flash, it and shockwave are being replaced by air.

The fact shockwave is gone on the web doesn't mean its gone.

Still a lot of people write in it and standalone shockwave and flash are
used.

And web is not fully accessible at all times either.

It would be nice to just kill all custom controls and interfaces but no
one would like that.

Flash is dieing because of security and the fact adobe can't be bothered
maintaining it now html5 can cover its functions.

Pdfs well the tools are out there, but people have to use all of them.



On 11/04/2020 7:29 pm, Felix G. wrote:
> Hi,
> of course the world's most used web engine should be rock solid in
> terms of accessibility. Thankfully, most of the time it actually is.
> We are closer to the golden age of the accessible web than ever
> before, which is the primary reason why the occasional glitch manages
> to stand out so much.
> Now that Flash is practically dead and in the process of being buried,
> the next thing I'd love to see dead is the tangled mess of half-open
> pseudo-standards we have come to know as pdf. Either trash it, or
> revise it such that it simply fails validation if it's not accessible.
> Best,
> Felix
>
> Am Fr., 10. Apr. 2020 um 12:48 Uhr schrieb mohammad suliman
> <Mohmad.s93@...>:
>> Hello Brion!
>>
>> Thanks for the appreciation and encouragement!
>> Yah i see that. Although I searched the tracker for similar issues, but couldn't find this one. In any case, I think that by raising this issue, we got the fix to be in a future Chrome 81 update, and not have to wait until 82 is released.
>>
>> Thanks again!
>> Mohammad
>>
>> On Thu, 9 Apr 2020 at 23:53, Brian Vogel <britechguy@...> wrote:
>>> Mohammad,
>>>
>>>              Just as an FYI, your report was deemed a duplicate and merged into
>>>
>>> Issue 1069448: neither NVDA nore Jaws screen readers are able to read PDF documents in latest Chrome version 81 stable
>>>
>>>
>>>              It was deemed a regression bug, and apparently a fix has already been made as of earlier this afternoon.  The final line of the issue above notes:
>>>
>>> Good news, this is a duplicate of bug 1047856 which has just been verified as having been fixed. I'll merge this bug now. If you have any questions or concerns after Chrome updates with the fix, please let us know!
>>> --
>>>
>>> Brian - Windows 10 Pro, 64-Bit, Version 1909, Build 18363
>>>
>>> Power is being told you're not loved and not being destroyed by it.
>>>
>>>         ~ Madonna
>>>
>>>
>>>
>>>
>>
>
>




Re: NVDA Audio Themes Add On

bhanu computer
 

and i want some docmentation of this addon can any one send me the link of documentation?


Re: Time Zoner addon for NVDA

Eilana Benish
 

OK, now it works

Thanks for the Clarification 


 

 

ובכבוד רב | Sincerely,

אילנה בניש מורשה נגישות שירות 2200 | Eilana Benish, service Accessibility authorized (2200)

ניהול פרויקטים – נגישות ושמישות אינטרנט וטכנולוגיות מידע  | Projects manager – Accessibility & usability on internet and ICT

📱 +972-50-7100367 | 📧 benish.ilana@...  

נכתב על ידי Vlad Dragomir, ב־11/04/2020 בשעה 10:47:

Hello,

I think you need to press the shortcut twice rapidly in order to have the second time zone, three times to have the third, and so on. At least that's how it works on my machine.

I hope this will help you a bit.

Best regards,

Vlad.





Re: Time Zoner addon for NVDA

Vlad Dragomir
 

Hello,

I think you need to press the shortcut twice rapidly in order to have the second time zone, three times to have the third, and so on. At least that's how it works on my machine.

I hope this will help you a bit.

Best regards,

Vlad.


Time Zoner addon for NVDA

Eilana Benish
 

Hello everyone

has anybody tried to work with Time Zonerthe addon for NVDA?

https://addons.nvda-project.org/addons/timeZoner.en.html

·       My default time zone is recognized and when pressing NVDA+Alt+T the time zone is announced

·       To add more time zones , I am pressing  the Configure Timezone Ring from the settings and Choose from the list the time zone I want to add so that when pressing NVDA + Alt + T, NVDA will read all the time zones I have added

·       but something goes wrong .after I am selecting and pressing one of the time zones and then saving the configurations still NVDA don't read the added time zones

so, I am trying to understand if there is anything I am missing, or the problem is in the add on which is in developer stage right now

Great  addon!

This is a great idea 4 dealing with the time zones issues from third party services and can be very helpful for screen reader users

 

·        

--

 

 

ובכבוד רב | Sincerely,

אילנה בניש מורשה נגישות שירות 2200 | Eilana Benish, service Accessibility authorized (2200)

ניהול פרויקטים – נגישות ושמישות אינטרנט וטכנולוגיות מידע  | Projects manager – Accessibility & usability on internet and ICT

📱 +972-50-7100367 | 📧 benish.ilana@...  


Re: google chrome version 81

 

The problem is that pdf is more than a file.

Its an image format, a archive, a document.

A lot of manuals come in it.

At home we save archives of photos and scanned images in it.

Many scanners and such use it as it is a commen format.

So its not going away any time soon.

A properly designed pdf should just work.

But if it doesn't you can use something like codex to convert any pdf into something that can be used freely.

Now it would be nice if all manuals and stuff the blind need to read from books to everything else were in actual html code.

Pdfs are like a zip file for images and documents.

Now what needs to happen is that if a pdf is supposed to be for us blind people to read there needs to be something that stops it being compiled if its not accessible.

But there are pdf documents that we don't need to read as such.

As I said a lot of scanners and such use pdf generally.

Right now adobe controls all this pdf cloud and other things.

I do think there needs to be something for us users to edit, and view pdfs, handle forms etc and make things accessible and working.

Most of the time I am converting a pdf into something else though an accessibly done pdf can be read and its fine.

To be honest if pdfs did go, it would be back to image files.

The good news is that a lot of pdfs for a lot of things like manuals and the like were created from word documents.

As for flash, it and shockwave are being replaced by air.

The fact shockwave is gone on the web doesn't mean its gone.

Still a lot of people write in it and standalone shockwave and flash are used.

And web is not fully accessible at all times either.

It would be nice to just kill all custom controls and interfaces but no one would like that.

Flash is dieing because of security and the fact adobe can't be bothered maintaining it now html5 can cover its functions.

Pdfs well the tools are out there, but people have to use all of them.

On 11/04/2020 7:29 pm, Felix G. wrote:
Hi,
of course the world's most used web engine should be rock solid in
terms of accessibility. Thankfully, most of the time it actually is.
We are closer to the golden age of the accessible web than ever
before, which is the primary reason why the occasional glitch manages
to stand out so much.
Now that Flash is practically dead and in the process of being buried,
the next thing I'd love to see dead is the tangled mess of half-open
pseudo-standards we have come to know as pdf. Either trash it, or
revise it such that it simply fails validation if it's not accessible.
Best,
Felix

Am Fr., 10. Apr. 2020 um 12:48 Uhr schrieb mohammad suliman
<Mohmad.s93@...>:
Hello Brion!

Thanks for the appreciation and encouragement!
Yah i see that. Although I searched the tracker for similar issues, but couldn't find this one. In any case, I think that by raising this issue, we got the fix to be in a future Chrome 81 update, and not have to wait until 82 is released.

Thanks again!
Mohammad

On Thu, 9 Apr 2020 at 23:53, Brian Vogel <@britechguy> wrote:
Mohammad,

Just as an FYI, your report was deemed a duplicate and merged into

Issue 1069448: neither NVDA nore Jaws screen readers are able to read PDF documents in latest Chrome version 81 stable


It was deemed a regression bug, and apparently a fix has already been made as of earlier this afternoon. The final line of the issue above notes:

Good news, this is a duplicate of bug 1047856 which has just been verified as having been fixed. I'll merge this bug now. If you have any questions or concerns after Chrome updates with the fix, please let us know!
--

Brian - Windows 10 Pro, 64-Bit, Version 1909, Build 18363

Power is being told you're not loved and not being destroyed by it.

~ Madonna




Re: google chrome version 81

Felix G.
 

Hi,
of course the world's most used web engine should be rock solid in
terms of accessibility. Thankfully, most of the time it actually is.
We are closer to the golden age of the accessible web than ever
before, which is the primary reason why the occasional glitch manages
to stand out so much.
Now that Flash is practically dead and in the process of being buried,
the next thing I'd love to see dead is the tangled mess of half-open
pseudo-standards we have come to know as pdf. Either trash it, or
revise it such that it simply fails validation if it's not accessible.
Best,
Felix

Am Fr., 10. Apr. 2020 um 12:48 Uhr schrieb mohammad suliman
<Mohmad.s93@...>:


Hello Brion!

Thanks for the appreciation and encouragement!
Yah i see that. Although I searched the tracker for similar issues, but couldn't find this one. In any case, I think that by raising this issue, we got the fix to be in a future Chrome 81 update, and not have to wait until 82 is released.

Thanks again!
Mohammad

On Thu, 9 Apr 2020 at 23:53, Brian Vogel <@britechguy> wrote:

Mohammad,

Just as an FYI, your report was deemed a duplicate and merged into

Issue 1069448: neither NVDA nore Jaws screen readers are able to read PDF documents in latest Chrome version 81 stable


It was deemed a regression bug, and apparently a fix has already been made as of earlier this afternoon. The final line of the issue above notes:

Good news, this is a duplicate of bug 1047856 which has just been verified as having been fixed. I'll merge this bug now. If you have any questions or concerns after Chrome updates with the fix, please let us know!
--

Brian - Windows 10 Pro, 64-Bit, Version 1909, Build 18363

Power is being told you're not loved and not being destroyed by it.

~ Madonna