Skip to content
https://writeablog.net

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
47
GRADE
F
FIX
8
REVIEW
4
PASS
1
INFO
0
Checks
13
1 PASS 4 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>.
Info::
1 <nav> landmark(s) 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.
Page Structure — as a screen reader sees it
BANNER (missing!) 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

F
404 Error Page
Action
HTTP 404, bare page
FIX
HTTP 404, bare page
Info::
Correct 404 status code returned
Got: HTTP 404
Warning::
Bare server default 404 page
The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.
404 Page Quality Default 404 Page
Status Code HTTP 404 ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
D
Favicon & Branding
Action
3 icon(s) detected
FIX
3 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
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 Present
✗ 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
No navigation patterns
FIX
No navigation patterns
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)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
D
Lighthouse Accessibility Audits
Action
Score 54/100 — 6 failing, 8 passed
FIX
54

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

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body#body > button#open-button body#body > button#open-button

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
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire
body#body > img.fire body#body > img.fire

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
ul.social-icons > li > div > a.social-icon ul.social-icons > li > div > a.social-icon
ul.social-icons > li > div > a.social-icon ul.social-icons > li > div > a.social-icon
ul.social-icons > li > div > a.social-icon ul.social-icons > li > div > a.social-icon
ul.social-icons > li > div > a.social-icon ul.social-icons > li > div > a.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.

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
ABOUT div#menu > div > a.menu-link > span
SERVICES div#menu > div > a.menu-link > span
FEATURES div#menu > div > a.menu-link > span
JOIN US span.btn > span.btn-label > a > b

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
Easy Customization div.about-features > div.row > div.col-lg-3 > h6
User Friendly div.fb-table > div.fb-table-cell > div > h6

These are opportunities to improve keyboard navigation in your application.

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-hidden="true"]` is not present on the document `<body>`
●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
●Touch targets have sufficient size and spacing.
●Document has a main landmark.
○`[accesskey]` values are unique
○`[aria-*]` attributes match their roles
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA attributes are used as specified for the element's role
○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
○Elements use only permitted ARIA attributes
○`[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
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○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
○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.
○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.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○Identical links have the same purpose.
○Elements with visible text labels have matching accessible names.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
C
Heading Hierarchy
Action
15 headings, 2 skip(s)
REVIEW
15 headings, 2 skip(s)
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Write A Blog
  • H1 Simple & Powerful blog solution. duplicate H1
  • H2 We work for a purpose & we believe in it.
  • H6 easy customization skipped
  • H6 social media feeds
  • H6 security is top priority
  • H6 multi browser support
  • H2 Comes with unlimitedposibilities and features.
  • H6 user friendly skipped
  • H6 easy customization
  • H6 Lots of themes
  • H6 Connect multiple services
  • H6 Create your own themes
  • H6 Social MediaFeeds
  • H2 Subscribe & Stay Updated

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

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

C
Alt Text Quality
Action
150 of 150 images have issues
REVIEW
150 of 150 images have issues
Critical::
150 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
150 images 150 missing
IssueCount
missing150 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 Write A Blog
1.07:1
#000000
on
#0D0B0D
needs 3.0:1 (large text)
32px · above the fold
h1 Simple & Powerful
1.06:1
#000000
on
#0C0A0B
needs 3.0:1 (large text)
32px · above the fold
h1 blog solution.
1.08:1
#000000
on
#0E0C0D
needs 3.0:1 (large text)
32px · above the fold
h2 We work for a
1.08:1
#000000
on
#0E0C0D
needs 3.0:1 (large text)
24px · mid-page
h2 & we believe in it.
1.09:1
#000000
on
#100E0F
needs 3.0:1 (large text)
24px · mid-page
h2 Comes with
1.15:1
#000000
on
#181512
needs 3.0:1 (large text)
24px · bottom of viewport
h2 posibilities and features.
1.08:1
#000000
on
#100C0B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Subscribe & Stay Updated
1.06:1
#000000
on
#0C0909
needs 3.0:1 (large text)
24px · bottom of viewport
title Oyo
1.05:1
#000000
on
#09080A
needs 4.5:1 (normal text)
16px · top of page (header area)
span home
1.05:1
#000000
on
#09080A
needs 4.5:1 (normal text)
16px · top of page (header area)
span about
1.06:1
#000000
on
#09090A
needs 4.5:1 (normal text)
16px · top of page (header area)
span services
1.06:1
#000000
on
#09090A
needs 4.5:1 (normal text)
16px · top of page (header area)
span features
1.06:1
#000000
on
#09090B
needs 4.5:1 (normal text)
16px · above the fold
b Hencework © 2017.
1.06:1
#000000
on
#0A090A
needs 3.0:1 (large text)
16px · above the fold
p Get startted with your own new blog now
1.07:1
#000000
on
#0D0B0B
needs 4.5:1 (normal text)
16px · above the fold
b Join us
1.08:1
#000000
on
#0F0D0E
needs 3.0:1 (large text)
16px · above the fold
i purpose
1.08:1
#000000
on
#0E0D0E
needs 4.5:1 (normal text)
16px · mid-page
p Write A Blog is a free, user-friendly bl…
1.10:1
#000000
on
#110F0F
needs 4.5:1 (normal text)
16px · mid-page
p Write A Blog is free. The cost of settin…
1.12:1
#000000
on
#131110
needs 4.5:1 (normal text)
16px · mid-page
i unlimited
1.13:1
#000000
on
#151210
needs 4.5:1 (normal text)
16px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Write A Blog1.07:13.0:1
#000000
#0D0B0D
Fail
h1 Simple & Powerful1.06:13.0:1
#000000
#0C0A0B
Fail
h1 blog solution.1.08:13.0:1
#000000
#0E0C0D
Fail
h2 We work for a1.08:13.0:1
#000000
#0E0C0D
Fail
h2 & we believe in it.1.09:13.0:1
#000000
#100E0F
Fail
h2 Comes with1.15:13.0:1
#000000
#181512
Fail
h2 posibilities and fea…1.08:13.0:1
#000000
#100C0B
Fail
h2 Subscribe & Stay Upd…1.06:13.0:1
#000000
#0C0909
Fail
title Oyo1.05:14.5:1
#000000
#09080A
Fail
span home1.05:14.5:1
#000000
#09080A
Fail
span about1.06:14.5:1
#000000
#09090A
Fail
span services1.06:14.5:1
#000000
#09090A
Fail
span features1.06:14.5:1
#000000
#09090B
Fail
b Hencework © 2017.1.06:13.0:1
#000000
#0A090A
Fail
p Get startted with yo…1.07:14.5:1
#000000
#0D0B0B
Fail
b Join us1.08:13.0:1
#000000
#0F0D0E
Fail
i purpose1.08:14.5:1
#000000
#0E0D0E
Fail
p Write A Blog is a fr…1.10:14.5:1
#000000
#110F0F
Fail
p Write A Blog is free…1.12:14.5:1
#000000
#131110
Fail
i unlimited1.13:14.5:1
#000000
#151210
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.

A
Form Accessibility
1 of 1 controls have issues
PASS
1 of 1 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="email" name="email">
1 controls
0 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
emailemail(Your Email ID)placeholder only

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

<input type="email" name="email">

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

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

Send Feedback