Skip to content
https://demilked.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
45
GRADE
F
FIX
8
REVIEW
3
PASS
2
INFO
0
Checks
13
2 PASS 3 REVIEW 8 FIX
D
Landmark Structure
Action
1 landmarks
FIX
1 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 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 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

F
Alt Text Quality
Action
20 of 20 images have issues
FIX
20 of 20 images have issues
Critical::
20 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
18 image-in-link without alt text
An image inside a link with no alt creates an empty link.
20 images 20 missing
IssueCount
missing20 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

F
Form Accessibility
Action
8 of 9 controls have issues
FIX
8 of 9 controls have issues
Critical::
3 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="search" name="s" id="s">; <input type="submit" name="user-submit" id="login-user">; <input type="submit" name="user-submit" id="add-user">
Warning::
5 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="log" id="user_login">; <input type="password" name="pwd" id="user_pass">; <input type="text" name="user_email" id="user_email">; <input type="text" name="user_login" id="user_login">; <input type="password" name="user_pass" id="user_pass">
Info::
1 control(s) properly labeled
9 controls
1 labeled
5 placeholder only
3 unlabeled
ControlTypeLabelMethod
fields[email]emailemailaria-label
#user_logintext(Username)placeholder only
#user_passpassword(Password)placeholder only
#user_emailtext(Email)placeholder only
#user_logintext(Username)placeholder only
#user_passpassword(Password)placeholder only
#login-usersubmit(none)none
#ssearch(none)none
#add-usersubmit(none)none

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

<input type="search" name="s" id="s">; <input type="submit" name="user-submit" id="login-user">; <input type="submit" name="user-submit" id="add-user">

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="log" id="user_login">; <input type="password" name="pwd" id="user_pass">; <input type="text" name="user_email" id="user_email">; <input type="text" name="user_login" id="user_login">; <input type="password" name="user_pass" id="user_pass">

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

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
No navigation patterns
FIX
No navigation patterns
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)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found | DeMilked ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✓
C
Favicon & Branding
Action
14 icon(s) detected
REVIEW
14 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
C
Lighthouse Accessibility Audits
Action
Score 76/100 — 6 failing, 26 passed
REVIEW
76

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
Advertisement div.pw-ad-scroll-container > div#standard_iab_cntr1 > div.pw_report_ad_container > span

These are opportunities to improve the legibility of your content.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These are opportunities to improve the interpretation of your content by users in different locales.

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
header > div.header > a.logo > img header > div.header > a.logo > img
article.post > div.featured-image > a.featured > img article.post > div.featured-image > a.featured > img
div.pw-ad-scroll-container > div.pw-ad-container-logo > a > img div.pw-ad-scroll-container > div.pw-ad-container-logo > a > img
article.post > div.featured-image > a.featured > img article.post > div.featured-image > a.featured > img
article.post > div.featured-image > a.featured > img article.post > div.featured-image > a.featured > img
article.post > div.featured-image > a.featured > img article.post > div.featured-image > a.featured > img
article.post > div.featured-image > a.featured > img article.post > div.featured-image > a.featured > img
div.pw-ad-scroll-container > div.pw-ad-container-logo > a > img div.pw-ad-scroll-container > div.pw-ad-container-logo > a > img
article.post > div.featured-image > a.featured > img article.post > div.featured-image > a.featured > img
article.post > div.featured-image > a.featured > img article.post > div.featured-image > a.featured > img
article.post > div.featured-image > a.featured > img article.post > div.featured-image > a.featured > img
article.post > div.featured-image > a.featured > img article.post > div.featured-image > a.featured > img
article.post > div.featured-image > a.featured > img article.post > div.featured-image > a.featured > img
article.post > div.featured-image > a.featured > img article.post > div.featured-image > a.featured > img
article.post > div.featured-image > a.featured > img article.post > div.featured-image > a.featured > img

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.searchbox-wrapper > form#search-form > div.search-wrapper > input#s div.searchbox-wrapper > form#search-form > div.search-wrapper > input#s

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
body.home > header > div.header > a.logo body.home > header > div.header > a.logo
div.centered-wrapper > article.post > div.featured-image > a.featured div.centered-wrapper > article.post > div.featured-image > a.featured
div#demilkedcom_dynamic_Articles_4_pw > div.pw-ad-scroll-container > div.pw-ad-container-logo > a div#demilkedcom_dynamic_Articles_4_pw > div.pw-ad-scroll-container > div.pw-ad-container-logo > a
div.centered-wrapper > article.post > div.featured-image > a.featured div.centered-wrapper > article.post > div.featured-image > a.featured
div.centered-wrapper > article.post > div.featured-image > a.featured div.centered-wrapper > article.post > div.featured-image > a.featured
div.centered-wrapper > article.post > div.featured-image > a.featured div.centered-wrapper > article.post > div.featured-image > a.featured
div.centered-wrapper > article.post > div.featured-image > a.featured div.centered-wrapper > article.post > div.featured-image > a.featured
div#demilkedcom_dynamic_Articles_3_pw > div.pw-ad-scroll-container > div.pw-ad-container-logo > a div#demilkedcom_dynamic_Articles_3_pw > div.pw-ad-scroll-container > div.pw-ad-container-logo > a
div.centered-wrapper > article.post > div.featured-image > a.featured div.centered-wrapper > article.post > div.featured-image > a.featured
div.centered-wrapper > article.post > div.featured-image > a.featured div.centered-wrapper > article.post > div.featured-image > a.featured
div.centered-wrapper > article.post > div.featured-image > a.featured div.centered-wrapper > article.post > div.featured-image > a.featured
div.centered-wrapper > article.post > div.featured-image > a.featured div.centered-wrapper > article.post > div.featured-image > a.featured
div.centered-wrapper > article.post > div.featured-image > a.featured div.centered-wrapper > article.post > div.featured-image > a.featured
div.centered-wrapper > article.post > div.featured-image > a.featured div.centered-wrapper > article.post > div.featured-image > a.featured
div.centered-wrapper > article.post > div.featured-image > a.featured div.centered-wrapper > article.post > div.featured-image > a.featured

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

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta head > meta

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
●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
●Document has a `<title>` element
●`<frame>` or `<iframe>` elements have a title
●Links are distinguishable without relying on color.
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●`[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
●All heading elements contain content.
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[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 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 a valid value for its `[lang]` attribute
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○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>`.
○Image elements do not have `[alt]` attributes that are redundant text.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
A
Heading Hierarchy
22 headings, 1 skip(s)
PASS
22 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Illustrations By Martina Paukova Enrich The Daily Routine With Striking Visuals >
  • H2 10 Mysterious Faces Partially Obscured By Enamel Mark Oliver Jeffers’ Dipped Painting Project
  • H2 25 Annoying Habits Women Display That Irritate Their Significant Other
  • H2 25 Cultural Habits People Were Stunned To Realize Were Unique To Their Nation
  • H2 25 Times People Were Justly Served Karmic Consequences For Their Actions
  • H2 20 Magical Driftwood Sculptures By Debra Bernier That Blend Humanity With The Natural World
  • H2 40 Random Photos That Are Funny For Absolutely No Reason
  • H2 40 Times Grandparents Used Social Media And Created Comedy Gold
  • H2 40 Memes That Make Life’s Daily Chaos A Little More Bearable
  • H2 Artist Creates Complex Pencil Sketches Referencing Science Fiction And Architectonics
  • H2 25 Times Superstars’ Reputations Took A Hit While Trying To Do The Right Thing
  • H2 35 Funny Texting ‘Chess Matches’ That Had One Party In A Check-Mate
  • H2 35 Of The Funniest Posts From A Dedicated Cringe Page
  • H4 Subscribe skipped
  • H3 This Dad And Daughter Have Been Taking Pictures In The Same Spot Every Year For 40 Years
  • H3 This Brazilian Street Artist Used Real Trees To Complete These Portraits Of Women
  • H3 30 Funny, Wholesome, And Memorable Tweets Posted By Celebrities
  • H3 Chinese Have Built A 350ft Waterfall On A Skyscraper And It Looks Straight Out Of A Sci-Fi Movie
  • H3 30 Times 7-Year-Olds Surprised Their Parents With Their Logic
  • H3 Sign in for a whole new way to experience art.
  • H4 Don’t have an account yet?
  • H3 Register a new user

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

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

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

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h3 Sign in for a whole …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Register a new user21.00:13.0:1
#000000
#FFFFFF
Pass
title DeMilked - Design Mi…21.00:14.5:1
#000000
#FFFFFF
Pass
span Featured21.00:14.5:1
#000000
#FFFFFF
Pass
a Illustrations By Mar…19.26:14.5:1
#000000
#F5F5F5
Pass
a Popular20.29:14.5:1
#000000
#FBFBFB
Pass
a Latest21.00:14.5:1
#000000
#FFFFFF
Pass
a Topics21.00:14.5:1
#000000
#FFFFFF
Pass
span Create Post21.00:14.5:1
#000000
#FFFFFF
Pass
a Sign in21.00:14.5:1
#000000
#FFFFFF
Pass
span / Register21.00:14.5:1
#000000
#FFFFFF
Pass
a Popular21.00:14.5:1
#000000
#FFFFFF
Pass
a Latest21.00:14.5:1
#000000
#FFFFFF
Pass
a Topics21.00:14.5:1
#000000
#FFFFFF
Pass
a Advertising21.00:14.5:1
#000000
#FFFFFF
Pass
a Animals21.00:14.5:1
#000000
#FFFFFF
Pass
a Architecture21.00:14.5:1
#000000
#FFFFFF
Pass
a Art21.00:14.5:1
#000000
#FFFFFF
Pass
a Beauty21.00:14.5:1
#000000
#FFFFFF
Pass
a Body Art21.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.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback