Skip to content
https://dev.to

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
60
GRADE
D
FIX
5
REVIEW
5
PASS
3
INFO
0
Checks
13
3 PASS 5 REVIEW 5 FIX
F
Alt Text Quality
Action
32 of 88 images have issues
FIX
32 of 88 images have issues
Critical::
32 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
27 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
19 decorative image(s) correctly marked
Info::
37 image(s) with good alt text
88 images 37 good alt text 19 decorative 32 missing
IssueCount
missing32 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

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
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
No print-specific styles detected
When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.
Print Stylesheet No Print Styles
Print stylesheet Not found Inline @media print Not detected
F
Navigation UX
Action
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
4 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 4 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Homepage link present on 404 page
404 Page Quality Custom 404 Page
Status Code HTTP 404 Page Title 404: Page Not Found Custom Styling Navigation Homepage Link Search Form
B
Favicon & Branding
8 icon(s) detected
REVIEW
8 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
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
Dark-specific theme-color detected
A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.
Info::
prefers-color-scheme CSS detected in inline styles
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark Mode Dark Mode Supported
color-scheme meta Not set Dark theme-color #ffffff CSS indicators Detected

Detection limited to meta tags and inline styles.

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

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

11 pass 9 fail WCAG AA
h2 DEV Community
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · above the fold
h2 DEV Community is a community of 3,828,72…
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · above the fold
a Log in
3.44:1
#000000
on
#626262
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
a Create account
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · above the fold
p We're a place where coders share, stay u…
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · above the fold
a Create account
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · above the fold
a Log in
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · above the fold
a Home
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · above the fold
a DEV++
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · above the fold

1 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 Posts21.00:13.0:1
#000000
#FFFFFF
Pass
h2 DEV Community1.00:13.0:1
#000000
#000000
Fail
h2 DEV Community is a c…1.00:13.0:1
#000000
#000000
Fail
h2 Other21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Easiest way to help …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Announcing the First…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Popular Tags21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Jess Lee for The DEV…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Featured Product Lau…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Challenges 🤗21.00:13.0:1
#000000
#FFFFFF
Pass
title DEV Community21.00:14.5:1
#000000
#FFFFFF
Pass
a Skip to content21.00:14.5:1
#000000
#FFFFFF
Pass
a Powered by Algolia19.43:14.5:1
#000000
#F6F6F6
Pass
a Log in3.44:14.5:1
#000000
#626262
Fail
a Create account1.00:14.5:1
#000000
#000000
Fail
p We're a place where …1.00:14.5:1
#000000
#000000
Fail
a Create account1.00:14.5:1
#000000
#000000
Fail
a Log in1.00:14.5:1
#000000
#000000
Fail
a Home1.00:14.5:1
#000000
#000000
Fail
a DEV++1.00:14.5: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.

B
Lighthouse Accessibility Audits
Score 80/100 — 6 failing, 21 passed
REVIEW
80

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.

ARIA

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.crayons-story > div.crayons-story__body > div.crayons-story__top > button#sponsorship-close-trigger-238627 div.crayons-story > div.crayons-story__body > div.crayons-story__top > button#sponsorship-close-trigger-238627

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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
Learn at your own pace, and earn a badge upon completion. Easy! div.crayons-story__body > div.crayons-story__indention-billboard > div.text-styles > h4

These are opportunities to improve keyboard navigation in your application.

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.multiple_reactions_aggregate > span.multiple_reactions_icons_container > span.crayons_icon_container > img div.multiple_reactions_aggregate > span.multiple_reactions_icons_container > span.crayons_icon_container > img
div.multiple_reactions_aggregate > span.multiple_reactions_icons_container > span.crayons_icon_container > img div.multiple_reactions_aggregate > span.multiple_reactions_icons_container > span.crayons_icon_container > img
div.multiple_reactions_aggregate > span.multiple_reactions_icons_container > span.crayons_icon_container > img div.multiple_reactions_aggregate > span.multiple_reactions_icons_container > span.crayons_icon_container > img
div.multiple_reactions_aggregate > span.multiple_reactions_icons_container > span.crayons_icon_container > img div.multiple_reactions_aggregate > span.multiple_reactions_icons_container > span.crayons_icon_container > img
div.multiple_reactions_aggregate > span.multiple_reactions_icons_container > span.crayons_icon_container > img div.multiple_reactions_aggregate > span.multiple_reactions_icons_container > span.crayons_icon_container > img
div.multiple_reactions_aggregate > span.multiple_reactions_icons_container > span.crayons_icon_container > img div.multiple_reactions_aggregate > span.multiple_reactions_icons_container > span.crayons_icon_container > img
div.multiple_reactions_aggregate > span.multiple_reactions_icons_container > span.crayons_icon_container > img div.multiple_reactions_aggregate > span.multiple_reactions_icons_container > span.crayons_icon_container > img
div.multiple_reactions_aggregate > span.multiple_reactions_icons_container > span.crayons_icon_container > img div.multiple_reactions_aggregate > span.multiple_reactions_icons_container > span.crayons_icon_container > img
div.multiple_reactions_aggregate > span.multiple_reactions_icons_container > span.crayons_icon_container > img div.multiple_reactions_aggregate > span.multiple_reactions_icons_container > span.crayons_icon_container > img
div.multiple_reactions_aggregate > span.multiple_reactions_icons_container > span.crayons_icon_container > img div.multiple_reactions_aggregate > span.multiple_reactions_icons_container > span.crayons_icon_container > img
div.multiple_reactions_aggregate > span.multiple_reactions_icons_container > span.crayons_icon_container > img div.multiple_reactions_aggregate > span.multiple_reactions_icons_container > span.crayons_icon_container > img
div.multiple_reactions_aggregate > span.multiple_reactions_icons_container > span.crayons_icon_container > img div.multiple_reactions_aggregate > span.multiple_reactions_icons_container > span.crayons_icon_container > img
div.multiple_reactions_aggregate > span.multiple_reactions_icons_container > span.crayons_icon_container > img div.multiple_reactions_aggregate > span.multiple_reactions_icons_container > span.crayons_icon_container > img
div.multiple_reactions_aggregate > span.multiple_reactions_icons_container > span.crayons_icon_container > img div.multiple_reactions_aggregate > span.multiple_reactions_icons_container > span.crayons_icon_container > img
div.multiple_reactions_aggregate > span.multiple_reactions_icons_container > span.crayons_icon_container > img div.multiple_reactions_aggregate > span.multiple_reactions_icons_container > span.crayons_icon_container > img
div.multiple_reactions_aggregate > span.multiple_reactions_icons_container > span.crayons_icon_container > img div.multiple_reactions_aggregate > span.multiple_reactions_icons_container > span.crayons_icon_container > img
div.multiple_reactions_aggregate > span.multiple_reactions_icons_container > span.crayons_icon_container > img div.multiple_reactions_aggregate > span.multiple_reactions_icons_container > span.crayons_icon_container > img
div.multiple_reactions_aggregate > span.multiple_reactions_icons_container > span.crayons_icon_container > img div.multiple_reactions_aggregate > span.multiple_reactions_icons_container > span.crayons_icon_container > img
div.multiple_reactions_aggregate > span.multiple_reactions_icons_container > span.crayons_icon_container > img div.multiple_reactions_aggregate > span.multiple_reactions_icons_container > span.crayons_icon_container > img
div.multiple_reactions_aggregate > span.multiple_reactions_icons_container > span.crayons_icon_container > img div.multiple_reactions_aggregate > span.multiple_reactions_icons_container > span.crayons_icon_container > img
div.multiple_reactions_aggregate > span.multiple_reactions_icons_container > span.crayons_icon_container > img div.multiple_reactions_aggregate > span.multiple_reactions_icons_container > span.crayons_icon_container > img
div.multiple_reactions_aggregate > span.multiple_reactions_icons_container > span.crayons_icon_container > img div.multiple_reactions_aggregate > span.multiple_reactions_icons_container > span.crayons_icon_container > img
div.multiple_reactions_aggregate > span.multiple_reactions_icons_container > span.crayons_icon_container > img div.multiple_reactions_aggregate > span.multiple_reactions_icons_container > span.crayons_icon_container > 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.crayons-story__indention-billboard > div.text-styles > h4 > a div.crayons-story__indention-billboard > div.text-styles > h4 > 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.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
The DEV Team logo div.crayons-story__top > div.crayons-story__meta > div.crayons-story__author-pic > a.crayons-logo
Jess Lee div.crayons-story__meta > div > div > a.crayons-story__secondary
Apr 1 div.crayons-story__top > div.crayons-story__meta > div > a.crayons-story__tertiary
Jess Lee div.crayons-story__meta > div > div > a.crayons-story__secondary
Mar 31 div.crayons-story__top > div.crayons-story__meta > div > a.crayons-story__tertiary
Apr 1 div.crayons-story__top > div.crayons-story__meta > div > a.crayons-story__tertiary
Apr 2 div.crayons-story__top > div.crayons-story__meta > div > a.crayons-story__tertiary
Johnson div.crayons-story__meta > div > div > a.crayons-story__secondary
Apr 4 div.crayons-story__top > div.crayons-story__meta > div > a.crayons-story__tertiary
Apr 4 div.crayons-story__top > div.crayons-story__meta > div > a.crayons-story__tertiary
fmerian div.crayons-story__meta > div > div > a.crayons-story__secondary
Apr 3 div.crayons-story__top > div.crayons-story__meta > div > a.crayons-story__tertiary
Apr 1 div.crayons-story__top > div.crayons-story__meta > div > a.crayons-story__tertiary
‍경규찬 div.crayons-story__meta > div > div > a.crayons-story__secondary
Apr 4 div.crayons-story__top > div.crayons-story__meta > div > a.crayons-story__tertiary
Apr 3 div.crayons-story__top > div.crayons-story__meta > div > a.crayons-story__tertiary
Google Developer Experts logo div.crayons-story__top > div.crayons-story__meta > div.crayons-story__author-pic > a.crayons-logo
xbill div.crayons-story__meta > div > div > a.crayons-story__secondary
Apr 3 div.crayons-story__top > div.crayons-story__meta > div > a.crayons-story__tertiary
Google Developer Experts logo div.crayons-story__top > div.crayons-story__meta > div.crayons-story__author-pic > a.crayons-logo
xbill div.crayons-story__meta > div > div > a.crayons-story__secondary
Apr 3 div.crayons-story__top > div.crayons-story__meta > div > a.crayons-story__tertiary
M Media div.crayons-story__meta > div > div > a.crayons-story__secondary
Apr 3 div.crayons-story__top > div.crayons-story__meta > div > a.crayons-story__tertiary
WiScale logo div.crayons-story__top > div.crayons-story__meta > div.crayons-story__author-pic > a.crayons-logo
Julien L div.crayons-story__meta > div > div > a.crayons-story__secondary
Apr 4 div.crayons-story__top > div.crayons-story__meta > div > a.crayons-story__tertiary
Apr 3 div.crayons-story__top > div.crayons-story__meta > div > a.crayons-story__tertiary
Apr 3 div.crayons-story__top > div.crayons-story__meta > div > a.crayons-story__tertiary
Apr 4 div.crayons-story__top > div.crayons-story__meta > div > a.crayons-story__tertiary
vitoriazzp div.crayons-story__meta > div > div > a.crayons-story__secondary
Apr 3 div.crayons-story__top > div.crayons-story__meta > div > a.crayons-story__tertiary

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
288 div.crayons-story__indention > div.crayons-story__bottom > div.crayons-story__details > a.crayons-btn
72 div.crayons-story__indention > div.crayons-story__bottom > div.crayons-story__details > a.crayons-btn
90 div.crayons-story__indention > div.crayons-story__bottom > div.crayons-story__details > a.crayons-btn
25 div.crayons-story__indention > div.crayons-story__bottom > div.crayons-story__details > a.crayons-btn
160 div.crayons-story__indention > div.crayons-story__bottom > div.crayons-story__details > a.crayons-btn
52 div.crayons-story__indention > div.crayons-story__bottom > div.crayons-story__details > a.crayons-btn
119 div.crayons-story__indention > div.crayons-story__bottom > div.crayons-story__details > a.crayons-btn
56 div.crayons-story__indention > div.crayons-story__bottom > div.crayons-story__details > a.crayons-btn
1 div.crayons-story__indention > div.crayons-story__bottom > div.crayons-story__details > a.crayons-btn
2 div.crayons-story__indention > div.crayons-story__bottom > div.crayons-story__details > a.crayons-btn
1 div.crayons-story__indention > div.crayons-story__bottom > div.crayons-story__details > a.crayons-btn
1 div.crayons-story__indention > div.crayons-story__bottom > div.crayons-story__details > a.crayons-btn
81 div.crayons-story__indention > div.crayons-story__bottom > div.crayons-story__details > a.crayons-btn
53 div.crayons-story__indention > div.crayons-story__bottom > div.crayons-story__details > a.crayons-btn
3 div.crayons-story__indention > div.crayons-story__bottom > div.crayons-story__details > a.crayons-btn
1 div.crayons-story__indention > div.crayons-story__bottom > div.crayons-story__details > a.crayons-btn
2 div.crayons-story__indention > div.crayons-story__bottom > div.crayons-story__details > a.crayons-btn
30 div.crayons-story__indention > div.crayons-story__bottom > div.crayons-story__details > a.crayons-btn
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 are valid and not misspelled
Buttons have an accessible name
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
ARIA attributes are used as specified for the element's role
`[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
Skip links are focusable.
Document has a main landmark.
Deprecated ARIA roles were not used
Identical links have the same purpose.
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
Elements with `role="dialog"` or `role="alertdialog"` 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
`<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.
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.
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+
Landmark Structure
14 landmarks
PASS
14 landmarks
Info::
<main> landmark present
Info::
4 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "DEV Community" MAIN ASIDE "Primary sidebar" CONTENTINFO footer
A
Heading Hierarchy
32 headings, 1 skip(s)
PASS
32 headings, 1 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.
  • H2 DEV Community
  • H2 DEV Community is a community of 3,828,726 amazing developers
  • H2 Other
  • H3 Popular Tags
  • H2 Easiest way to help the DEV community feel more like a community?
  • H1 Posts
  • H4 Learn at your own pace, and earn a badge upon completion. Easy! skipped
  • H2 Announcing the First DEV Education Track: "Build Apps with Google AI Studio"
  • H3 Jess Lee for The DEV Team ・ Jul 2
  • H2 Join our April Fools Challenge for a chance at TEA-RRIFIC prizes!!!
  • H2 A Year of Change and Persistence
  • H2 The Great Claude Code Leak of 2026: Accident, Incompetence, or the Best PR Stunt in AI History?
  • H2 9 Things You’re Overengineering (The Browser Already Solved Them)
  • H2 Debugging Filestash 'Invalid Account': How Response Time Led Me to a Swapped Config Field
  • H2 Memory Requires Loss: What 9 Days of Dying Taught Me About Identity
  • H2 Who's hiring — April 2026
  • H2 Trading My Body for Logic: The Physical Decay We Ignore
  • H2 I Read a 1999 Book About How Geniuses Think. Then I Built an AI Framework With a Real Nervous System.
  • H2 Depresso-Tron 418: I Built a Bureaucratic Coffee Machine That Cannot Make Coffee
  • H2 Deploying ADK Agents on Azure ACA (Azure Container Apps)
  • H2 Deploying ADK Agents on Azure ACI
  • H2 I built a BIP-39 seed phrase scanner that reads raw disk sectors - and just open-sourced the engine
  • H2 I built a database in France because the Cloud Act makes EU data sovereignty impossible
  • H2 I Built Boreal UI — An Accessibility-First Component Library for React and Next.js
  • H2 Scraped 300 pages successfully. Site updated robots.txt at page 187 and blocked me.
  • H2 Same Model, Different Environment, Different Results
  • H2 De front-end para UX, e de volta ao código: o que significa ser Design Engineer em 2026
  • H3 Featured Product Launch 🚀
  • H3 Challenges 🤗
  • H4 Have a great week ❤️
  • H3 #discuss
  • H4 trending guides/resources

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
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="text" name="q" id="search-input">
1 controls
0 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
#search-inputtext(Search...)placeholder only

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

<input type="text" name="q" id="search-input">

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