Review of PDF standards and accessibility#1891
Draft
cwickham wants to merge 1 commit intoprereleasefrom
Draft
Conversation
cwickham
commented
Feb 20, 2026
Comment on lines
35
to
64
| +------------------+------------------------------------------+--------------------+ | ||
| | Standard | Description | Format Support | | ||
| +==================+==========================================+====================+ | ||
| | `ua-1` | PDF/UA-1 for screen reader accessibility | Typst only | | ||
| +------------------+------------------------------------------+--------------------+ | ||
| | `ua-2` | PDF/UA-2 (newer accessibility standard) | LaTeX only | | ||
| +------------------+------------------------------------------+--------------------+ | ||
| | `a-1a`, `a-1b` | PDF/A-1 for long-term archival | Typst (`a-1a`), | | ||
| | | | both (`a-1b`) | | ||
| +------------------+------------------------------------------+--------------------+ | ||
| | `a-2a`, `a-2b`, | PDF/A-2 archival with newer features | Both formats | | ||
| | `a-2u` | | | | ||
| +------------------+------------------------------------------+--------------------+ | ||
| | `a-3a`, `a-3b`, | PDF/A-3 archival allowing embedded files | Both formats | | ||
| | `a-3u` | | | | ||
| +------------------+------------------------------------------+--------------------+ | ||
| | `a-4`, `a-4f` | PDF/A-4 (based on PDF 2.0) | Both formats | | ||
| +------------------+------------------------------------------+--------------------+ | ||
| | `a-4e` | PDF/A-4e (engineering variant) | Typst only | | ||
| +------------------+------------------------------------------+--------------------+ | ||
| | `x-4`, `x-4p`, | PDF/X for print production | LaTeX only | | ||
| | `x-5g`, `x-5n`, | | | | ||
| | `x-5pg`, `x-6`, | | | | ||
| | `x-6n`, `x-6p` | | | | ||
| +------------------+------------------------------------------+--------------------+ | ||
| | `1.4`, `1.5`, | Explicit PDF version | Both formats | | ||
| | `1.6`, `1.7`, | | | | ||
| | `2.0` | | | | ||
| +------------------+------------------------------------------+--------------------+ | ||
|
|
Collaborator
Author
There was a problem hiding this comment.
@gordonwoodhull I wonder if there is a way to tailor this better to the page it is on. I.e. If I'm on PDF Basics, I probably only care which are supported by format: pdf, and may not even know Typst is a different format.
That might mean two completely separate tables and a conditional include...a pain to update, but possibly worth it to avoid confusion.
The table in its current form should still live somewhere. Maybe a blog post? Or a dedicated Accessibility page?
cwickham
commented
Feb 20, 2026
| @@ -93,7 +93,7 @@ | |||
|
|
|||
| Although Quarto can't on its own guarantee accessibility requirements are met, many are satisfied through the Markdown structure of the document: | |||
Collaborator
Author
There was a problem hiding this comment.
@gordonwoodhull Should we say anything about the YAML values that get propogated to the PDF document metadata too? I.e. I think you always need to set title.
gordonwoodhull
added a commit
that referenced
this pull request
Feb 22, 2026
Split the standards table into format-specific versions using content-visible so each page only shows relevant standards, and remove the now-unnecessary Format Support column. Add document metadata bullet to accessibility section. Split document tagging bullet into format-specific content. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
No description provided.