Your cart is empty.
Keep shopping
Teach on Udemy
Turn what you know into an opportunity and reach millions around the world.
Learn MoreSection 508 Accessibility: Federal ICT Compliance
Section 508 Accessibility: Federal ICT Compliance
Master WCAG 2.1 Level AA, accessible documents, multimedia, testing, and federal Section 508 program management
Created byShamir George
Last updated 7/2026
English
What you'll learn
- Explain the history and legal authority of Section 508 under the Rehabilitation Act of 1973 as amended
- Describe the scope of the 2017 Section 508 Refresh and its incorporation of WCAG 2.1 Level AA standards
- Apply the four POUR principles — Perceivable, Operable, Understandable, Robust — to evaluate ICT conformance
- Create accessible Word, PDF, Excel, and PowerPoint documents that meet federal Section 508 requirements
- Implement captions, audio descriptions, and accessible media players for federal video and audio content
- Use automated and manual testing tools to evaluate websites and documents for Section 508 conformance
- Apply the Revised 508 Standards to ICT procurement decisions including Accessibility Conformance Reports
- Build and manage an agency Section 508 program covering training, reporting, remediation, and governance
Explore related topics
Course content
6 sections • 32 lectures • 2h 25m total length
- The Barrier Before the Law — Who Section 508 Actually Serves5:35Before a single statute or standard makes sense, one question has to be answered: what does a digital barrier actually feel like to the person who hits it? This lecture opens not with law but with people — a blind analyst whose screen reader announces 'image, image, image' on an untagged budget PDF, a federal employee with a motor disability who cannot submit a benefits form because it traps keyboard focus, a Deaf veteran locked out of an uncaptioned training video. By grounding the course in the real experience of visual, auditory, motor, speech, and cognitive disabilities, and in the assistive technologies people use to work around barriers, it answers the tension that drives everything that follows: accessibility is not a paperwork exercise or a checkbox — it is the difference between a citizen or coworker being able to do their job and get government services, or being shut out. Every technical requirement in this course exists to remove one of these barriers, and this lecture is why they matter.
- What Is Section 508? Law, Purpose, and Scope4:35If accessibility barriers are the problem, what is the legal force that requires the federal government to fix them? Section 508 of the Rehabilitation Act, codified at 29 U.S.C. § 794d, requires federal agencies to ensure the Information and Communications Technology (ICT) they develop, procure, maintain, or use is accessible to people with disabilities — both federal employees and members of the public. Originally enacted in 1986 and substantially strengthened by the Workforce Investment Act of 1998, it reaches a wide universe of ICT: websites, software, hardware, electronic documents, kiosks, and telecommunications products. This lecture explains the statute's purpose — eliminating barriers in the digital federal workplace and ensuring equal access to government information — and resolves the first question every practitioner asks: is this optional? It is not. Students learn the law's basic structure, exactly who it protects, and why it stands as a distinct legal mandate rather than a mere policy aspiration.
- 508 in the Family of Disability Law — ADA, 501, 504, and 2554:37Section 508 does not operate in a vacuum, and the single most common source of confusion for federal practitioners is mistaking it for — or conflating it with — the other disability laws swirling around it. Why does the ADA not directly govern most federal agencies, and yet DOJ's 2024 ADA Title II web rule matters enormously to federal accessibility work? How does Section 501 (federal employment of people with disabilities) connect to 508 through reasonable-accommodation obligations, and where does Section 504 (the complaint machinery 508 borrows) fit in? What is Section 255, and why does it appear as its own column on a VPAT? This lecture untangles the whole family: it draws the clean line between 508 (federal ICT), the ADA (state/local government and public accommodations), Sections 501 and 504 of the Rehabilitation Act, and Section 255 of the Communications Act — so that when these acronyms surface later in complaints, procurement, and program-building, students already know precisely which law is doing the work.
- The 2017 ICT Refresh — 36 CFR Part 1194 Explained5:19The Section 508 that governs today is not the one written in 1998 — so what changed, and why does every current requirement trace back to a single 2017 rulemaking? The U.S. Access Board issued its Revised 508 Standards on January 18, 2017, effective January 18, 2018. Published at 36 CFR Part 1194, this 'ICT Refresh' replaced the original 2000 standards with a modern, technology-neutral framework organized into functional performance criteria and technical specifications for software, hardware, support documentation, and support services. Most consequentially, it incorporated WCAG 2.0 Level AA success criteria by reference, retiring the outdated homegrown web provisions in favor of an internationally recognized standard. This lecture walks through the structure of Part 1194, how Appendices A, B, and C are organized, and the key shift the Refresh introduced — from product-category-specific rules to functional, outcome-based requirements that apply across every ICT category.
- What ICT Must Comply — Covered Technologies and Exceptions4:54Section 508's reach is remarkably broad — but a practitioner who assumes it covers absolutely everything is as wrong as one who assumes their pet system is somehow exempt. So where exactly does the mandate stop? Under 36 CFR Part 1194, covered ICT includes public and internal websites and web apps, installed software, electronic documents (Word, PDF, PowerPoint, Excel), hardware such as computers, printers, and kiosks, telecommunications products, and agency video and multimedia. But the standards also define real boundaries: national security systems (per 40 U.S.C. § 11103(a)) are categorically excluded, ICT incidental to a contract may fall outside scope, and certain legacy systems can qualify for limited relief. This lecture builds a practical taxonomy of what's in and what's out — so students can look at a public website, a procured SaaS tool, a training deck, or a policy PDF and correctly answer the everyday question, 'Does 508 apply to this?'
- Section 1 Quiz: Why Section 508 Exists — People, Barriers, and the Law
- ShiftEase Rollout — Accessibility Sign-Off
- WCAG, Levels, and the 2.0/2.1/2.2 Question Every Team Faces4:47Here is the tension at the heart of every modern federal accessibility program: Section 508 legally requires WCAG 2.0 Level AA, yet almost every practitioner is told to target WCAG 2.1 AA — and WCAG 2.2 is already published. Which one actually governs your work, and why isn't the answer simply 'the newest'? This lecture resolves the confusion by explaining what WCAG is (the W3C's Web Content Accessibility Guidelines), how it's structured into four principles, guidelines, and testable success criteria, and what Level A, AA, and AAA really mean in practice. Then it tackles the version story head-on: 36 CFR Part 1194 incorporates WCAG 2.0 AA by reference (the binding floor), while GSA and the Access Board urge agencies to voluntarily meet WCAG 2.1 AA, and DOJ's April 2024 ADA Title II final rule adopted 2.1 AA outright — which is why forward-looking federal teams design to 2.1 (with an eye on 2.2) even though 2.0 is the letter of 508. Students leave knowing exactly what to build to, and why.
- The POUR Framework — Four Principles of Web Accessibility3:26How can four words possibly organize every accessibility requirement — from a missing alt attribute to a broken custom widget? The answer is POUR: Perceivable, Operable, Understandable, and Robust, the conceptual architecture beneath all of WCAG. This lecture shows how these principles turn a sprawling checklist into a diagnostic mental model. Content rendered as an image with no text alternative fails Perceivable; a modal that traps keyboard users fails Operable; an error that says only 'invalid input' fails Understandable; a widget assistive tech can't interpret fails Robust. By mapping each principle to the concrete needs of users with visual, motor, auditory, and cognitive disabilities, POUR gives practitioners a way to reason about failures instead of memorizing rules — and it is the frame that makes every remaining lecture in the course cohere rather than feel like a pile of criteria.
- Perceivable — Text Alternatives, Color, Contrast, and Captions3:52Why can a page look perfect on screen and still be completely invisible to some users? Because 'perceivable' means the content must reach the user through whatever sense they can actually use — and content that lives only in an image, only in color, or only in audio leaves someone out. This lecture works through the Perceivable criteria most relevant to federal teams: text alternatives for non-text content (SC 1.1.1), captions and transcripts for time-based media (SC 1.2.x), adaptable structure that survives being re-presented (SC 1.3.x), and content that is easy to see and hear through sufficient contrast and independence from color (SC 1.4.x). It confronts the failures auditors flag most — missing or meaningless alt text, contrast below the 4.5:1 (normal) and 3:1 (large) thresholds of SC 1.4.3, and content that breaks when zoomed to 200% — and ties each one back to the specific visual or auditory barrier it removes.
- Operable — Keyboard, Focus, Gestures, and Time Limits4:24What happens to a user who cannot use a mouse — and why is that far more common in a federal workforce than teams assume? Many users with motor disabilities rely entirely on the keyboard, switch devices, or voice control, so the Operable principle demands that every interaction work without a pointer and without punishing time limits. This lecture makes the requirements concrete: all functionality operable by keyboard (SC 2.1.1) with no keyboard traps (SC 2.1.2), visible focus, logical focus order, skip links, and meaningful page titles (SC 2.4.x), plus the touch-and-mobile criteria WCAG 2.1 added for pointer gestures, pointer cancellation, and motion actuation (SC 2.5.x). It walks through the failure patterns most often caught in 508 audits — suppressed focus indicators, hover-only menus, dialogs that swallow focus — and shows exactly what each looks like in a real federal application so students can spot them before an auditor does.
- Understandable — Language, Predictability, and Error Handling4:33A form can be perfectly keyboard-operable and still defeat the user — if they can't tell what went wrong or how to fix it. The Understandable principle governs whether people can read the content, predict how the interface behaves, and recover from mistakes, and for federal audiences that include people with cognitive disabilities, low literacy, or limited English proficiency, the stakes are enormous. This lecture unpacks the criteria that matter most for federal forms and applications: declaring page and inline language so screen readers pronounce content correctly (SC 3.1.1, 3.1.2), consistent navigation and predictable behavior (SC 3.2.x), and the error-handling cluster that makes or breaks a government transaction — error identification (3.3.1), labels and instructions (3.3.2), helpful suggestions (3.3.3), and error prevention for legal and financial actions (3.3.4). The throughline is the gap between a form that guides a stressed user to success and one that silently blocks them.
- Robust — ARIA, Name/Role/Value, and Status Messages5:15Why does a beautifully designed federal web app sometimes turn to gibberish the instant a screen reader touches it? Because the Robust principle lives in the invisible layer — the markup and accessibility tree that assistive technologies actually read. This lecture focuses on where robustness succeeds or fails: exposing every component's name, role, and value to assistive tech (SC 4.1.2), and announcing dynamically injected updates like 'form submitted' or '3 errors found' without stealing focus (SC 4.1.3, Status Messages, added in WCAG 2.1). It explains why custom widgets with wrong or missing ARIA roles, no keyboard event handling, or silent live-region updates are the classic reason an app that 'looks fine' is unusable non-visually — and it equips students to recognize these breakdowns, while noting how the treatment of the old Parsing criterion (4.1.1) evolved in later WCAG versions.
- Section 2 Quiz: The WCAG Standard — POUR and the Version Question
- Unemployment Portal: Accessibility Sign-Off
- Accessible Word Documents — Structure, Headings, and Alt Text4:59Word documents are the single most-produced content type in most agencies — and among the most frequently inaccessible. Why do so many well-meaning authors fail, and what actually makes a document navigable to a screen reader? The answer is that accessibility is structural, not cosmetic: real Heading styles that create a navigable outline, meaningful alt text on informative images (SC 1.1.1) with truly decorative images marked as such, genuine lists instead of typed dashes, tables with designated header rows, sufficient text contrast, no reliance on color alone, and meaningful link text instead of pasted URLs. This lecture walks the full Microsoft 365 workflow, including the built-in Accessibility Checker, and resolves a tension authors rarely see coming: the structure you build in Word is exactly what determines whether the exported PDF is accessible or a tagged mess — so the fix starts upstream, at the source document.
- Accessible PDFs — Tags, Reading Order, and Fillable Forms4:35PDFs are the currency of official federal publishing — and the format most likely to be a black box to a screen reader. How can a document that prints perfectly be completely opaque to assistive technology? Because visual layout and machine-readable structure are two different things, and a PDF needs the second one built in: a tag tree that labels every heading, paragraph, list, table, and figure by role; a logical reading order matching the visual flow; alt text on informative images; real selectable text rather than a scanned picture of text; a set document title and language; and, for forms, labeled fields with correct tab order and tooltips. This lecture covers both pathways — authoring cleanly in Word or InDesign and exporting with accessibility enabled, versus remediating an existing PDF in Adobe Acrobat Pro using the Tags panel, Reading Order tool, and Accessibility Checker — so students can both prevent and fix inaccessible PDFs in the federal context.
- Accessible PowerPoint and Data Presentations4:15Slides that dazzle in the room can vanish for a screen reader user reading them later — so what turns a briefing deck into a genuinely accessible file once it's posted or emailed? This lecture answers with the interlocking pieces that make PowerPoint conformant: a unique descriptive title on every slide set through the layout's title placeholder, using built-in layouts instead of stray text boxes, a correct reading order set through the Selection Pane, alt text on every image and chart (or a decorative marking), tables used for data rather than layout, adequate contrast, and never relying on animation alone to convey meaning — plus captioning and description for any embedded media. Special attention goes to the hardest case in government decks: making complex charts and data visualizations perceivable to someone who can't see them. Students see, feature by feature, what a fully accessible federal presentation looks like from structure through visual design.
- Video Captioning — Requirements, Methods, and Quality3:45When an agency posts a training video or a public briefing, captions aren't a courtesy — they're a Section 508 obligation, so what exactly does compliant captioning require, and why won't the auto-captions get you there? This lecture ties the requirement to WCAG SC 1.2.2 (prerecorded) and 1.2.4 (live), and explains what 'compliant' actually means: captions that are accurate, synchronized, and identify speakers and meaningful non-speech sounds like [applause] or [alarm]. It confronts the trap teams fall into — auto-generated captions from YouTube, Stream, or Zoom are a starting point, not a finish line, and almost always need human review to reach federal accuracy. Students learn when captions are required, the difference between open and closed captions, how to judge caption quality, and how agencies actually get captioning done — human transcription services, third-party vendors, or platform tools with human correction — for both internally produced and externally procured video.
- Audio Description — Making Visual Content Accessible4:25Captions solve the audio track for Deaf users — but what about the blind analyst watching a software demo where all the meaning is on screen and the narrator never says what they're clicking? That gap is exactly what audio description fills, and Section 508 requires it for prerecorded synchronized media under WCAG SC 1.2.5. This lecture explains audio description as a narrated track conveying the visual information the dialogue omits — on-screen text, meaningful action, scene changes, and any visual demonstration central to the content — and distinguishes standard description (slotted into natural pauses) from extended description (where the video pauses to allow more). It resolves the practical judgment call every producer faces: which visual content genuinely needs description versus what can simply be spoken into the main audio at scripting time, and it walks the federal workflow, including cost-effective approaches and vendor requirements, for both new and legacy video.
- Section 3 Quiz: Creating Accessible Documents and Multimedia
- Onboarding Video: 508 Sign-Off Before Launch
- The Testing Mindset — Why Automation Alone Fails4:18If accessibility can be tested with a scanner, why do agencies with clean automated scores still get complaints? Because automated tools, for all their speed, catch only roughly 20-40% of WCAG failures — the machine-checkable ones like missing alt attributes, low contrast, absent labels, and duplicate IDs. The remaining majority require a human: is the alt text meaningful or just present, does the reading order make sense, does the custom widget actually work with a real screen reader, are the error messages genuinely helpful? This lecture establishes the layered testing philosophy that underpins defensible 508 work — automation as a fast first pass to catch obvious failures at scale, then targeted manual testing for everything automation is blind to. Students learn how to structure a test plan, what to prioritize, and how to document findings in a form developers and designers can actually act on.
- Keyboard-Only Testing — Navigating Without a Mouse5:04What is the highest-yield accessibility test that costs nothing and needs no tools? Put the mouse down. Keyboard-only testing directly evaluates SC 2.1.1 (Keyboard), 2.1.2 (No Keyboard Trap), and 2.4.3 (Focus Order), and it exposes failures automated scanners can't see — a focus indicator hidden by CSS, a modal that traps focus forever, a menu that only opens on hover. This lecture drills the primitives every tester must master: Tab and Shift+Tab to move through interactive elements, Enter and Space to activate controls, arrow keys to move within composite widgets like menus and radio groups, and Escape to dismiss dialogs. Then it lays out a systematic protocol for a federal page — inventorying interactive elements, checking focus visibility, testing skip links, exercising custom widgets, and writing up keyboard failures so a developer knows exactly what to reproduce and fix.
- Screen Reader Testing — JAWS, NVDA, and VoiceOver4:56How do you verify that a site truly works for a blind user — not in theory, but in the audio-driven, shortcut-dependent way they actually experience it? You test with a screen reader, which means learning an entirely different mode of interacting with content. This lecture introduces the three that matter federally: JAWS (commercial, the most-used by federal employees with disabilities), NVDA (free, open-source, the testing workhorse), and VoiceOver (built into macOS/iOS, essential for mobile and cross-platform checks), along with the browser pairings that make them behave. Students learn the core mechanics — switching between browse/virtual mode for reading and forms/application mode for interacting, and the key navigation shortcuts (H for headings, B for buttons, F for form fields, T for tables) — and, most importantly, what to listen for: whether images are announced meaningfully, labels are clear, errors are announced automatically, and custom widgets report their role, state, and value.
- Automated Tools — axe, WAVE, and Lighthouse4:26Given that automation can't certify accessibility, why is it still indispensable — and how do you get real value from it without being misled? This lecture makes automated scanning earn its place as the efficient first layer of a federal workflow. It compares the three tools practitioners actually reach for: axe DevTools (Deque), prized for a low false-positive rate and precise WCAG citations and embeddable in CI/CD; WAVE (WebAIM), whose visual overlay lets non-technical stakeholders see issues in context; and Lighthouse (in Chrome DevTools), whose axe-powered audit yields a 0-100 score handy for tracking trend over time. Students learn to read each tool's output correctly — separating confirmed errors from alerts that need human judgment from mere structural notes — and how to wire automated scans into a repeatable process, including running axe programmatically to catch regressions in development before they ever reach production.
- GSA's Trusted Tester Process and the ICT Testing Baseline4:16If ten different testers evaluate the same federal page, how do you get results that actually agree — and that hold up under scrutiny? The answer is a standardized methodology, and DHS built one with GSA: the Trusted Tester for Web process, backed by the ICT Testing Baseline. Together they specify exactly which conditions to evaluate, which tools and keyboard commands to use, and how to record findings — producing an auditable, reproducible result that's consistent across testers and agencies, and a certification program that trains testers to a common technical bar. This lecture explains how Trusted Tester works, why a defensible and repeatable evaluation record matters when an agency has to prove its diligence, and how this rigorous manual process fits alongside the automated and screen-reader testing from earlier lectures to form a complete, credible conformance evaluation.
- Section 4 Quiz: Testing Federal ICT for Conformance
- 508 Sign-Off: Benefits Portal Launch
- ICT Procurement Rules — FAR Subpart 39.2 Explained4:15When an agency buys technology rather than builds it, whose job is accessibility — and at what point in the deal does it become legally binding? The answer surprises many: it's baked into the Federal Acquisition Regulation from the start. FAR Subpart 39.2 (Information and Communication Technology), updated effective September 10, 2021 to incorporate the Revised 508 Standards, requires agencies to identify the applicable technical and functional requirements from 36 CFR Part 1194 and write them into solicitations, contracts, and task orders for ICT. That means a contracting officer issuing an RFP, a COR overseeing a web contractor, or anyone buying commercial software is legally obligated to specify 508 requirements and evaluate vendor responses for conformance. This lecture shows how that works in practice — how 508 language should appear in Statements of Work, how CORs and program managers evaluate vendor claims, and why accessibility considered before award is cheap while remediation after award is expensive and contractually painful.
- Reading and Writing VPATs and Accessibility Conformance Reports5:19A vendor hands you a VPAT that says 'Supports' on every single line — should you trust it? Learning to answer that question is one of the most valuable procurement skills in this course. The Voluntary Product Accessibility Template is the industry-standard document vendors use to disclose conformance, delivered as an Accessibility Conformance Report (ACR); the current VPAT 2.x covers four frameworks — Section 508, WCAG 2.x, EN 301 549, and Section 255 — and rates each criterion Supports, Partially Supports, Does Not Support, Not Applicable, or Not Evaluated, each with a remarks column. This lecture teaches students to read a VPAT critically rather than at face value: a blanket 'Supports' with no explanation is a red flag, while an honest VPAT names known issues and describes workarounds. Students learn to read, write, and evaluate VPATs, and to use them as living documents that track a vendor's remediation commitments across the life of a contract.
- Exceptions and Exemptions — When 508 Doesn't Apply4:50Section 508 is broad, but not absolute — and practitioners get in trouble at both extremes: over-applying it and creating needless burden, or falsely claiming an exception that doesn't exist. So where are the real limits, and what does it take to invoke them legitimately? This lecture walks the genuine categories: national security systems (40 U.S.C. § 11103(a)), which are categorically excluded; ICT incidental to a contract — technology a contractor uses internally rather than delivering to the agency; and legacy ICT that would require a fundamental alteration to remediate. It then covers the undue-burden exemption — which is not a casual escape hatch but a written determination signed by agency leadership, and which still obligates the agency to provide an alternative means of access to affected users. The recurring caution: these exceptions are narrow, documented, and authorized at a level most staff can't reach, so invoking one prematurely is itself a compliance failure.
- Filing a Section 508 Complaint — Agency and DOJ Channels5:00When a person with a disability hits a wall in federal ICT — a site they can't navigate, a form they can't submit, an uncaptioned video — what recourse does the law actually give them, and how far does it go? This lecture traces the complaint pathway: individuals file with the responsible agency through its Section 504 complaint process (usually run by its Office of Civil Rights or EEO office), in writing, generally within about 180 days of the barrier, with the agency required to acknowledge and respond within set timelines; unresolved matters can escalate to DOJ, which exercises governmentwide oversight and can investigate and negotiate corrective action. Crucially, it resolves a point that shapes the entire enforcement landscape: unlike the ADA, Section 508 does not authorize money damages — remedies are limited to injunctive relief and attorney's fees — which is precisely why proactive compliance, not reactive litigation defense, is the winning strategy for an agency.
- DOJ Oversight, Reporting, and Governmentwide Accountability4:29If 508 rarely produces lawsuits or damages, what actually pressures agencies to improve — and how does anyone even know how a given agency is doing? The answer is transparency-driven accountability. Under 29 U.S.C. § 794d-1, agencies must submit conformance reports to the Access Board and OMB, and GSA runs the annual governmentwide Section 508 assessment, collecting standardized data from more than 200 agencies on policy, testing, training, and conformance, then publishing results that effectively rank performance and expose systemic weaknesses. This lecture explains how that assessment ecosystem works, how the questionnaire is structured, what agencies are graded on, and what the public data reveals about the real state of federal digital accessibility — giving students the context to see where their own agency stands and what 'good' looks like at the governmentwide level, ahead of the program-building work in the final section.
- Section 5 Quiz: Procurement, Complaints, and Enforcement
- ClaimsFlow ACR Review — Pre-Award Sign-Off
- The Section 508 Program Manager — Mandate, Placement, and Power4:04Every agency is expected to name a Section 508 Program Manager — so why do some drive real change while others hold a title and nothing more? The difference isn't the person; it's the position. A Program Manager buried under a frontline IT manager, with no budget, no voice in procurement, and no line to leadership, is structurally set up to fail, while an effective one carries a clear mandate from senior leadership, sits high enough to shape IT governance, joins acquisition planning before contracts are awarded, and runs a network of 508 liaisons across program offices. This lecture defines the role as GSA and the Access Board describe it, lays out the core competencies it demands, maps how it should connect to the CIO office, acquisition, and HR, and presents a maturity spectrum from reactive compliance clerk to proactive accessibility leader — so students can see what a well-resourced, strategically placed accessibility function truly looks like.
- Assessing Where You Stand — The Four-Dimensional Baseline4:35You can't build a roadmap to better compliance without an honest map of where you are today — so how do you take an unflinching measurement of an agency's real accessibility posture? This lecture provides a structured, four-dimensional assessment: policy and governance (is there a written, current, actively enforced 508 policy reflecting the Revised Standards?), ICT inventory and testing coverage (which systems have actually been tested, and what share of high-priority ICT has a current ACR on file?), procurement (are 508 requirements consistently in solicitations and are VPATs evaluated by people who understand them?), and training and awareness (who's been trained, how deeply, and is it role-specific?). Critically, it aligns the internal assessment with the criteria of GSA's annual governmentwide assessment, so the agency's own results are directly comparable to the federal benchmark and can feed straight into its official submission — turning a self-check into a strategic instrument.
- Policies, Processes, and Governance That Make Access the Default4:08Why do accessibility gains built on a few dedicated individuals quietly evaporate the moment those people move on? Because heroics don't scale — only institutional structure does. This lecture lays out the three layers that make accessibility the default rather than the exception. The policy layer is a formal, signed 508 policy defining scope, responsibilities, complaint procedures, and expectations for procurement and development. The process layer embeds 508 into the workflows where ICT decisions actually happen: governance gate reviews that demand testing evidence before deployment, acquisition checklists that verify 508 is in solicitations, publishing workflows that require accessibility review before content goes live, and development pipelines that scan every build. The governance layer creates accountability through portfolio dashboards, regular reporting to CIO and agency-head leadership, and clear escalation paths. Students leave with a model governance structure and a concrete roadmap to build or strengthen this infrastructure.
- Supporting the Assistive Technology Ecosystem3:33Making content technically conformant is necessary — but is it enough to actually let a blind analyst or a voice-input user do their federal job? Not quite, because those users depend on assistive technology, and the agency has to support that ecosystem, not just accommodate it on paper. This lecture surveys the AT federal employees rely on — screen readers (JAWS, NVDA), magnifiers (ZoomText), voice recognition (Dragon), alternative keyboards, switch and eye-tracking devices, and refreshable Braille displays — and connects Section 508's ICT-accessibility duty to the Rehabilitation Act's Section 501 obligation to provide AT as a reasonable accommodation. It explains why testing with real assistive technology reveals problems automated scans never will (and why both are required), how to build AT into the agency's testing protocols, and how the accommodation process links an employee's Section 501 rights to the 508 conformance of the tools they're handed.
- Remediating a Backlog — Prioritizing at Scale4:18Here is the question that stops most programs cold: we already have ten thousand inaccessible PDFs, dozens of aging systems, and years of posted content — where on earth do we start? This lecture confronts the reality that no agency can remediate everything at once and that trying to boil the ocean is how programs stall. It presents a risk-and-impact prioritization approach: triage by reach and consequence (high-traffic public pages and mission-critical transactions before rarely-touched archives), by legal exposure (content tied to active complaints or benefits), and by cost-to-fix versus benefit. It weighs remediate-versus-retire-versus-replace decisions, when to fix a document versus provide an accessible alternative on request, and how to fold remediation into normal refresh and redesign cycles so the backlog shrinks structurally instead of demanding a heroic one-time campaign. Students leave with a defensible way to sequence the work — and to explain that sequence to leadership.
- Training, Metrics, and Continuous Improvement4:32Once the structure exists, how do you keep it alive — making sure people actually have the skills 508 demands, and proving to leadership that the program is improving rather than just spending? This closing lecture ties the human and measurement dimensions together. On training, it lays out a role-stratified program: deep WCAG/ARIA knowledge for developers, practical document skills for content creators, FAR 39.2 and VPAT literacy for contracting staff, and go-live testing awareness for program managers — drawing on GSA's free section508.gov resources and a refresh cadence of roughly every two years. On metrics, it builds a dashboard that tracks the share of high-priority systems with current ACRs, open defects by severity, documents passing review, and 508 language appearing in solicitations — all mapped to GSA's governmentwide assessment criteria. The throughline: a program that can measure itself can justify its budget, demonstrate accountability, and improve on purpose, turning compliance from an episodic scramble into a sustained, provable capability.
- Section 6 Quiz: Building and Sustaining an Agency 508 Program
- 508 PM Placement & Budget Check-in
Requirements
- No prior accessibility or web development experience required — this course is suitable for beginners
- Basic familiarity with common office software such as Word, PDF, and PowerPoint is helpful
- Access to a web browser and standard document creation tools is useful for hands-on practice
Description
This course contains the use of artificial intelligence.
Section 508 of the Rehabilitation Act requires federal agencies to ensure that all information and communication technology (ICT) they develop, procure, maintain, or use is accessible to people with disabilities. Since the 2017 Refresh incorporated WCAG 2.1 Level AA as the technical standard, the scope of that obligation now reaches web content, software, electronic documents, multimedia, hardware, and support services. This course gives you a thorough, practical grounding in Section 508 compliance from the statute through implementation.
You will start with the legal framework: the Rehabilitation Act, the Access Board, GSA, and the functional performance criteria that define what accessible means in practice. From there the course works through the WCAG 2.1 Level AA success criteria — organized under the four POUR principles (Perceivable, Operable, Understandable, Robust) — and applies them to the most common ICT types federal agencies deal with: websites, PDFs, Word documents, Excel spreadsheets, PowerPoint presentations, and video with captions and audio description.
The final section covers testing and procurement: how to use automated and manual tools to evaluate conformance, how to apply the Revised 508 Standards in an Accessibility Conformance Report (ACR), and how to build and sustain an agency Section 508 program. By the end of this course you will be able to create, test, and procure accessible federal ICT with confidence.
Who this course is for:
- Federal agency employees responsible for creating or procuring accessible information and communication technology
- IT professionals, developers, and web managers at federal agencies subject to Section 508 requirements
- Section 508 program coordinators and accessibility leads building or improving agency compliance programs
- Document authors, content managers, and communications staff who create federal digital content
- Federal contractors delivering ICT products or services that must conform to the Revised 508 Standards