https://amandaai.com
Accessibility
· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.SCORE
74
GRADE
C
FIX
6
REVIEW
6
PASS
12
INFO
0
Checks
2412 PASS 6 REVIEW 6 FIX
DAlt Text QualityAction5 of 24 images have issuesFIX
Alt Text Quality
Action5 of 24 images have issues
5 of 24 images have issues
Critical::
5 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
1 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
10 decorative image(s) correctly marked
Info::
9 image(s) with good alt text
24 images 9 good alt text 10 decorative 5 missing
| Issue | Count |
|---|---|
| missing | 5 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
DTabindex Anti-PatternsAction0 positive, 28 -1-on-focusableFIX
Tabindex Anti-Patterns
Action0 positive, 28 -1-on-focusable
0 positive, 28 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
DWeb ManifestActionNot foundFIX
Web Manifest
ActionNot found
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.
DDark Mode SupportActionTheme color onlyFIX
Dark Mode Support
ActionTheme color only
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #000000
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark ModePartial Dark Mode
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗
Detection limited to meta tags and inline styles.
DPrint StylesheetActionNo print stylesFIX
Print Stylesheet
ActionNo print styles
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 ✗
BLandmark Structure25 landmarksREVIEW
Landmark Structure
25 landmarks
25 landmarks
Info::
<main> landmark present
Info::
16 <nav> landmark(s) found
Warning::
8 of 16 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Warning::
Skip link target(s) don't exist on page: #content
The skip-link anchor (e.g., `href="#main"`) points at an ID that has no corresponding element on the page. Activating the link does nothing -- a silent WCAG 2.4.1 failure that the visual link presence hides. Add `id="main"` (or whichever matches the href) to the target landmark.
Page Structure — as a screen reader sees it
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
The skip-link anchor (e.g., `href="#main"`) points at an ID that has no corresponding element on the page. Activating the link does nothing -- a silent WCAG 2.4.1 failure that the visual link presence hides. Add `id="main"` (or whichever matches the href) to the target landmark.
Why this matters
Skip link points at an ID that doesn't exist on the page. The link looks fine visually but does nothing when activated -- silent WCAG 2.4.1 failure.
Learn more ▾ ▴
Find the target landmark (typically <main> or the first <h1>) and add `id="..."` matching the skip link's href fragment. Test by tabbing to the skip link and pressing Enter -- focus should jump to the target.
Source: WCAG 2.1 SC 2.4.1
BHeading Hierarchy17 headingsREVIEW
Heading Hierarchy
17 headings
17 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
- H2 Better ads. Less effort.
- H2 Better ads. Less effort.
- H2 One platform to rule them all
- H2 One platform to rule them all
- H2 Efficiency beyond traditional limits
- H2 “With Amanda AI’s world-class platform, we strengthen the quality for our customers while creating added value for our staff.”
- H2 “With Amanda AI’s world-class platform, we strengthen the quality for our customers while creating added value for our staff.”
- H2 “With Amanda AI’s world-class platform, we strengthen the quality for our customers while creating added value for our staff.”
- H2 “With Amanda AI’s world-class platform, we strengthen the quality for our customers while creating added value for our staff.”
- H2 “With Amanda AI’s world-class platform, we strengthen the quality for our customers while creating added value for our staff.”
- H2 “With Amanda AI’s world-class platform, we strengthen the quality for our customers while creating added value for our staff.”
- H2 Powered by the best in the business
- H2 Dance to the algorithms!
- H2 Product
- H2 Resources
- H2 Company
- H2 Join our newsletter
Every page should have one H1 that describes the page content.
Why this matters
No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.
Learn more ▾ ▴
The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.
Source: WCAG 2.4.6 / Google Search Central
CLink & Button QualityAction10 issue(s) across 111 links and 2 buttonsREVIEW
Link & Button Quality
Action10 issue(s) across 111 links and 2 buttons
10 issue(s) across 111 links and 2 buttons
Critical::
10 link(s) with no accessible text
Links without text are announced as raw URLs by screen readers.
Got: https://amandaai.com; #elementor-action%3Aaction%3Dpopup%3Aopen%26settings%3DeyJpZCI6IjM0MDMiLCJ0b2…; https://amandaai.com; https://amandaai.com; https://www.google.com/partners/agency?id=4834493995; https://apps.shopify.com/amanda-ai; https://amandaai.com; #elementor-action%3Aaction%3Dpopup%3Aclose%26settings%3DeyJkb19ub3Rfc2hvd19hZ…; #elementor-action%3Aaction%3Dpopup%3Aclose%26settings%3DeyJkb19ub3Rfc2hvd19hZ…; #elementor-action%3Aaction%3Dpopup%3Aclose%26settings%3DeyJkb19ub3Rfc2hvd19hZ…
Warning::
8 link(s) open in new tab without warning
Add '(opens in new tab)' to link text or aria-label.
Got: https://app.amandaai.com/join; https://app.amandaai.com/join; http://KungSängen; http://KungSängen; https://se.linkedin.com/company/amanda-ai; https://www.facebook.com/amandaaiads/; https://www.youtube.com/@advertisingrobot; https://app.amandaai.com/login
Info::
93 link(s) with descriptive text
111 links
10 empty
0 generic text
8 new tab
0 empty buttons
| Element | Text | Issue | Suggested Fix |
|---|---|---|---|
| https://amandaai.com | (empty) | empty | Add link text or aria-label |
| #elementor-action%3Aaction%3Dpopup%3Aope… | (empty) | empty | Add link text or aria-label |
| https://amandaai.com | (empty) | empty | Add link text or aria-label |
| https://app.amandaai.com/join | Sign up | new tab | Add '(opens in new tab)' to text |
| https://app.amandaai.com/join | SIGN UP | new tab | Add '(opens in new tab)' to text |
| http://KungSängen | GroupM Nexus | new tab | Add '(opens in new tab)' to text |
| http://KungSängen | GroupM Nexus | new tab | Add '(opens in new tab)' to text |
| https://amandaai.com | (empty) | empty | Add link text or aria-label |
| https://se.linkedin.com/company/amanda-a… | new tab | Add '(opens in new tab)' to text | |
| https://www.facebook.com/amandaaiads/ | new tab | Add '(opens in new tab)' to text | |
| https://www.youtube.com/@advertisingrobo… | Youtube | new tab | Add '(opens in new tab)' to text |
| https://www.google.com/partners/agency?i… | (empty) | empty | Add link text or aria-label |
| https://apps.shopify.com/amanda-ai | (empty) | empty | Add link text or aria-label |
| https://amandaai.com | (empty) | empty | Add link text or aria-label |
| #elementor-action%3Aaction%3Dpopup%3Aclo… | (empty) | empty | Add link text or aria-label |
| https://app.amandaai.com/login | Login | new tab | Add '(opens in new tab)' to text |
| #elementor-action%3Aaction%3Dpopup%3Aclo… | (empty) | empty | Add link text or aria-label |
| #elementor-action%3Aaction%3Dpopup%3Aclo… | (empty) | empty | Add link text or aria-label |
95 links and buttons have descriptive text
Links without text are announced as raw URLs by screen readers.
https://amandaai.com; #elementor-action%3Aaction%3Dpopup%3Aopen%26settings%3DeyJpZCI6IjM0MDMiLCJ0b2…; https://amandaai.com; https://amandaai.com; https://www.google.com/partners/agency?id=4834493995; https://apps.shopify.com/amanda-ai; https://amandaai.com; #elementor-action%3Aaction%3Dpopup%3Aclose%26settings%3DeyJkb19ub3Rfc2hvd19hZ…; #elementor-action%3Aaction%3Dpopup%3Aclose%26settings%3DeyJkb19ub3Rfc2hvd19hZ…; #elementor-action%3Aaction%3Dpopup%3Aclose%26settings%3DeyJkb19ub3Rfc2hvd19hZ…
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
Add '(opens in new tab)' to link text or aria-label.
https://app.amandaai.com/join; https://app.amandaai.com/join; http://KungSängen; http://KungSängen; https://se.linkedin.com/company/amanda-ai; https://www.facebook.com/amandaaiads/; https://www.youtube.com/@advertisingrobot; https://app.amandaai.com/login
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
C404 Error PageActionCould not testREVIEW
404 Error Page
ActionCould not test
Could not test
Info::
404 page could not be tested
The 404 page check encountered an error. This may be due to a timeout or network issue.
404 page quality check not available.
CFavicon & BrandingAction3 icon(s) detectedREVIEW
Favicon & Branding
Action3 icon(s) detected
3 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
CColor Contrast (Screenshot)Action20 text elements analyzed, 20 fail WCAG AAREVIEW
Color Contrast (Screenshot)
Action20 text elements analyzed, 20 fail WCAG AA
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
h2 Better ads.
1.00:1#000000
on#000000
needs 3.0:1 (large text)24px · mid-page
h2 Less effort.
1.00:1#000000
on#000000
needs 3.0:1 (large text)24px · mid-page
h2 Better ads.
1.00:1#000000
on#000000
needs 3.0:1 (large text)24px · mid-page
h2 Less effort.
1.00:1#000000
on#000000
needs 3.0:1 (large text)24px · mid-page
h2 One platform
to rule them all
1.00:1#000000
on#000000
needs 3.0:1 (large text)24px · bottom of viewport
h2 One platform to rule them all
1.00:1#000000
on#000000
needs 3.0:1 (large text)24px · bottom of viewport
h2 Efficiency beyond traditional limits
1.00:1#000000
on#000000
needs 3.0:1 (large text)24px · bottom of viewport
h2 “With Amanda AI’s world-class platfo…
1.00:1#000000
on#000000
needs 3.0:1 (large text)24px · bottom of viewport
h2 “With Amanda AI’s world-class platfo…
1.00:1#000000
on#000000
needs 3.0:1 (large text)24px · bottom of viewport
h2 “With Amanda AI’s world-class platfo…
1.00:1#000000
on#000000
needs 3.0:1 (large text)24px · bottom of viewport
h2 “With Amanda AI’s world-class platfo…
1.00:1#000000
on#000000
needs 3.0:1 (large text)24px · bottom of viewport
h2 “With Amanda AI’s world-class platfo…
1.00:1#000000
on#000000
needs 3.0:1 (large text)24px · bottom of viewport
h2 “With Amanda AI’s world-class platfo…
1.00:1#000000
on#000000
needs 3.0:1 (large text)24px · bottom of viewport
h2 Powered by the best in the business
1.00:1#000000
on#000000
needs 3.0:1 (large text)24px · bottom of viewport
h2 Dance to the
1.00:1#000000
on#000000
needs 3.0:1 (large text)24px · bottom of viewport
h2 algorithms!
1.00:1#000000
on#000000
needs 3.0:1 (large text)24px · bottom of viewport
h2 Product
1.00:1#000000
on#000000
needs 3.0:1 (large text)24px · bottom of viewport
h2 Resources
1.00:1#000000
on#000000
needs 3.0:1 (large text)24px · bottom of viewport
h2 Company
1.00:1#000000
on#000000
needs 3.0:1 (large text)24px · bottom of viewport
h2 Join our newsletter
1.00:1#000000
on#000000
needs 3.0:1 (large text)24px · bottom of viewport
Show all checked elements (20)
| Element | Ratio | Required | FG | BG | Result |
|---|---|---|---|---|---|
| h2 Better ads. | 1.00:1 | 3.0:1 | #000000 | #000000 | Fail |
| h2 Less effort. | 1.00:1 | 3.0:1 | #000000 | #000000 | Fail |
| h2 Better ads. | 1.00:1 | 3.0:1 | #000000 | #000000 | Fail |
| h2 Less effort. | 1.00:1 | 3.0:1 | #000000 | #000000 | Fail |
| h2 One platform to ru… | 1.00:1 | 3.0:1 | #000000 | #000000 | Fail |
| h2 One platform to rule… | 1.00:1 | 3.0:1 | #000000 | #000000 | Fail |
| h2 Efficiency beyond tr… | 1.00:1 | 3.0:1 | #000000 | #000000 | Fail |
| h2 “With Amanda AI’… | 1.00:1 | 3.0:1 | #000000 | #000000 | Fail |
| h2 “With Amanda AI’… | 1.00:1 | 3.0:1 | #000000 | #000000 | Fail |
| h2 “With Amanda AI’… | 1.00:1 | 3.0:1 | #000000 | #000000 | Fail |
| h2 “With Amanda AI’… | 1.00:1 | 3.0:1 | #000000 | #000000 | Fail |
| h2 “With Amanda AI’… | 1.00:1 | 3.0:1 | #000000 | #000000 | Fail |
| h2 “With Amanda AI’… | 1.00:1 | 3.0:1 | #000000 | #000000 | Fail |
| h2 Powered by the best … | 1.00:1 | 3.0:1 | #000000 | #000000 | Fail |
| h2 Dance to the | 1.00:1 | 3.0:1 | #000000 | #000000 | Fail |
| h2 algorithms! | 1.00:1 | 3.0:1 | #000000 | #000000 | Fail |
| h2 Product | 1.00:1 | 3.0:1 | #000000 | #000000 | Fail |
| h2 Resources | 1.00:1 | 3.0:1 | #000000 | #000000 | Fail |
| h2 Company | 1.00:1 | 3.0:1 | #000000 | #000000 | Fail |
| h2 Join our newsletter | 1.00:1 | 3.0:1 | #000000 | #000000 | 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.
AHeading Text Quality1 heading-text-quality issue(s) detectedPASS
Heading Text Quality
1 heading-text-quality issue(s) detected
1 heading-text-quality issue(s) detected
Warning::
3 heading(s) are over 120 characters -- likely a misformatted paragraph
Headings beyond 120 characters are almost always full sentences or paragraphs that received heading semantics by mistake (e.g., a CMS editor selected the wrong block type, or a template wrapped a body paragraph in `<h2>`). Screen readers will announce these as "heading" and read the entire paragraph at heading prosody. Affected:
- H2: 126 chars
- H2: 126 chars
- H2: 126 chars
Got: 3 >120-char heading(s)
AForm Accessibility1 of 3 controls have issuesPASS
Form Accessibility
1 of 3 controls have issues
1 of 3 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit" id="gform_submit_button_3">
Info::
2 control(s) properly labeled
3 controls
2 labeled
0 placeholder only
1 unlabeled
| Control | Type | Label | Method |
|---|---|---|---|
| #form-field-email | for/id | ||
| #input_3_1 | for/id | ||
| #gform_submit_button_3 | submit | (none) | none |
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
<input type="submit" id="gform_submit_button_3">
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
A+Form Input Types3 form control(s) checked, no type mismatchesPASS
Form Input Types
3 form control(s) checked, no type mismatches
3 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+Form Input Quality3 form control(s) checked, no input-semantic issuesPASS
Form Input Quality
3 form control(s) checked, no input-semantic issues
3 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+Mobile Keyboard & AutofillNo autofill-eligible form controlsPASS
Mobile Keyboard & Autofill
No autofill-eligible form controls
No autofill-eligible form controls
Info::
No autofill-eligible form controls (no name/email/tel/address fields)
A+Document LanguageLang attribute set to "en-US"PASS
Document Language
Lang attribute set to "en-US"
Lang attribute set to "en-US"
Info::
<html lang="en-US"> is set and valid
Got: en-US
A+Iframe AccessibilityAll 1 iframe(s) have descriptive titlesPASS
Iframe Accessibility
All 1 iframe(s) have descriptive titles
All 1 iframe(s) have descriptive titles
Info::
All 1 iframe(s) have title attributes
A+Tap Target AdequacyAll tap targets meet WCAG 2.5.5/2.5.8 sizingPASS
Tap Target Adequacy
All tap targets meet WCAG 2.5.5/2.5.8 sizing
All tap targets meet WCAG 2.5.5/2.5.8 sizing
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+Mobile-Readable Font SizesAll 42 visible text node(s) render at >= 12 CSS pixelsPASS
Mobile-Readable Font Sizes
All 42 visible text node(s) render at >= 12 CSS pixels
All 42 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
A+PWA DepthNo PWA depth issues detectedPASS
PWA Depth
No PWA depth issues detected
No PWA depth issues detected
Info::
No PWA depth issues detected
A+Mobile UX Depth1 mobile-depth signal(s) detectedPASS
Mobile UX Depth
1 mobile-depth signal(s) detected
1 mobile-depth signal(s) detected
Info::
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.
ALighthouse Accessibility AuditsScore 92/100 — 2 failing, 29 passedPASS
Lighthouse Accessibility Audits
Score 92/100 — 2 failing, 29 passed
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.
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.elementor-element > div.elementor-widget-container > webien-image.has-thumb > img.thumb div.elementor-element > div.elementor-widget-container > webien-image.has-thumb > img.thumb |
div.elementor-element > div.elementor-widget-container > a > img div.elementor-element > div.elementor-widget-container > a > img |
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.webien-container-padding-none > div.elementor-element > div.elementor-widget-container > a div.webien-container-padding-none > div.elementor-element > div.elementor-widget-container > a |
div.elementor-element > div.elementor-widget-container > div.elementor-icon-wrapper > a.elementor-icon div.elementor-element > div.elementor-widget-container > div.elementor-icon-wrapper > a.elementor-icon |
div.e-con-inner > div.elementor-element > div.elementor-widget-container > a.e-lottie__container__link div.e-con-inner > div.elementor-element > div.elementor-widget-container > a.e-lottie__container__link |
div.e-con-inner > div.elementor-element > div.elementor-widget-container > a div.e-con-inner > div.elementor-element > div.elementor-widget-container > a |
div.e-con-inner > div.elementor-element > div.elementor-widget-container > a div.e-con-inner > div.elementor-element > div.elementor-widget-container > a |
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.
○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
●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
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Background and foreground colors have a sufficient contrast ratio
●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
●Touch targets have sufficient size and spacing.
●`[lang]` attributes have a valid value
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Uses ARIA roles only on compatible elements
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements 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
○Links are distinguishable without relying on color.
○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.
○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.
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.