Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

13 PASS 5 REVIEW 6 FIX

Landmark Structure

Action

No landmarks

FIX

No landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

No <nav> landmark found

No banner (header) landmark

No contentinfo (footer) landmark

Skip navigation link is missing (WCAG 2.4.1)

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

No landmarks detected

Screen reader users have no way to navigate by region.

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.

Learn more ▾

WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.

Source: WCAG 2.1 SC 2.4.1

Document Language

Action

Missing <html lang> attribute (WCAG 3.1.1)

FIX

Missing <html lang> attribute (WCAG 3.1.1)

Without `<html lang="...">`, screen readers default to the user's system language even when reading content in a different one -- words get pronounced wrong (English text read with French phonetics, etc.). Add a BCP-47 language tag to the <html> root element.

Web Manifest

Action

Not found

FIX

Not found

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.

Dark Mode Support

Action

Theme color only

FIX

Theme color only

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: #ffffff

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

Hamburger menu detected (responsive design)

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

Form Accessibility

Action

22 of 22 controls have issues

REVIEW

22 of 22 controls have issues

22 control(s) without accessible label

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Got: <select name="os0">; <input type="image" name="submit">; <select name="os0">; <input type="image" name="submit">; <select name="os0">; <input type="image" name="submit">; <select name="os0">; <input type="image" name="submit">; <select name="os0">; <input type="image" name="submit"> (+12 more)

22 controls

0 labeled

0 placeholder only

22 unlabeled

Control	Type	Label	Method
os0	select	(none)	none
submit	image	(none)	none
os0	select	(none)	none
submit	image	(none)	none
os0	select	(none)	none
submit	image	(none)	none
os0	select	(none)	none
submit	image	(none)	none
os0	select	(none)	none
submit	image	(none)	none
os0	select	(none)	none
submit	image	(none)	none
os0	select	(none)	none
submit	image	(none)	none
os0	select	(none)	none
submit	image	(none)	none
os0	select	(none)	none
submit	image	(none)	none
os0	select	(none)	none
submit	image	(none)	none
input	image	(none)	none
submit	image	(none)	none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<select name="os0">; <input type="image" name="submit">; <select name="os0">; <input type="image" name="submit">; <select name="os0">; <input type="image" name="submit">; <select name="os0">; <input type="image" name="submit">; <select name="os0">; <input type="image" name="submit"> (+12 more)

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title The Tobacco Seed Company ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Favicon & Branding

Action

4 icon(s) detected

REVIEW

4 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

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

p Do you want to grow your own tobacco ?

3.98:1

#000000

#C03D40

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

p We have a collection of over 60 of the w…

4.25:1

#000000

#C54248

needs 4.5:1 (normal text)

16px · above the fold

p Growing your own tobacco isn't against t…

3.88:1

#000000

#C13833

needs 4.5:1 (normal text)

16px · mid-page

p We have an impressive collection, carefu…

3.38:1

#000000

#B33126

needs 4.5:1 (normal text)

16px · mid-page

1 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)

Element	Ratio	Required	FG	BG	Result
h1 Grow on...You know i…	15.28:1	3.0:1	#000000	#DFDBDA	Pass
title The Tobacco Seed Com…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div The Tobacco Seed Com…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p International & Dome…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a HOME	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a SEEDS	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a GALLERY	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a HELP	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a ABOUT US	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a CONTACT	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p Do you want to grow …	3.98:1	4.5:1	#000000	#C03D40	Fail
p We have a collection…	4.25:1	4.5:1	#000000	#C54248	Fail
p Growing your own tob…	3.88:1	4.5:1	#000000	#C13833	Fail
p We have an impressiv…	3.38:1	4.5:1	#000000	#B33126	Fail
b Here are some of our…	14.79:1	3.0:1	#000000	#DDD7D8	Pass
a seed menu	14.95:1	4.5:1	#000000	#D4DBDB	Pass
a Burley Original	13.40:1	4.5:1	#000000	#CDCFCD	Pass
p The original and pop…	15.30:1	4.5:1	#000000	#D4DEDE	Pass
p It is used for its h…	14.67:1	4.5:1	#000000	#CDDADD	Pass
option pack of 100 seeds £…	21.00:1	4.5:1	#000000	#FFFFFF	Pass

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.

Lighthouse Accessibility Audits

Action

Score 70/100 — 7 failing, 14 passed

REVIEW

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
International & Domestic Retailers of Tobacco Seed Since 1999 `div.container-fluid > div.header > div.header-top > p.footer-class`
seed menu `div#homepage-head > p > b > a`
NAVIGATION `div.container-fluid > div.footer > div.col-md-4 > h4`
HOME `div.col-md-4 > ul.nav-bottom > li > a`
BLOG `div.col-md-4 > ul.nav-bottom > li > a`
GALLERY `div.col-md-4 > ul.nav-bottom > li > a`
SEEDS `div.col-md-4 > ul.nav-bottom > li > a`
PELLETED SEEDS `div.col-md-4 > ul.nav-bottom > li > a`
HELP `div.col-md-4 > ul.nav-bottom > li > a`
ABOUT US `div.col-md-4 > ul.nav-bottom > li > a`
FAQ `div.col-md-4 > ul.nav-bottom > li > a`
PRIVACY POLICY `div.col-md-4 > ul.nav-bottom > li > a`
GET IN TOUCH `div.container-fluid > div.footer > div.col-md-4 > h4`
CONTACT US `div.col-md-4 > ul.nav-bottom > li > a`
PRIVACY POLICY `div.col-md-4 > ul.nav-bottom > li > a`
TERMS & CONDITIONS `div.col-md-4 > ul.nav-bottom > li > a`
The Tobacco Seed Company™ 1999-2026© All Rights Reserved `div.container-fluid > div.footer > div.col-12 > p.footer-class`

These are opportunities to improve the legibility of your content.

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
NAVIGATION `div.container-fluid > div.footer > div.col-md-4 > h4`

These are opportunities to improve keyboard navigation in your application.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

These are opportunities to improve the interpretation of your content by users in different locales.

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.row > div.col-12 > div#homepage-head > img.header-img `div.row > div.col-12 > div#homepage-head > img.header-img`

When an image is being used as an `<input>` button, providing alternative text can help screen reader users understand the purpose of the button. Learn about input image alt text.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
div#homepage > div.col-12 > form.paypalContainer > input `div#homepage > div.col-12 > form.paypalContainer > input`
div#homepage > div.col-12 > form.paypalContainer > input `div#homepage > div.col-12 > form.paypalContainer > input`
div#homepage > div.col-12 > form.paypalContainer > input `div#homepage > div.col-12 > form.paypalContainer > input`
div#homepage > div.col-12 > form.paypalContainer > input `div#homepage > div.col-12 > form.paypalContainer > input`
div#homepage > div.col-12 > form.paypalContainer > input `div#homepage > div.col-12 > form.paypalContainer > input`
div#homepage > div.col-12 > form.paypalContainer > input `div#homepage > div.col-12 > form.paypalContainer > input`
div#homepage > div.col-12 > form.paypalContainer > input `div#homepage > div.col-12 > form.paypalContainer > input`
div#homepage > div.col-12 > form.paypalContainer > input `div#homepage > div.col-12 > form.paypalContainer > input`
div#homepage > div.col-12 > form.paypalContainer > input `div#homepage > div.col-12 > form.paypalContainer > input`
div#homepage > div.col-12 > form.paypalContainer > input `div#homepage > div.col-12 > form.paypalContainer > input`

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
pack of 100 seeds £3.45 pack of 200 seeds £4.95 pack of 500 seeds £6.95 pack of… `div#homepage > div.col-12 > form.paypalContainer > select`
pack of 100 seeds £3.45 pack of 200 seeds £4.95 pack of 500 seeds £6.95 pack of… `div#homepage > div.col-12 > form.paypalContainer > select`
pack of 100 seeds £3.45 pack of 200 seeds £4.95 pack of 500 seeds £6.95 pack of… `div#homepage > div.col-12 > form.paypalContainer > select`
pack of 100 seeds £3.45 pack of 200 seeds £4.95 pack of 500 seeds £6.95 pack of… `div#homepage > div.col-12 > form.paypalContainer > select`
pack of 100 seeds £3.45 pack of 200 seeds £4.95 pack of 500 seeds £6.95 pack of… `div#homepage > div.col-12 > form.paypalContainer > select`
pack of 100 seeds £3.45 pack of 200 seeds £4.95 pack of 500 seeds £6.95 pack of… `div#homepage > div.col-12 > form.paypalContainer > select`
pack of 100 seeds £3.45 pack of 200 seeds £4.95 pack of 500 seeds £6.95 pack of… `div#homepage > div.col-12 > form.paypalContainer > select`
pack of 100 seeds £3.45 pack of 200 seeds £4.95 pack of 500 seeds £6.95 pack of… `div#homepage > div.col-12 > form.paypalContainer > select`
pack of 100 seeds £3.45 pack of 200 seeds £4.95 pack of 500 seeds £6.95 pack of… `div#homepage > div.col-12 > form.paypalContainer > select`
pack of 100 seeds £3.45 pack of 200 seeds £4.95 pack of 500 seeds £6.95 pack of… `div#homepage > div.col-12 > form.paypalContainer > select`

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.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

These items highlight common accessibility best practices.

○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>`

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●ARIA attributes are used as specified for the element's role

●Elements use only permitted ARIA attributes

●Document has a `<title>` element

●Links are distinguishable without relying on color.

●Links have a discernible name

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●Touch targets have sufficient size and spacing.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Deprecated ARIA roles were not used

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○`[aria-hidden="true"]` elements do not contain focusable descendents

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○`[role]`s have all required `[aria-*]` attributes

○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

○`[role]` values are valid

○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

○`<frame>` or `<iframe>` elements have a title

○`<html>` element has a valid value for its `[lang]` attribute

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○Form elements have associated labels

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Skip links are focusable.

○No element has a `[tabindex]` value greater than 0

○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

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○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.

○Identical links have the same purpose.

○Elements with visible text labels have matching accessible names.

○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.

Heading Hierarchy

13 headings, 1 skip(s)

PASS

13 headings, 1 skip(s)

Single H1 present

Heading level skipped: H2 → H4 (missing H3)

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

H1 Grow on...You know it makes sense!
H2 Burley Original
H2 Maryland
H2 Cherry Red
H2 Pennsylvania Red
H2 Costello
H2 Virginian Gold #1
H2 Turkish Basma
H2 Lizard Tail Orinoco
H2 Silk Leaf
H2 Stag Horn
H4 navigation skipped
H4 get in touch

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

A+

Heading Text Quality

All 13 heading(s) have substantive, well-formed text

PASS

All 13 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

Alt Text Quality

1 of 15 images have issues

PASS

1 of 15 images have issues

1 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

3 decorative image(s) correctly marked

11 image(s) with good alt text

15 images 11 good alt text 3 decorative 1 missing

Issue	Count
missing	1 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

A+

Link & Button Quality

40 links, 1 buttons — all OK

PASS

40 links, 1 buttons — all OK

1 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://www.statcounter.com/

39 link(s) with descriptive text

40 links

0 empty

0 generic text

1 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.statcounter.com/	StatCounter - Free Web Tracker…	new tab	Add '(opens in new tab)' to text

40 links and buttons have descriptive text

Add '(opens in new tab)' to link text or aria-label.

https://www.statcounter.com/

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

A+

Form Input Types

22 form control(s) checked, no type mismatches

PASS

22 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

22 form control(s) checked, no input-semantic issues

PASS

22 form control(s) checked, no input-semantic issues

All form input semantics look correct

A+

Mobile Keyboard & Autofill

No autofill-eligible form controls

PASS

No autofill-eligible form controls

No autofill-eligible form controls (no name/email/tel/address fields)

A+

Tabindex Anti-Patterns

No explicit tabindex attributes found

PASS

No explicit tabindex attributes found

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

A+

Tap Target Adequacy

All tap targets meet WCAG 2.5.5/2.5.8 sizing

PASS

All tap targets meet WCAG 2.5.5/2.5.8 sizing

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

Mobile-Readable Font Sizes

All 56 visible text node(s) render at >= 12 CSS pixels

PASS

All 56 visible text node(s) render at >= 12 CSS pixels

All text uses legible mobile font sizes (>= 12 CSS px)

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

Browser-chrome `theme-color` meta tag present

The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.