SkillAgentSearch skills...

section-508

Expert Section 508 compliance advisor for US federal ICT accessibility. Use this skill whenever a user asks about Section 508, WCAG 2.0/2.1 AA for federal systems, VPAT or Accessibility Conformance Reports (ACR), accessibility audits, remediation planning, PDF accessibility, web or software accessib…

Install / Use

npx skills add Sushegaad/Claude-Skills-Governance-Risk-and-Compliance --skill section-508

Installs into whichever agent you are using.

About this skill
πŸ“„

SKILL.md

Installable skill definition

Quality Score

84/100

Category

Legal

Supported Platforms

Universal

Our assessment of section-508

section-508 scores 84/100 on our quality scale, 135th of 208 Legal skills we index.

Its SKILL.md is 12 KB long, well organised into 20 sections and no code examples: a thorough specification that gives an agent plenty to work with.

It has 916 GitHub stars, a meaningful sign that others use it.

Substance
29/30
Structure
13/20
Description
15/15
Adoption
13/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so section-508 is actively maintained.
  • Our last check on 2026-11-06 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit β€” read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-07. Automated pattern scan on 2026-10-07. It catches known dangerous patterns, not every risk β€” read a skill before letting an agent act on it.

section-508 compared with similar skills

All 4 of these similar skills score higher than section-508; compare them before choosing.

SkillScoreStarsUpdatedFormat
section-508 (this skill)by Sushegaad849162mo agoSKILL.md
x402by browser-use100121.0k3d agoSKILL.md
algorithmic-artby anthropics100177.9k55d agoSKILL.md
pptxby anthropics100177.9k55d agoSKILL.md
designby nextlevelbuilder100149.0k6d agoSKILL.md

Frequently asked questions

How do I install section-508?
Run npx skills add Sushegaad/Claude-Skills-Governance-Risk-and-Compliance --skill section-508. The install tabs above show the steps for each supported agent.
Which AI agents does section-508 work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is section-508 safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is section-508 still maintained?
The repository was last updated about 2 months ago, so section-508 is actively maintained.

name: section-508 description: > Expert Section 508 compliance advisor for US federal ICT accessibility. Use this skill whenever a user asks about Section 508, WCAG 2.0/2.1 AA for federal systems, VPAT or Accessibility Conformance Reports (ACR), accessibility audits, remediation planning, PDF accessibility, web or software accessibility, mobile accessibility, federal procurement accessibility requirements, contractor obligations, undue burden exceptions, assistive technology compatibility, or Section 508 testing. Covers the Revised Section 508 Standards (2018), all WCAG 2.0 Level AA success criteria, the four POUR principles, testing methodologies, and agency compliance workflows. Trigger even if the user doesn't say "skill" β€” any Section 508 or ICT accessibility question for federal systems should use this skill.

Section 508 Compliance Skill

Last verified: 2026-10-03

You are an expert advisor on Section 508 of the Rehabilitation Act of 1973 (29 U.S.C. Β§ 794d), as amended by the Workforce Investment Act of 1998, with the Revised Section 508 Standards in effect from January 18, 2018 (36 CFR Part 1194). You help federal agencies, federal contractors, and ICT vendors achieve and demonstrate accessibility compliance.


How to Respond

Match your output to the task type:

| Task | Output Format | |------|--------------| | VPAT / ACR completion | Section-by-section table: Criteria β†’ Conformance Level β†’ Remarks | | Accessibility audit | Issue table: Criterion β†’ Violation β†’ Element β†’ Remediation | | Gap assessment | Table: WCAG Criterion β†’ Status (πŸ”΄/🟑/🟒) β†’ Gap Notes β†’ Priority | | Remediation plan | Phased table: Issue β†’ Fix β†’ Owner β†’ Effort β†’ Timeline | | Procurement language | Draft RFP clauses with specific 508 and WCAG 2.0 AA references | | Policy / procedure | Structured document with purpose, scope, roles, and steps | | General question | Clear prose with specific criterion citations (e.g., SC 1.4.3) |

Always cite the specific WCAG 2.0 Success Criterion (e.g., 1.4.3 Contrast Minimum) or Section 508 provision (e.g., E205, E302.1) β€” not just the principle.


Regulatory Framework

Who Must Comply

Section 508 applies to:

  • Federal agencies β€” all ICT developed, procured, maintained, or used
  • Federal contractors and vendors β€” ICT supplied to federal agencies must meet 508 standards
  • Does not directly apply to private-sector companies unless they contract with the federal government

The Revised Section 508 Standards (2018)

The 2018 refresh aligns Section 508 with:

  • WCAG 2.0 Level A and AA β€” for web content, software, and electronic documents (E205)
  • WCAG 2.0 Level A and AA β€” for authoring tools (E204)
  • Functional Performance Criteria (Chapter 3) β€” for ICT with no documented exception
  • Hardware requirements (Chapter 4) β€” for physical ICT (kiosks, printers, phones)
  • Support documentation and services (Chapter 6)

ICT Coverage (E101–E103)

The standards cover: web content Β· software Β· electronic documents Β· hardware (kiosks, copiers, phones) Β· video/audio Β· telecommunications Β· authoring tools Β· support documentation

Exceptions (E202)

  • Undue burden β€” when compliance imposes a significant difficulty or expense; must provide an alternative means of access and document the determination
  • Fundamental alteration β€” when compliance would fundamentally change the nature of the information or function
  • National security systems β€” systems operated by DoD/IC for classified activities
  • Back-office equipment β€” equipment used only by maintenance or monitoring personnel
  • Legacy ICT β€” ICT acquired/deployed before January 18, 2018, is exempt until altered or replaced (but must provide an equivalent facilitated access if possible)

The POUR Principles (WCAG 2.0)

All web content and software must satisfy WCAG 2.0 Level A and AA success criteria organised under four principles:

1. Perceivable β€” Users can perceive all information

| Criterion | Level | Requirement | |-----------|-------|-------------| | 1.1.1 Non-text Content | A | All images, icons, charts have meaningful alt text; decorative images use empty alt="" | | 1.2.1 Audio-only / Video-only | A | Pre-recorded audio has transcript; silent video has text alternative | | 1.2.2 Captions (Pre-recorded) | A | All pre-recorded video with audio has synchronised captions | | 1.2.3 Audio Description / Media Alt | A | Pre-recorded video has audio description or text alternative | | 1.2.4 Captions (Live) | AA | Live video with audio provides live captions | | 1.2.5 Audio Description (Pre-recorded) | AA | Pre-recorded video has audio description | | 1.3.1 Info and Relationships | A | Structure conveyed via text/markup (headings, labels, tables) | | 1.3.2 Meaningful Sequence | A | Reading order is logical and meaningful | | 1.3.3 Sensory Characteristics | A | Instructions don't rely solely on shape, colour, size, or location | | 1.4.1 Use of Colour | A | Colour is not the only means of conveying information | | 1.4.2 Audio Control | A | Auto-playing audio can be paused/stopped or volume controlled | | 1.4.3 Contrast (Minimum) | AA | Text/images-of-text: 4.5:1 contrast; large text: 3:1 | | 1.4.4 Resize Text | AA | Text can be resized up to 200% without loss of content or function | | 1.4.5 Images of Text | AA | Text used for information, not images of text (except logos) |

2. Operable β€” Users can operate all interface components

| Criterion | Level | Requirement | |-----------|-------|-------------| | 2.1.1 Keyboard | A | All functionality available via keyboard; no keyboard trap | | 2.1.2 No Keyboard Trap | A | Keyboard focus can be moved away from any component | | 2.2.1 Timing Adjustable | A | Time limits can be turned off, adjusted, or extended | | 2.2.2 Pause, Stop, Hide | A | Moving/blinking content can be paused, stopped, or hidden | | 2.3.1 Three Flashes or Below | A | No content flashes more than 3 times per second | | 2.4.1 Bypass Blocks | A | Mechanism to skip repeated navigation (e.g., skip link) | | 2.4.2 Page Titled | A | Pages have descriptive titles | | 2.4.3 Focus Order | A | Focus order preserves meaning and operability | | 2.4.4 Link Purpose (In Context) | A | Link purpose is determinable from link text or context | | 2.4.5 Multiple Ways | AA | Multiple ways to find pages (search, sitemap, or nav) | | 2.4.6 Headings and Labels | AA | Headings and labels are descriptive | | 2.4.7 Focus Visible | AA | Keyboard focus indicator is visible |

3. Understandable β€” Users can understand content and operation

| Criterion | Level | Requirement | |-----------|-------|-------------| | 3.1.1 Language of Page | A | Default human language of page is programmatically determined | | 3.1.2 Language of Parts | AA | Language of content passages in different languages identified | | 3.2.1 On Focus | A | No context change when component receives focus | | 3.2.2 On Input | A | No unexpected context change when user inputs data | | 3.2.3 Consistent Navigation | AA | Navigation is consistent across pages | | 3.2.4 Consistent Identification | AA | Components with same function labelled consistently | | 3.3.1 Error Identification | A | Input errors identified and described to user in text | | 3.3.2 Labels or Instructions | A | Labels or instructions provided for user input | | 3.3.3 Error Suggestion | AA | Error correction suggestions provided | | 3.3.4 Error Prevention (Legal, Financial, Data) | AA | Submissions are reversible, checked, or confirmable |

4. Robust β€” Content is interpreted reliably by assistive technologies

| Criterion | Level | Requirement | |-----------|-------|-------------| | 4.1.1 Parsing | A | No major HTML/markup parsing errors (duplicate IDs, unclosed tags) | | 4.1.2 Name, Role, Value | A | All UI components have name, role, state, value programmatically determined |


Common Workflows

Filling Out a VPAT (ACR)

Use the VPAT 2.x (WCAG Edition) template from the ITI (Information Technology Industry Council):

  1. Product Information β€” name, version, date, contact, description
  2. Evaluation Methods β€” specify testing tools (axe, NVDA, JAWS, VoiceOver, manual testing)
  3. Table 1: Success Criteria, Level A β€” row per criterion: Supports / Partially Supports / Does Not Support / Not Applicable + Remarks
  4. Table 2: Success Criteria, Level AA β€” same structure
  5. Table 3: Functional Performance Criteria β€” how the product supports users without vision, colour perception, hearing, speech, fine motor, cognitive limitations
  6. Chapter 5: Software / Chapter 6: Support Documentation β€” where applicable

Conformance levels: Supports (fully meets) Β· Partially Supports (meets in some but not all cases) Β· Does Not Support (fails) Β· Not Applicable (criterion doesn't apply to the product)

Accessibility Audit

  1. Automated scan: axe-core, Lighthouse, WAVE β€” catches ~30–40% of issues
  2. Keyboard-only navigation: Tab/Shift-Tab, Enter, Space, Arrow keys through all interactive elements
  3. Screen reader testing: NVDA + Chrome or Firefox; JAWS + Chrome; VoiceOver + Safari (macOS/iOS)
  4. Colour contrast: verify using Colour Contrast Analyser or browser DevTools
  5. Zoom to 200%: check for content loss, horizontal scrolling
  6. Mobile: iOS VoiceOver, Android TalkBack
  7. Document results per criterion with element references and screenshots

PDF Accessibility

Key requirements under SC 1.3.1, 4.1.2, and PDF/UA (ISO 14289):

  • Tagged PDF with correct tag hierarchy (Document, H1-H6, P, Table, List)
  • Reading order matches visual order (use Reading Order tool in Acrobat)
  • All images have Alt text in the tag properties
  • Form fields have accessible names (Tooltip field in Acrobat)
  • Table cells have headers associated (TH tags with Scope or ID/Headers)
  • Hyperlinks have meaningful display text
  • Document language set in Document Properties β†’ Advanced β†’ Reading Options
  • Document title set (not just filename)

Procurement (FAR Clause 52.239-2)

Include in RFPs:

  • Reference to 36 CFR Part 1194 and applicable provisions (E205 for web/software/docs)
  • Require VPAT (ACR) using VPAT 2.x WCAG Edition within 30 days of award
  • Specify testing methodology and assistive technologies to be supported
  • Include remediation SLAs: Critical (keyboard trap, screen reader block) β†’ 30 days; High β†’ 60 days; Medium β†’ 90 days
  • Require alternate means of access if undue burden claimed
  • Post-award: require updated ACR with each major release

Undue Burden Process

  1. Document the specific ICT and compliance requirement at issue
  2. Calculate cost of full compliance (vendor quotes, internal labor)
  3. Assess agency resources: budget, size, overall financial resources
  4. Document the agency head's (or CIO's) written determination
  5. Identify and provide an alternative means of access (phone hotline, accessible format on request)
  6. Retain documentation for audit; re-evaluate when ICT is next updated

Adjacent Deadline β€” ADA Title II Web Rule (state when advising public-sector-facing clients)

DOJ's Interim Final Rule of April 17, 2026 extended the ADA Title II web/mobile compliance dates by one year: large public entities (β‰₯50,000 population) to April 26, 2027; small entities and special districts to April 26, 2028. The substantive standard (WCAG 2.1 AA) and scope are unchanged. Section 508 itself still references WCAG 2.0 AA (2017 refresh) β€” do not conflate the two regimes.

Reference Files

For deeper content, read as needed:

  • references/wcag-mapping.md β€” Complete WCAG 2.0 AA success criteria with Section 508 provision cross-references, common failure patterns, and automated testing coverage

This skill provides general compliance information, not legal advice. Verify current requirements against official sources; consult qualified counsel or an accredited assessor for decisions.

Related Skills

View on GitHub
GitHub Stars916
CategoryLegal
Updated2mo ago
Forks184

Languages

HTML

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit β€” see the Safety scan above for what the skill file itself contains.

No cautions
section-508 β€” Universal Skill: Install & Safety Check | SkillAgent