Digital Accessibility Inspection
Can every customer actually use your website?
A manual, code-level review of your winery website against WCAG 2.2 AA, which is the current standard for web accessibility. Real fixes in the code, not a widget in the corner.
PDG's founder has used crutches full-time for over forty years. That doesn't make him a compliance lawyer, and it doesn't replace WCAG training. It does mean that when we talk about accessibility, we're not reading from a script.
Why this matters
Two reasons, and the honest one first: more than one in four American adults…over 70 million people…live with a disability, according to the CDC. Many of those disabilities affect how people use the web. A site they can’t navigate is a tasting room with a step at the door — those visitors don’t complain; they just leave.
The second reason is legal exposure. Digital accessibility lawsuits are on track to top 6,000 in 2026 — a record year, per UsableNet’s 2026 midyear report — and e-commerce sites draw roughly two-thirds of the filings. Illinois and several other wine-producing states have surged to the second most active state in the country. And the “accessibility widget” shortcut doesn’t help: companies using overlay widgets kept getting sued at a steady clip all year. Real fixes are the only real protection.
This isn’t worst-case-scenario storytelling. It’s website maintenance that used to be optional and no longer is. We treat it the way we treat backups — not because something bad is about to happen, but because you don’t want to be the winery that finds out the hard way.
What we do differently
Many providers install an “accessibility widget”, which is a small tool in the corner of the site offering font-size and contrast adjustments. Widgets help a small number of users, and they do not fix the underlying code. Courts have increasingly treated widget-only sites as evidence of awareness without action.
Real accessibility work happens at the code level: alt text, form labels, keyboard navigation, focus states, semantic HTML, ARIA roles. That is what this inspection covers.
What the inspection covers
Every WCAG 2.2 AA success criterion, organized under the standard's four principles, in plain language:
Perceivable
Can users perceive the information? Images, video, color contrast, and text alternatives.
Operable
Can users operate the interface? Keyboard access, timing, seizure risks, and navigation.
Understandable
Is the content readable and predictable for people and for the tools they rely on?
Robust
Can assistive technologies, such as screen readers and other tools, reliably parse the site?
How the inspection is done
Page by page, manually. Automated tools catch what the human eye misses, but they are never the sole check.
- Screen reader testing
- Keyboard-only navigation testing
- Color contrast measurement
What you receive
A dated Inspection Record. Each finding maps to a specific WCAG 2.2 AA success criterion, includes a severity estimate, effort estimate, and remediation approach, and every finding can be reproduced with a specific source or screenshot. You can check each claim yourself.
Price and timeline
$2,500
Two to three weeks from kickoff to delivery.
The inspection fee credits 100% toward remediation if you choose to have PDG fix what it found.
Staying accessible after the fix
A one-time inspection is a snapshot. Content gets added, forms get updated, images get swapped, and every change can make the accessibility baseline drift. Staying accessible means checking as you go, not checking once and hoping it holds.
That’s where this connects to a Care Plan: the baseline established here gets maintained as the site changes, which is the only way compliance actually holds over time.
Wondering where your site stands?
Start with the free call. It's a 20–30-minute call, with no commitment. We'll look at your site together and tell you honestly whether a full inspection makes sense.
Book a free visibility call