A federal rule requires state and local governments to make the digital documents they post accessible to people with disabilities, and that includes PDFs. Because agencies post the qualifications packages and deliverables they receive from consultants, the requirement is reaching the A/E firms that produce them, usually as a clause in the RFP.
Two things are worth knowing before your first clause arrives. The compliance dates moved in April 2026, so much of the guidance still circulating is wrong. And the requirement is almost never what firms have been told it is, which matters because a wrong belief produces the wrong fix. When it does reach you, it arrives as a condition of acceptance: remediation at your cost, a deliverable held at review, or a submittal that misses a stated requirement.
What Is the ADA Title II Accessibility Rule?
The rule sits under Title II of the Americans with Disabilities Act, which covers state and local government entities: cities, counties, transit agencies, school districts, public colleges and universities, and special districts. In 2024 the Department of Justice adopted WCAG 2.1 Level AA as the technical standard for those entities' web content and mobile apps.
The part that matters to a proposal team is the scope. The rule covers conventional electronic documents the entity posts, including PDF, word processing, spreadsheet, and presentation files. There is an exception for documents that already existed before the compliance date, unless they are currently used to apply for or access a service.
So a stack of archived 2019 SOQs on a county website is largely out of scope. A current solicitation package, a standing consultant roster, or the design report your firm delivered last month and the agency posted is not.
When Do the Accessibility Deadlines Actually Hit?
This is the part that changed, and it changed recently enough that most industry guidance still has the old dates.
On April 20, 2026, DOJ published an interim final rule (91 FR 20902) extending both compliance dates by one year. It took effect the day it published, and its comment period closed June 22, 2026.
| Entity | Original date | Current date |
|---|---|---|
| State or local government serving 50,000 or more | April 24, 2026 | April 26, 2027 |
| Smaller entities and special district governments | April 26, 2027 | April 26, 2028 |
Neither the standard nor the scope changed. Only the clock. If somebody told you this was a spring 2026 problem, it is now a spring 2027 problem for your larger public clients, and a 2028 problem for the water districts, irrigation districts, and small municipalities that fill out a lot of a civil firm's client list.
That is not a reason to ignore it for a year. It is a reason to do the work deliberately rather than under deadline pressure, because the panic version of this work is document-by-document remediation, and that is the expensive version.
Why This Reaches A/E Firms and Not Just Agencies
There are two paths from an agency's obligation to your submittal.
The first is direct. The rule reaches content that contractors post on the entity's behalf, because responsibility stays with the entity. If your firm posts anything to a client's site, that content carries the requirement.
The second path is the common one: agencies post what you send them. Board packets with your SOQ attached, selection results, environmental documents, planning studies, design reports, public meeting exhibits. Once it is on the agency's site, it is the agency's web content and it has to meet the standard.
Agencies solve that the cheapest way available, which is to push it into procurement. The guidance written for public buyers says exactly that: put it in the solicitation, make it a condition of acceptance, flow it down to subconsultants. Expect a submittal instruction, a deliverable acceptance criterion, or a request for an accessibility conformance report, which states how your document conforms and where it does not.
California already ran this experiment. California law requires state entities to comply with Section 508 (Government Code section 7405), and Caltrans states plainly that as of July 1, 2019, environmental documents not in compliance can no longer be posted on the Caltrans internet. A consultant-produced document that fails accessibility does not get published. That flow-down is seven years old.
Does Section 508 Already Cover This for Federal Work?
Firms doing federal work already have a version of this. Section 508 of the Rehabilitation Act requires federal agencies to make their electronic content accessible, and the Revised 508 Standards adopt WCAG 2.0 Level A and AA for electronic content.
Those standards apply to non-web documents, not just websites. Four WCAG criteria are excepted because they only make sense for websites, all of them about navigating between pages. Everything else carries over, which means a PDF you deliver is held to nearly the same standard as the agency's own web pages.
| Section 508 | ADA Title II | |
|---|---|---|
| Who it obligates | Federal agencies | State and local government entities |
| Technical standard | WCAG 2.0 Level A and AA | WCAG 2.1 Level AA |
| How it reaches your firm | Contract terms on deliverables | Submittal and contract clauses, plus anything the agency posts |
| In force | Since 2018 | April 2027 or April 2028, by client size |
So a report or exhibit set delivered under a federal contract has carried this expectation for years. What is new is the same expectation arriving from cities, counties, transit agencies, and state DOTs, where most of the industry's volume sits. Firms working state DOT prequalification and local on-call and IDIQ contracts should expect it there first.
What the Rules Actually Require (It Is Not Fonts and Margins)
This is where most firms get bad information, and the bad information leads to the wrong fix.
Neither WCAG nor the DOJ rule specifies a typeface, a point size, or a page margin. There is no rule that says Arial 11. There is no rule that says one-inch margins.
Those specs come from agency style guides. Plenty of public agencies publish accessible-document guidance recommending sans-serif type at 11 or 12 points with generous margins, and some of it is finding its way into submittal instructions. Following it is fine. Believing it is the requirement is the problem, because a proposal set in Arial 11 with one-inch margins can still fail every test that matters.
| What firms are told | What the standard actually tests |
|---|---|
| Use Arial at 11 points | The text is real text, not a picture of text |
| Use one-inch margins | Reading order follows the visual order |
| Avoid small type | Headings are tagged as headings, in hierarchy |
| Keep the layout simple | Images have alternative text, or are marked decorative |
| Use dark text on white | Contrast meets a measurable ratio, 4.5:1 for normal text |
| Send it as a PDF | Tables identify their header rows and columns |
The Access Board publishes an ICT Testing Baseline for Electronic Documents, the closest thing to an official checklist. Its tests cover content structure and headings, meaningful sequence, images and alternative text, tables, links, document title, language, and contrast.
Read that list next to your last submittal and the gap becomes obvious.
What Breaks in a Typical AEC Proposal Template
AEC marketing collateral fails accessibility in a few predictable ways, and they repeat from firm to firm because the production habits do.
- Project sheets exported as flat images. A page laid out in a graphics tool and flattened contains no readable text at all. To a screen reader it is a blank page. This is the failure worth checking first, and it lands hardest on project experience sheets, because the most carefully designed page in your package is the one most likely to be flattened.
- Multi-column resumes with no reading order set. A two-column resume reads across the columns instead of down them unless the reading order is defined. The content is all there and the sequence is nonsense.
- Headings that are only styled, never tagged. Bold, larger, brand-colored text looks like a heading to you. Unless it is tagged as one, it is just big text, and nobody navigating the document by structure can find it.
- Org charts, project photos, maps, and logos with no alternative text. An org chart carries more information per square inch than anything else in the package and is the least likely to carry a text alternative. An evaluator using a screen reader gets silence where your team structure should be.
- Data tables without header rows. Fee schedules, staffing matrices, project reference tables, prequal grids. Without identified headers, a screen reader reads a wall of cells with no idea which column they belong to.
- Brand colors that miss contrast. Light gray subheads, colored callout boxes, white type over a photograph. Many AEC palettes were chosen for print and never checked against a 4.5:1 ratio.
- Scanned appendices. Licenses, certifications, DBE and SBE letters, insurance certificates. Scanned and appended, every one of them is an image.
Every item on that list is a template decision. None of them is a writing decision. That distinction is the whole problem.
Why Accessibility Is a Template Problem, Not a Document Problem
Accessibility work goes badly at A/E firms, and not because the requirements are hard.
If your staff resumes and project sheets exist as individually formatted files, then meeting the requirement means opening and fixing every file. A firm with 60 staff resumes and 200 project sheets has 260 remediation jobs. Then it has 260 more the next time a client format changes, the brand gets refreshed, or a principal gets promoted and every resume needs a new title.
If the same content lives as structured records (staff, projects, certifications, past performance) and the format is applied at generation, accessibility becomes a property of the template. Fix the template once and everything generated afterward inherits the fix.
This is the same argument as managing multiple resume versions and building a reusable qualifications library, arriving from a different direction. Accessibility is one more format requirement in a job that already has too many: this client's SOQ format, that state's prequal form, the federal form, the brand refresh. Each is cheap when content and format are separate and expensive when they are welded together.
RFPM.ai keeps staff and project information as structured records and applies formatting at generation, so a template change propagates instead of being redone per document. A person still decides which staff and which projects belong in a package. What changes is how many format requirements a small team can absorb without adding headcount.
This is the argument for structured content generally, not for any particular tool. A firm that solves it with disciplined Word styles and a strict template library has solved it. The only question is whether that discipline survives a Friday deadline, which is the same question behind every build-or-buy decision.
What to Do Before Your First Accessibility Clause
- Sort your public clients by deadline. Serving 50,000 or more means April 26, 2027. Everything else, including special districts, means April 26, 2028. Most firms' client lists split across both dates, and the earlier one usually holds your largest accounts.
- Read the submittal instructions on your next three public RFPs. Search them for accessibility, 508, WCAG, ADA, remediation, and conformance. That tells you whether this has reached your market yet, which is worth more than any prediction.
- Test one project sheet and one resume. Open the PDF and try to select the body text with your cursor. If you cannot select it, it is an image and the document fails outright. Then run Acrobat's built-in accessibility check. Five minutes tells you the size of your problem.
- Fix the template, not the file. Whatever the test surfaces, apply it upstream. Remediating one submittal buys you one submittal.
- Price the surprise case before it surprises you. Decide what happens when a clause appears mid-pursuit on a proposal you want. Remediation is a service you can buy per document, and for a single pursuit that is almost always the right call. Get a quote while you are not under deadline, then settle who owns the cost and whether it goes in the fee. It is scope, not a favor.
- Check your deliverables, not just your proposals. Reports, studies, plan sets, and public-meeting exhibits are more likely to be posted on an agency website than your SOQ is. The contract clause may land on the deliverable side first.
When This Is Not Your Problem Yet
An honest counterweight, because a compliance headline is a bad reason to rebuild a marketing library.
If your work is mostly private, this is a watch item and not a project. Developers, industrial owners, and private institutional clients carry no Title II obligation. And if you already deliver under federal contracts, you likely have some version of this running. Extend it to your state and local pursuits rather than starting over.
And if one RFP asks for something you cannot produce, buy the remediation for that pursuit and move on. Re-cutting a whole template library over a single solicitation is an overreaction. The trigger is a pattern across clients, not one instance. Just do not bet on the pattern never forming. The dates are on the calendar, and they apply to the clients most civil, transportation, and municipal firms depend on.
Frequently Asked Questions
Does my proposal have to be ADA compliant?
Not directly. The obligation belongs to the public agency, not to your firm. It reaches you when the agency posts your document on its website, or when it writes accessibility into the RFP or the contract as a submittal or deliverable requirement. That is happening more often as the compliance dates approach.
What is ADA Title II?
Title II of the Americans with Disabilities Act covers state and local government entities, including cities, counties, transit agencies, school districts, special districts, and public universities. A 2024 Department of Justice rule set WCAG 2.1 Level AA as the technical accessibility standard for those entities' web content, mobile apps, and posted documents.
When is the ADA Title II compliance deadline?
April 26, 2027 for state and local entities serving 50,000 people or more, and April 26, 2028 for smaller entities and special district governments. Both dates were extended by one year in an interim final rule published April 20, 2026. The original dates were April 24, 2026 and April 26, 2027.
Does WCAG require a specific font or margin size?
No. Neither WCAG nor the DOJ rule names a typeface, a point size, or a page margin. Guidance recommending sans-serif type at 11 or 12 points comes from individual agency style guides, not from the standard. The standard tests structure, reading order, alternative text, table headers, and measurable color contrast.
What makes a PDF accessible?
The text has to be real selectable text, not an image. Headings must be tagged in a proper hierarchy, reading order must follow the visual order, images need alternative text or a decorative marking, data tables need identified headers, and color contrast has to meet a measurable ratio. The document also needs a title and a declared language.
Does Section 508 apply to A/E consultants?
Section 508 obligates federal agencies, but the obligation flows to contractors through contract terms, because an agency cannot accept a deliverable it is not allowed to publish. If you deliver electronic reports, studies, or exhibits under a federal contract, expect the requirement in your scope.
Who is responsible if the agency posts my document and it is not accessible?
The agency carries the legal obligation. In practice, agencies manage that risk by moving it into procurement, which means the cost of a non-conforming document tends to land on the firm that produced it, as remediation at your expense, a rejected deliverable, or a delayed acceptance.