Kozea
PDF/UA support improvement
This issue is for grouping PDF/UA features requests and bugs.
If you’d like to have a new feature regarding PDF/UA properties or encounter an issue related to PDF/UA, you can check here if an issue isn’t already opened. If not, please open an issue and we’ll link it there :)
- [ ] Support nested tags in anchors – #185
- [ ] Use better PDF tags for
<figure> - [ ] Use better PDF tags for
<dl> - [ ] Remove useless PDF Span tags that PAC complains about
- [x] Validate PDF/UA documents in CI – #2496
- [ ] Use valid order for PDF drawing commands when drawing SVGs, as PAC complains – #2533
- [ ] Avoid useless empty anonymous blocks, for example when list items are displayed as inline – #2504
- [ ] Fix structure of tables – #2508
- [ ] Support
aria-*attributes – #2550
Will there be a release with all these fixes coming up?
Yes, as soon as it’s tested. It takes some time because it requires to setup PDF validators in our CI pipelines.
@liZe Will the PDF/UA support improvements are part of the next release?
I think that creating PDF documents with accessibility can be considered as a unique selling point in the open source sector. Regardless of the fact that accessibility alone is extremely important and should be provided everywhere, there are guidelines on this in Europe. These guidelines are applied in the laws of individual European countries. This means that there is even an obligation – even if this should already be a given – to ensure accessibility. I do not know the priorities of this project but I see a huge opportunity for WeasyPrint and widespread use here.
Hi @froschdesign!
There’s no need to argue, we already know that accessibility is important, and we already spend a lot of time to improve the support (and develop all the other important features), and everybody can use all that for free. What we need is code, tests, feedback, time and money. 😄
Will the PDF/UA support improvements are part of the next release?
Everything that’s already merged in main and everything that is in the 67.0 milestone will be part of the next release.
@liZe Please don't get me wrong, I am grateful for your work and commitment. And I also realise that there are many areas where something needs to be done. I just wanted to know what the current status is, but I definitely didn't want to put any extra pressure on it.
…and everybody can use all that for free.
That's not what I'm concerned about, because after all, you run a library here that is worthy of support. 👍🏻 I will also test the points listed here.
Thanks for the quick response and update! 👍🏻