A group smiling during a business meeting

WCAG vs PDF UA: Which Standards Apply to You?

WCAG and PDF UA solve related but different accessibility problems. WCAG focuses on making web content accessible, while PDF UA ensures that PDF documents are usable by people with disabilities. Many organizations need to follow both accessibility standards simultaneously to deliver a fully inclusive digital experience and meet formal accessibility requirements.

Quick Overview of WCAG and PDF UA

Both WCAG and PDF UA are internationally recognized accessibility standards, but they apply to different types of content and technologies.

WCAG in Simple Terms

The Web Content Accessibility Guidelines (WCAG) define how to make web content accessible to people with disabilities. WCAG covers structure, code, design, and interaction for websites and web applications. It ensures that text, images, multimedia, and navigation are perceivable, operable, understandable, and robust. The current version, WCAG 2.2, expands on earlier versions by adding new success criteria for focus indicators, accessible authentication, and touch targets.

Accessibility standards and when they apply across web content, websites, and PDFs
Area	When it applies	What it covers	Why it matters for accessibility and SEO
WCAG for digital content	Whenever you publish content on the web, including websites, intranets and web based applications	Most online content that users can view or interact with	Ensuring WCAG compliance improves accessibility for disabled users and supports clearer navigation, stronger usability, and more consistent engagement across diverse user needs
WCAG for websites and web apps	When you design or build any website or web application, regardless of technology	Sites and apps built with HTML, JavaScript or any content management system	WCAG provides a stable framework for web accessibility so teams can optimise UX and technical SEO without locking into a specific platform or framework
Legal duties and WCAG	When your organisation is covered by accessibility regulations in regions such as the US, EU, UK, Canada or Australia	Public sector websites and many private sector services that must meet WCAG 2.2 Level AA	WCAG Level AA is the benchmark used by many regulators, so meeting it reduces legal risk, supports tenders and builds trust with users who rely on accessible services
WCAG and non web documents	When your website links to downloadable files such as PDFs or other documents	Documents that sit behind links on pages that otherwise meet WCAG	If those documents are inaccessible, the overall service can still fail an accessibility audit, which damages credibility and can block public sector or enterprise contracts
PDF UA for public facing PDFs	Whenever you use the PDF format to share information with the public or customers	Forms, reports, brochures and other PDFs intended for general use	PDF UA ensures that PDF content is perceivable and operable with screen readers and other assistive technologies, which is essential where key information is locked in PDF format
PDF UA for long and complex documents	When documents are long or detailed and rely on structure for navigation	Annual reports, policy manuals, application forms and other structured PDFs with headings, lists, tables and bookmarks	Proper PDF UA tagging makes complex documents navigable, so users can move through sections efficiently instead of being trapped in a flat, unreadable block of text
Sector expectations for PDF UA	When you work with public bodies, financial institutions or large organisations that run formal accessibility checks	Customer facing PDFs used in procurement, contracts, compliance reporting and customer communication	Many buyers now expect accessible PDFs by default, so meeting PDF UA can be the difference between passing or failing audits and can influence who wins or loses a tender

How WCAG and PDF UA Work Together

WCAG and PDF UA complement each other by covering different parts of the digital accessibility landscape.

Linking Standards in Practice

WCAG ensures that content is available in an accessible way, while PDF UA ensures that each PDF behaves correctly once opened. In practice, WCAG governs how users find and access content, and PDF UA governs how they experience it within a document.

Example Public Sector Service

Consider a city council website. The site itself must meet WCAG 2.2 Level AA to ensure web accessibility. However, downloadable forms, reports, and meeting minutes must also meet PDF UA to ensure PDF accessibility. Together, these standards guarantee that all users can access both online and offline content.

Alternative Formats and Strategy

Organizations can meet WCAG by reducing reliance on PDFs, offering HTML versions of key content, or ensuring that any PDFs used comply with PDF UA.

Deciding Which Standards Apply to You

Determining whether WCAG, PDF UA, or both apply depends on your content types, legal obligations, and user needs.

Map Your Content Types

Start by listing all your digital content: websites, web apps, PDFs, office documents, and multimedia. Mark where WCAG and PDF UA are relevant. For example, your website and intranet fall under WCAG, while your downloadable reports and forms fall under PDF UA.

Consider Your Legal and Policy Duties

Check your national laws, sector regulations, contracts, and internal policies to see which standards they reference. Many public sector accessibility frameworks explicitly name WCAG 2.2 Level AA and ISO 14289 (PDF UA) as required standards.

Risk-Based Decisions

Prioritize accessibility work for high-traffic services, legal documents, and customer communications. These materials have the greatest impact on users and carry the highest compliance risk.

Practical Steps to Comply with WCAG

WCAG compliance requires planning, testing, and continuous improvement.

Build Accessible by Design

Integrate WCAG into your design systems, component libraries, and development workflows from the start. Building accessibility into your process is more efficient than retrofitting later.

Test with Real Users and Tools

Combine automated accessibility testing with manual keyboard checks and user testing with assistive technology. Real-world testing ensures that your site works for people using screen readers, magnifiers, or voice input.

Fixing Common WCAG Issues

Common WCAG issues include missing alternative text, poor color contrast, keyboard traps, and unclear focus states. Addressing these problems improves usability for everyone.

Practical Steps to Comply with PDF UA

PDF UA compliance focuses on document structure, tagging, and navigation.

Create Tagged PDFs from Source Files

Start with well-structured source documents in Word, PowerPoint, or InDesign. Use built-in heading styles, lists, and tables, then export to PDF with tags enabled. Tagged PDFs preserve structure and make content readable by assistive technologies.

Check Structure and Reading Order

Validate tags, headings, lists, and tables using appropriate PDF accessibility checking methods. Verify the reading order to ensure that screen readers present content logically. Manual testing with screen readers like NVDA or JAWS helps confirm accuracy.

Interactive Forms and Signatures

Ensure that form fields, labels, and error messages are accessible. Add tooltips and logical tab order for keyboard users. Digital signatures should also be accessible under PDF UA to maintain usability and compliance.

Tools and Workflows That Support Both Standards

Organizations can streamline accessibility work by using tools and workflows that support both WCAG and PDF UA.

Choosing Authoring Tools

Select content management systems, office suites, and design tools that support accessibility tagging and validation. Tools like Grackle PDF and Adobe Acrobat help maintain compliance with both standards.

Training for Content Owners

Editors, designers, and document owners need basic training in web and document accessibility. Understanding WCAG and PDF UA principles helps teams create accessible content consistently.

Governance and Ongoing Checks

Establish light-touch governance processes for review, sign-off, and regular audits. Continuous monitoring prevents accessibility drift and ensures long-term compliance.

Common Mistakes When Applying WCAG and PDF UA

Avoiding common pitfalls helps maintain accessibility quality across all content types.

Relying Only on Automated Tests

Automated tools can detect many issues but cannot judge clarity of language, meaningful link text, or correct reading order. They also miss context-based problems, such as confusing instructions or inconsistent headings. Manual review remains essential to confirm that content is genuinely accessible and user-friendly.

Treating PDF as an Escape Route

Posting important information only in PDF format can exclude users if the files are not accessible. Some users may struggle to open or navigate PDFs, especially on mobile devices or with assistive technologies. Always provide accessible HTML alternatives or ensure that PDFs meet PDF UA standards to guarantee equal access for all.

Ignoring Mobile and Assistive Technology

Accessibility compliance means little if real users still struggle. Test your content on mobile devices and with assistive technologies to ensure usability across platforms.

Choosing the Right Standard with Confidence

WCAG applies to your web presence, while PDF UA applies to your PDF documents, together supporting a more robust and inclusive service. By aligning with WCAG 2.2 for web accessibility and ISO 14289 (PDF UA) for PDF accessibility, organizations can meet legal obligations, improve user experience, and demonstrate a genuine commitment to accessibility standards.

Back to Knowledgebase