Separate legal scope from file testing
The Americans with Disabilities Act applies in organizational and service contexts that a PDF alone cannot reveal. Before describing a test as an ADA review, identify the responsible entity, the service or program, the audience, and the publication channel. Seek qualified legal advice for applicability and exceptions.
Test the document's actual use
Determine whether the PDF provides instructions, a form, a public notice, a report, or another part of a service. Check text alternatives, structure, reading order, headings, lists, tables, links, language, forms, errors, color, and keyboard operation. Review any alternative format in the same service journey rather than assuming its presence resolves access.
Use the current rule and standard named by the project
The Department of Justice adopted a web accessibility rule for state and local governments under Title II in 2024. The rule includes WCAG 2.1 Level AA as the technical standard and sets compliance dates based on entity size, with exceptions and details in the regulation. Other ADA contexts can differ, so a report should name its authority and scope instead of using “ADA compliant” as a generic checker label.
Keep a reviewable record
Record the exact file, ruleset, tools, manual checks, failures, limitations, repairs, and retest. Include the document's role in the service and the owner responsible for unresolved work. This evidence helps product, content, and legal teams discuss the same artifact without collapsing their decisions into one score.