PDF ACCEPTANCE CRITERIA FOR PUBLIC BUYERS Published by Trilatic Desks. General information, not legal advice. 1. PASS/FAIL CHECKLIST FOR ACCEPTING A REMEDIATED PDF A file is accepted only if every item passes. 1. Tagged structure. The file has a tag tree (structure tree) and is marked as tagged. Untagged files fail. [ ] Pass [ ] Fail 2. Title and language. The document title is set and shown in the window title bar, and the document language is set correctly. [ ] Pass [ ] Fail 3. Reading order. The logical reading order matches the visual order, including across columns, sidebars, footnotes and page breaks. [ ] Pass [ ] Fail 4. Headings. Headings reflect the real structure of the document, are in order, and are not just large bold text. [ ] Pass [ ] Fail 5. Tables. Data tables have header cells with a scope (row or column), and are not used for layout. [ ] Pass [ ] Fail 6. Images. Meaningful images, charts and maps have alternative text that says what they convey. Decorative images are marked as artifacts. [ ] Pass [ ] Fail 7. Forms. Every form field has an accessible name and the tab order is logical. Instructions and required fields are not conveyed by colour alone. [ ] Pass [ ] Fail 8. Text unchanged. No text is lost or changed compared with the original document: numbers, names, dates, amounts and legal wording are identical. [ ] Pass [ ] Fail 9. Validation. The file validates as PDF/UA-1 in veraPDF, the open-source PDF/UA validator, with a report supplied per file. [ ] Pass [ ] Fail 10. Screen-reader spot check. A person reads a sample of the files with a screen reader and confirms headings, tables, forms and reading order work. [ ] Pass [ ] Fail 2. CONTRACT LANGUAGE (adapt the numbers in brackets; have counsel review) 1. All deliverable documents shall conform to WCAG 2.1 Level AA and to PDF/UA-1 (ISO 14289-1). 2. The Vendor shall supply, for each delivered file, a PDF/UA-1 validator report generated by a validator the Buyer can run itself (for example veraPDF). 3. The Buyer may test any delivered file, by any method, and may reject any file that does not meet the criteria in this contract. Acceptance shall not occur on the Vendor's statement alone. 4. Within [10] business days of written notice of rejection, the Vendor shall correct the rejected files at no additional charge and supply proof of correction, including a new validator report. 5. The Vendor's remediation shall not remove, add or change the text content of the original document. 6. Output produced with the assistance of automated or AI-based tools shall meet the same criteria as any other output, and the Vendor remains responsible for it. 7. Payment of the final instalment is conditioned on the Buyer's acceptance of the delivered batch. 3. HOW TO SAMPLE-CHECK A BATCH 1. Pick the sample before you look at the files: at least 5 documents, or 10% of the batch, whichever is larger, chosen at random. 2. Make sure the sample includes every document type in the batch: text, tables, forms and any scans. 3. Run each sampled file through the validator and read the report. Any failure fails the file. 4. Open each sampled file with a screen reader and read the first pages, one table and one form field set. 5. Compare the text of each sampled file with the original. Check numbers and names especially. 6. If more than one file in the sample fails, reject the batch and ask the vendor to correct all of it, not just the files you sampled. SOURCES - Section508.gov, Requiring business partners to provide accessible documents: https://www.section508.gov/buy/requiring-business-partners-provide-accessible-documents/ - NASPO, accessibility testing tools: https://www.naspo.org/accessibility/testing-tools/ - State of Colorado, accessibility and state contracts: https://osc.colorado.gov/financial-operations/osc-policies-guidance/contract-policies/accessibility-and-state-contracts - U.S. Department of Justice, ADA Title II web rule: https://www.ada.gov/resources/2024-03-08-web-rule/ A checker or validator result is not a compliance determination.