An accessibility widget can be visible on a website while customers still encounter barriers to making a purchase. That is the concern raised by the supplied complaint summary in Rice v. Jack’s Surf & Sport LLC, involving the business known as Jack’s Surfboards.
For local retailers, restaurants, and service businesses, the practical lesson is to test the tasks customers depend on: opening navigation, choosing an option, submitting a form, booking an appointment, and checking out.
This article is based on a supplied summary of a 21-page complaint, reported as filed October 9, 2026. We could not independently retrieve the linked complaint or verify subsequent docket developments for this October 19 article. The case details below are attributed to that summary; they are not findings of liability or a report of the website’s current condition.
Who is suing, and what do they allege?
The supplied summary identifies two plaintiffs: Lucas Rice, of Wisconsin, and Samuel Wilson, of New York. Both are described as legally blind customers who use screen readers, software that conveys page content and controls through speech or braille.
Rice allegedly attempted to purchase a Psycho Tech 3/2mm Back Zip Full Wetsuit. Wilson allegedly attempted to purchase Sex Pistols 17-inch Album Boardshorts. Both say accessibility barriers prevented them from completing their purchases.
The summary says the complaint refers to a third-party accessibility expert who independently confirmed errors, but does not attach a detailed technical audit. It identifies paragraph 34 as a set of illustrative examples, rather than an exhaustive list of alleged barriers.
The three specific barriers described
1. A mobile menu that would not stay open
According to the summary of paragraph 34(a), page 11, opening the Main Menu caused it to expand briefly and immediately collapse. The screen reader announced “collapsed,” and focus moved to the browser’s address bar.
Business impact: A customer who cannot navigate the menu may never reach the product or service they want.
What to ask your developer: Test that the menu stays open while a customer uses it, that focus follows a predictable path, and that the control communicates whether it is expanded. Adding an accessibility attribute alone will not fix code that closes the menu unexpectedly.
2. Gift card options that did not communicate their meaning or selection
The summary of paragraph 34(b), page 12, describes different gift card designs announced with the same generic label and an unintelligible alphanumeric string. Selecting an amount reportedly changed a button’s color without VoiceOver announcing the selection.
Business impact: A customer may be unable to distinguish products or confirm the amount they are about to purchase. Similar problems can affect size, color, appointment, and subscription choices.
What to ask your developer: Give options meaningful names and expose their selected state to assistive technology. For a choice of one amount from several, native radio buttons are often a useful starting point. Confirm the result with a screen reader; color alone is not enough.
3. A cart popup that customers could not reach
According to the summary of paragraph 34(c), page 13, selecting Add to Cart opened a popup with product information, a price, and View Cart and Checkout buttons. Screen-reader focus reportedly stayed on the page underneath. A processing message was announced, and the popup eventually disappeared without the customer being able to interact with it.
Business impact: Even a customer who successfully finds a product can lose access to the next step in the purchase.
What to ask your developer: Determine whether the component is an interactive dialog or a status notification, and implement the appropriate behavior. An interactive modal needs an accessible name, deliberate focus management, reachable controls, and a usable closing mechanism. Essential checkout controls must remain available long enough to use. A dialog label alone does not make the interaction work.
What this says about overlays and automated scores
The supplied summary says the complaint describes an accessibility overlay on the website. It does not identify the vendor or establish that the overlay caused the alleged defects. The lawsuit therefore should not be presented as proof that a particular product failed, or as a ruling about every overlay.
As a development matter, the examples point to behavior that needs investigation in the site’s theme, components, and integrations. A label cannot keep a menu open, and a successful scan cannot demonstrate that a person completed checkout.
Automated tools remain useful for finding some accessibility problems. But W3C’s guidance on selecting evaluation tools explains that tools alone cannot determine whether a site meets accessibility standards; human evaluation is necessary. Use automated checks alongside keyboard testing, screen-reader testing, and feedback from people with disabilities.
“Can you show me someone navigating our mobile menu, selecting a product option, correcting a form error, and completing checkout using a keyboard and a screen reader?” Ask for the test results and fixes, as well as the scan report.
What the plaintiffs want
According to the supplied summary, the requested permanent injunction goes beyond fixing three interactions. It would require:
- An accessibility consultant acceptable to the plaintiffs and implementation of the consultant’s recommendations within 60 days.
- Periodic automated audits and human accessibility testing at least quarterly.
- Training for relevant employees every two years, plus customer-service training.
- A published accessibility policy and accessible channels for feedback.
- Monitoring by the plaintiffs and their experts for up to two years after accessibility is validated.
The summary also identifies requests for attorneys’ fees and costs, and a separate request by Wilson for compensatory damages under New York law, without a specified dollar amount. These are requests described in the complaint summary, not remedies shown to have been awarded.
For an owner planning a website budget, the implication is that accessibility work can involve recurring testing, staff time, and maintenance as well as repairs. The requested deadlines and testing schedule are specific to this complaint; they are not a universal checklist imposed on every business.
Does filing a lawsuit mean a trial is inevitable?
No. Filing a civil lawsuit does not prevent the parties from negotiating a settlement. The U.S. Courts’ guide to civil cases explains that cases can resolve through settlement or a judicial order before trial.
This article does not establish whether Jack’s has settled, whether negotiations are underway, or whether a court has issued a later ruling. Those questions require current court records. A complaint alone does not establish a violation of law.
Practical steps for business owners
- Start with the tasks that drive your business. List the steps for buying, booking, requesting a quote, and contacting support. Include mobile menus, product options, popups, and error messages.
- Commission both automated and human evaluation. Ask which pages, device and browser combinations, screen readers, and complete customer journeys will be tested. Include people with disabilities where possible.
- Prioritize barriers that block completion. A broken menu or unreachable checkout deserves prompt attention. Assign each issue an owner and verify the repair by repeating the affected task.
- Fix the underlying implementation. Ask your developer and third-party providers to address behavior in the theme, components, or integration responsible. Evaluate any widget by demonstrated results.
- Retest after changes. New themes, booking tools, payment integrations, and promotional popups can change accessibility. Build checks into releases and schedule periodic reviews.
- Make feedback actionable. Provide an accessible way to report problems, train staff to route them, and retain a record of testing, repairs, and follow-up. Documentation supports maintenance; it is not a guarantee against a claim.
A useful first project is a documented review of your most important customer journey, followed by repairs and a repeat test. That produces a clearer picture of what customers can actually do than a badge or score alone.
If you want help reviewing your website’s interactions and planning improvements, tell us about your website.
Sources and scope
Case-specific details are drawn from the supplied complaint summary, which cites paragraphs 23 and 34 and links to the Rice v. Jack’s Surf & Sport LLC complaint on CourtListener. The complaint itself and subsequent case status were not independently verified for this article. Technical and civil-procedure references are linked above.
This is a website-development perspective and general information, not legal advice. A qualified attorney can assess obligations or a claim involving your business.