Skip to content
https://avada.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
54
GRADE
F
FIX
7
REVIEW
2
PASS
4
INFO
0
Checks
13
4 PASS 2 REVIEW 7 FIX
F
Alt Text Quality
Action
112 of 151 images have issues
FIX
112 of 151 images have issues
Critical::
112 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
112 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
39 image(s) with good alt text
151 images 39 good alt text 112 missing
IssueCount
missing112 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

D
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
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'>.
Info::
SVG favicon detected — scales perfectly to any size
✓ favicon.ico Present
✓ PNG Icons Present
✗ Apple Touch Missing
✓ SVG Favicon Present
✗ 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
No dark mode signals
FIX
No dark mode signals
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 ModeNo Dark Mode Detected
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::
3 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 3 <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
Form Accessibility
2 of 25 controls have issues
REVIEW
2 of 25 controls have issues
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="email" name="email" id="email">; <input type="text" id="fss-demo-tag-search">
Info::
23 control(s) properly labeled
25 controls
23 labeled
2 placeholder only
0 unlabeled
ControlTypeLabelMethod
#all_websitescheckboxnone
#Corporatecheckboxnone
#Shop / WooCommercecheckboxnone
#Creativecheckboxnone
#Portfoliocheckboxnone
#Educationcheckboxnone
#Health & Beautycheckboxnone
#Eventscheckboxnone
#Foodcheckboxnone
#One Pagecheckboxnone
#Marketingcheckboxnone
#Sportscheckboxnone
#Travelcheckboxnone
#Blog / Magazinecheckboxnone
#bbPresscheckboxnone
#Coming Sooncheckboxnone
#all_websitescheckboxnone
#bbpresscheckboxnone
#woocommercecheckboxnone
#the events calendarcheckboxnone
#slider revolutioncheckboxnone
#layer slidercheckboxnone
#hubspotcheckboxnone
#fss-demo-tag-searchtext(Search Websites)placeholder only
#emailemail(Your email *)placeholder only

Placeholder text disappears on focus and is not a reliable label.

<input type="email" name="email" id="email">; <input type="text" id="fss-demo-tag-search">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

B
404 Error Page
HTTP 404, custom page
REVIEW
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
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found – Avada Website Builder ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
A+
Landmark Structure
6 landmarks
PASS
6 landmarks
Info::
<main> landmark present
Info::
3 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
No contentinfo (footer) landmark
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Main Menu" MAIN CONTENTINFO (missing!)
A
Heading Hierarchy
42 headings, 1 skip(s)
PASS
42 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 The Ultimate
  • H2 WordPressOnline StoreCreativePortfolio
  • H3 Website Builder
  • H2 Launch your first website
  • H2 Launch your first website
  • H2 Generate leads and conversions
  • H2 Generate leads and conversions
  • H2 Take your projects to the next level
  • H2 Take your projects to the next level
  • H2 Design Anything, Build Everything
  • H4 Live Visual Builder skipped
  • H4 Layout Builder
  • H4 Header Builder
  • H4 Mega Menu
  • H4 Footer Builder
  • H4 Form Builder
  • H4 Off-Canvas
  • H4 Setup Wizard
  • H4 Performance Wizard
  • H4 Live Visual Builder
  • H4 Layout Builder
  • H4 Header Builder
  • H4 Mega Menu
  • H4 Footer Builder
  • H4 Form Builder
  • H4 Off-Canvas
  • H4 Setup Wizard
  • H4 Performance Wizard
  • H2 All-In-One Website Builder
  • H3 112 Prebuilt Websites
  • H3 120+ design elements
  • H3 Built For Performance
  • H3 Mobile Friendly
  • H3 Dynamic content
  • H3 WooCommerce Builder
  • H2 1,058,725 Website OwnersTrust Avada
  • H3 World-Class Support
  • H3 Documentation & Tutorials
  • H3 100% Built In-House
  • H3 Free Lifetime Updates
  • H2 Frequently Asked Questions
  • H2 Build Successful Websites With Avada

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+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

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

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 The Ultimate21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Launch your first we…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Launch your first we…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Generate leads and c…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Generate leads and c…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Take your projects t…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Take your projects t…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Design Anything, Bui…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 All-In-One Website B…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Website Owners21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Trust Avada21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Frequently Asked Que…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Build Successful Web…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Website Builder21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Prebuilt Websites21.00:13.0:1
#000000
#FFFFFF
Pass
h3 120+ design elements21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Built For Performanc…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Mobile Friendly21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Dynamic content21.00:13.0:1
#000000
#FFFFFF
Pass
h3 WooCommerce Builder21.00:13.0: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.

A
Lighthouse Accessibility Audits
Score 92/100 — 4 failing, 27 passed
PASS
92

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
Visual Builder div.fusion-column-wrapper > div > a.fusion-button > span.fusion-button-text
Documentation div.fusion-column-wrapper > div > a.fusion-button > span.fusion-button-text
Support div.fusion-column-wrapper > div > a.fusion-button > span.fusion-button-text
Prebuilt Websites div.fusion-column-wrapper > div > a.fusion-button > span.fusion-button-text
Design div.fusion-column-wrapper > div > a.fusion-button > span.fusion-button-text
SEO div.fusion-column-wrapper > div > a.fusion-button > span.fusion-button-text
Shop Builder div.fusion-column-wrapper > div > a.fusion-button > span.fusion-button-text
Form Builder div.fusion-column-wrapper > div > a.fusion-button > span.fusion-button-text
All-In-One div.fusion-column-wrapper > div > a.fusion-button > span.fusion-button-text
Patcher div.fusion-column-wrapper > div > a.fusion-button > span.fusion-button-text
WCAG div.fusion-column-wrapper > div > a.fusion-button > span.fusion-button-text
Dynamic Data div.fusion-column-wrapper > div > a.fusion-button > span.fusion-button-text

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
Live Visual Builder ul.nav-tabs > li.active > a#mobile-fusion-tab-e16e0257f5041363303 > h4.fusion-tab-heading

These are opportunities to improve keyboard navigation in your application.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.fusion-builder-row > div.fusion-layout-column > span.fusion-column-inner-bg > a.fusion-column-anchor div.fusion-builder-row > div.fusion-layout-column > span.fusion-column-inner-bg > a.fusion-column-anchor
div.fusion-builder-row > div.fusion-layout-column > span.fusion-column-inner-bg > a.fusion-column-anchor div.fusion-builder-row > div.fusion-layout-column > span.fusion-column-inner-bg > a.fusion-column-anchor
div.fusion-builder-row > div.fusion-layout-column > span.fusion-column-inner-bg > a.fusion-column-anchor div.fusion-builder-row > div.fusion-layout-column > span.fusion-column-inner-bg > a.fusion-column-anchor

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.

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
Discover More div.fusion-layout-column > div.fusion-column-wrapper > div > a.fusion-button
Buy Avada For $69 div.fusion-layout-column > div.fusion-column-wrapper > div.md-text-align-center > a.fusion-button
○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
●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
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●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.
●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 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
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○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 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 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
○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
○`<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.
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback