610.432.2600
A Legal Obligation, Not
a Design Preference
Accessibility laws have been settled in court for years. Websites are considered public accommodations under Title III of the ADA, with businesses facing identical liability to physical storefronts with hazardous conditions.
Across Philadelphia, firms specializing in accessibility law employ AI-powered tools that scan thousands of sites, flag non-compliance, and generate automated demand letters before human review. Remediation is a calculated cost-saving measure, regardless of business scope or longevity online.
Project Snapshot: The 5 Ws
The Scope of Digital Accessibility Obligations
The Who
The What
The When
The Where
The Why
Who: The Parties With Skin in the Game
Site Owners and Operators: The business owner, the marketing director and the developer all sit inside the same legal accountability, covering every page, every PDF and every media file published under the domain.
The Affected Audience: About one Pennsylvania adult in four, roughly 25%, lives with a disability. Visual impairment, auditory impairment, motor impairment and cognitive impairment each raise a distinct access barrier, and an inaccessible site leaves every one of them standing.
What: The Standards That Define Compliance
WCAG 2.1 Level AA: When a digital accessibility claim gets evaluated, the benchmark referenced by courts, by the Department of Justice and by most state regulators is the Web Content Accessibility Guidelines at Level AA.
Full Digital Footprint: Scope runs well past the website itself, reaching every downloadable document, all video and audio content, each third-party embedded tool, and any mobile application the organization operates.
When: The Timing of Liability
At Launch: Legal exposure begins the moment a site goes live. No grace period exists in ADA enforcement, and ignorance of the standard has never functioned as a defense in accessibility litigation.
After Every Update: A new page, an uploaded PDF, an embedded video, a third-party widget installation. Any of these can introduce violations into a site that passed its last audit. Compliance is a condition, not an achievement.
Where: Every Surface the Public Can Reach
Owned Properties: Everything under the organization’s own control, which means the primary website, the subdomain landing pages, the email newsletters, and any web-based portals or client-facing applications it runs.
Embedded Third-Party Tools: Everything dropped in from somewhere else, meaning booking widgets, payment processors, map embeds, chat tools and social media integrations. Whichever business hosts the tool is the one carrying the compliance responsibility. The vendor’s name on the code is not a legal shield.
Why: The Legal and Commercial Stakes
Litigation Risk: ADA accessibility lawsuits carry no fixed penalty cap. Defense costs, plaintiff attorney fees, and settlement amounts routinely reach five figures before the first remediation invoice arrives.
Market Access: One in four adults. That is not a niche segment. An inaccessible site turns away a statistically significant share of potential customers, and none of them show up in any attribution report as a loss.
Web Content Accessibility
Guidelines (WCAG)
The Technical Standard
Courts Actually Use
The ADA’s silence on specific technical web standards is often filled by courts and the Department of Justice through their consistent reference to the Web Content Accessibility Guidelines. This specification, maintained by the W3C, has become a benchmark for evaluating whether a website meets its public accommodation obligations.
- Level A:
- Level A covers the most fundamental accessibility requirements: text alternatives for images, keyboard operability, seizure prevention, and basic navigability. Failing Level A means the site has barriers so severe that entire categories of disabled users cannot interact with it at all. Most automated scanners test Level A criteria first, and most demand letters cite Level A failures as the primary violations.
- Level AA:
- Most commercial websites strive for Level AA conformance, which encompasses a range of critical accessibility standards including color contrast ratios, consistent navigation patterns, visible focus indicators, and captioning requirements for pre-recorded video. Documenting compliance at this level gives Philadelphia businesses a defensible position if a demand letter arrives.
- Level AAA:
- The pursuit of Level AAA conformance is typically reserved for government agencies and specialized disability services organizations due to its high standards and complexity. For most businesses, the more practical question revolves around achieving Level AA conformance, which strikes a balance between accessibility and feasibility.
- WCAG 2.2 and the Regulatory Shift:
- WCAG 2.2, published in 2023, adds success criteria for focus appearance, dragging movements, and accessible authentication. The Department of Justice has not formally adopted 2.2 yet, but regulatory bodies and plaintiff attorneys are already citing it. Organizations auditing against 2.1 today should expect 2.2 to become the reference standard within the next regulatory cycle.
Achieving Level AA conformance through documented processes significantly enhances a business’s defense posture in ADA-related claims, making it substantially more credible and reducing the risk of commonly cited violations.
Screen Reader Compatibility & Semantic Structure
Blind Users Hear the Code, Not the Design
Screen readers (JAWS, NVDA, VoiceOver) parse HTML and convert it to synthesized speech or Braille output. For that process, the visual layer might as well not be there. What the software reads is the markup. Judge a page on visual effect alone and it can pass inspection in a browser while making no sense at all to someone hearing it through a screen reader; structural integrity is what settles that question, not polish. Broken semantic markup is not rare. Most template-based site builders produce exactly that by default.
Heading Hierarchy:
Ask how a screen reader user gets around a page and the answer is the heading tags, jumping H1 to H2 to H3. Simulate a heading with large bold text and leave the actual heading tag out of the HTML, and that navigation stops working entirely. The user cannot skim. The words arrive one at a time, in whatever sequence the DOM hands them over. Read heading tags as typography and the point has been missed: they are the navigational infrastructure the page runs on.
Alternative Text for Images:
Reaching an image element, the screen reader reads out the alt attribute. An empty alt attribute produces silence. Open the media library and every IMG_5044.jpg sitting in it is noise, carrying no informational content whatsoever. Alt text descriptive enough to carry what the image communicates does two jobs from one edit: it satisfies WCAG and it gives search indexing something to read. Set the compliance requirement beside the SEO requirement and both point at the same piece of work.
Semantic HTML solves most of this. ARIA fills the gaps HTML cannot address. Apply ARIA incorrectly to a page that was already well structured and the result is new problems, not old ones solved. The tools work together; neither replaces the other.
Keyboard Navigation & Focus Management
Three Keys Are the Entire Interface
Motor impairments, tremors, and paralysis make a mouse unusable. Keyboard navigation is the alternative: Tab moves forward, Shift-Tab moves back, Enter or Space activates. A website that cannot be fully operated through this three-key sequence is inaccessible to every user who cannot grip or control a pointing device.
Visible Focus Indicators:
Links, buttons, form fields, and custom controls all need a visible outline or highlight when selected via keyboard. CSS resets and design systems routinely suppress browser default focus styles for aesthetic reasons, stripping the only visual signal keyboard users have about their position on the page. WCAG 2.2 tightened the requirements: focus indicators now need a minimum contrast ratio and area to qualify.
Skip Navigation Links:
A skip link at the top of each page lets keyboard users bypass the navigation menu and jump straight to main content. Without it, every interior page load forces the user to tab through every menu item before reaching the first word of actual content. On sites with 50 or more navigation elements, that is not an inconvenience. It is a barrier.
Custom components like carousels and date pickers have specific keyboard interaction patterns defined in the ARIA Authoring Practices Guide. A carousel that looks operational but cannot be advanced with arrow keys, or a date picker that traps focus without an escape route, is a compliance failure regardless of how polished it appears visually.
Color Contrast & Visual Accessibility
Light Grey Text on White Is Not Subtle. It Is a Violation.
Design trends favor muted palettes and thin typography. WCAG requires minimum contrast ratios. These two priorities collide constantly. Some form of color vision deficiency affects roughly 8% of men, which is no rounding error in any audience. Low vision affects a large share of adults over 60, a demographic with significant purchasing power. The contrast ratio is not subjective; a contrast analyzer produces a number, and that number either passes or fails. Two colors that look plainly different on a designer’s monitor can come back at 2.8:1 under the WCAG luminance formula, and the formula is what gets cited in a complaint.
Normal Text Contrast Threshold:
Body text and interface labels require a 4.5:1 contrast ratio against the background. This applies to every text element a user needs to read, including navigation links, form labels, error messages, and placeholder text. Thin fonts at small sizes often fail this threshold even when the color appears readable on a designer’s calibrated monitor.
Large Text and Graphical Elements:
Large text, defined as 18pt regular or 14pt bold, requires a 3:1 contrast ratio against adjacent colors. Graphical elements like icons and form control outlines fall under the same 3:1 threshold. Decorative elements without informational content are exempt, but that exemption is narrower than designers typically assume.
Color as the Sole Differentiator:
Color alone should never be relied upon to convey crucial information. A required field marked only by color can fail users with red-green color vision deficiency. Similarly, a hyperlink distinguished solely by color, without additional treatment, risks failing the same criterion. A simple test: convert the page to grayscale. If the information still conveys meaning, it passes; if it disappears, it fails.
Initial WCAG audits often reveal at least one brand color palette failure. Fortunately, remediation is usually minor. A 2-3% adjustment in luminance can recover the necessary ratio without significantly altering the brand’s visual identity. The audit provides specific values to target; the fix rarely requires drastic changes.
Video Captioning & Media Accessibility
Uncaptioned Video Excludes More Users Than Expected
Video is among the easiest accessibility failures to identify and among the most consistently deprioritized. Deaf and hard-of-hearing users cannot access audio content. Blind users cannot access visual content. Both populations are larger than organizations typically assume, and neither failure is difficult to remediate when addressed before publication. The cost of captioning a video at production is a fraction of the cost of retrofitting a library of published content after an audit or a demand letter.
Closed Captions:
Pre-recorded video with audio requires synchronized captions that identify speakers, convey relevant sound effects, and time-align with the spoken content. Auto-generated captions from YouTube or Vimeo do not meet WCAG standards without human review and correction; documented error rates on automated transcription exceed 20%, and they climb higher on proper nouns and industry vocabulary. Caption files (SRT, VTT) should be edited for accuracy, proper punctuation, and speaker identification before publication.
Audio Description:
Video that conveys information visually, through on-screen graphics, demonstrations, or text, requires an audio description track for blind users. Audio description narrates the visual content during natural pauses in the dialogue. Where the existing pauses are too short to adequately describe the visual content, extended audio description halts playback so the narration can be accommodated. The requirement applies to informational content; decorative visuals without informational function are exempt.
Transcripts and Autoplay Prohibition:
Audio-only content requires a full text transcript. Beyond satisfying WCAG, transcripts produce indexable text that search engines rank; a podcast without a transcript is invisible to search. Auto-playing video with sound violates WCAG 1.4.2 directly. The silent hero loop counts here too: video that auto-plays without sound, muted background loops very much included, can trigger vestibular disorders and talks over screen reader audio at the same time. The user initiates playback. That is the rule.
Building media accessibility into production workflows costs almost nothing per asset. Retrofitting it across a library of 200 published videos is a major remediation project. The timing of that decision determines the invoice.
Accessibility Overlays vs. Manual Remediation
The Widget in the Corner Does Not Change the Code Underneath It
The sales pitch for an overlay product is a single script and nothing more: install the tag, receive compliance. The market for these products is large. There is a documented record of how they fared in actual litigation, and it is largely negative. More than one federal case has moved forward against a defendant who was running an overlay product. In several, the overlay was cited not as a mitigating factor but as a contributing one, interfering with screen reader operation and producing a worse experience for users with disabilities than the unmodified site would have.
Why Overlays Do Not Produce Compliance:
An overlay operates on the rendered DOM output. Semantic structure absent from the source HTML remains absent, keyboard interaction patterns inside JavaScript-driven components remain uncorrected, and focus management failures in custom interfaces remain unaddressed. The automated logic then manufactures fresh errors of its own: images it misidentifies pick up the wrong alt text, content gets reshuffled into an order that damages comprehension, and screen reader announcements come out doubled or flatly contradicting each other. What an overlay contributes is a layer of interference; the underlying problem sits there unresolved beneath it.
What the Litigation Record Shows:
ADA accessibility lawsuits have gone as far as naming the overlay vendor itself as a co-defendant. Formal published positions from the National Federation of the Blind and from other major disability advocacy organizations oppose overlays as a compliance path. Organizations that installed an overlay product and filed the matter under resolved went on to receive demand letters and to face litigation. The overlay did not function as protection. In some, it was entered as proof that the organization already knew the obligation existed.
The longer accessibility sat deferred, the larger the remediation bill turns out to be. A site addressed during design and development costs a fraction of what a legacy site with structural HTML problems costs to fix after the fact.
Accessibility Audits & Testing Protocols
Automated Tools Find 30% of Issues. The Rest Require a Human.
Automated scanners like WAVE, Axe, and Lighthouse crawl the DOM and flag measurable infractions: missing alt attributes, contrast failures, absent form labels, empty links. These tools are fast and consistent, but they catch roughly 30% of WCAG violations by most professional estimates. The remaining 70% require human judgment because they are contextual. An automated tool can detect that a button has a label; it cannot determine whether that label makes sense.
An audit is a snapshot. Content updates, code deployments, plugin changes, and third-party integrations introduce new variables the day after the audit report is delivered. Commercial sites typically need quarterly automated scans combined with an annual manual audit. High-volume publishing operations may need even more frequent review.
- Automated Scanning: Automated tools serve as a baseline, consistently identifying mechanical infractions with reliability. Running these tools in continuous integration pipelines catches mechanical regressions before deployment, keeping new code from reintroducing violations that were already fixed. The limitation is contextual judgment: automated checks flag an ambiguous button label but cannot determine whether the label makes sense to a screen reader user in that specific workflow.
- Manual Testing with Assistive Technology: Testing with a keyboard and a running screen reader (JAWS, NVDA, VoiceOver) exposes problems automated tools miss entirely. Can a user complete checkout using only a keyboard? Does the page announce dynamic content changes to the screen reader? These questions require a human sitting in front of the interface, operating it the way a disabled user would.
Mobile App &
Responsive Accessibility
Desktop Compliance Does Not Mean Mobile Compliance
Mobile accessibility falls under the same WCAG guidelines as desktop, but mobile interactions introduce problems desktop testing does not catch. The majority of local search traffic in Philadelphia originates on phones. A site that passes desktop accessibility checks can still fail its mobile users on touch targets, zoom behavior, and gesture handling. Desktop and mobile testing require separate passes.
Touch Target Size and Spacing
Touch Target Size and SpacingWCAG 2.2 sets a minimum touch target size of 24×24 CSS pixels, with a recommendation of 44×44. Targets smaller than this cause errors for users with motor impairments, tremors, or limited fine motor control. Spacing between adjacent targets matters as much as the target size itself; tightly packed links and buttons create compound failure points on touchscreens.
Screen Orientation and Text Zoom
Screen Orientation and Text ZoomScreen orientation cannot be restricted; some users rely on devices mounted in fixed positions for optimal use. This includes individuals with disabilities who require specialized equipment. Text must remain legible at a zoom level of 200%, without content loss, and content must reflow without horizontal scrolling at 400% zoom. Many organizations fail to test their responsive layouts properly, often only testing at standard zoom.
Document Remediation (PDFs)
The Files in the Media Library Carry the Same Legal Weight as the Pages
Inaccessible documents lurk in the background of many websites. Menus, rate sheets, annual reports, application forms, and installation guides pile up as PDFs, silently sabotaging accessibility efforts. Almost every PDF exported from InDesign or Illustrator is a visual representation devoid of semantic structure: no reading order, no heading tags, no alt text for charts, no table markup. Screen readers encounter these documents in whatever chaotic sequence the layout engine produced.
- Tagging and Reading Order: The foundation of PDF remediation is building a semantic tag tree: paragraph tags, heading tags, list tags, and table tags that provide an explicit navigation structure for assistive technologies to follow. This contrasts sharply with the unpredictable sequence that screen readers encounter when encountering untagged documents.
- Alternative Text and Artifact Marking: Effective alt text is crucial for conveying information within charts, graphs, and images embedded in PDFs. Decorative elements must be tagged as such so screen readers can skip them, rather than announcing their presence. A precise description of a data visualization is accessible; conversely, an untagged chart communicates nothing to visually impaired users.
- Form Fields and Tab Order: PDF forms require meticulous attention: form fields need to be tagged and programmatically associated with clear labels, while a defined tab order makes the form keyboard-operable. Without this remediation, the form remains visually present but functionally invisible to assistive technology.
Each document on a website requires independent assessment; compliance status does not inherit from the site’s own remediation. Organizations that complete site remediation without auditing their document library create a vulnerability that can lead to costly follow-up demands.
Frequently asked questions
Does the ADA apply to small businesses with no physical location?
Title III of the Americans with Disabilities Act (ADA) applies broadly to places of public accommodation, and courts have consistently held that websites are included, regardless of whether a physical location exists. The ADA’s reach is not limited by business size or revenue threshold. In fact, it’s precisely because smaller businesses may struggle to absorb the costs of litigation that they’re often targeted with ADA claims. This creates an uneven playing field, where larger companies can afford to litigate and smaller ones are more vulnerable.
What are the actual financial consequences of an ADA accessibility violation?
ADA Title III lawsuits award no monetary damages to a private plaintiff at all, but defense costs, plaintiff attorney fees, and settlement amounts routinely reach five figures before remediation work begins. Serial plaintiffs and their attorneys file hundreds of cases per year. The initial demand letter typically requests a settlement in the $5,000 to $25,000 range. Ignoring the letter escalates costs significantly. A case that proceeds past the demand stage routinely reaches $50,000 to $100,000 in combined expenses, even though the statute itself awards the plaintiff no damages.
Do accessibility overlays satisfy ADA compliance requirements?
No. Federal courts have addressed overlay products directly in litigation, and multiple courts have allowed ADA claims to proceed against defendants using them. The Department of Justice has not endorsed overlays as a compliance solution, and the National Federation of the Blind has formally opposed them. Installing an overlay demonstrates awareness of accessibility obligations but does not discharge it. In documented cases, the overlay was cited as evidence that the defendant knew about the problem and chose a cosmetic response over a substantive one.
How often does an accessible site need to be retested?
Websites are dynamic systems that change through content updates, code deployments, plugin modifications, and third-party tool integrations. This introduces new compliance variables after the fact. A site that passed a thorough audit at launch can fail it six months later with no deliberate change to accessibility work. A defensible maintenance cadence for most commercial sites involves quarterly automated scanning plus an annual manual audit.
What does WCAG Level AA actually require in practical terms?
Level AA includes requirements such as text alternatives for non-text content, captions for pre-recorded audio and video, content that reflows without information loss at 400% zoom, sufficient color contrast across all text and graphics, full keyboard operability, visible focus indicators, no flashing content more than three times per second, descriptive page titles and headings, correctly labeled form inputs, and error messages identifying specific problems. The full specification lists 55 success criteria across Levels A and AA combined.
Are PDF documents covered under ADA digital accessibility requirements?
Yes. PDFs published on a website are part of the digital public accommodation and subject to the same obligations as surrounding web pages. A remediated PDF adds semantic tag structure, establishes reading order, applies heading and list markup within the document, and writes alt text for embedded charts and images. Each document is evaluated independently.
What is the difference between an accessibility audit and an accessibility certification?
An audit assesses conformance against WCAG criteria at a specific point in time, producing findings, severity ratings, and remediation guidance. A certification from a private organization indicates that an audit was completed and conformance was verified at the time of issuance. Neither document guarantees ongoing compliance; both are superseded by new content changes or code deployments.
Does an accessibility statement on the website provide legal protection?
An accessibility statement is not a shield against litigation but rather supports a good-faith defense by demonstrating awareness of obligations and documented commitment to meeting them. Check any statement against three tests: does it name the conformance standard it is targeting, does it acknowledge the limitations already known, and does the contact mechanism it offers actually work for a user who encounters a barrier.
Who is responsible when an embedded third-party tool fails accessibility standards?
The business operating the website bears the compliance obligation, not the vendor’s code. Installing a booking widget or payment form that fails WCAG creates a violation on the host site regardless of who wrote it. Vendor contracts should include explicit accessibility conformance representations, and new third-party tools should be tested for accessibility before going live.
What is the relationship between web accessibility and search engine optimization?
Substantial overlap exists between what WCAG requires and what search algorithms reward. Semantic heading structure, descriptive alt text, meaningful link text, video transcripts, logical document hierarchy, and clean HTML satisfy both simultaneously. Accessibility remediation typically improves technical SEO metrics as a secondary effect with no additional optimization work required.
Google partner
Premiere Agency
