From e2935f68adc99ac644e2ceb7c5faa97501a86167 Mon Sep 17 00:00:00 2001 From: Chrissy Date: Sun, 2 Aug 2026 22:06:43 -0400 Subject: [PATCH] fix two misspellings in accessible pdf post --- _posts/2026-06-11-accessible-pdf-question.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/_posts/2026-06-11-accessible-pdf-question.md b/_posts/2026-06-11-accessible-pdf-question.md index 10049b8..81cef14 100644 --- a/_posts/2026-06-11-accessible-pdf-question.md +++ b/_posts/2026-06-11-accessible-pdf-question.md @@ -1,5 +1,5 @@ --- -title: Accessibile PDFs? +title: Accessible PDFs? tags: accessibility pdf html authors: - clontz @@ -12,7 +12,7 @@ And, even setting aside the large commercial incentives for certain businesses t there is a huge community working towards this goal! I have so much respect for professionals like [Deyan Ginev](https://kwarc.info/people/dginev/), codeveloper of [LaTeXML](https://github.com/brucemiller/LaTeXML/) and instrumental in the [ar5iv project](https://ar5iv.labs.arxiv.org/) converting arXiv preprints -to accessibile HTML. +to accessible HTML. But that's just it -- why are the most significant projects aiming to make accessible scholarly STEM documents aiming not for an accessible PDF, but instead aiming to help authors create accessible HTML?