- From: Mike Bremford via GitHub <noreply@w3.org>
- Date: Thu, 25 Sep 2025 16:44:53 +0000
- To: public-css-archive@w3.org
> It is sadly common for PDF generators to ignore all this so you see that some topic is on page n, you go to page n and it is actually n-7 or something. Common, but also disallowed when generating accessible PDFs under the new(ish) [PDF/UA-2](https://pdfa.org/iso-14289-2-pdfua-2/) specification, which requires that these "PageLabels" now have to match the printed page number on the page. > 8.12.3 **Page labels** If a page label as specified in ISO 32000-2:2020, 12.4.2 is present, it shall represent the same number as that perceived by a user. The custom page formatting you've described is relatively easy to solve using custom counters, one for the preface and one for the document body. But PDF creation software is unlikely to recognise these as a page counter unless it's called "page", and so will be unable to align the page labels with these values. So actually this is a very strong argument for @MurakamiShinyu's suggestion - without it, generating PDFs compliant with the latest accessibility specification is going to be a lot harder. -- GitHub Notification of comment by faceless2 Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12824#issuecomment-3335040003 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 25 September 2025 16:44:54 UTC