349
Here’s what we’re working on in Firefox | The Mozilla Blog
(blog.mozilla.org)
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
So - I don’t think Firefox would be generating captions for PDFs on PDF creation.
But of the major ways that PDF’s do get created - converted from text editors or design software, I know that Microsoft Word automatically suggests captions when the document creator adds an image (but does not automatically apply captions), and I believe that some design software does, as well.
I think that, functionally, both suggesting captions at time of document creation, or at time of document read are prone to the same issues - that the software may not be smart enough to properly identify the object, and if it is, that it is not necessarily smart enough to explain it in context.
By way of example, a screenshot of a computer program will have the automatic suggestion of “A graphical user interface” (or similar), but depending on the context and usage, it could be “A virus installer disguised as ___ video game installer.” Or “The ___ video game installer.” Between the document creator and the creation software or screen reader, only the document creator would really know the context for the image.
Which is all to say that I think that Mozilla has the right idea with auto-tagging, but it will always fail on context. The only way to actually address the issue is to deal with it within the document creation software.
But I wouldn’t be opposed to ML on those that can auto-suggest things or even critique how content authors write their descriptions.
I'm not sure. The blog post is not entirely clear on that.
Agreed. Context is usually very important for images. But with an auto-generated caption embedded in the document itself, you already lose some context. Because if the automatic caption is incorrectly stored as "The ___ video game installer" you cannot decide anymore if this was written by the author with the context in mind or just generated. Which I would argue is worse than no caption, as it lowers your trust in all captions.
Absolutely, I think that will be by far the best solution. It could massively encourage users to write their own captions if in most cases you only need to accept the suggestion. But so far, that seems unlikely to be the way forward. Why do that when you can just throw even more "AI" at the problem?