Accessibility report for proflowers.com
Based on an automated WCAG 2.1 Level AA scan on July 13, 2026.
proflowers.com does not yet meet WCAG 2.1 Level AA, the accessibility standard written into U.S. and EU law. This automated scan found 7 types of barrier affecting people with disabilities.
On this page, the most frequent barrier is "Some images on this page have no description for screen readers" — found on 10 elements. In total the scan flagged 24 issues across 7 categories of WCAG 2.1 Level AA.
WCAG 2.1 Level AA is the standard U.S. courts apply under the ADA, and the law across the EU under the European Accessibility Act. These barriers block screen-reader, keyboard-only, and low-vision users — and every one of them is fixable. Here's how.
What needs fixing to meet the standard
Some buttons have no description that screen readers can announce.
WCAG 4.1.2 (Level A) Section 508EN 301 549 Affects screen-reader users
Why it matters: Visual users see an icon (a heart, a trash can, an X), but screen-reader users hear only 'button' — they don't know if it'll favorite a post, delete it, or close a dialog. This is a critical accessibility blocker and a top lawsuit driver.
How to fix it: Every button needs a text label. If you can't put text inside the button (icon-only design), in your platform's button settings look for an 'Aria label' or 'Screen reader text' field — fill it with what the button does ('Close', 'Add to cart', 'Open menu').
Some images on this page have no description for screen readers.
WCAG 1.1.1 (Level A) Section 508EN 301 549 Affects screen-reader users
Why it matters: Blind and low-vision users rely on screen readers to read pages aloud. When an image has no description, the screen reader either skips it entirely or reads out the file name — useless. Missing alt text is the #2 lawsuit-magnet category.
How to fix it: In your site editor, click each image and look for an 'Alt text' or 'Image description' field. Write a short sentence describing what the image shows or what it links to. For purely decorative images (dividers, background flourishes), enter empty alt text or check a 'decorative' box if the platform offers one.
A button's visible text doesn't match the description it announces to screen readers.
WCAG 2.5.3 (Level A) EN 301 549 Affects screen-reader users
Why it matters: A user dictating 'click Submit' to voice-control software may see 'Submit' on screen but the announce-name is something else, so the voice command fails.
How to fix it: Developer fix: 'aria-label should start with or fully contain the visible button text'.
Some links have no readable text — usually icon-only links.
WCAG 4.1.2 (Level A) Section 508EN 301 549 Affects screen-reader users
Why it matters: Screen-reader users hear 'link' but not where the link goes. Users navigate by listening to a list of links — useless if every entry is just 'link, link, link'.
How to fix it: In your site editor, for icon-only links (social-media icons, navigation arrows), set an 'Aria label' or 'Title' field describing where it goes ('Follow us on Twitter', 'Next page').
An interactive element (link, button) is inside another interactive element.
WCAG 4.1.2 (Level A) EN 301 549 Affects keyboard-only users
Why it matters: Keyboard and screen-reader users can't reliably reach the inner element. Common in 'card-as-link' designs where a button sits inside a clickable card.
How to fix it: Developer fix: 'avoid putting buttons inside links or links inside buttons; use a single interactive element with internal helpers'.
Get compliant, free
The free wcagcheckr browser extension finds every one of these issues on your own pages and gives you the fix recipe for each — at no cost. Run it, fix what it finds, and re-check this page anytime.
Own this site? Fix the issues, then re-scan — this report updates automatically, and comes down entirely once you pass.
Heading levels skip — for example, an H2 jumps directly to an H4 with no H3 between them.
Affects screen-reader users
Why it matters: Screen-reader users navigate by heading levels. Skipped levels suggest missing content and break the page's outline. Confusing for everyone.
How to fix it: In your editor, find the headings that skip levels and either bump them up to the right level (H4 → H3 if no H2 exists between) or insert the missing level. Headings should follow a logical outline like a document outline.
The page tells mobile browsers users can't zoom in.
WCAG 1.4.4 (Level AA) EN 301 549 Affects low-vision and colorblind users
Why it matters: People with low vision rely on pinch-zoom to read small text. Disabling zoom is a real WCAG failure and a common lawsuit target.
How to fix it: In platform site settings, look for a 'Mobile zoom' or 'Pinch zoom' option and enable it. If your developer added user-scalable=no in a viewport meta tag, ask them to remove it.
This is an automated scan and catches a portion of accessibility barriers; full WCAG 2.1 Level AA conformance also requires manual and assistive-technology testing. See our methodology for what we do and don't claim.
Learn more
How this report was produced
This report is an automated scan of the page as it was publicly served on
,
using [email protected]. The captured page and these results are sealed with a
tamper-evident hash (f15f4c45e3b7fa00…).
We report only what the page publicly returned at that time.
This seal is anchored to a trusted RFC-3161 timestamp via freetsa.org on . Independently verify this receipt →