Begin with ordinary page access
A visitor should be able to read the page, use its main navigation and reach important actions without opening chat. Inspect the collapsed control on a narrow screen and beside any sticky purchase bar or cookie notice. Two individually reasonable overlays can combine to hide the content. Check landscape as well as portrait where practical. Treat any obscured control as a page integration problem even if each component claims to be accessible in isolation.
Walk through the conversation by keyboard
Use the keyboard to reach the opener, enter the conversation, move among available controls and close it. Focus should remain visible and the visitor should be able to return to the page. Read labels and error messages rather than inferring meaning from icons alone. Document the browser and exact state of the test. A screenshot of an open widget cannot establish that focus order, announcements or closing behaviour work correctly.
Test enlargement and narrow reflow
W3C’s reflow guidance uses a width equivalent to 320 CSS pixels for ordinary horizontal content, with exceptions for material that genuinely requires two dimensions. Use that as a useful test context, not a blanket certification rule. Enlarge text and check whether messages, buttons and close controls remain usable. LiveChat publishes an accessibility guide, but its statements do not certify your theme, custom content or the interaction of several overlays on your website.
Record limitations and provide another route
If the widget blocks a user from completing an essential task, correct the integration or disable the problematic configuration before relying on it. Keep a visible alternative contact route. Ask a qualified accessibility reviewer when the stakes or unresolved complexity require it; this checklist is not a conformance audit. Preserve the exact observed problem and retest the changed region after repair instead of treating a general vendor statement as evidence that the defect is gone.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- LiveChat accessibility guide — merchant statement, not our audit — Merchant documentation · livechat.com · Merchant-controlled · checked 2026-09-19
- W3C Understanding Reflow — standards guidance, not a certification of this site — Standards and certification reference · w3.org · Publisher independence not verified · checked 2026-09-19