Every serious web developer eventually meets a requirement list that includes four words: Section 508, WCAG, accessibility. The words arrive from procurement documents and government contracts, and behind them stands a law that quietly governs a large share of the professional web. Section 508 of the Rehabilitation Act requires federal agencies, and the technology they buy and build, to be accessible to people with disabilities, and since American law reaches deep into vendor ecosystems, the requirement effectively exports itself to every shop that has ever wanted public-sector work.
The export mechanism deserves a sentence of its own, because it explains why a statute about federal agencies shapes private practice. When an agency buys a website, the contract carries the accessibility standard to the vendor, the vendor trains its staff to the standard, and the staff carry the competence to their next employer, private or not. Multiply the mechanism across two decades of procurement and the result is a workforce trained by regulation, serving a market that inherited the requirement without ever reading the law. Most developers who build accessible interfaces conscientiously have never opened the Rehabilitation Act, and the law would count that as its quietest success.
The official home of the requirement is Section508.gov, the government’s own resource for digital accessibility compliance, maintained by the General Services Administration, and it is one of the rare regulatory sites that doubles as a genuinely useful developer education. The site translates the statute into practice: what accessible procurement means, how to test conformance, and how to build and manage digital content that meets the standard, which since the 2017 refresh has aligned American federal rules with the international WCAG success criteria the rest of the world uses.
What The Rules Actually Ask
The technical core is less exotic than its legal wrapper suggests. The government’s guide to accessible web design and development walks through the practices that make a page usable with a screen reader, a keyboard, and human eyes of every ability: semantic structure that assistive technology can parse, alt text that describes rather than decorates, color contrast that survives low vision, focus states that make keyboard navigation visible, forms with labels, video with captions, and content that never flashes more than three times per second, a requirement with a seizure-prevention reason behind it. None of these are exotic. All of them are testable, which is why conformance audits can pass or fail a page as objectively as a validator checks markup.
For content management work, the requirements land on the system and the content together. A CMS either supports accessible output natively, semantic headings, accessible form markup, aria where needed, or it fights the builder at every template, and an editorial team either produces accessible content, real alt text, meaningful link text, structured headings, or it undermines the best theme in the world. Accessibility in a CMS project is a chain from core to module to theme to editor, and the chain’s strength is set by its weakest author.
The testing layer deserves a practical paragraph, because it is where good intentions most often diverge from conformance. Automated scanners catch a minority of accessibility failures, the machine-checkable ones like missing alt attributes and contrast ratios, and they pass pages that remain unusable, because the majority of success criteria, is this heading structure meaningful, does this link text make sense out of context, can a task be completed by keyboard alone, require human judgment. The professional standard is a hybrid: automated scanning in the build pipeline, manual keyboard walkthroughs of the core tasks, and a screen reader session for anything a user must actually read. The government’s own testing guidance describes exactly this mix, and shops that adopt it discover that the manual hour, spent early, is the cheapest accessibility remediation that exists, compared with the retrofit after launch, which multiplies the same hour across every affected template and every published page that inherited the flaw.
|
The Practice |
The User It Serves |
| Semantic HTML structure | Screen reader users |
| Keyboard operability | Non-mouse navigation |
| Contrast and resizing | Low vision users |
| Captions and transcripts | Deaf and hard of hearing |
| Flash limits | Photosensitive users |
The Security Sibling
Public-sector web work carries a second baseline, and the same agencies publish it. The Cybersecurity and Infrastructure Security Agency’s Secure by Design guidance describes what software manufacturers should build into their products and what buyers should demand, and for CMS operators the practical translation is the maintenance discipline: applied security updates, managed plugins, and a hard look at every extension’s update history before it enters a public site. An outdated component on a public-facing CMS is the digital equivalent of an unlocked service door, and the government’s alerts about CMS vulnerabilities over the years have made the same point with case numbers.
Open source development resources that serve public-sector builders, like the coverage at SparkDrupal, treat accessibility and security as first-class curriculum rather than compliance fine print, because in the government-adjacent market they are the difference between a site that ships and a site that stalls in review. The law set the floor, the international standard supplied the test, and the agencies published the manual. The developer who reads all three stops treating accessibility as a checklist bolted to the end of a project and starts building it into the first template, which is cheaper, faster, and, as the procurement documents keep reminding everyone, the law.
The market logic completes the argument for shops outside the government orbit entirely. Accessibility requirements have migrated from statute into procurement across the private economy, banks under settlement agreements, retailers under state civil rights law, universities under multiple regimes, and each migration converts the skill from compliance overhead into billable competence. A development shop that can demonstrate conformance holds a qualification a large customer category now demands, and the demonstration costs less every year as the tooling matures. The floor became a market, the market became a specialization, and the specialization began, as these things tend to, with a paragraph in a rehabilitation statute that most developers never read and every public website now answers to.
