Skip to content
https://flourist.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
56
GRADE
D
FIX
6
REVIEW
4
PASS
3
INFO
0
Checks
13
3 PASS 4 REVIEW 6 FIX
F
Alt Text Quality
Action
22 of 179 images have issues
FIX
22 of 179 images have issues
Critical::
22 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
21 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
150 decorative image(s) correctly marked
Info::
7 image(s) with good alt text
179 images 7 good alt text 150 decorative 22 missing
IssueCount
missing22 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
No apple-touch-icon detected
iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.
✗ favicon.ico Missing
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
D
Web Manifest
Action
Not found
FIX
Not found
Info::
No web manifest found
No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #503629
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark ModePartial Dark Mode
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
No print-specific styles detected
When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.
Print Stylesheet No Print Styles
Print stylesheet Not found ✗Inline @media print Not detected ✗
F
Navigation UX
Action
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
2 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 2 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
B
Heading Hierarchy
6 headings, 1 skip(s)
REVIEW
6 headings, 1 skip(s)
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H2 Currency
  • H1 Shop Online
  • H1 Visit Our Bakery duplicate H1
  • H2 Sourdough Bread Class
  • H6 - The Cool Hunter skipped
  • H3 Newsletter

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 4 fail WCAG AA
REVIEW

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

16 pass 4 fail WCAG AA
span Cart
3.84:1
#000000
on
#6C6963
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
span $0.00
2.75:1
#000000
on
#585349
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
span (0)
3.37:1
#000000
on
#68604E
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
span Pastry
4.40:1
#000000
on
#7E715C
needs 4.5:1 (normal text)
16px · mid-page

3 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Shop Online18.49:13.0:1
#000000
#F3F0EC
Pass
h1 Visit Our Bakery18.49:13.0:1
#000000
#F3F0EC
Pass
h2 Currency18.49:13.0:1
#000000
#F3F0EC
Pass
h2 Sourdough Bread Clas…18.49:13.0:1
#000000
#F3F0EC
Pass
h3 Newsletter18.49:13.0:1
#000000
#F3F0EC
Pass
title Flourist | Fresh Mil…16.52:14.5:1
#000000
#E4E4E4
Pass
a Skip to content18.49:14.5:1
#000000
#F3F0EC
Pass
p We offer local deliv…18.49:14.5:1
#000000
#F3F0EC
Pass
p We offer local deliv…11.47:14.5:1
#000000
#C4BFB5
Pass
span Mill + Bakery11.11:14.5:1
#000000
#C1BCB3
Pass
span Rewards Club11.68:14.5:1
#000000
#C4C1B9
Pass
span Subscribe12.19:14.5:1
#000000
#C8C5BE
Pass
p We offer local deliv…11.81:14.5:1
#000000
#C5C2BB
Pass
p We offer local deliv…12.18:14.5:1
#000000
#C8C5BD
Pass
span Cart3.84:14.5:1
#000000
#6C6963
Fail
span $0.002.75:14.5:1
#000000
#585349
Fail
span (0)3.37:14.5:1
#000000
#68604E
Fail
span Shop9.52:14.5:1
#000000
#B4AEA3
Pass
span Available Locally16.22:14.5:1
#000000
#E5E2DA
Pass
span Pastry4.40:14.5:1
#000000
#7E715C
Fail

Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.

B
Lighthouse Accessibility Audits
Score 82/100 — 6 failing, 23 passed
REVIEW
82

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Newsletter div.footer__block > div.footer__newsletter > div.footer__newsletter__body > h3
Get news, recipes and exclusive offers delivered to your inbox. We'll send you … div.footer__newsletter > div.footer__newsletter__body > div.rte > p
your-email@example.com div.footer__newsletter__body > form#footer-newsletter > div.input-group > input#mail-footer-newsletter

These are opportunities to improve the legibility of your content.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.product-grid-item__container > a > span.absolute > img div.product-grid-item__container > a > span.absolute > img
div.product-grid-item__container > a > span.absolute > img div.product-grid-item__container > a > span.absolute > img
div.product-grid-item__container > a > span.absolute > img div.product-grid-item__container > a > span.absolute > img
div.product-grid-item__container > a > span.absolute > img div.product-grid-item__container > a > span.absolute > img
div.product-grid-item__container > a > span.absolute > img div.product-grid-item__container > a > span.absolute > img
div.product-grid-item__container > a > span.absolute > img div.product-grid-item__container > a > span.absolute > img

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body#flourist-fresh-milled-flour-amp-premium-dry-goods-shop-here > div#gb_container_8247439015 > div.gb_protect > iframe#btnIframe body#flourist-fresh-milled-flour-amp-premium-dry-goods-shop-here > div#gb_container_8247439015 > div.gb_protect > iframe#btnIframe
body#flourist-fresh-milled-flour-amp-premium-dry-goods-shop-here > div#gb_container_8247439015 > div.gb_protect > iframe#wdgtIframe body#flourist-fresh-milled-flour-amp-premium-dry-goods-shop-here > div#gb_container_8247439015 > div.gb_protect > iframe#wdgtIframe
body#flourist-fresh-milled-flour-amp-premium-dry-goods-shop-here > div#gb_container_8247439015 > div.gb_protect > iframe#toastIframe body#flourist-fresh-milled-flour-amp-premium-dry-goods-shop-here > div#gb_container_8247439015 > div.gb_protect > iframe#toastIframe

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
- THE COOL HUNTER div.icon__column > div.icon__column__text > div.rte > h6

These are opportunities to improve keyboard navigation in your application.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
TERMS OF SERVICE div.subfooter__items > div.subfooter__item > span.subfooter__copyright > a

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Organic Sifted Red Spring Wheat Flour Organic Sifted Red Spring Wheat Flour F… div.slide-item > product-grid-item.product-grid-item > div.product__grid__info > a
Organic Sifted Red Fife Flour Organic Sifted Red Fife Flour FROM $20.95 div.slide-item > product-grid-item.product-grid-item > div.product__grid__info > a
Organic Whole Grain Red Spring Wheat Flour Organic Whole Grain Red Spring Whea… div.slide-item > product-grid-item.product-grid-item > div.product__grid__info > a
○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Form elements have associated labels
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●`button`, `link`, and `menuitem` elements have accessible names
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links have a discernible name
●No element has a `[tabindex]` value greater than 0
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Identical links have the same purpose.
○`[accesskey]` values are unique
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
○`[role]`s are contained by their required parent element
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○ARIA IDs are unique
○No form fields have multiple labels
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Links are distinguishable without relying on color.
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`[lang]` attributes have a valid value
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
A
Landmark Structure
5 landmarks
PASS
5 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
1 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV MAIN CONTENTINFO footer

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

A+
Form Accessibility
All 6 controls labeled
PASS
All 6 controls labeled
Info::
6 control(s) properly labeled
6 controls
6 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
qsearchSearch our storearia-label
#mail-footer-newsletteremailyour-email@example.comaria-label
#accordion-linklist-2-1-checkboxcheckboxCompanyfor/id
#accordion-linklist_mrfX88-2-checkboxcheckboxShopfor/id
#accordion-linklist-1-3-checkboxcheckboxSupportfor/id
qsearchSearch our storearia-label
A
404 Error Page
HTTP 404, custom page
PASS
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 Not Found – Flourist ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback