Improve PDF accessibility by enabling --export-tagged-pdf Chromium option #269
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add
--export-tagged-pdf
option as the default option of Puppeteer to create PDF with improved accessibility.Chromium team announced upcoming Chrome is going to be able to make tagged PDF.
https://blog.chromium.org/2020/07/using-chrome-to-generate-more.html
Puppeteer had tried to make
--export-tagged-pdf
as the default option since Jan at puppeteer/puppeteer#5337. However, currently it's not yet added. By adding the option in Marp CLI, users will benefit of this in early.Marp CLI have recieved a feedback by users who uses screen reader in #236. So this is important to keep continuous improvements for optically challenged users.
In addition, the added meta data may improve the quality of editable PPTX converted from PDF by third-party tools. Just Marp CLI cannot create the editable PPTX (#166 (comment)) so it's also important for power users who using extra tools.