{"canonical_url":"https://engineer.company/portfolio/reached-pdf-ua-1-conformance-at-106-of-106/","content_markdown":"# Passed 106 of 106 PDF/UA‑1 profile checks\n\nRecorded PDF/UA‑1 validation across nine documents with 106 of 106 configured accessibility‑profile checks passing, while the archival variant failed one of 146 rules.\n\nAugust 2026\n\n**Situation.** A PDF that looks correct on screen tells you nothing about whether a screen reader can read it, whether its headings form a structure, whether its language is declared, or whether it will still open in twenty years. Accessible‑PDF and archival‑PDF conformance are both machine‑checkable standards, and a document that has never been run through the validator is a document making an unverified claim.\n\n**Task.** The generated documents had to be measured against both standards, with the result recorded as a number rather than as an intention.\n\n**Action.** Nine documents — the CV in its variants, the reference sheet, the portfolio and the cover letter, across languages — were run through an independent validator for the accessibility profile and the archival profile separately. The accessibility profile passes at 106 of 106 rules, which required tagged structure, declared document language, alternative text on every non‑decorative graphic, a real title in the metadata, and an explicit reading order rather than the one the layout happens to produce. The archival profile is the more interesting result: it fails exactly one rule of 146. That is the shape of result that is easy to misreport. One hundred and forty‑five passes reads like conformance in a summary, and it is not conformance; it is a document that will be rejected by a system enforcing the standard. The failing rule is recorded with what it is and why it has not been closed, rather than rounded away.\n\n**Result.** All configured accessibility‑profile checks passed. The archival claim is stated honestly as a near‑miss with the specific gap named. The limit worth being direct about is that both numbers come from one validator; another implementation may disagree, and a rule that passes is only evidence that this checker had nothing to say about it.\n\n---\n\n- Role: Accessibility Specialist\n- Categories: [Web Development](https://engineer.company/categories/web-development/), [Automation \u0026 CI/CD](https://engineer.company/categories/automation/), [Testing \u0026 QA](https://engineer.company/categories/testing/), [Python](https://engineer.company/categories/python/), [UX / UI Design](https://engineer.company/categories/ux-ui/), [Documentation](https://engineer.company/categories/documentation/)\n- Services: [Website Development \u0026 CMS](https://engineer.company/services/web-development/), [UI/UX Design \u0026 Design Systems](https://engineer.company/services/ui-ux-design/), [Technical Documentation](https://engineer.company/services/technical-documentation/)\n\n\u003chttps://engineer.company/portfolio/reached-pdf-ua-1-conformance-at-106-of-106/\u003e\n","date_modified":"2026-11-12T05:34:23Z","description":"All configured accessibility-profile checks passed. The archival claim is stated honestly as a near-miss with the specific gap named.","formats":{"gemtext":"https://engineer.company/portfolio/reached-pdf-ua-1-conformance-at-106-of-106/index.gmi","gopher":"https://engineer.company/portfolio/reached-pdf-ua-1-conformance-at-106-of-106/gophermap","html":"https://engineer.company/portfolio/reached-pdf-ua-1-conformance-at-106-of-106/","json":"https://engineer.company/portfolio/reached-pdf-ua-1-conformance-at-106-of-106/index.json","markdown":"https://engineer.company/portfolio/reached-pdf-ua-1-conformance-at-106-of-106/index.md","pdf":"https://engineer.company/portfolio/reached-pdf-ua-1-conformance-at-106-of-106/index.pdf"},"kind":"page","language":"en","title":"Passed 106 of 106 PDF/UA-1 profile checks","url":"https://engineer.company/portfolio/reached-pdf-ua-1-conformance-at-106-of-106/","version":1}