Section 508 for Federal Websites: ICT Baseline v3.1 Workflow

Section 508 requires covered federal information and communication technology, including public-facing websites, to conform to the Revised 508 Standards, which are mapped to WCAG 2.0 Level A and AA. If your organization builds, buys, or hosts web content for a federal agency, the first two moves are simple: confirm whether your content falls under the E205 scoping categories, then set an ICT Testing Baseline for a representative sample of pages.
TL;DR:
- Most non-compliant issues stem from recurring mistakes at the content and code level, such as missing alt text, improper heading order, and low contrast, not complex edge cases.
- Effective compliance requires defining scope early using the ICT Testing Baseline and assigning a dedicated owner to ongoing accessibility maintenance.
- Procurement processes must include vendor testing, detailed conformance reports, and contractual remediation timelines to prevent inheriting accessibility gaps.
- Manual keyboard-only testing and screen reader walkthroughs are crucial, as automated scans often miss focus traps, focus order issues, and assistive technology barriers.
- Maintaining compliance is an ongoing effort that demands regular retesting, documentation, and clear responsibilities among agencies and contractors to mitigate enforcement risks.
Table of Contents
- What Section 508 Covers: Law, Timeline, and Scope of ICT
- How Section 508 Maps to WCAG (What Level A/AA Means for Your Site)
- Practical Compliance Workflow: Policy, Procurement, and Acquisition Checkpoints
- Design, Development, and Content Practices to Meet Section 508
- Testing and Evidence: ICT Testing Baseline and a Composite Testing Approach
- Governance, Accessibility Statements, and Complaint Handling Best Practices
- Why Trust This Guide: Tatem Web Design’s Relevant Experience and Available Services
- Detailed Guidance on Remediation Strategies for Existing Non-Compliant Web Content
- Role and Responsibilities of Federal Agencies or Contractors in Maintaining Compliance
- Case Studies or Examples of Enforcement Actions and Their Implications
- Updates and Differences Between Section 508 and Other Accessibility Standards
- Common Challenges and Pitfalls in Achieving Section 508 Website Accessibility Compliance
- What This Guide Gets Right That Most Advice Misses
- If You Need Hands-On Help: Tatem Web Design Services for Accessibility and Compliance
- Primary Resources and Tools to Consult
- Sources
- FAQ
What Section 508 Covers: Law, Timeline, and Scope of ICT
Section 508 is a federal law that governs information and communication technology used or provided by federal agencies. The Revised Section 508 Standards final rule was published on January 18, 2017, and took effect January 18, 2018, replacing the older 508 standards with requirements built around modern web and software technology, according to the Department of the Interior’s overview.
Scope matters more than most teams assume. The E205 scoping provisions determine which electronic content counts, and coverage extends well past a public homepage:
- Public-facing agency websites and web applications
- Agency intranets and internal tools used by federal employees
- Electronic documents distributed by or for an agency, including PDFs
- Software procured or developed for agency use
- Multimedia content, including video and audio, published by an agency
Private businesses are not automatically bound by Section 508. Obligations typically arise when a company contracts with a federal agency or builds a deliverable an agency will use, according to Section508. A Florida landscaping company’s marketing site has no Section 508 exposure; the same company’s website built under a federal facilities contract likely does.
How Section 508 Maps to WCAG (What Level A/AA Means for Your Site)
The Revised 508 Standards do not reinvent accessibility rules. They incorporate WCAG 2.0 Level A and Level AA Success Criteria directly for covered web content, according to Section508.gov’s applicability guidance, with narrow non-web exceptions for hardware and certain closed functionality.
In practice, this means your team is checking against four principles: perceivable, operable, understandable, and robust. That translates into concrete, testable items:
- Alt text on meaningful images, decorative images marked so screen readers skip them
- Captions on prerecorded video and transcripts for audio-only content
- Keyboard access to every interactive element without a mouse
- Contrast ratios that meet WCAG 2.0 AA thresholds for text and interface components
- Semantic structure using proper heading order and landmark regions
- Labeled forms with clear instructions and accessible error messages
Pro Tip: Run a full keyboard-only pass on your site before any automated scan. It surfaces focus-order and trap issues a scanner will never catch.
WCAG 2.2 guidance appears in some federal testing materials as explanatory reference, but the actual conformance target for Section 508 remains WCAG 2.0. Do not promise a client or an auditor WCAG 2.2 AA as your compliance baseline; it is not what the regulation requires.
Practical Compliance Workflow: Policy, Procurement, and Acquisition Checkpoints
Turning Section 508 into a working program means building the process before you build the page. Section508.gov and GSA lay out several components that consistently separate organizations that pass audits from those that scramble during a complaint investigation, according to Section508.gov.
- Write an accessibility policy that names who signs off on releases and how often existing content gets reviewed.
- Use the Accessibility Requirements Tool (ART) early in procurement to identify which 508 provisions apply to a specific purchase.
- Require an Accessibility Conformance Report (ACR), often built on a VPAT, from any vendor before signing a contract.
- Test the actual deliverable rather than accepting a vendor’s self-reported ACR at face value.
- Write acceptance-testing and remediation-timeline language into the contract so noncompliance has a documented, enforceable fix path.
Procurement is where a surprising amount of 508 risk originates. A contract that never asks for evidence, and never tests what arrives, inherits every accessibility gap the vendor shipped.
Design, Development, and Content Practices to Meet Section 508
Most 508 failures trace back to a small set of recurring mistakes at the authoring and code level, not exotic edge cases. Fixing them is mostly discipline, not new tooling.
Content authors carry a specific set of responsibilities:
- Write alt text that describes the image’s purpose, not its filename
- Keep heading levels in order (H1, then H2, then H3) instead of skipping for visual size
- Use descriptive link text (“download the 2026 accessibility policy”) instead of “click here”
- Label every form field and write error messages that say what went wrong and how to fix it
Developers own a parallel checklist: build with semantic HTML elements instead of generic divs styled to look like buttons, preserve a logical keyboard focus order, avoid layering ARIA roles onto elements that already have native semantics, and keep visible focus indicators and skip-to-content links intact through every redesign.
Pro Tip: Test your site with at least one real screen reader, such as NVDA or VoiceOver, before launch. Automated tools miss the experience gaps that assistive technology users hit first.
Documents and media need their own checkpoints: tag PDFs with proper reading order, provide captions and transcripts for video and audio, and confirm any embedded media player supports keyboard control and assistive-technology compatibility.
Testing and Evidence: ICT Testing Baseline and a Composite Testing Approach
The ICT Testing Baseline Web v3.1, published April 1, 2024, is the recommended federal starting point for evaluating Revised Section 508 conformance. It is a benchmark, not a finished audit process.
The Baseline sets minimum evaluation requirements, published April 1, 2024, for federal ICT accessibility testing. Treat it as one input among several: automated scans catch a portion of issues fast, but manual keyboard-only review, screen-reader walkthroughs, task-based evaluations, and regression testing after every release catch the rest.
A composite approach generally combines:
- Automated scanning tools for quick, repeatable coverage of common code-level errors
- Manual keyboard-only navigation testing across primary user flows
- Screen reader testing (NVDA, JAWS, or VoiceOver) on representative pages
- Task-based evaluations that mirror what a real visitor needs to accomplish
- Regression testing after each content or code deployment
Keep the paper trail. Auditors and complainants both respond to documented evidence: test results by page, issue tickets tied to specific WCAG criteria, remediation logs showing what changed and when, and retest records confirming the fix held.
Governance, Accessibility Statements, and Complaint Handling Best Practices
An accessibility statement is not boilerplate. It should state the scope of your conformance claim, list contact options for reporting a barrier, give an expected response time, and disclose known limitations rather than implying a perfect site.
DOJ guidance on accessibility statements points to what actually makes a complaint actionable: the exact URL, the browser and operating system, the assistive technology in use, the steps that reproduce the problem, and a timestamp, according to the DOJ’s accessibility statement guidance.
Build an intake process around that structure:
- A visible, easy-to-find contact method for reporting barriers
- A required-fields form or email template that collects URL, environment, and reproduction steps
- A documented triage and remediation timeline, tracked in an issue system
Transparent, timestamped tracking does more than tidy your files. It shows a pattern of good-faith remediation, which measurably reduces exposure if a complaint ever escalates to formal enforcement review.
Why Trust This Guide: Tatem Web Design’s Relevant Experience and Available Services
An experienced web design agency offers services including AI-driven cybersecurity compliance consulting for frameworks like CMMC Level 2 and HIPAA, serving Florida businesses, professional practices, and government-adjacent organizations. This compliance-consulting experience supports 508 work such as scoping content, aligning audits, conducting remediation, training teams, and creating accessible procurement language. The same discipline used in cybersecurity documentation and audit evidence applies to accessibility testing records, issue tracking, and retest verification.
Detailed Guidance on Remediation Strategies for Existing Non-Compliant Web Content
Fixing an existing site is a different job than building a new one accessibly from the start. Start with a triage pass instead of trying to fix everything at once.
Rank issues by severity and reach. A missing skip link affects every keyboard user on every page; a poorly labeled contact form affects one workflow. Fix the widest-reach, highest-severity issues first: broken keyboard traps, missing form labels, and low-contrast text typically top that list because they block task completion outright.
Group fixes by root cause rather than by page. If your CMS template lacks a proper heading structure, fixing the template once fixes every page that inherits it, which is far more efficient than editing pages individually. The same logic applies to a broken focus style in your CSS framework or a captioning gap across a video library.
Set a realistic remediation timeline and document it. Federal partners and auditors respond better to a published schedule with dates than to a vague promise of “ongoing improvement.” Batch related fixes into sprints: one sprint for document tagging, one for form and error-message repairs, one for media captioning.
Retest after every batch, not just at the end. A fix that solves one WCAG criterion sometimes breaks another, particularly around focus order and ARIA attributes, so regression testing catches new problems before they reach production. Keep before-and-after evidence for every batch, since that record is what demonstrates good-faith progress if a complaint or audit ever asks for it.

Role and Responsibilities of Federal Agencies or Contractors in Maintaining Compliance
Federal agencies carry the primary legal obligation under Section 508, but the practical work of staying compliant is distributed across several roles inside and outside government.
Agencies are responsible for setting internal policy, training staff who create or publish content, and applying the Accessibility Requirements Tool during procurement to make sure a purchase’s 508 obligations are explicit before money changes hands. Agency compliance offices also typically own the accessibility statement, the public complaint channel, and the recordkeeping that documents remediation over time.
Contractors and vendors inherit specific obligations once they sign on to build or supply ICT for an agency. That includes delivering an accurate Accessibility Conformance Report, often built on a VPAT, rather than a boilerplate one copied from a different product. It includes fixing issues an agency identifies during acceptance testing within the timeline the contract specifies. It also includes maintaining accessibility through the life of the contract, not just at initial delivery, since a redesign, a plugin update, or a new third-party widget can quietly reintroduce barriers that passed testing at launch.
The split works best when it is written into the contract explicitly: which party runs ongoing testing, who owns remediation after launch, and what documentation changes hands at each milestone. Contracts that leave this vague tend to produce disputes later about whose responsibility a given accessibility gap actually is.

Case Studies or Examples of Enforcement Actions and Their Implications
Section 508 enforcement generally moves through agency-level complaint processes rather than the kind of public lawsuit that characterizes some ADA cases, and DOJ accessibility guidance frames the complaint path around detailed reproduction evidence rather than broad allegations, according to the DOJ’s accessibility statement guidance.
A pattern that shows up repeatedly in accessibility complaint handling: reports that include a specific URL, the assistive technology used, the exact steps that trigger the barrier, and a timestamp move through review faster and produce a clearer resolution than vague complaints. The practical implication for any organization managing federal ICT is that your own intake process should be built to capture that same level of detail from the start, since it mirrors what reviewing bodies expect to see.
The other consistent lesson from how these processes work is that documentation before a complaint arrives matters as much as the fix itself. An organization that can show a dated accessibility policy, testing records tied to the ICT Testing Baseline, and a remediation log demonstrating a pattern of good-faith fixes is in a fundamentally different position than one that has no paper trail at all, regardless of how the underlying code compares. Enforcement risk, in practice, tracks recordkeeping discipline as closely as it tracks the accessibility of the code itself.
Updates and Differences Between Section 508 and Other Accessibility Standards
Section 508, the ADA, and WCAG are related but not identical, and mixing them up in a compliance plan creates real gaps.
Section 508 is a federal statute that applies to federal agencies’ ICT and to contractors delivering ICT under federal contracts. It incorporates WCAG 2.0 Level A and AA as its technical reference, according to Section508.gov. The ADA is a broader civil rights law covering public accommodations and, depending on the entity, can apply to state and local government sites and to many private businesses; it does not itself specify a web technical standard the way Section 508 does. A separate Tatem Web Design guide to ADA compliance walks through when ADA obligations apply distinctly from Section 508’s federal scope.
WCAG itself is a technical standard published by the W3C, not a law. Version 2.0 is what Section 508 currently references. WCAG 2.1 added criteria for mobile accessibility and low vision, and WCAG 2.2 added further criteria, but neither is the official Section 508 conformance target as of this writing. WCAG 3.0 remains in draft and is not a conformance reference for any current U.S. regulation.
The practical takeaway: know which law applies to your organization, and build to WCAG 2.0 AA as your Section 508 floor even if you also choose to adopt later WCAG versions as an internal best practice.
Common Challenges and Pitfalls in Achieving Section 508 Website Accessibility Compliance
Most organizations do not fail Section 508 because of a single hard problem. They fail because of a handful of recurring, avoidable gaps.
Scoping comes first on the list. Teams often assume their entire site needs the same level of scrutiny, or conversely assume a section is exempt when it is not, according to Section508.gov’s scope guidance. Starting with generic automated scans before determining actual scope wastes effort and produces a false sense of coverage.
Third-party content is another common blind spot. Embedded video players, chat widgets, and payment forms built by outside vendors frequently fail 508 checks even when the surrounding site passes, because the organization never asked the vendor for evidence of conformance.
Procurement is the third recurring failure point. Contracts that skip an ACR/VPAT request, or accept one without verifying it, inherit whatever accessibility gaps the vendor’s product already has, according to Section508.gov’s guidance on mapping WCAG to functional performance criteria.
Maintenance drift rounds out the list. A site that passes an audit at launch can lose conformance months later through a plugin update, a redesigned component, or a content editor who did not receive training. Treating 508 as a one-time project instead of an ongoing practice is the single most common reason organizations that passed a prior review fail a later one.
What This Guide Gets Right That Most Advice Misses
Most Section 508 content online treats the rule as a checklist you run once and file away. That framing is the biggest thing working against organizations that actually have to maintain compliance. The Revised 508 Standards do not expire when your site launches, and neither does the risk.
The conventional advice overweights automated scanning tools and underweights everything else in a composite testing approach. A clean scan report feels like proof of compliance. It is not. Keyboard traps, confusing focus order, and screen-reader-hostile widgets routinely pass automated checks and fail the first real user who relies on assistive technology.
If you take one thing from this guide, prioritize scope and governance before you touch a line of code. Know which content is actually covered, assign a real owner to accessibility maintenance, and build your testing process around the ICT Testing Baseline rather than a single tool’s dashboard. Everything else, from alt text to ARIA attributes, is easier to get right once that structure exists, and far harder to sustain without it.
— Matt
If You Need Hands-On Help: Tatem Web Design Services for Accessibility and Compliance
Building a Section 508 program while also running a business is a lot to carry alone. Services are available that map directly onto the workflow in this guide, from initial audit through ongoing maintenance.
- AI Web Design for building or rebuilding pages with accessible structure from the start
- ADA and WCAG accessibility services for audits and remediation of existing content
- Cybersecurity and compliance consulting, including CMMC 2.0 and HIPAA work, for organizations already managing federal or regulated obligations
- Website hosting plans, including Launch, Enhance, Grow, and Expand, which support ongoing regression testing as pages change
For teams building for a federal partner directly, our defense contractor web design services address contract-driven compliance needs specifically. Call 772-224-8118 or visit our AI services page to talk through what an audit and remediation plan would look like for your site.
Primary Resources and Tools to Consult
For the rule text and scoping questions, start with Section508.gov’s applicability and conformance guidance. For testing methodology, use the ICT Testing Baseline Portfolio. For procurement tools like ART and ACR guidance, see Section508.gov’s laws and policies page. For complaint handling and accessibility statement structure, consult DOJ’s accessibility statement guidance. A complementary process view is available from Mastermind Advisor’s five-stage ADA workflow.
Sources
FAQ
What Are the Section 508 Compliance Requirements for Websites?
Covered federal websites must conform to the Revised 508 Standards, which incorporate WCAG 2.0 Level A and AA success criteria for content that falls under the E205 scoping categories. That includes public-facing pages, many electronic documents, and embedded media, evaluated using the ICT Testing Baseline as a starting methodology.
How Do I Know if My Website Is 508 Compliant?
You need documented evidence, not a guess: run automated scans plus manual keyboard and screen-reader testing against the ICT Testing Baseline Web v3.1, sampled across representative task-based pages. A site is compliant when that combined testing shows it meets WCAG 2.0 A/AA criteria and you can produce records of the testing and any remediation.
Does Section 508 Require WCAG?
Yes, the Revised Section 508 Standards directly incorporate WCAG 2.0 Level A and Level AA as the technical conformance reference for covered web content. Later WCAG versions like 2.1 or 2.2 may appear in explanatory materials, but they are not the official Section 508 conformance target.
Does Section 508 Apply to the Public?
Section 508 applies directly to federal agencies and to contractors delivering information and communication technology under federal contracts, not automatically to private businesses or the general public, according to Section508.gov. A private company may face separate accessibility obligations under the ADA depending on its own contracts, services, or state and local rules.
Recommended
Tatem Web Design
26+ YearsWeb Design & SEO Specialist · Tatem Web Design
Matt Tatem has been designing websites professionally since 1999, making Tatem Web Design one of Florida's longest-running web agencies. Based in Stuart, FL, he specializes in WordPress, local SEO, Shopify e-commerce, and cybersecurity consulting for small businesses.

CMMC Level 2 vs Level 1: Which One Applies to You?
CMMC Level 1 vs Level 2 compared: data types, 15 vs 110 requirements, self-assessment vs third-party audits, POA&M rules and how to pick your level.

Phishing Awareness Training for Small Business: A Practical Guide
How to build phishing awareness training for a small business: what to teach, how to run simulations, which numbers to track, and what to pair it with.

AI Content Pricing: What Florida Businesses Really Pay in 2026
What AI content costs in 2026: per-post ranges, tool subscriptions, editing time and agency retainers, plus how to budget and avoid hidden costs.

