Social proof every visitor can use
Make Testimonial Widgets More Accessible
A testimonial slider that drifts on its own, swallows the Tab key or prints pale grey quotes on a pale card shuts out the visitors who rely on a keyboard, a screen reader or a steady page. None of that shows up when you glance at the widget with a mouse. Run the checks below against the widget on your live page, based on the W3C Web Accessibility Initiative guidance we read, then fix what fails with the choices you control.
- Motion, keyboard, focus, contrast and structure checks
- Each check points at the W3C WAI page behind it
- Run it on your own page with no account
The problem, solved
Where testimonial widgets lock people out, and what you can change
StoryProof does not claim any accessibility feature for its widgets. These fixes use choices you control, and every one still needs the test above it.
Situation 1 of 6
The slider keeps moving while I read
Motion that starts by itself and runs past five seconds needs a way to pause, stop or hide it. Without one, slow readers lose the quote halfway through.
How StoryProof solves it
You are not tied to a moving layout. 19 widget layouts, from walls and carousels to compact badges and avatar strips. Try a static one, such as a wall or list, and run the motion checks again.
Situation 2 of 6
Tab jumps straight past the testimonials
If the previous and next controls are not buttons a keyboard can reach, anyone who cannot use a mouse sees only the first quote.
How StoryProof solves it
Choose which approved testimonials go into the widget so that the best one sits first, where every visitor meets it, then test whether the rest are reachable.
Situation 3 of 6
Forty quotes to tab through before the footer
A long selection makes keyboard users press Tab dozens of times to get past one section of the page.
How StoryProof solves it
Each widget shows the approved testimonials you pick for it, so a short selection of six or eight keeps the section quick to pass.
Situation 4 of 6
Screen reader users cannot find the section
A widget dropped in with no heading above it is a block of quotes with no label, so nobody navigating by headings can jump to it.
How StoryProof solves it
The embed is a div you place yourself, so the heading above it and the region around it are part of your page. Give it a real heading such as "What customers say".
Situation 5 of 6
Our proof is all video with sound
A visitor who cannot hear, or is reading in a quiet office, gets nothing from a page where every testimonial is a clip.
How StoryProof solves it
The same collection link accepts a written review as well as video or audio, so ask for written ones too and place them in the widget beside the clips.
Situation 6 of 6
We want a second way in
If a widget fails a check you cannot fix this week, visitors need another place to read the same testimonials.
How StoryProof solves it
Every plan includes a Wall of Love, a hosted page of approved testimonials with its own link. Link it beside the widget, and run the same checks on that page too.
Checklist
Test the testimonial widget on your live page
Open the page with the widget, put the mouse aside, and work down the list. A tick means you saw it work, not that it should.
Ticks are kept in this browser tab only. Nothing is sent or saved.
What failed, and the change to try first
In StoryProof
Work the fixes into StoryProof
- 1
Record what failed
Copy the open items from the checklist into a ticket, with the page address and the browser you used.
- 2
Try a still layout
If motion failed, choose a layout from the range that does not move by itself and rerun the motion checks.
- 3
Shorten and balance the selection
Pick fewer testimonials for the widget, and include written ones next to any clips.
- 4
Label the section on your page
Add a visible heading directly above the widget div, then check it appears when a screen reader lists headings.
- 5
Link the hosted page
Add a plain text link to your Wall of Love beside the widget as a second route to the same testimonials.
What happens next: Retest with the checklist after every redesign. A theme update can change contrast and focus styles without anyone touching the widget.
Before you start
What this checklist is not
Not an audit or a conformance statement
Passing these checks does not make a page conform to WCAG. A full audit covers the whole page with assistive technology and, ideally, people who use it daily.
StoryProof makes no accessibility claim
We have not verified any accessibility feature of the widgets, so this page does not say they have one. Test the widget on your page and judge by what you see.
Not legal advice
Accessibility duties differ by country and sector. This page does not say what the law requires of your site; ask a specialist if that is the question.
Your page styles affect the result
Fonts, backgrounds and focus styles from your theme can change what a visitor sees around the widget. Test on the real page, not a blank one.
W3C pages are the authority
The checks summarise the WAI pages listed under sources. Where a check here and the W3C wording differ, follow the W3C page.
FAQ
Questions people ask
Short answers to what usually comes up next.
Is the StoryProof widget WCAG compliant?
StoryProof has not published an accessibility statement for its widgets, so this page makes no such claim. Run the checks above on your own page and contact support with anything that fails.
Do I have to stop a testimonial carousel from moving?
WCAG 2.2.2 asks for a way to pause, stop or hide motion that starts on its own, lasts more than five seconds and sits beside other content. A layout that does not move avoids the question.
What contrast ratio should testimonial text have?
WCAG 1.4.3 sets at least 4.5:1 for normal text and 3:1 for large text. Measure it with a contrast tool against the actual card colour behind the quote.
How do I test with a screen reader if I have never used one?
Most computers include one: VoiceOver on a Mac, Narrator on Windows. Turn it on, move to the section by heading, and listen for the section heading, the button names and the slide position.
Are audio and video testimonials a problem for accessibility?
Only when they are the sole way the point is made. Keep written testimonials in the same widget so a visitor who cannot listen still gets the proof.
Still have a question? Ask the StoryProof team or book a demo.
Show proof every visitor can read
Collect written, video and audio testimonials with one link, then pick a layout and test it on your page.
Sources
- Carousels Tutorial, W3C Web Accessibility Initiative. Checked 2026-11-13.
- Carousels Tutorial: Functionality, W3C Web Accessibility Initiative. Checked 2026-11-13.
- Understanding Success Criterion 2.2.2: Pause, Stop, Hide, W3C Web Accessibility Initiative. Checked 2026-11-13.
- Understanding Success Criterion 2.1.1: Keyboard, W3C Web Accessibility Initiative. Checked 2026-11-13.
- Understanding Success Criterion 2.4.7: Focus Visible, W3C Web Accessibility Initiative. Checked 2026-11-13.
- Understanding Success Criterion 1.4.3: Contrast (Minimum), W3C Web Accessibility Initiative. Checked 2026-11-13.
Last updated 2026-11-13.