Accessibility

F

Heading Hierarchy

Action

97 headings, 10 skip(s)

FIX

97 headings, 10 skip(s)

Single H1 present

Heading level skipped: H1 → H4 (missing H2)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H5 (missing H3)

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

Heading level skipped: H2 → H5 (missing H3)

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

Heading level skipped: H2 → H5 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H6 (missing H3)

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

H1 WordPress page builder that gives you design superpowers
H4 No skipped
H2 Design your entire website right inside the WP Customizer
H4 Header skipped
H4 Page Content
H4 Footer
H4 Blog Pages
H4 Search Page
H2 Design features that will make your websites stand out
H4 Awesome hero sections with video, slideshows & image collage skipped
H4 Shape dividers & section overlap
H4 Looks great on any device by default
H4 Complete control over navigation layout & design
H2 Ready to create an awesome website?
H2 Ready to create an awesome website?
H2 90+ Full Website Templates for a Variety of Niches
H2 Create pages lightning-fast with 150+ predefined blocks
H5 20+ Beautiful headers skipped
H5 About, features & content
H5 Team, testimonials & clients
H5 Portfolio & photo gallery
H5 Contact blocks
H5 Footer blocks
H2 Ready to create an awesome website?
H2 Ready to create an awesome website?
H2 Customize any element on the page to pixel-perfection
H5 Background & Colors skipped
H5 Typography & Alignment
H5 Border & Shadow
H5 Margins & Paddings
H2 40+ Drag and Drop Components
H2 Start designing your website with 0 setup using Colibri Cloud
H5 1. Create a new project in your Colibri account skipped
H5 2. Design your site using the Colibri builder
H5 3. Publish to any hosting server with just a few clicks
H2 Free and PRO versions compared
H4 free skipped
H4 pro
H2 What our customers say on wordpress.org
H2 Awesome features, tons of pre-made blocks, and amazing support
H2 I love this theme.
H2 I built a full company site in about 4 hours from start to finish.
H2 It’s so flexible and beautiful!
H2 It was super easy to build the pages.
H2 Simple & intuitive
H2 Customer service team was very responsive.
H2 The most powerful theme for free & pro.
H2 Easy to use and helpful support
H2 Responsive & attractive
H2 Awesome features, tons of pre-made blocks, and amazing support
H2 I love this theme.
H2 Choose your plan
H4 Personal skipped
H2 € 79
H2 Get More Customers and the Best Deal
H3 Colibri Page Builder
H3 Colibri Marketing Bundle
H4 Business
H2 € 99
H2 Get More Customers and the Best Deal
H3 Colibri Page Builder
H3 Colibri Marketing Bundle
H4 Agency
H2 € 199
H2 Get More Customers and the Best Deal
H3 Colibri Page Builder
H3 Colibri Marketing Bundle
H4 Personal
H3 Special Offer - 15% OFF
H2 € 199 € 169
H2 Get More Customers and the Best Deal
H3 Colibri Page Builder
H3 Colibri Marketing Bundle
H4 Business
H3 Special Offer - 20% OFF
H2 € 299 € 239
H2 Get More Customers and the Best Deal
H3 Colibri Page Builder
H3 Colibri Marketing Bundle
H4 Agency
H3 Special Offer - 25% OFF
H2 € 599 € 449
H2 Get More Customers and the Best Deal
H3 Colibri Page Builder
H3 Colibri Marketing Bundle
H2 Our Awesome Support Team
H4 Amazing Support skipped
H4 Constant Updates
H4 Excellent Documentation
H4 Open a Support Ticket
H2 Need WordPress Hosting?
H6 Works Seamlessly with Colibri skipped
H6 Officially Recommended by WordPress
H6 Amazing Speed
H6 Security-first mindset
H6 Top-rated Support
H2 Need WordPress Hosting?

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

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

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

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

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

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

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

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

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

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

F

Alt Text Quality

Action

31 of 70 images have issues

FIX

31 of 70 images have issues

31 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

2 image-in-link without alt text

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

35 decorative image(s) correctly marked

4 image(s) with good alt text

70 images 4 good alt text 35 decorative 31 missing

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

Link & Button Quality

Action

6 issue(s) across 94 links and 27 buttons

FIX

6 issue(s) across 94 links and 27 buttons

5 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: #pricing; #pricing; https://colibriwp.com/; https://colibriwp.com/; https://colibriwp.com/

1 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: https://colibriwp.com/wordpress-hosting/ ("learn more")

35 link(s) open in new tab without warning

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

Got: https://www.youtube.com/channel/UCN3ZM-C7TJgklVfseVHamHQ; https://app.colibriwp.com?_=get-started/#/get-started; https://app.colibriwp.com?_=get-started/#/get-started; https://app.colibriwp.com?_=get-started/#/get-started; https://colibriwp-work.colibriwp.com/business-iv/; https://app.colibriwp.com?_=get-started/#/get-started/?source=try-template&te…; https://colibriwp-work.colibriwp.com/gym-demo; https://app.colibriwp.com?_=get-started/#/get-started/?source=try-template&te…; https://colibriwp-work.colibriwp.com/designer-portfolio-iii; https://app.colibriwp.com?_=get-started/#/get-started/?source=try-template&te… (+25 more)

53 link(s) with descriptive text

94 links

5 empty

1 generic text

35 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
#pricing	(empty)	empty	Add link text or aria-label
#pricing	(empty)	empty	Add link text or aria-label
https://colibriwp.com/	(empty)	empty	Add link text or aria-label
https://www.youtube.com/channel/UCN3ZM-C…	Tutorials	new tab	Add '(opens in new tab)' to text
https://app.colibriwp.com?_=get-started/…	try colibri online	new tab	Add '(opens in new tab)' to text
https://app.colibriwp.com?_=get-started/…	try colibri online	new tab	Add '(opens in new tab)' to text
https://app.colibriwp.com?_=get-started/…	try colibri online	new tab	Add '(opens in new tab)' to text
https://colibriwp-work.colibriwp.com/bus…	preview	new tab	Add '(opens in new tab)' to text
https://app.colibriwp.com?_=get-started/…	try now	new tab	Add '(opens in new tab)' to text
https://colibriwp-work.colibriwp.com/gym…	preview	new tab	Add '(opens in new tab)' to text
https://app.colibriwp.com?_=get-started/…	try now	new tab	Add '(opens in new tab)' to text
https://colibriwp-work.colibriwp.com/des…	preview	new tab	Add '(opens in new tab)' to text
https://app.colibriwp.com?_=get-started/…	try now	new tab	Add '(opens in new tab)' to text
https://colibriwp-work.colibriwp.com/wed…	preview	new tab	Add '(opens in new tab)' to text
https://app.colibriwp.com?_=get-started/…	try now	new tab	Add '(opens in new tab)' to text
https://colibriwp-work.colibriwp.com/seo…	preview	new tab	Add '(opens in new tab)' to text
https://app.colibriwp.com?_=get-started/…	try now	new tab	Add '(opens in new tab)' to text
https://colibriwp-work.colibriwp.com/my-…	preview	new tab	Add '(opens in new tab)' to text
https://app.colibriwp.com?_=get-started/…	try now	new tab	Add '(opens in new tab)' to text
https://colibriwp-work.colibriwp.com/med…	preview	new tab	Add '(opens in new tab)' to text
https://app.colibriwp.com?_=get-started/…	try now	new tab	Add '(opens in new tab)' to text
https://colibriwp-work.colibriwp.com/pho…	preview	new tab	Add '(opens in new tab)' to text
https://app.colibriwp.com?_=get-started/…	try now	new tab	Add '(opens in new tab)' to text
https://colibriwp-work.colibriwp.com/sus…	preview	new tab	Add '(opens in new tab)' to text
https://app.colibriwp.com?_=get-started/…	try now	new tab	Add '(opens in new tab)' to text
https://app.colibriwp.com?_=get-started/…	try colibri online	new tab	Add '(opens in new tab)' to text
https://app.colibriwp.com?_=get-started/…	try colibri cloud	new tab	Add '(opens in new tab)' to text
https://app.colibriwp.com?_=get-started/…	get free version	new tab	Add '(opens in new tab)' to text
https://iconvertpromoter.com	Learn more about iConvert Prom…	new tab	Add '(opens in new tab)' to text
https://iconvertpromoter.com	Learn more about iConvert Prom…	new tab	Add '(opens in new tab)' to text
https://iconvertpromoter.com	Learn more about iConvert Prom…	new tab	Add '(opens in new tab)' to text
https://iconvertpromoter.com	Learn more about iConvert Prom…	new tab	Add '(opens in new tab)' to text
https://iconvertpromoter.com	Learn more about iConvert Prom…	new tab	Add '(opens in new tab)' to text
https://iconvertpromoter.com	Learn more about iConvert Prom…	new tab	Add '(opens in new tab)' to text
https://www.siteground.com/index.htm?afc…	get siteground hosting	new tab	Add '(opens in new tab)' to text
https://colibriwp.com/wordpress-hosting/	learn more	generic text	Replace with descriptive text
Before: learn more Suggested: Wordpress Hosting
https://colibriwp.com/cookies-policy/	use of cookies	new tab	Add '(opens in new tab)' to text
https://colibriwp.com/	(empty)	empty	Add link text or aria-label
https://www.youtube.com/channel/UCN3ZM-C…	Tutorials	new tab	Add '(opens in new tab)' to text
https://colibriwp.com	Colibri	new tab	Add '(opens in new tab)' to text
https://colibriwp.com/	(empty)	empty	Add link text or aria-label

80 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

#pricing; #pricing; https://colibriwp.com/; https://colibriwp.com/; https://colibriwp.com/

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Generic link text like 'click here' doesn't describe the destination.

https://colibriwp.com/wordpress-hosting/ ("learn more")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

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

https://www.youtube.com/channel/UCN3ZM-C7TJgklVfseVHamHQ; https://app.colibriwp.com?_=get-started/#/get-started; https://app.colibriwp.com?_=get-started/#/get-started; https://app.colibriwp.com?_=get-started/#/get-started; https://colibriwp-work.colibriwp.com/business-iv/; https://app.colibriwp.com?_=get-started/#/get-started/?source=try-template&te…; https://colibriwp-work.colibriwp.com/gym-demo; https://app.colibriwp.com?_=get-started/#/get-started/?source=try-template&te…; https://colibriwp-work.colibriwp.com/designer-portfolio-iii; https://app.colibriwp.com?_=get-started/#/get-started/?source=try-template&te… (+25 more)

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

D

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.

D

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

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

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)

Skip navigation link detected

4 navigation landmark(s) detected

Breadcrumbs

Search

Skip Link Skip link detected

Labeled Navigation 4 <nav> element(s)

Back to Top

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

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

C

Landmark Structure

Action

6 landmarks

REVIEW

6 landmarks

No <main> landmark found

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

4 <nav> landmark(s) found

4 of 4 <nav> elements are unlabeled

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

No contentinfo (footer) landmark

Skip navigation link present

Page Structure — as a screen reader sees it

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

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

C

Form Accessibility

Action

3 of 7 controls have issues

REVIEW

3 of 7 controls have issues

2 control(s) without accessible label

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

Got: <textarea name="g-recaptcha-response" id="g-recaptcha-response">; <input type="submit">

1 control(s) rely on placeholder only

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

Got: <input type="text" name="coupon">

4 control(s) properly labeled

7 controls

4 labeled

1 placeholder only

2 unlabeled

Control	Type	Label	Method
your-name	text	Your Name (required)	none
your-email	email	Your Email (required)	none
sub	text	Subject	none
your-message	textarea	Your Message	none
coupon	text	(Coupon Code)	placeholder only
#g-recaptcha-response	textarea	(none)	none
input	submit	(none)	none

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

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

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

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

C

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page not found – ColibriWP ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

B

Favicon & Branding

4 icon(s) detected

REVIEW

4 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

C

Color Contrast (Screenshot)

Action

20 text elements analyzed, 19 fail WCAG AA

REVIEW

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

1 pass 19 fail WCAG AA

h2 Design your entire website right inside …

1.72:1

#000000

on

#2E363F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Design features that will make your webs…

1.72:1

#000000

on

#2E363F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Ready to create an awesome website?

1.72:1

#000000

on

#2E363F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Ready to create an awesome website?

1.72:1

#000000

on

#2E363F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 90+ Full Website Templates for a Variety…

1.72:1

#000000

on

#2E363F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Create pages lightning-fast with 150+ pr…

1.72:1

#000000

on

#2E363F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Ready to create

1.72:1

#000000

on

#2E363F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 an awesome website?

1.72:1

#000000

on

#2E363F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Ready to create an awesome website?

1.72:1

#000000

on

#2E363F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Customize any element on the page

1.72:1

#000000

on

#2E363F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 to pixel-perfection

1.72:1

#000000

on

#2E363F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 40+ Drag and Drop Components

1.72:1

#000000

on

#2E363F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Start designing your website with 0 setu…

1.72:1

#000000

on

#2E363F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Free and PRO versions compared

1.72:1

#000000

on

#2E363F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 What our customers say on

1.72:1

#000000

on

#2E363F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Awesome features, tons of pre-made block…

1.72:1

#000000

on

#2E363F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 I love this theme.

1.72:1

#000000

on

#2E363F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 I built a full company site in about 4 h…

1.72:1

#000000

on

#2E363F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 It’s so flexible and beautiful!

1.72:1

#000000

on

#2E363F

needs 3.0:1 (large text)

24px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 WordPress page build…	16.67:1	3.0:1	#000000	#E8E3EF	Pass
h2 Design your entire w…	1.72:1	3.0:1	#000000	#2E363F	Fail
h2 Design features that…	1.72:1	3.0:1	#000000	#2E363F	Fail
h2 Ready to create an a…	1.72:1	3.0:1	#000000	#2E363F	Fail
h2 Ready to create an a…	1.72:1	3.0:1	#000000	#2E363F	Fail
h2 90+ Full Website Tem…	1.72:1	3.0:1	#000000	#2E363F	Fail
h2 Create pages lightni…	1.72:1	3.0:1	#000000	#2E363F	Fail
h2 Ready to create	1.72:1	3.0:1	#000000	#2E363F	Fail
h2 an awesome website?	1.72:1	3.0:1	#000000	#2E363F	Fail
h2 Ready to create an a…	1.72:1	3.0:1	#000000	#2E363F	Fail
h2 Customize any elemen…	1.72:1	3.0:1	#000000	#2E363F	Fail
h2 to pixel-perfection	1.72:1	3.0:1	#000000	#2E363F	Fail
h2 40+ Drag and Drop Co…	1.72:1	3.0:1	#000000	#2E363F	Fail
h2 Start designing your…	1.72:1	3.0:1	#000000	#2E363F	Fail
h2 Free and PRO version…	1.72:1	3.0:1	#000000	#2E363F	Fail
h2 What our customers s…	1.72:1	3.0:1	#000000	#2E363F	Fail
h2 Awesome features, to…	1.72:1	3.0:1	#000000	#2E363F	Fail
h2 I love this theme.	1.72:1	3.0:1	#000000	#2E363F	Fail
h2 I built a full compa…	1.72:1	3.0:1	#000000	#2E363F	Fail
h2 It’s so flexible a…	1.72:1	3.0:1	#000000	#2E363F	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.

C

Lighthouse Accessibility Audits

Action

Score 78/100 — 8 failing, 22 passed

REVIEW

78

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
TRY COLIBRI ONLINE `div.h-x-container-inner > span.h-button__outer > a.d-flex > span`
TRY COLIBRI ONLINE `div.h-x-container-inner > span.h-button__outer > a.d-flex > span`
VIEW ALL TEMPLATES `div.h-x-container-inner > span.h-button__outer > a.d-flex > span`
TRY COLIBRI ONLINE `div.h-x-container-inner > span.h-button__outer > a.d-flex > span`
TRY COLIBRI CLOUD `div.h-x-container-inner > span.h-button__outer > a.d-flex > span`
free `div.w-100 > div.h-global-transition-all > div.h-heading__outer > h4`
GET FREE VERSION `div.h-x-container-inner > span.h-button__outer > a.d-flex > span`
LEARN MORE `div.h-x-container-inner > span.h-button__outer > a.d-flex > span`

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Colibri `div.w-100 > div.style-67 > div.h-global-transition-all > a`

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.d-block > div.h-image__frame-container-outer > div.h-image__frame-container > img.lazyload `div.d-block > div.h-image__frame-container-outer > div.h-image__frame-container > img.lazyload`
div.d-block > div.h-image__frame-container-outer > div.h-image__frame-container > img.lazyload `div.d-block > div.h-image__frame-container-outer > div.h-image__frame-container > img.lazyload`
div.d-block > div.h-image__frame-container-outer > div.h-image__frame-container > img.lazyload `div.d-block > div.h-image__frame-container-outer > div.h-image__frame-container > img.lazyload`
div.d-block > div.h-image__frame-container-outer > div.h-image__frame-container > img.lazyload `div.d-block > div.h-image__frame-container-outer > div.h-image__frame-container > img.lazyload`
div.d-block > div.h-image__frame-container-outer > div.h-image__frame-container > img.lazyload `div.d-block > div.h-image__frame-container-outer > div.h-image__frame-container > img.lazyload`
div.d-block > div.h-image__frame-container-outer > div.h-image__frame-container > img.lazyload `div.d-block > div.h-image__frame-container-outer > div.h-image__frame-container > img.lazyload`
div.d-block > div.h-image__frame-container-outer > div.h-image__frame-container > img.lazyload `div.d-block > div.h-image__frame-container-outer > div.h-image__frame-container > img.lazyload`
div.d-block > div.h-image__frame-container-outer > div.h-image__frame-container > img.lazyload `div.d-block > div.h-image__frame-container-outer > div.h-image__frame-container > img.lazyload`
div.d-block > div.h-image__frame-container-outer > div.h-image__frame-container > img.lazyload `div.d-block > div.h-image__frame-container-outer > div.h-image__frame-container > img.lazyload`
div.d-block > div.h-image__frame-container-outer > div.h-image__frame-container > img.lazyload `div.d-block > div.h-image__frame-container-outer > div.h-image__frame-container > img.lazyload`
div.d-block > div.h-image__frame-container-outer > div.h-image__frame-container > img.lazyload `div.d-block > div.h-image__frame-container-outer > div.h-image__frame-container > img.lazyload`
div.d-block > div.h-image__frame-container-outer > div.h-image__frame-container > img.lazyload `div.d-block > div.h-image__frame-container-outer > div.h-image__frame-container > img.lazyload`
div.d-block > div.h-image__frame-container-outer > div.h-image__frame-container > img.lazyload `div.d-block > div.h-image__frame-container-outer > div.h-image__frame-container > img.lazyload`
div.d-block > div.h-image__frame-container-outer > div.h-image__frame-container > img.lazyload `div.d-block > div.h-image__frame-container-outer > div.h-image__frame-container > img.lazyload`
div.d-block > div.h-image__frame-container-outer > div.h-image__frame-container > img.lazyload `div.d-block > div.h-image__frame-container-outer > div.h-image__frame-container > img.lazyload`
div.d-block > div.h-image__frame-container-outer > div.h-image__frame-container > img.lazyload `div.d-block > div.h-image__frame-container-outer > div.h-image__frame-container > img.lazyload`
div.d-block > div.h-image__frame-container-outer > div.h-image__frame-container > img.lazyload `div.d-block > div.h-image__frame-container-outer > div.h-image__frame-container > img.lazyload`
div.d-block > div.h-image__frame-container-outer > div.h-image__frame-container > img.lazyload `div.d-block > div.h-image__frame-container-outer > div.h-image__frame-container > img.lazyload`
div.d-block > div.h-image__frame-container-outer > div.h-image__frame-container > img.lazyload `div.d-block > div.h-image__frame-container-outer > div.h-image__frame-container > img.lazyload`
div.d-block > div.h-image__frame-container-outer > div.h-image__frame-container > img.lazyload `div.d-block > div.h-image__frame-container-outer > div.h-image__frame-container > img.lazyload`
div.d-block > div.h-image__frame-container-outer > div.h-image__frame-container > img.lazyload `div.d-block > div.h-image__frame-container-outer > div.h-image__frame-container > img.lazyload`
div.d-block > div.h-image__frame-container-outer > div.h-image__frame-container > img.lazyload `div.d-block > div.h-image__frame-container-outer > div.h-image__frame-container > img.lazyload`
div.d-block > div.h-image__frame-container-outer > div.h-image__frame-container > img.lazyload `div.d-block > div.h-image__frame-container-outer > div.h-image__frame-container > img.lazyload`
div.d-block > div.h-image__frame-container-outer > div.h-image__frame-container > img.lazyload `div.d-block > div.h-image__frame-container-outer > div.h-image__frame-container > img.lazyload`
div.d-block > div.h-image__frame-container-outer > div.h-image__frame-container > img.lazyload `div.d-block > div.h-image__frame-container-outer > div.h-image__frame-container > img.lazyload`
div.d-block > div.h-image__frame-container-outer > div.h-image__frame-container > img.lazyload `div.d-block > div.h-image__frame-container-outer > div.h-image__frame-container > img.lazyload`
div.d-block > div.h-image__frame-container-outer > div.h-image__frame-container > img.lazyload `div.d-block > div.h-image__frame-container-outer > div.h-image__frame-container > img.lazyload`

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
div.d-block > div.video-container > div.h-global-transition-all > iframe.h-video-main `div.d-block > div.video-container > div.h-global-transition-all > iframe.h-video-main`

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.d-flex > div.w-100 > div.d-flex > a.d-flex `div.d-flex > div.w-100 > div.d-flex > a.d-flex`

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
No `div.w-100 > div.h-global-transition-all > div.h-heading__outer > h4`
Header `div.w-100 > div.h-global-transition-all > div.h-heading__outer > h4`
Awesome hero sections with video, slideshows & image collage `div.w-100 > div.h-global-transition-all > div.h-heading__outer > h4`
20+ Beautiful headers `div.w-100 > div.h-global-transition-all > div.h-heading__outer > h5`
Background & Colors `div.w-100 > div.h-global-transition-all > div.h-heading__outer > h5`
1. Create a new project in your Colibri account `div.w-100 > div.h-global-transition-all > div.h-heading__outer > h5`
free `div.w-100 > div.h-global-transition-all > div.h-heading__outer > h4`
Personal `div.w-100 > div.h-global-transition-all > div.h-heading__outer > h4`
Business `div.w-100 > div.h-global-transition-all > div.h-heading__outer > h4`
Agency `div.w-100 > div.h-global-transition-all > div.h-heading__outer > h4`
Amazing Support `div.w-100 > div.h-global-transition-all > div.h-heading__outer > h4`

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
Go to slide 1 `div.h-swiper-dots__outer > div.h-swiper-dots__wrapper > div#swiper-pagination__5-c512 > span.swiper-pagination-bullet`
Go to slide 2 `div.h-swiper-dots__outer > div.h-swiper-dots__wrapper > div#swiper-pagination__5-c512 > span.swiper-pagination-bullet`
Go to slide 3 `div.h-swiper-dots__outer > div.h-swiper-dots__wrapper > div#swiper-pagination__5-c512 > span.swiper-pagination-bullet`
Go to slide 4 `div.h-swiper-dots__outer > div.h-swiper-dots__wrapper > div#swiper-pagination__5-c512 > span.swiper-pagination-bullet`
Go to slide 5 `div.h-swiper-dots__outer > div.h-swiper-dots__wrapper > div#swiper-pagination__5-c512 > span.swiper-pagination-bullet`
Go to slide 6 `div.h-swiper-dots__outer > div.h-swiper-dots__wrapper > div#swiper-pagination__5-c512 > span.swiper-pagination-bullet`
Go to slide 7 `div.h-swiper-dots__outer > div.h-swiper-dots__wrapper > div#swiper-pagination__5-c512 > span.swiper-pagination-bullet`
Go to slide 8 `div.h-swiper-dots__outer > div.h-swiper-dots__wrapper > div#swiper-pagination__5-c512 > span.swiper-pagination-bullet`
Go to slide 9 `div.h-swiper-dots__outer > div.h-swiper-dots__wrapper > div#swiper-pagination__5-c512 > span.swiper-pagination-bullet`
Go to slide 10 `div.h-swiper-dots__outer > div.h-swiper-dots__wrapper > div#swiper-pagination__5-c512 > span.swiper-pagination-bullet`

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

●`[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

●Input buttons have discernible text.

●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

●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

●`[lang]` attributes have a valid value

●Deprecated ARIA roles were not used

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

○Skip links are focusable.

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

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