I have just found about this amazing feature. And it can add much value to my previous article – introduction to PDF accessibility – where I scratched the surface of PDF accessibility tooling.
So after late August, Chrome will be able to automatically generate accessible PDF when user will choose “Save as PDF” after triggering print (opens in new window). This means that PDF’s will be tagged as the formal adjective for accessible PDF’s is used.
But it is also worth mentioning that developers will also be able to use programmatic PDF generation, with using Chrome Headless, from their command line (or for example on the server or in the cloud). I think this is extremely valuable to whole community and will also add a lot to the overall accessibility on the long run.
I am looking forward to test this and they mention that it will be possible to experiment with it when using the chrome://flags/#export-tagged-pdf flag.
Will write a follow-up on this as soon as it will be possible, and I guess the community will be thriving with this too, so you will for sure know about the practical aspects very soon.
