Thanks for your feedback! I'll definitely look into all this.
Also I should mention that I'm a big Linux user too! In fact the screenreader I've been using to test accessibility is orca, the standard Linux screenreader for this reason. I do have Windows so I plan to test accessibility on there too (with the free screenreader NVDA). But I only use Windows for things I can't do on Linux (or can't do easily--I don't really enjoy using WINE so I prefer to stick to Windows for Windows-specific apps even if they can be emulated).
I use mobile extensively, but thanks for reminding me of the text size issue. While it doesn't pose an issue for me personally, I can certainly understand the issues such small text could pose for a large number of mobile users.
I think it's actually the (also TeX derived) software ConTeXt that can generate accessible tagged PDFs--I just haven't figured out the actual tagging part yet. Though given the performance of all the other PDFs I've tried (including one I found online that *specifically* said it was accessible), the fault may not actually lie in the ConTeXt tagging itself. I think for the PDFs, I will continue to try to make them as accessible as I can reasonably make them, but I'm going to focus on accessibility for the HTML because the takeaway from my current research on this matter is that the most accessible PDF is an HTML page.
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
no subject
Date: 2023-10-13 09:43 pm (UTC)Also I should mention that I'm a big Linux user too! In fact the screenreader I've been using to test accessibility is orca, the standard Linux screenreader for this reason. I do have Windows so I plan to test accessibility on there too (with the free screenreader NVDA). But I only use Windows for things I can't do on Linux (or can't do easily--I don't really enjoy using WINE so I prefer to stick to Windows for Windows-specific apps even if they can be emulated).
I use mobile extensively, but thanks for reminding me of the text size issue. While it doesn't pose an issue for me personally, I can certainly understand the issues such small text could pose for a large number of mobile users.
I think it's actually the (also TeX derived) software ConTeXt that can generate accessible tagged PDFs--I just haven't figured out the actual tagging part yet. Though given the performance of all the other PDFs I've tried (including one I found online that *specifically* said it was accessible), the fault may not actually lie in the ConTeXt tagging itself. I think for the PDFs, I will continue to try to make them as accessible as I can reasonably make them, but I'm going to focus on accessibility for the HTML because the takeaway from my current research on this matter is that the most accessible PDF is an HTML page.