Extensions

Chat Widget Accessibility Review

Your chat widget is checked against WCAG 2.2 AA and fixed, so people using keyboards or screen readers can use it too.

If your chat widget cannot be used with a keyboard or a screen reader, some visitors simply cannot ask you anything. This add-on reviews the chat interface of the agent you already run against WCAG 2.2 AA criteria, fixes the problems found and checks it again. You get a before-and-after report showing what changed.

Checks the widget against WCAG 2.2 AA criteria
Fixes the problems found, not just lists them
Tested with a keyboard and a screen reader

$1,500 10–20 working days

Choose delivery and add to cart Ask an expert

Wooden ramp with a brass rail leading to a small doorway, a chat widget anyone can reach and use.

What it is

Chat Widget Accessibility Review is an add-on that reviews the chat interface of an existing Upmark Labs agent against WCAG 2.2 AA criteria and fixes the problems it finds. It covers keyboard use, screen readers, contrast, focus and text sizing. It fits messaging agents and knowledge chatbots.

Why businesses buy it

Accessibility problems turn away customers you never hear from, and in many markets they are also a legal risk. Automated scanners only find part of the issues and fix nothing. This review includes real keyboard-only and screen reader use, then fixes the widget itself and checks it again. The written scope covers keyboard use, screen readers, contrast, focus and text sizing for one widget, with a before-and-after report, so you can show what was done.

Problems this solves

Visitors using a keyboard or screen reader cannot use the chat

This add-on reviews your chat interface against WCAG 2.2 AA criteria, covering keyboard use and screen readers. The problems it finds are then fixed in the widget itself.

Low contrast or tiny text makes chat replies hard to read

Contrast, focus and text sizing are part of the review. Each issue found is corrected, so more visitors can read and follow the conversation comfortably.

You cannot show what was checked when accessibility comes up

The test report records what was reviewed and what was fixed. You have a clear record of the work when customers or partners ask about accessibility.

Scope card SKU UPM-A0050

Chat Widget Accessibility Review

Everything this build includes, written down before you pay. Choose how you want it, own the code or license it yearly, then the delivery speed and any add-ons.

$1,500 one-time build price

What is included

Channel: As per the parent product
Integrations: As described in the add-on
Knowledge: As per the parent product
Workflows: Reviews and fixes an existing chat interface against WCAG 2.2 AA criteria
Languages: As per the parent product
Testing: Tested together with the parent product
Revisions: 1 round
Handoff: Written handover report
Support: 14 days after launch

A good fit if

Your website has accessibility commitments, and the chat widget has never been checked against them.

A customer has reported they could not use the chat with a keyboard or screen reader.

Your organization works to WCAG 2.2 AA, or is moving to it.

The widget belongs to an Upmark Labs messaging agent or knowledge chatbot.

Not the right fit if

You want the widget redesigned to your brand rather than reviewed. Custom Chat Widget Design does that, and pairs well with this review.

Your agent has no website chat yet. Web Chat Channel Add-on adds the widget first.

You need your whole website audited, not just the chat. That is outside this add-on; ask for a Change Quote.

Your product is a voice agent or action agent. This review applies to messaging agents and knowledge chatbots.

How it works

The widget is reviewed. We check it against WCAG 2.2 AA criteria that apply to a chat interface, on desktop and mobile.
Assistive technology is used. The widget is operated with a keyboard alone and with a screen reader, start to finish.
Findings are listed. Each problem is recorded with the criterion it fails and how it affects a user.
Problems are fixed. Fixes are made in the parent agent's widget, such as labels, focus order, contrast and announcements of new messages.
The widget is checked again, then you receive the before-and-after report, one revision round and a written walkthrough.

What you provide within 72 hours

Your portal lists these the moment you order. Delivery starts the working day after everything is in and your access is checked.

The order reference of the agent whose widget is reviewed
Links to the pages where the widget appears
Your accessibility statement or policy, if you have one
Any accessibility complaints or feedback you have received about the chat
One person who approves the fixes

The 72-hour rule. Send everything on your checklist, including access, within 72 hours of ordering so your build starts on time.

Timeline

Start Widget pages and existing feedback collected

Weeks 1–2 Review against WCAG 2.2 AA criteria

Week 2 Findings report sent to you

Week 2 Fixes made in the widget

Week 2 Re-check, your review and one revision round

Go-live Accessible widget live, report and walkthrough handed over

Delivery options, in working days (Monday to Friday) from completed intake. They can extend because of national or public holidays, technical issues outside our control (such as platform outages, third-party changes, account approvals or access delays), or natural disasters and other events beyond our control. If a delay happens, we tell you in writing with a new date.
Option	Delivery time	Price
Standard	10–20 working days	$1,500

What you receive at handover

Your chat interface reviewed against WCAG 2.2 AA criteria
Fixes applied to the problems found
A test report listing what was checked and fixed
Updated documentation, a handoff note and a short written walkthrough

Expected benefits and how to measure them

Helps more visitors use your chat, including those with disabilities
Can reduce complaints about a hard-to-use widget
Gives you a record of accessibility work

Open accessibility issues: Compare the issues listed in the review with a recheck after fixes.
Keyboard-only test: Have a staff member complete a full chat using only the keyboard, before and after.
Accessibility complaints: Count related complaints or support tickets in the months before and after.

Before you start: Try the chat with keyboard only and a screen reader, and note what fails. Keep any past accessibility feedback.

These are things to track, not promised results. Outcomes depend on your data, your team and your market.

Running costs

Accessibility fixes add no running cost. The agent's usage stays in your own accounts as before.

Ask about running costs

Custom requirements

Fixing parts of your website around the widget, reviewing other interfaces, or providing a formal conformance certificate is beyond this add-on. Add a checkout note for a written Change Quote. Larger or bespoke projects go through the Custom AI request form instead.

Request a custom version

Keep it running

Later changes to the widget can reintroduce problems. Checking a change for accessibility fits within the change hours of the parent product's maintenance, which grows in line with the add-on's price.

Adds $75/mo to maintenance

Covered by the main product's maintenance, which grows by this amount.

How maintenance works

How this compares

	Do it yourself with a SaaS tool	Hire a custom agency	Upmark Labs
Price	Automated scanners bill monthly and do not fix anything	An accessibility consultancy quotes per audit	Ours is one fixed price with review and fixes included, shown before you buy
Method	Automated scan only	Depends on the brief	Ours includes keyboard-only and screen reader use
Result	A list of issues	Set per project	Ours is a fixed widget with a before-and-after report

Questions about this product

Which WCAG criteria does the chat widget review cover?

The WCAG 2.2 AA criteria that apply to a chat interface. In practice that means keyboard access, visible focus, labels for buttons and fields, color contrast, text resizing, and announcing new messages to screen readers. The report lists each criterion checked and whether the widget passed before and after fixes.

Do you fix the problems or just report them?

Both. Problems in the widget itself are fixed as part of the add-on, then the widget is checked again. The report shows what failed, what was changed and the result. Problems in your surrounding website are noted but not fixed, because they sit outside the widget.

Is this an accessibility certification?

No. It is a review and fix against WCAG 2.2 AA criteria for the chat widget, documented in a report you can share. A formal conformance statement for your whole site needs a wider audit. The report is useful evidence for your own accessibility statement.

Do you test with real assistive technology?

Yes. Besides automated checks, we use the widget with a keyboard alone and with a screen reader, from opening the chat to reading a reply and closing it. Many chat problems, such as new messages not being announced, only show up this way.

Is a conformance certificate included with the review?

No. You get a review against WCAG 2.2 AA, fixes to the widget and a before-and-after report, but not a formal certificate. The report is useful evidence for your own accessibility statement. The review follows the delivery speed chosen for its product, with a fixed price and date shown before you pay.

Why is it not available for action agents?

The add-on is matched to products whose main surface is a chat widget: messaging agents and knowledge chatbots. If your action agent does use a website chat widget, describe it in the custom requirements note and we confirm whether a review can be quoted.