Skip to content
https://supsystic.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
51
GRADE
F
FIX
6
REVIEW
5
PASS
2
INFO
0
Checks
13
2 PASS 5 REVIEW 6 FIX
D
Form Accessibility
Action
5 of 8 controls have issues
FIX
5 of 8 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit" name="login" id="toeLoginFormSubmit">; <input type="submit" name="register">
Warning::
3 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="s" id="s">; <input type="email" name="email">; <input type="password" name="password">
Info::
3 control(s) properly labeled
8 controls
3 labeled
3 placeholder only
2 unlabeled
ControlTypeLabelMethod
#supsysticUserLogintextUsername or Emailfor/id
#supsysticUserPasswordpasswordPasswordfor/id
remembercheckboxnone
#stext(Search)placeholder only
emailemail(Email)placeholder only
passwordpassword(Password)placeholder only
#toeLoginFormSubmitsubmit(none)none
registersubmit(none)none

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

<input type="submit" name="login" id="toeLoginFormSubmit">; <input type="submit" name="register">

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.

<input type="text" name="s" id="s">; <input type="email" name="email">; <input type="password" name="password">

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

F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Info::
favicon.ico present at site root
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 Present
PNG Icons Missing
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
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::
Back-to-top link detected
Info::
1 navigation landmark(s) detected
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 1 <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
2 landmarks
REVIEW
2 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
1 <nav> landmark(s) found
Info::
No contentinfo (footer) landmark
Warning::
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.
Page Structure — as a screen reader sees it
BANNER header NAV MAIN (missing!) CONTENTINFO (missing!)

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

C
Alt Text Quality
Action
6 of 81 images have issues
REVIEW
6 of 81 images have issues
Critical::
6 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
75 image(s) with good alt text
81 images 75 good alt text 6 missing
IssueCount
missing6 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

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

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

0 pass 20 fail WCAG AA
h1 Ultimate WordPress Plugins by Supsystic
1.55:1
#000000
on
#2E2E2E
needs 3.0:1 (large text)
32px · bottom of viewport
h2 What Is A Plugin For A Website?
1.55:1
#000000
on
#2E2E2E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Are Plugins Worth It On WordPress?
1.55:1
#000000
on
#2E2E2E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 What Are The Things To Look Out For When…
1.55:1
#000000
on
#2E2E2E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 How Do I Add Plugins To My Website?
1.55:1
#000000
on
#2E2E2E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 How Many Plugins Should I Use in WordPre…
1.55:1
#000000
on
#2E2E2E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 What Are The Best WordPress Plugins?
1.55:1
#000000
on
#2E2E2E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Conclusion
1.55:1
#000000
on
#2E2E2E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Frequently Asked Questions
1.55:1
#000000
on
#2E2E2E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Supsystic
1.55:1
#000000
on
#2E2E2E
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Advantages
1.55:1
#000000
on
#2E2E2E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Disadvantages
1.55:1
#000000
on
#2E2E2E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Plugin features
1.55:1
#000000
on
#2E2E2E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 User reviews and average Ratings
1.55:1
#000000
on
#2E2E2E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Active users
1.55:1
#000000
on
#2E2E2E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Support and documentation
1.55:1
#000000
on
#2E2E2E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Plugin compatibility
1.55:1
#000000
on
#2E2E2E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Regular updates
1.55:1
#000000
on
#2E2E2E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 1. WordPress Page Building Plugins
1.55:1
#000000
on
#2E2E2E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 2. WordPress SEO Plugins
1.55:1
#000000
on
#2E2E2E
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Ultimate WordPress P…1.55:13.0:1
#000000
#2E2E2E
Fail
h2 What Is A Plugin For…1.55:13.0:1
#000000
#2E2E2E
Fail
h2 Are Plugins Worth It…1.55:13.0:1
#000000
#2E2E2E
Fail
h2 What Are The Things …1.55:13.0:1
#000000
#2E2E2E
Fail
h2 How Do I Add Plugins…1.55:13.0:1
#000000
#2E2E2E
Fail
h2 How Many Plugins Sho…1.55:13.0:1
#000000
#2E2E2E
Fail
h2 What Are The Best Wo…1.55:13.0:1
#000000
#2E2E2E
Fail
h2 Conclusion1.55:13.0:1
#000000
#2E2E2E
Fail
h2 Frequently Asked Que…1.55:13.0:1
#000000
#2E2E2E
Fail
h2 Supsystic1.55:13.0:1
#000000
#2E2E2E
Fail
h3 Advantages1.55:13.0:1
#000000
#2E2E2E
Fail
h3 Disadvantages1.55:13.0:1
#000000
#2E2E2E
Fail
h3 Plugin features1.55:13.0:1
#000000
#2E2E2E
Fail
h3 User reviews and ave…1.55:13.0:1
#000000
#2E2E2E
Fail
h3 Active users1.55:13.0:1
#000000
#2E2E2E
Fail
h3 Support and document…1.55:13.0:1
#000000
#2E2E2E
Fail
h3 Plugin compatibility1.55:13.0:1
#000000
#2E2E2E
Fail
h3 Regular updates1.55:13.0:1
#000000
#2E2E2E
Fail
h3 1. WordPress Page Bu…1.55:13.0:1
#000000
#2E2E2E
Fail
h3 2. WordPress SEO Plu…1.55:13.0:1
#000000
#2E2E2E
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 — 4 failing, 18 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
Photo Gallery div.menu-footer-menu-container > ul#menu-footer-menu > li#menu-item-20731 > a
Data Tables div.menu-footer-menu-container > ul#menu-footer-menu > li#menu-item-20733 > a
Pricing Table div.menu-footer-menu-container > ul#menu-footer-menu > li#menu-item-20738 > a
Google Maps div.menu-footer-menu-container > ul#menu-footer-menu > li#menu-item-20728 > a
Leaflet, Bing, Mapbox div.menu-footer-menu-container > ul#menu-footer-menu > li#menu-item-20726 > a
Popup div.menu-footer-menu-container > ul#menu-footer-menu > li#menu-item-20732 > a
Contact Form div.menu-footer-menu-container > ul#menu-footer-menu > li#menu-item-20735 > a
Slider div.menu-footer-menu-container > ul#menu-footer-menu > li#menu-item-20743 > a
Social Share Buttons div.menu-footer-menu-container > ul#menu-footer-menu > li#menu-item-20740 > a
Maintenance Mode div.menu-footer-menu-container > ul#menu-footer-menu > li#menu-item-20739 > a
Flipbook div.menu-footer-menu-container > ul#menu-footer-menu > li#menu-item-20734 > a
Product Filter div.menu-footer-menu-container > ul#menu-footer-menu > li#menu-item-27314 > a
GDPR Compliance div.menu-footer-menu-container > ul#menu-footer-menu > li#menu-item-20727 > a
WordPress Plugins div.menu-header-menu-container > ul#menu-header-menu > li.menu-item > a
Downloads div.menu-header-menu-container > ul#menu-header-menu > li.menu-item > a
Pricing div.menu-header-menu-container > ul#menu-header-menu > li.menu-item > a
Support div.menu-header-menu-container > ul#menu-header-menu > li.menu-item > a
Blog div.menu-header-menu-container > ul#menu-header-menu > li.menu-item > a
Contact us div.footer-section > ul.menu > li > a.footer-link
Terms & Conditions div.footer-section > ul.menu > li > a.footer-link
Copyright © 2026 Supsystic. All Rights Reserved. div.container > div.row > div.footer-section > div.footer-copy

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#lc_text-widget > button#lc_text-widget--btn > div.icon > img.circular-image div#lc_text-widget > button#lc_text-widget--btn > div.icon > img.circular-image

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.footer-social > div.footer-social__icon > span.social-icon > a.footer-social__icon div.footer-social > div.footer-social__icon > span.social-icon > a.footer-social__icon
div.footer-social > div.footer-social__icon > span.social-icon > a.footer-social__icon div.footer-social > div.footer-social__icon > span.social-icon > a.footer-social__icon
div.footer-social > div.footer-social__icon > span.social-icon > a.footer-social__icon div.footer-social > div.footer-social__icon > span.social-icon > a.footer-social__icon
div.footer-social > div.footer-social__icon > span.social-icon > a.footer-social__icon div.footer-social > div.footer-social__icon > span.social-icon > a.footer-social__icon
div.footer-social > div.footer-social__icon > span.social-icon > a.footer-social__icon div.footer-social > div.footer-social__icon > span.social-icon > a.footer-social__icon

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.js html.js

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
`<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
Touch targets have sufficient size and spacing.
Heading elements appear in a sequentially-descending order
Uses ARIA roles only on compatible elements
Identical links have the same purpose.
`[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 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
Form elements have associated labels
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
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.
Image elements do not have `[alt]` attributes that are redundant text.
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.
A+
Heading Hierarchy
91 headings
PASS
91 headings
Info::
Single H1 present
  • H1 Ultimate WordPress Plugins by Supsystic
  • H2 What Is A Plugin For A Website?
  • H2 Are Plugins Worth It On WordPress?
  • H3 Advantages
  • H4 Reliable
  • H4 Saves Time
  • H4 Flexible
  • H3 Disadvantages
  • H4 Slow your site
  • H4 Security vulnerabilities
  • H4 Compatibility issues
  • H2 What Are The Things To Look Out For When Choosing The Best WordPress Plugins?
  • H3 Plugin features
  • H3 User reviews and average Ratings
  • H3 Active users
  • H3 Support and documentation
  • H3 Plugin compatibility
  • H3 Regular updates
  • H2 How Do I Add Plugins To My Website?
  • H2 How Many Plugins Should I Use in WordPress?
  • H2 What Are The Best WordPress Plugins?
  • H3 1. WordPress Page Building Plugins
  • H4 Why use a WordPress page-building plugin?
  • H4 What are the drawbacks of using page-building plugins in WordPress?
  • H4 What are the best WordPress page builders?
  • H3 2. WordPress SEO Plugins
  • H4 Why use a WordPress SEO Plugin?
  • H4 What are the drawbacks of using WordPress SEO Plugins?
  • H4 What are the best WordPress SEO Plugins?
  • H3 3. WordPress Email Marketing Plugins
  • H4 Why use a WordPress email marketing plugin?
  • H4 What are the drawbacks of using WordPress email marketing plugins?
  • H4 What are the best WordPress email marketing plugins?
  • H3 4. e-Commerce Plugins
  • H4 Why use an e-Commerce plugin?
  • H4 What are the drawbacks of using e-Commerce plugins?
  • H4 What are the best WordPress eCommerce Plugins?
  • H3 5. WordPress Pricing Table Plugins
  • H4 Why use a WordPress pricing table plugin?
  • H4 What are the drawbacks of using WordPress pricing table plugins?
  • H4 What are the best WordPress pricing table plugins?
  • H3 6. WordPress Security Plugins
  • H4 Why use a WordPress security plugin?
  • H4 What are the drawbacks of using WordPress security plugins?
  • H4 What are the best WordPress Security Plugins?
  • H3 7. WordPress Anti-Spam Plugins
  • H4 Why use a WordPress anti-spam plugin?
  • H4 What are the drawbacks of using WordPress anti-spam plugins?
  • H4 What are the best WordPress anti-spam plugins?
  • H3 8. WordPress Backup and Caching Plugins
  • H4 Why use backup and caching plugins?
  • H4 What are the drawbacks of using WordPress backup and caching plugins?
  • H4 What are the best WordPress backup and caching plugins?
  • H3 9. WordPress Plugins For Galleries, Sliders, and Slideshows
  • H4 Why use a WordPress plugin for galleries or sliders?
  • H4 What are the drawbacks of using WordPress gallery or slider plugins?
  • H4 What are the best WordPress gallery and slider plugins?
  • H3 10. WordPress Table Plugins
  • H4 Why use a WordPress data table plugin?
  • H4 What are the drawbacks of using WordPress data table plugins?
  • H4 What are the best WordPress table plugins?
  • H3 11. WordPress Map Plugins
  • H4 Why use a WordPress map plugin?
  • H4 What are the drawbacks of using WordPress map plugins?
  • H4 What are the best WordPress map plugins?
  • H3 12. WordPress Social Media Sharing Plugins
  • H4 Why use a WordPress social media sharing plugin?
  • H4 What are the drawbacks of using WordPress social media sharing plugins?
  • H4 What are the best WordPress social media sharing plugins?
  • H3 13. WordPress Contact Form Plugins
  • H4 Why use a WordPress contact form plugin?
  • H4 What are the drawbacks of using WordPress contact form plugins?
  • H4 What are the best WordPress contact form plugins?
  • H3 14. WordPress Popup Plugins
  • H4 Why use a WordPress Popup plugin?
  • H4 What are the drawbacks of using WordPress popup plugins?
  • H4 What are the best WordPress popup plugins?
  • H3 15. WordPress Google Analytics Dashboard Integration Plugins
  • H4 Why use a Google Analytics Dashboard integration plugin?
  • H4 What are the drawbacks of using these plugins?
  • H4 What are the best WordPress plugins for Google Analytics integration?
  • H3 16. WordPress Consent Plugins
  • H4 Why use a WordPress consent plugin?
  • H4 What are the drawbacks of using WordPress consent plugins?
  • H4 What are the best WordPress consent plugins?
  • H2 Conclusion
  • H2 Frequently Asked Questions
  • H3 Q1. What are the most useful plugins for WordPress?
  • H3 Q2. Which plugin is better than Elementor?
  • H3 Q3. What is the best free WordPress plugin?
  • H2 Supsystic
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 Page not found | Supsystic 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