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:
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.

Am Fr., 10. Apr. 2020 um 12:48 Uhr schrieb mohammad suliman
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!

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

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

Join to automatically receive all group messages.