Skip to content
https://archdaily.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
65
GRADE
D
FIX
3
REVIEW
8
PASS
2
INFO
0
Checks
13
2 PASS 8 REVIEW 3 FIX
D
Landmark Structure
Action
7 landmarks
FIX
7 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
4 <nav> landmark(s) found
Warning::
4 of 4 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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 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

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

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

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::
4 navigation landmark(s) detected
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 4 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Heading Hierarchy
28 headings, 1 skip(s)
REVIEW
28 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H1 The world's most visited architecture platform
  • H3 By using ArchDaily, you agree to our Terms of Use, Privacy Policy and Cookie Policy. skipped
  • H3 By using ArchDaily, you agree to our Terms of Use, Privacy Policy and Cookie Policy.
  • H4 (empty)
  • H3 Featured Qing Shui Meditation Retreat Center / RESP Studio
  • H3 Featured The German Pavilion at the Kerala Literature Festival 2026 / The Purple Ink Studio
  • H3 Featured The House of Time / Natura Futura
  • H3 Editor's Choice Choreographing Lagos: Dele Adeyemo on Dance, Cosmology, and Spatial Practices
  • H3 GS House / Studio FP02
  • H3 Newhouse Building Replacement / Miller Hull Partnership
  • H3 Casa Lèvanzo / Margine
  • H3 Light Structures, Heavy Footprints? The Environmental Paradox of Lightweight Materials
  • H3 El Grove Family Home / Olson Kundig
  • H3 Sharjah Architecture Triennial Presents "A Journey into Architecture Archives" Focused on Baghdad, Damascus, and Tunis
  • H3 Artistic Office of a Notary / Dolgopiatova Interior Design
  • H3 Centre Pompidou Expands to Seoul with the New Hanwha Center Designed by Wilmotte & Associés
  • H3 Why Do We Want to Float? The Psychology of Lightness in Architecture
  • H3 Goethe-Institut Sénégal / Kéré Architecture
  • H3 Jingu Studio / YNAS
  • H3 Nanhai Dali "Yanbu 1432" Yanbu Grain Processing Plant & Distillery Renovation / Atelier cnS
  • H3 House & Office SH / 1-1 Architects
  • H3 Tietê178 / Gabriel Kogan
  • H3 Limberlost Place / Moriyama Teshima Architects
  • H3 Trim House / Robert Konieczny + KWK Promes
  • H3 Jaali, Mashrabiya, Cobogó: The Lightest Skins in Architecture
  • H3 House of Light Oaxaca / T804 Arquitectura e Interiorismo Estratégico
  • H3 You've started following your first account!
  • H3 Did you know?

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

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

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
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title ArchDaily | Broadcasting Architecture Worldwide, page ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
B
Favicon & Branding
16 icon(s) detected
REVIEW
16 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 Present
✓ Multiple Sizes Present
B
Web Manifest
PWA-ready
REVIEW
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: New notification
Info::
192x192 icon present
Info::
Display mode: standalone
PWA Install Criteria ✓ Installable
Name New notification ✓192×192 icon ✓512×512 icon ✗Start URL / ✓Display Mode standalone ✓
Name New notification Display Mode standalone Icons 1 icon(s)
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 archdaily ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

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

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

12 pass 8 fail WCAG AA
h3 By using ArchDaily, you agree to our
1.45:1
#000000
on
#29292B
needs 3.0:1 (large text)
19px · bottom of viewport
h3 and
1.45:1
#000000
on
#29292B
needs 3.0:1 (large text)
19px · bottom of viewport
h3 By using ArchDaily, you agree to our
1.45:1
#000000
on
#29292B
needs 3.0:1 (large text)
19px · bottom of viewport
h3 and
1.45:1
#000000
on
#29292B
needs 3.0:1 (large text)
19px · bottom of viewport
h3 You've started following your first acco…
1.45:1
#000000
on
#29292B
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Did you know?
1.45:1
#000000
on
#29292B
needs 3.0:1 (large text)
19px · bottom of viewport
title ArchDaily | Broadcasting Architecture Wo…
1.45:1
#000000
on
#29292B
needs 4.5:1 (normal text)
16px · top of page (header area)
div DATA PROTECTION IS IMPORTANT TO US
3.97:1
#000000
on
#6C6C65
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient

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
h3 By using ArchDaily, …1.45:13.0:1
#000000
#29292B
Fail
h3 and1.45:13.0:1
#000000
#29292B
Fail
h3 By using ArchDaily, …1.45:13.0:1
#000000
#29292B
Fail
h3 and1.45:13.0:1
#000000
#29292B
Fail
h3 You've started follo…1.45:13.0:1
#000000
#29292B
Fail
h3 Did you know?1.45:13.0:1
#000000
#29292B
Fail
title ArchDaily | Broadcas…1.45:14.5:1
#000000
#29292B
Fail
div DATA PROTECTION IS I…3.97:14.5:1
#000000
#6C6C65
Fail
span On our websites and …9.11:14.5:1
#000000
#ABAC9C
Pass
span The data collected w…14.50:14.5:1
#000000
#DAD7C4
Pass
div Store and/or access …13.46:14.5:1
#000000
#D6CEC1
Pass
div Ensure security, pre…15.96:14.5:1
#000000
#E2E1D5
Pass
div Deliver and present …11.33:14.5:1
#000000
#BDBFBA
Pass
div Save and communicate…14.02:14.5:1
#000000
#D4D3CF
Pass
div Personalised adverti…17.17:14.5:1
#000000
#EBE8E2
Pass
span Save & Exit11.32:14.5:1
#000000
#C0BEBB
Pass
span Accept all15.85:14.5:1
#000000
#E0E0DB
Pass
a Customize your choic…12.18:14.5:1
#000000
#C2C6C5
Pass
a Privacy policy15.84:14.5:1
#000000
#DEE0E0
Pass
a Terms of Use16.18:14.5:1
#000000
#DDE3E4
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.

C
Lighthouse Accessibility Audits
Action
Score 74/100 — 8 failing, 23 passed
REVIEW
74

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

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
body#js-home > div.tp-modal > div.tp-iframe-wrapper body#js-home > div.tp-modal > div.tp-iframe-wrapper

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.

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
div.auth-container > button.close-button div.auth-container > button.close-button
div.auth-container > button.close-button div.auth-container > button.close-button
body#js-home > div.tp-modal > div.tp-iframe-wrapper > button.tp-close body#js-home > div.tp-modal > div.tp-iframe-wrapper > button.tp-close

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body#js-home > div.tp-modal > div.tp-iframe-wrapper > iframe#offer_7d3f992b914609e59ba7-0 body#js-home > div.tp-modal > div.tp-iframe-wrapper > iframe#offer_7d3f992b914609e59ba7-0

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.footer-content > div.repel > div.cluster > a div.footer-content > div.repel > div.cluster > a
div.footer-content > div.repel > div.cluster > a div.footer-content > div.repel > div.cluster > a
div.footer-content > div.repel > div.cluster > a div.footer-content > div.repel > div.cluster > a
div.footer-content > div.repel > div.cluster > a div.footer-content > div.repel > div.cluster > a
div.footer-content > div.repel > div.cluster > a div.footer-content > div.repel > div.cluster > 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.

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
div.afd-mobile-search-form__container > form#afd-search-actions-mobile > div.afd-nav__search__searchfield > input.afd-nav__search__input div.afd-mobile-search-form__container > form#afd-search-actions-mobile > div.afd-nav__search__searchfield > input.afd-nav__search__input

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Terms of Use div.afd-container-main > div.kth-toast__body > h3.kth-toast__call > a
Privacy Policy div.afd-container-main > div.kth-toast__body > h3.kth-toast__call > a
Cookie Policy div.afd-container-main > div.kth-toast__body > h3.kth-toast__call > a
BRAZIL div.afd-specs > div.afd-specs__header > div.afd-specs__header-location > a

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
By using ArchDaily, you agree to our Terms of Use, Privacy Policy and Cookie Po… div.kth-toast > div.afd-container-main > div.kth-toast__body > h3.kth-toast__call

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-*]` 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
●Image elements have `[alt]` attributes
●Form elements have associated labels
●`button`, `link`, and `menuitem` elements have accessible names
●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
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●`[lang]` attributes have a valid value
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○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 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>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○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.
A
Alt Text Quality
All 111 images OK
PASS
All 111 images OK
Info::
11 image(s) with alt text over 125 characters
Info::
2 decorative image(s) correctly marked
Info::
98 image(s) with good alt text
111 images 98 good alt text 2 decorative
IssueCount
too long11 image(s)
A
Form Accessibility
1 of 2 controls have issues
PASS
1 of 2 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="text">
Info::
1 control(s) properly labeled
2 controls
1 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
texttextSearcharia-label
texttext(Search Products)placeholder only

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

<input type="text" name="text">

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