Skip to content
https://folkd.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
51
GRADE
F
FIX
6
REVIEW
4
PASS
3
INFO
0
Checks
13
3 PASS 4 REVIEW 6 FIX
D
Landmark Structure
Action
No landmarks
FIX
No landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Warning::
No <nav> landmark found
Info::
No banner (header) landmark
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.

No landmarks detected

Screen reader users have no way to navigate by region.

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

Why this matters

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

Learn more ▾

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

Source: WAI-ARIA / WCAG 2.4.1

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

Why this matters

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

Learn more ▾

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

Source: WCAG 2.1 SC 2.4.1

F
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
Soft 404: server returns HTTP 200 for non-existent pages
The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.
Got: Status: 200 for /beavercheck-404-test-5r8wdi
404 Page Quality ✗ Soft 404 (HTTP 200)
Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://folkd.com/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://folkd.com/manifest.json

Manifest contains invalid JSON.

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
No navigation patterns
FIX
No navigation patterns
Info::
Hamburger menu detected (responsive design)
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
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Heading Hierarchy
Action
20 headings, 3 skip(s)
REVIEW
20 headings, 3 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H4 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Looking for love? Or just a hot date tonight?
  • H4 Millions of Members skipped
  • H4 Fast & Easy to Join
  • H4 Safe + Secure
  • H2 Millions of Singles for You
  • H2 Join today! Millions of singles are waiting…
  • H2 Member Testimonials
  • H5 Eric S. skipped
  • H5 Sarah T.
  • H5 Bret D.
  • H6 About Folkd
  • H3 Millions of Members.Easy to use.Free to Join.
  • H2 The secret of dating success is Folkd
  • H5 Millions of Members skipped
  • H5 Mobile + Desktop
  • H5 Verified Upfront
  • H5 Free to Join
  • H2 Join now and meet singles today!
  • H2 Join for Free Today (3 sec)
  • H2 Join for Free Today (60 sec)

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

B
Favicon & Branding
4 icon(s) detected
REVIEW
4 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
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, 14 fail WCAG AA
REVIEW

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

6 pass 14 fail WCAG AA
h1 Looking for love? Or just a hot date ton…
2.21:1
#000000
on
#3D4844
needs 3.0:1 (large text)
32px · above the fold · over background image/gradient
h2 The secret of dating success is Folkd
1.38:1
#000000
on
#25252B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Join now and meet singles today!
1.38:1
#000000
on
#25252B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Join for Free Today (3 sec)
1.38:1
#000000
on
#25252B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Join for Free Today (60 sec)
1.38:1
#000000
on
#25252B
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Millions of Members.
1.38:1
#000000
on
#25252B
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Easy to use.
1.38:1
#000000
on
#25252B
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Free to Join.
1.38:1
#000000
on
#25252B
needs 3.0:1 (large text)
19px · bottom of viewport
title Folkd
1.21:1
#000000
on
#151B1F
needs 4.5:1 (normal text)
16px · top of page (header area)
span Folkd
1.29:1
#000000
on
#241F1D
needs 4.5:1 (normal text)
16px · top of page (header area)
a Home
1.17:1
#000000
on
#24120C
needs 4.5:1 (normal text)
16px · top of page (header area)
a Sign Up
2.26:1
#000000
on
#53452F
needs 4.5:1 (normal text)
16px · top of page (header area)
a Member Login
1.59:1
#000000
on
#352F29
needs 4.5:1 (normal text)
16px · above the fold
p Folkd has been connecting millions of pe…
2.65:1
#000000
on
#4A5446
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient

2 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Looking for love? Or…2.21:13.0:1
#000000
#3D4844
Fail
h2 Millions of Singles …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Join today! Millions…5.57:13.0:1
#000000
#A17C62
Pass
h2 Member Testimonials10.09:13.0:1
#000000
#CCAE9A
Pass
h2 The secret of dating…1.38:13.0:1
#000000
#25252B
Fail
h2 Join now and meet si…1.38:13.0:1
#000000
#25252B
Fail
h2 Join for Free Today …1.38:13.0:1
#000000
#25252B
Fail
h2 Join for Free Today …1.38:13.0:1
#000000
#25252B
Fail
h3 Millions of Members.1.38:13.0:1
#000000
#25252B
Fail
h3 Easy to use.1.38:13.0:1
#000000
#25252B
Fail
h3 Free to Join.1.38:13.0:1
#000000
#25252B
Fail
title Folkd1.21:14.5:1
#000000
#151B1F
Fail
span Folkd1.29:14.5:1
#000000
#241F1D
Fail
a Home1.17:14.5:1
#000000
#24120C
Fail
a Sign Up2.26:14.5:1
#000000
#53452F
Fail
a Member Login1.59:14.5:1
#000000
#352F29
Fail
p Folkd has been conne…2.65:14.5:1
#000000
#4A5446
Fail
span Join now for free17.93:14.5:1
#000000
#ECEDEF
Pass
h4 Millions of Members21.00:13.0:1
#000000
#FFFFFF
Pass
p Folkd has millions o…21.00:14.5:1
#000000
#FFFFFF
Pass

Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.

A+
Alt Text Quality
All 7 images OK
PASS
All 7 images OK
Info::
7 decorative image(s) correctly marked
7 images 7 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 2 controls labeled
PASS
All 2 controls labeled
Info::
2 control(s) properly labeled
2 controls
2 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#ays-pb-modal-checkbox_2checkboxmodal-checkfor/id
#ays-pb-modal-checkbox_3checkboxmodal-checkfor/id
A
Lighthouse Accessibility Audits
Score 90/100 — 3 failing, 21 passed
PASS
90

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
Ok div#cookie-notice > div.cookie-notice-container > span#cn-notice-buttons > button#cn-accept-cookie

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Millions of Members div.wp-block > div.position-relative > div.position-relative > h4#heading
Eric S. div.wp-block > div.position-relative > div.position-relative > h5.wp-block
Millions of Members div.wp-block > div.position-relative > div.position-relative > h5.wp-block

These are opportunities to improve keyboard navigation in your application.

Names and labels

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.position-relative > figure.wp-block > div.position-relative > a.position-relative div.position-relative > figure.wp-block > div.position-relative > a.position-relative
div.position-relative > figure.wp-block > div.position-relative > a.position-relative div.position-relative > figure.wp-block > div.position-relative > a.position-relative
div.position-relative > figure.wp-block > div.position-relative > a.position-relative div.position-relative > figure.wp-block > div.position-relative > a.position-relative
div.position-relative > figure.wp-block > div.position-relative > a.position-relative div.position-relative > figure.wp-block > div.position-relative > a.position-relative
div.position-relative > figure.wp-block > div.position-relative > a.position-relative div.position-relative > figure.wp-block > div.position-relative > a.position-relative
div.position-relative > figure.wp-block > div.position-relative > a.position-relative div.position-relative > figure.wp-block > div.position-relative > a.position-relative

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
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●`[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.
●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.
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements 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
○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
○`<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
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
○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.
○`[lang]` attributes have a valid value
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○Identical links have the same purpose.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback