Oregon's ADA Title II deadline.
What Oregon state and local governments must do to make their websites, apps, and documents accessible — the standard, the dates, and how to get there in time.
The short version
Under the U.S. Department of Justice's 2024 ADA Title II rule, Oregon state and local governments must make their websites, mobile apps, and online documents meet WCAG 2.1 Level AA. Entities serving 50,000 or more people had to comply by April 24, 2026. Entities serving fewer than 50,000 people and special district governments have until April 24, 2027. PDFs and other posted documents are included.
If you run a city, county, school district, community college, library, transit agency, or special district in Oregon, this rule applies to you. The good news: it is a defined, testable standard, and the work — audit, remediate, verify — is well understood.
The deadlines
-
April 24, 2026 deadline
Public entities serving a population of 50,000 or more. This date has passed — larger Oregon governments are already obligated, and non-conforming content is a live compliance risk today.
-
April 24, 2027 deadline
Public entities serving fewer than 50,000 people, and special district governments of any size. Most Oregon cities, school districts, and special districts fall here — and the clock is running.
What the rule requires
The standard is WCAG 2.1 Level AA. That covers keyboard operability, sufficient color contrast, text alternatives for images, captions for media, clear labels and structure, and content that works with screen readers and other assistive technology. Building to the current WCAG 2.2 AA meets and exceeds the requirement.
It applies to the content the public uses: your website, your mobile apps, and the documents you post — including PDFs, forms, agendas, and reports. For most agencies, the document backlog is the largest single piece of the work.
- Websites
- Mobile apps
- PDFs & documents
- Online forms
- Video & media
- Third-party tools you use
What's exempt (narrowly)
The rule includes limited, conditional exceptions — don't assume most of your content qualifies:
- Certain archived web content that meets specific conditions;
- Preexisting conventional electronic documents, unless they're used to apply for or access a service;
- Third-party content not posted by or on behalf of the government;
- Individualized password-protected documents (for example, a specific person's records);
- Preexisting social media posts.
Each exception has conditions, and anything used to apply for, access, or participate in a government service generally must be accessible. When in doubt, treat it as in scope.
A practical path to compliance
-
1. Audit
Test your site, apps, and a representative sample of documents against WCAG 2.1/2.2 AA. You get a prioritized findings list mapped to the exact criteria.
-
2. Remediate
Fix the website and apps, and work through the document backlog — tagging PDFs, adding alt text and reading order, and correcting structure and contrast.
-
3. Verify & document
Re-test with assistive technology, confirm conformance, and keep the records — useful for procurement, grants, and any complaint response.
-
4. Maintain
Set a standard so new content ships accessible: templates, author training, and a check in your publishing workflow.
How Auto-Flow helps Oregon agencies
We're a Portland-based, SDVBE-certified studio, so Oregon agencies can contract us directly. We do the audit and the remediation — websites, apps, and the PDF backlog — and every fix is tested with real assistive technology before it ships. Start free below, or send us your site and document set for a scoped quote.
-
Free WCAG scanner
Paste a URL and get a free WCAG 2.2 report ranked by impact — a fast gut-check on where you stand.
Scan a page free -
PDF remediation studio
Upload a PDF and tag, fix, and validate it for WCAG and PDF/UA compliance, then export an accessible file.
Open the PDF studio -
Full audit & remediation
The whole job, done and documented: audit, prioritized fixes, remediation of sites and documents, and verification for your records.
See the service
Frequently asked questions
What is the ADA Title II web accessibility deadline in Oregon?
Entities serving 50,000 or more people had to comply by April 24, 2026. Entities serving fewer than 50,000 people, and special district governments, must comply by April 24, 2027. It covers websites, apps, and posted documents.
What technical standard does it require?
WCAG 2.1 Level AA. Building to the current WCAG 2.2 AA meets and exceeds it.
Are PDFs and documents covered?
Yes. Documents you post — PDFs, Word files, forms — are web content and must meet WCAG 2.1 AA, meaning tagged, screen-reader-readable files with proper reading order, alt text, and language.
Are there exceptions?
A few narrow ones (certain archived content, some preexisting documents, third-party content, individualized password-protected files, preexisting social posts) — all conditional. Anything used to access a service must be accessible.
How do we actually get compliant?
Audit against WCAG 2.1/2.2 AA, remediate the site, apps, and document backlog, then re-test and document conformance. Auto-Flow does the audit and the remediation for Oregon agencies.
Is this the same as Section 508?
They're related but distinct: Section 508 covers federal agencies and federally funded programs; ADA Title II covers state and local governments. Both point to WCAG, so remediation work overlaps heavily.
Beat the 2027 deadline.
Send us your site and document set. We'll audit it, prioritize the fixes, and do the remediation — documented for your records.