I co-authored a Mozilla blog post about our #a11y work in celebration of International Day of Persons with Disabilities. I'm posting it a bit late here, but better late than never, I guess. :)
How we’re making Firefox accessible and delightful for everyone: blog.mozilla.org/en/products/f…
#a11y

Peter Vágner reshared this.

Unknown parent

mastodon - Link to source

Jamie Teh

@asadotzler @pvagner That's certainly a concern, though I think it's less of a problem with OCR. I think OCR has been around long enough that there's some intuitive understanding that it isn't perfect, plus when it fails, it (usually) fails in such a way as to be very clearly incorrect, rather than plausible enough to be misleading. That said, there's also the question of the technical feasibility of bundling Tesseract for a single OS, etc.
in reply to Jamie Teh

@Jamie Teh @Asa Dotzler Since tesseract v4 accuracy is greatly improved. For adding text layer to scanned pdf files I am using an app called #ocrmypdf which uses #tesseract and it works sufficiently well for me. There are even some unofficial builds of tesseract for #android. Other than self packaged tesseract there is mlkit by google people are using on android for recognizing images. Performance and interfacing with tesseract may not be that great, I understand.
in reply to pax

@pax We have a small team and a lot of high priority work to juggle. When that bug was first filed, MacOS 13 was in beta. None of our team were able to run it; running a beta OS (or even a newly released OS) is not without its risks. That bug is also very obscure; it seems to be due to a somewhat inexplicable change in VoiceOver, and as usual, Apple's documentation is poor to nonexistent.
@pax