Accessibility Is a Design Skill, Not a Specialty
Why graphic designers can’t afford to skip accessibility
For years, accessibility in print and document design has been treated as someone else’s problem: a compliance checkbox, a legal department concern, or something you deal with if a client specifically asks for it.
That window is closing.
The European Accessibility Act took effect in June 2025, extending accessibility requirements broadly across digital and document-based communications for organizations doing business in the EU. ADA litigation in the United States involving print and PDF materials has been climbing steadily. Section 508 already requires federal agencies to make electronic information and technology accessible, including many electronic documents. For contractors and vendors working with government clients, accessibility increasingly shows up in scopes of work, procurement language, and deliverable requirements. And the clients who hadn’t asked about accessibility are starting to.
If you’re a communications director who hires design contractors, this is the moment to start asking different questions. If you're a designer who's been producing PDFs without thinking about tags, reading order, or alt text, this is the moment to close that gap before a client closes it for you.
What “Accessible Design” Actually Means in Practice
Accessibility in print and document design is often misunderstood as a visual concern — high contrast, large type, readable fonts. Those things matter, but visual accessibility is only half the picture. The other half is structural: whether the document communicates its meaning to people who can't read it visually at all.
Screen readers (software used by many people who are blind, have low vision, or need nonvisual access to content) don't see your layout. They read a sequence of tagged content: this is a heading, this is a paragraph, this is an image that shows a bar graph with this description. If those tags are missing, wrong, or in the wrong order, the document fails — regardless of how beautiful it looks on the page.
This is the part most designers have never been asked to think about, and it's the part that's increasingly becoming a liability.
The Compliance Landscape Is Shifting
The legal and regulatory case for accessibility has been building for years. Here’s where it stands:
The Americans with Disabilities Act has increasingly been applied to digital and document accessibility through enforcement actions, settlements, agency guidance, and litigation. The Department of Justice’s 2024 Title II rule now gives state and local governments clearer requirements for accessible web content and mobile apps, including many documents made available online. For organizations that receive public funding, serve public functions, or work closely with government entities, the practical expectation is moving in one direction: documents need to be accessible, too.
Section 508 of the Rehabilitation Act requires that federal agencies and their contractors produce accessible electronic documents. If your clients include any organization that contracts with the federal government — and in the mission-centered sector, that's a significant portion of the landscape — 508 compliance is already a contractual requirement, whether or not anyone has been enforcing it.
The European Accessibility Act’s main requirements began applying on June 28, 2025, setting accessibility expectations for a broad range of covered products and services in the EU, including many digital services and customer-facing communications tied to those services.
The trend line is clear: Accessibility requirements are expanding, not contracting. The organizations that haven't been asking their designers about this are starting to. The designers who don't have an answer are going to find themselves at a disadvantage.
“I’ll Just Have AI Fix It”
This is the response that’s coming. Adobe is already building AI remediation into Acrobat. The tools will get better. And yes: for simple, well-structured documents, AI-assisted remediation will become genuinely useful.
But here’s the thing: AI remediation works best on documents that were already built with some structural discipline. It reads visual formatting and infers meaning — a large, bold line of text is probably a heading, a smaller indented block is probably a list. When the visual formatting is consistent and intentional, the inference is reasonably accurate.
When it isn't — when styles have been overridden manually, when heading styles have been applied for visual effect rather than structure, when reading order has never been considered — AI remediation produces mediocre output that still requires manual review, still fails edge cases, and still can't fully reconstruct the intent behind a layout that was never designed with structure in mind.
The designers who understand accessibility will use AI remediation as a final check. Everyone else will use it as a crutch, get inconsistent results, and wonder why their documents still fail accessibility audits.
Remediate or Rebuild?
When an accessible version of an existing document is needed, whether a client requests it, a compliance requirement surfaces, or someone simply notices that a PDF fails a screen reader, there are two paths: remediate the existing file, or rebuild it from the source.
The right answer depends almost entirely on how the original document was built.
Remediation is viable when:
Paragraph styles were applied consistently throughout the document, even if Export Tags were never set
The layout is relatively simple — single column, minimal floating elements, straightforward table structure
The document is a one-time piece that won't be reused as a template
The source file is unavailable and you're working directly in Acrobat
Rebuilding makes more sense when:
Styles were applied inconsistently, or overridden with manual formatting throughout
The document is a template that will be used repeatedly — remediation debt compounds with every use
The layout is complex and reading order is fundamentally broken
The document needs to live in multiple formats beyond print PDF
The diagnostic is simple: open the Paragraph Styles panel in InDesign. A clean list of named styles with no override indicators means the structure is there and remediation is workable. A panel full of manual overrides (styles named things like “Body Text copy 3” and “Heading 2 - modified”) means the document was built without style discipline, and remediation will be slower and more fragile than a rebuild.
This is why the remediate-or-rebuild question is really a question about how the document was built in the first place. The cost of accessibility isn't in the remediation. It's in the recovery from not building it in correctly from the start.
What It Actually Costs to Do It Right
Here’s the argument that tends to land best with designers who are skeptical about adding accessibility to their practice: if you're already using styles correctly, you're most of the way there.
A designer who builds documents with consistent paragraph styles, logical heading hierarchy, and named swatches is already doing the structural work that accessibility requires. Adding Export Tags to a well-built style system takes twenty minutes, once, when the template is created. Writing alt text for images adds a few minutes per document. Running the Acrobat accessibility checker before delivery adds maybe ten.
The marginal cost of building accessibility in from the start is low. The cost of remediation after the fact, or worse, of rebuilding a document that was never structured correctly, is high. And the cost of a client discovering that the materials you produced for them fail ADA compliance is higher still.
For communications directors evaluating design contractors, it’s worth asking about directly. Not “do you know about accessibility,” but “walk me through how you set up paragraph styles and Export Tags in your InDesign templates.” The answer will tell you what you need to know.
For designers: the accessibility conversation is coming whether you initiate it or not. The ones who get ahead of it will have a skill that differentiates them. The ones who wait will be retrofitting documents under deadline pressure.
The Bottom Line
Accessibility isn’t a specialization. It's a dimension of craft like color management, or print production, or proper file handoff. You don’t have to be an accessibility consultant to produce accessible documents. You have to understand the tools you're already using well enough to use them with structural intention.
The compliance pressure is real and growing. The AI remediation shortcut is less reliable than it sounds, and the cost of doing it right from the start is, in most cases, genuinely low.
The question isn’t whether accessibility belongs in a designer’s skillset. It’s whether you'd rather build it in now or pay for it later.
