Are Your Customer Reviews and Star Ratings Accessible? A Plain-English Guide for Business Owners
Customer reviews are some of the most valuable content on your website. They build trust, they help people decide to buy, and they quietly do a lot of your selling for you. So it is a little alarming to learn that the star ratings and review widgets on most small-business sites are completely invisible to a big group of potential customers.
If you use a third-party review tool — Trustpilot, Yotpo, Judge.me, Google review embeds, Shopify product reviews, or the testimonial section your web designer dropped in — there is a good chance that someone using a screen reader hears nothing useful when they reach it. No star rating. No score. Sometimes not even the review text. That is a problem for those customers, and increasingly it is a legal problem for you.
This guide explains, in plain English, what tends to go wrong with reviews and ratings, how to check your own site in a few minutes, and what to ask for to fix it. You will not need to touch any code.
Why reviews are a common accessibility blind spot
Reviews feel simple. Five stars, a few sentences, a name. But the way those stars get displayed on a web page is where the trouble starts.
Most star ratings are drawn with images, icons, or colored shapes. A human looking at the screen sees “four and a half gold stars out of five” instantly. But a screen reader — the software a blind or low-vision person uses to read a page aloud — does not see gold or shapes. It reads the underlying code. If that code does not include the words “rated 4.5 out of 5 stars,” the rating may as well not exist. The screen reader skips silently past it, or worse, reads out a confusing string of star characters one by one.
The second issue is that reviews are usually loaded by a third-party widget. That code is written by the review company, not by you, and not by your web designer. You inherited whatever accessibility decisions that company made — good or bad. Many popular widgets have improved over the years, but plenty still ship with ratings that are decorative-only, “read more” links that go nowhere for keyboard users, and review-submission forms that are missing labels.
The third issue is interactivity. If customers can leave a review on your site, that form has to work for everyone too. The “click a star to rate” control is one of the most frequently broken pieces of any website, because those clickable stars are often built without keyboard support. Someone who cannot use a mouse simply cannot select a rating.
Who this actually affects
It is easy to picture “screen reader users” as a tiny, rare group. They are not. Roughly one in forty adults in the US is blind or has serious difficulty seeing even with glasses, and that number climbs steeply with age. Your older customers — often your most loyal, highest-spending ones — are exactly the people most likely to use screen magnification, high-contrast modes, or a screen reader.
And it is not only blind users. People who navigate with a keyboard instead of a mouse (including many people with tremors, repetitive strain injuries, or limited hand mobility) need to be able to reach and operate the “write a review” button, the star selector, and the “show more reviews” control. Color-blind users — about one in twelve men — may not be able to tell a half-filled star from an empty one if color is the only difference.
When your reviews are inaccessible, all of these people lose the single most persuasive piece of content on the page. They are left to guess whether other customers trust you.
The legal angle, briefly
In the United States, the Americans with Disabilities Act (ADA) has been applied to business websites in court for years. Most lawsuits and demand letters do not single out reviews specifically — they hit the whole site — but an inaccessible review widget is exactly the kind of thing an automated scanner flags and a plaintiff’s firm cites. Missing text alternatives and unlabeled form controls are among the most common findings.
In Europe, the European Accessibility Act (EAA) began applying in June 2025, and it covers e-commerce and many online consumer services. If you sell to customers in the EU, your product pages — reviews and all — are expected to meet the WCAG 2.1 AA standard. None of this is legal advice, but the direction is clear: reviews are part of your site, and your whole site is expected to be usable by people with disabilities.
How to check your own reviews in five minutes
You do not need special software to spot the most common problems. Here are three quick tests anyone can run.
Test 1: The keyboard test
Open a page that shows your reviews. Click once in an empty area at the top of the page, then put your mouse away and press the Tab key repeatedly. This moves focus from one interactive element to the next, the way a keyboard-only user moves through a page.
Watch for a visible outline or highlight as you tab. Can you reach the “write a review” button? If there is a star-rating selector, can you land on it and change the rating using the arrow keys or the spacebar? Can you reach a “show more reviews” or “next page” control and activate it with Enter? If focus disappears, skips the review controls entirely, or you cannot tell where you are, you have found a real problem.
Test 2: The “listen to it” test
Every major computer has a screen reader built in, and you can turn it on for a couple of minutes to hear what your reviews sound like.
On a Mac, press Command + F5 to start VoiceOver. On Windows, press Ctrl + Windows + Enter to start Narrator. Then use the arrow keys to move through your review section and just listen. When you reach a star rating, does it say something like “rated four out of five stars,” or does it stay silent, read “image,” or rattle off star symbols? Does it read the reviewer’s name and the review text? Turn the screen reader off the same way when you are done. This one test tells you more than any report.
Test 3: The color test
Look at your star ratings and ask: if all the color were removed, could I still tell a four-star review from a two-star one? Filled and empty stars should differ in shape or outline, not only in color. If your “filled” stars are just gold and your “empty” stars are just gray with the identical shape, color-blind visitors are guessing.
The fixes, explained without jargon
If your tests turned up problems, here is what to ask your web designer or your review-platform’s support team for. You can copy these requests almost word for word.
Give every star rating a text equivalent. The rating needs to be available as actual words in the code, such as “Rated 4.5 out of 5 stars, based on 128 reviews.” Sighted users still see the stars; screen-reader users finally hear the score. This is the single most important fix, and it is usually small.
Make the star symbols themselves non-distracting to screen readers. If a rating is drawn from repeated star characters or icons, those should be hidden from assistive technology so they are not read one-by-one, while the text equivalent above carries the meaning. Your developer will know this as marking decorative content appropriately.
Make the “leave a review” star selector keyboard-operable. The clickable star control should be reachable with Tab and adjustable with the arrow keys, and it should announce the current selection (“3 of 5 stars selected”). A safe, simple alternative many sites use is a normal labeled dropdown or a set of radio buttons for the rating — those are accessible out of the box.
Label every field in the review form. The name, email, rating, and comment fields each need a visible, properly connected label — not just gray placeholder text that vanishes when you start typing. Unlabeled fields are one of the most common automated-scanner failures.
Make “show more” and pagination controls real buttons or links. Anything a customer clicks to load more reviews must be reachable by keyboard and announce what it does. “Show 10 more reviews” is far better than a bare arrow icon.
Do not rely on color alone. Filled and empty stars should differ in shape or outline. Any “verified buyer” or “recommended” badge that uses color should also include text or an icon with a text alternative.
A note on third-party widgets
If your reviews come from a tool like Trustpilot, Yotpo, Judge.me, or a Google reviews embed, you may not be able to edit the widget’s internal code yourself. That is normal, and it does not let you off the hook — but it does change your action.
First, check the vendor’s accessibility documentation. Many platforms now publish an accessibility statement or a conformance report (sometimes called a VPAT) describing how their widget performs. Second, ask their support team directly whether their review display includes text alternatives for ratings and whether the submission form is keyboard accessible. The more customers ask, the faster vendors prioritize it. Third, if a widget is badly broken and the vendor will not fix it, consider switching tools or having your developer render the review data in an accessible way on your own page using the platform’s data feed.
The point is to know where the problem lives. You are responsible for the experience on your site, even when part of it is powered by someone else’s code.
Where to start tomorrow
Pick your single most important page — usually a top product page or your homepage testimonial section — and run the three tests above. Most owners find one or two clear issues in under ten minutes. Write them down in plain language (“the star rating is silent for the screen reader,” “I can’t reach the write-a-review button with the keyboard”), and hand that list to whoever maintains your site or to your review platform’s support.
You do not have to fix everything at once. Getting a text equivalent onto your star ratings and labels onto your review form will resolve the large majority of real-world complaints, and both are quick changes. Reviews are too valuable to leave invisible to a chunk of your customers.
We’re building a simple accessibility checker for non-developers — no DevTools, no jargon. Join our waitlist to get early access.
Related Reading
- The Complete Guide to Accessible Forms — the review form is just a form, and the same labeling rules apply.
- Third-Party Widgets and Accessibility — how to handle the embedded tools you do not control.
- Color Contrast: A Plain-English Guide — why filled and empty stars need more than color to tell them apart.
Get our free accessibility toolkit
We're building a simple accessibility checker for non-developers. Join the waitlist for early access and a free EAA compliance checklist.
No spam. Unsubscribe anytime.