How to Create Accessible Pdfs From the Start
Key topics
The article discusses how to create accessible PDFs from the start using Typst, a document formatting tool, and the discussion revolves around the challenges and limitations of creating accessible PDFs, as well as the role of PDFs in the digital age.
Snapshot generated from the HN discussion
Discussion Activity
Active discussionFirst comment
10d
Peak period
12
Day 10
Avg / period
7
Based on 21 loaded comments
Key moments
- 01Story posted
Nov 1, 2025 at 10:02 AM EDT
2 months ago
Step 01 - 02First comment
Nov 11, 2025 at 2:32 AM EST
10d after posting
Step 02 - 03Peak activity
12 comments in Day 10
Hottest window of the conversation
Step 03 - 04Latest activity
Nov 13, 2025 at 6:10 AM EST
about 2 months ago
Step 04
Generating AI Summary...
Analyzing up to 500 comments to identify key contributors and discussion patterns
Want the full context?
Jump to the original sources
Read the primary article or dive into the live Hacker News thread when you're ready.
While reading the article I could only think that all this semantic stuff is what html is about!
So, I think it makes more sense to do what arxiv is doing: providing a html version of articles on top of pdfs. I’d even say html should be the source and the PDF should be generated from it instead.
It was more of a genuine question, if it can be useful for machines while not being "visible". This thinking is a slippery slope though, because it can be stretched to a point where it defeats the original purpose.
https://github.com/ading2210/linuxpdf
/s
This is obviously absurd, and we don't know what you really mean. Probably billions of people use PDFs; I expect hundreds of millions use them regularly. I use them all the time, no problem, they work great.
PDFs are also a rare format which is preserved and functions reliably over time (decades) over systems (just about anything you can name). If I have a document I want to read 10-20 or more years in the future, PDF is the best bet.
The far superior presentation of professionally prepared PDFs - layout, typography, formatting, etc - makes a large difference for me when reading long texts. Also, the markup works very well and is also preserved - I can read markup from entirely different systems going back decades, and the annotation I make today I can read in 2050.
Thing is people want to do bunch of things they shouldn’t with PDF like automated parsing, editing or adding forms to it.
Ideally you should have an API or other structured data to pass around but of course life is more complicated. Like PDF is all you get because API would cost more than it makes sense to do bad job parsing PDF.
ConTeXt has also been making strides in creating accessible PDF files:
* https://meeting.contextgarden.net/2024/talks/hans+mikael/con...
* https://wiki.contextgarden.net/Input_and_compilation/Accessi...
In my time using Typst, I found that Typst makes it possible/easy to make content even more abstract: write the content as a "data structure" and then present parts of it in various places around your document. For instance to list quantity/weight of a parts description in a parts index at the end.
Exactly: If instructions for how to style the content are in the same file as the content, then that is mixing content _with_ presentation logic. Avoiding this approach to documentation is what I alluded to in writing, "Presumably, Typst allows including styles from external sources."
Wondering why they omitted that information from a blog post promoting Typst for accessibility use cases...
I really dislike it when this happens. This also affects copy/pasting. This typically seems to happen with LaTeX-style two-column layouts, where columns are supposed to be read top to bottom, left to right, but tools end up reading paragraphs from left to right, top to bottom. It's infuriating.
PDFs suck. And it's awful that they're the least bad option for a lot of things.
I have smaller phone even but layout was good an spacing was great.
Black text on white background not some grayish to look different but perfectly legible.