Think Tank QA

Accessibility Consulting Services

WCAG and ADA Consulting for Digital Products: Building Toward Real Compliance and Usability

Trusted by product teams at leading enterprises and startups

Accessibility consulting services help organizations meet legal accessibility requirements and build products usable by everyone, including users with visual, motor, auditory, and cognitive impairments.

Think Tank QA works as a WCAG consultant across the work of identifying accessibility issues, planning remediation against the standards that apply to your product, and supporting development teams through the fixes.

Engagements span web applications, mobile apps, and product surfaces governed by WCAG 2.2 AA and ADA accessibility requirements.

What's Included

What Accessibility Consulting Covers

Accessibility consulting is the ongoing strategic and remediation work that sits around a baseline accessibility assessment. Each capability below is one part of the engagement; most engagements combine several.

01

WCAG and ADA Compliance Testing

Testing against WCAG 2.2 AA as the current published recommendation, with reference to WCAG 2.1 AA for the broader installed-base baseline. The assessment combines AI-accelerated automated scanning with manual review and assistive-technology testing. Compliance testing also covers the U.S.

Americans with Disabilities Act (ADA) and Section 508 of the Rehabilitation Act for federal-facing and state-and-local government contexts. Testing is the entry point to a broader engagement; the formal accessibility audit is the productized point-in-time assessment that establishes the baseline.

02

Assistive Technology Validation

Validation across screen readers, keyboard-only navigation, voice input, and magnification tools. Assistive technology testing surfaces issues that visual or automated review cannot: focus order problems, content read in the wrong sequence, controls that look usable but are unreachable, and form behavior that breaks under non-mouse input.

AT validation is where most accessibility issues that matter to real users get found, and it is done by hand, not by a scanner.

03

Accessible Design Review

Review across color contrast, content structure, heading hierarchy, tab order, form usage, and interactive elements. Design review identifies barriers at the layout and component level before they become remediation work downstream. Design teams typically engage on this earlier than engineering; the earlier accessibility enters the design system, the less remediation costs at release.

04

Remediation Support and Developer Enablement

Detailed guidance for fixing accessibility issues, including code-level recommendations, design corrections, and developer training. Remediation support runs alongside development teams rather than as a separate hand-off. The goal is for the team to be able to maintain accessibility past the engagement rather than depending on the consulting relationship indefinitely.

The Process

How We Engage

Most engagements follow a familiar arc: baseline established, prioritized remediation, ongoing support. The shape adapts to where the product is in its accessibility maturity.

01

Baseline Assessment

The engagement starts with an accessibility audit across the relevant product surfaces, pairing AI-accelerated automated scanning with manual and assistive-technology testing. The audit produces a documented inventory of conformance gaps against WCAG 2.2 AA, severity ratings, and a categorization that informs the prioritization that follows.

02

Prioritized Remediation Planning

Remediation is prioritized by severity and by risk: issues that block users with disabilities entirely come first, followed by issues with legal exposure (the conformance failures that drive demand letters and complaints), then issues that affect usability without blocking. The remediation plan reflects the product’s actual release cadence and the team’s capacity to absorb the work.

03

Developer and Design Team Support

Remediation support runs through the team’s normal development process. Where manual testing uncovers accessibility issues during the regular QA cycle, those issues route into the remediation backlog and inherit the same prioritization framework. Training sessions for engineering and design teams are scoped to the issues the audit surfaced rather than generic accessibility education.

Who This Is For

Engagement Deliverables

Case Study

Accessibility Audit and Consulting for Big Timber Media

Think Tank QA partnered with Big Timber Media (BTM) on a WCAG 2.2 AA conformance engagement covering four websites and two online ebook readers for their client, ABDO Publishing, ahead of a regulatory compliance deadline.

The work combined a two-week audit using automated tools (Axe DevTools, Google Lighthouse) and manual testing across JAWS, NVDA, and VoiceOver, followed by ongoing consultation with the BTM development team during the rebuild of abdodigital.com.

Deliverables included audit findings reports with critical- and high-severity categorization, walkthroughs to support the dev team’s implementation, and Voluntary Product Accessibility Templates (VPATs) using the latest ITI templates.

Frequently Asked Questions

Accessibility consulting is the strategic and operational work of making a digital product usable by people with disabilities and compliant with the accessibility laws that apply to it. The work typically covers assessment of the current state against WCAG and applicable regional standards, prioritized remediation planning, developer and design team support during the fixes, and ongoing verification as the product changes. Accessibility consulting differs from a one-off accessibility audit in that consulting wraps around the audit with the planning, remediation, and team enablement that turn audit findings into a product that actually works for users with disabilities.

A WCAG consultant assesses digital products against the Web Content Accessibility Guidelines (currently WCAG 2.2 AA as the published recommendation, with WCAG 2.1 AA still widely referenced in procurement and regulation), identifies conformance gaps, and supports the team through the remediation work. A consultant’s value lies in what comes after detection: explaining what fix each violation requires, what severity and risk it carries, and how to prevent the same class of issue in future development. A good WCAG consultant works with development and design teams rather than handing them a report and walking away.

Automated tools catch a subset of WCAG issues, primarily ones that can be detected from code structure: missing alt text on images, contrast ratios below threshold, ARIA attributes used incorrectly. The scan is AI-accelerated and fast, but it cannot reliably detect issues that depend on context or interaction: focus order, content read sequence, keyboard traps, form behavior under non-mouse input, and interaction patterns that look accessible in code but fail in use. WCAG compliance consultants combine automated scanning with manual review and assistive technology testing to find the issues automation cannot detect. The combination is what produces a defensible compliance posture, since automated coverage alone leaves the majority of real accessibility issues unaddressed.

WCAG 2.2 is the current published recommendation, released by the W3C in October 2023. It adds nine new success criteria to WCAG 2.1, covering focus visibility, target size for pointer inputs, accessible authentication, and consistent help. WCAG 2.1 remains widely referenced because it is named in most existing procurement requirements, government regulations, and legal settlements. Most current accessibility consulting engagements test against WCAG 2.2 AA as the forward-looking target while still ensuring conformance with WCAG 2.1 AA for any contractual or regulatory obligation that names it specifically.

ADA compliance services help organizations meet the accessibility requirements imposed by the Americans with Disabilities Act on digital products. The ADA itself does not name a specific technical standard, but courts and regulators reference WCAG 2.1 AA (and increasingly WCAG 2.2 AA) as the practical conformance bar. ADA compliance work covers public-facing websites, mobile apps, and certain internal applications, with scope expanded by ADA Title II for state and local governments. Engagements typically combine a WCAG-based audit, prioritized remediation planning aligned to litigation risk, and documentation that supports demand-letter response or procurement review. This is general information, not legal advice; confirm your obligations with counsel.

An accessibility audit is a productized point-in-time assessment that documents where a product currently stands against WCAG and applicable standards. Accessibility consulting is the broader engagement that wraps around the audit: the prioritization, the remediation support, the team enablement, and the ongoing work as the product evolves. Most organizations start with an audit to establish a baseline; consulting is what turns the audit findings into a product that actually works for users and a team that can maintain accessibility past the initial engagement.

A standard accessibility audit report documents each conformance gap found against the WCAG criteria audited, with severity rating, issue category, the specific page or component where the issue lives, evidence (screenshot, code snippet, or AT-output), and a remediation recommendation. Audit reports also typically include an executive summary suitable for compliance and risk stakeholders, a Voluntary Product Accessibility Template (VPAT) when procurement-driven, and walkthroughs of the most affected user flows. The report is the basis for the remediation plan; the remediation work itself is the consulting engagement that follows.

Four criteria distinguish accessibility consultants. Standards depth: does the consultant work across WCAG 2.1 AA, WCAG 2.2 AA, ADA, Section 508, and (if relevant) EAA and EN 301 549, or only the U.S. frameworks? Methodology: does the engagement combine automated tooling with manual review and assistive technology testing, or does it lean on one of those alone? Remediation support: does the consultant produce code-level guidance and work with engineering teams during fixes, or stop at the audit report? Engagement model: is the engagement a one-off audit or an ongoing consulting relationship that wraps around the product’s release cadence? The buyer’s actual need (one-time legal cover versus building accessibility into the product) should drive which model fits.

Standard assistive technology testing covers screen readers (the dominant AT category for users with visual impairments), keyboard-only navigation (a baseline for users with motor impairments and for users of many other AT categories), voice input (used by some users with motor impairments and increasingly by mainstream users), and magnification tools (used by users with low vision who have not moved to screen readers). Coverage of specific products varies by engagement; most consultants will name which products they use during AT validation when asked. Coverage on mobile-specific AT (VoiceOver on iOS, TalkBack on Android, Switch Control) is usually a separate scope decision based on the product’s mobile surface.

Accessibility risk mitigation is the structured prioritization of remediation work against legal, reputational, and operational risk. The compliance-driven version prioritizes issues most likely to surface in demand letters and lawsuits: missing alt text on consumer-facing imagery, keyboard traps, form errors that block transaction completion, and missing semantic structure on high-traffic pages. The reputation-driven version prioritizes issues most likely to surface in public complaints from users with disabilities. The operational version prioritizes issues that compound across the codebase if left unaddressed. Most mature programs sequence remediation against all three, weighted by what the organization can absorb in a release cycle.

Accessibility consulting integrates with broader QA practice in three ways. First, accessibility checks become part of the regular QA cycle rather than a separate effort, and the team that runs functional testing also catches surface-level accessibility regressions. Second, the remediation backlog inherits the team’s existing prioritization and tracking. Third, the accessibility consultant works with the team’s existing tooling and review processes rather than introducing parallel ones. For organizations evaluating where accessibility fits into a broader QA effort, a QA gap analysis can help map the current state and identify where accessibility integration is most feasible.

Most engagements begin with an audit (one to three weeks depending on product surface area), followed by a prioritized remediation plan delivered with the audit findings. Remediation support typically runs in parallel with the product’s development cycle for two to six months on first engagements; longer for products with significant existing accessibility debt. Training is usually scoped as one or two sessions for engineering and design teams, focused on the categories of issue the audit surfaced. Ongoing consulting after first remediation is usually a lighter retainer focused on review of new features, periodic re-audit of changed surfaces, and continued team support as the product evolves.

Get Started

Whether you are starting from scratch on accessibility, recovering from an audit that surfaced significant gaps, or building accessibility into a product before launch, accessibility consulting reduces legal exposure and produces digital products that work for everyone. Reach out to scope an engagement.

What Are You Working On?

We’d love to show you how Think Tank QA can help you achieve better quality outcomes for your business.​