Skip to content
https://labiennale.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
52
GRADE
F
FIX
7
REVIEW
4
PASS
2
INFO
0
Checks
13
2 PASS 4 REVIEW 7 FIX
D
Landmark Structure
Action
No landmarks
FIX
No landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Warning::
No <nav> landmark found
Info::
No banner (header) landmark
Info::
No contentinfo (footer) landmark
Warning::
Skip navigation link is missing (WCAG 2.4.1)
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

No landmarks detected

Screen reader users have no way to navigate by region.

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

Why this matters

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

Learn more ▾

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

Source: WAI-ARIA / WCAG 2.4.1

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

Why this matters

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

Learn more ▾

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

Source: WCAG 2.1 SC 2.4.1

F
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::
16 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

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.
D
Lighthouse Accessibility Audits
Action
Score 66/100 — 9 failing, 23 passed
FIX
66

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

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
1 div.lb-full-page-head-section > div.container > ul.slick-dots > li#slick-slide00
1 div.lb-news-carousel-wrap > div.container > ul.slick-dots > li#slick-slide20
1 div.row > section.lb-album-carousel > ul.slick-dots > li#slick-slide30
1 div.view > section.lb-channel-carousel > ul.slick-dots > li#slick-slide10

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
1 2 3 4 5 6 7 body.html > div.lb-full-page-head-section > div.container > ul.slick-dots
1 2 3 4 5 6 7 8 9 div.view > div.lb-news-carousel-wrap > div.container > ul.slick-dots
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 div.container-fluid > div.row > section.lb-album-carousel > ul.slick-dots
1 2 3 4 5 div.row > div.view > section.lb-channel-carousel > ul.slick-dots

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
1 div.lb-full-page-head-section > div.container > ul.slick-dots > li#slick-slide00
1 div.lb-news-carousel-wrap > div.container > ul.slick-dots > li#slick-slide20
1 div.row > section.lb-album-carousel > ul.slick-dots > li#slick-slide30
1 div.view > section.lb-channel-carousel > ul.slick-dots > li#slick-slide10

When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
PODCAST LA BIENNALE ON AIR ASCOLTA 9.05 - 22.11.2026 BIENNALE ARTE 2026 ACQUI… div.lb-full-page-head-section > div.lb-full-page-carousel-wrap > div.slick-list > div.slick-track
  CINEMA 3 APRILE 2026 BIENNALE COLLEGE CINEMA 2026/2027: ANCORA DIECI GIORNI P… div.lb-news-carousel-wrap > div.lb-news-carousel > div.slick-list > div.slick-track
BIENNALE DANZA 2025 Myth Makers BIENNALE MUSICA 2025 La Stella Dentro BIENN… div.row > section.lb-album-carousel > div.slick-list > div.slick-track
TEATRO 14 APRILE 2026 Biennale Teatro 2026 - Jacopo Giacomoni (trailer) TEATR… div.view > section.lb-channel-carousel > div.slick-list > div.slick-track

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
a.lb-entry-link > div.lb-entry-wrapper > div.lb-cta-wrap > button.lb-cta a.lb-entry-link > div.lb-entry-wrapper > div.lb-cta-wrap > button.lb-cta
a.lb-iniziative-content > div.lb-media-wrap > div.lb-media-content > button.lb-cta a.lb-iniziative-content > div.lb-media-wrap > div.lb-media-content > button.lb-cta
a.lb-iniziative-content > div.lb-media-wrap > div.lb-media-content > button.lb-cta a.lb-iniziative-content > div.lb-media-wrap > div.lb-media-content > button.lb-cta
a.lb-entry-link > div.lb-entry-wrapper > div.lb-cta-wrap > button.lb-cta a.lb-entry-link > div.lb-entry-wrapper > div.lb-cta-wrap > button.lb-cta
a.lb-entry-link > div.lb-entry-wrapper > div.lb-cta-wrap > button.lb-cta a.lb-entry-link > div.lb-entry-wrapper > div.lb-cta-wrap > button.lb-cta
a.lb-entry-link > div.lb-entry-wrapper > div.lb-cta-wrap > button.lb-cta a.lb-entry-link > div.lb-entry-wrapper > div.lb-cta-wrap > button.lb-cta

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.lb-entry-wrapper > div.lb-media-wrapper > div.lb-square > img.lb-media div.lb-entry-wrapper > div.lb-media-wrapper > div.lb-square > img.lb-media
article.lb-agenda-item > div.lb-media-wrapper > div.lb-square > img.lb-media article.lb-agenda-item > div.lb-media-wrapper > div.lb-square > img.lb-media
article.lb-agenda-item > div.lb-media-wrapper > div.lb-square > img.lb-media article.lb-agenda-item > div.lb-media-wrapper > div.lb-square > img.lb-media
div.row > div.col-sm-7 > div.lb-square > img.lazy div.row > div.col-sm-7 > div.lb-square > img.lazy
div.lb-entry-wrapper > div.lb-media-wrapper > div.lb-square > img.lazy div.lb-entry-wrapper > div.lb-media-wrapper > div.lb-square > img.lazy
div.lb-entry-wrapper > div.lb-media-wrapper > div.lb-square > img.lazy div.lb-entry-wrapper > div.lb-media-wrapper > div.lb-square > img.lazy
div.lb-entry-wrapper > div.lb-media-wrapper > div.lb-square > img.lazy div.lb-entry-wrapper > div.lb-media-wrapper > div.lb-square > img.lazy

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.html > div.lb-nav-head-wrap > a body.html > div.lb-nav-head-wrap > 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
CINEMA a.lb-entry-link > div.lb-entry-wrapper > div.lb-meta > div.lb-category
TEATRO 16 APRILE 2026 div.content-align-wrap > div.content-align-bottom > div.lb-channel-item-meta > div.lb-title
TUTTI I CONTATTI section#block-bean-box-contatti > div.lb-content > p > a.lb-cta-arrow-2
UFFICI STAMPA section#block-bean-box-press > div.lb-content > p > a.lb-cta-arrow-2
ISCRIVITI section#block-bean-box-newsletter > div.lb-content > p > a.lb-cta-arrow-2

These are opportunities to improve the legibility of your content.

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
1 section.lb-album-carousel > ul.slick-dots > li#slick-slide30 > button

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>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]`s are contained by their required parent element
●`[role]` values are valid
●`[aria-*]` attributes are valid and not misspelled
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●ARIA attributes are used as specified for the element's role
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●ARIA toggle fields have accessible names
●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
●`[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
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with the `role=text` attribute do not have focusable descendents.
○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.
○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.
○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.
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 Pagina non trovata | La Biennale di Venezia ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
B
Favicon & Branding
9 icon(s) detected
REVIEW
9 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
C
Web Manifest
Action
Valid manifest
REVIEW
Valid manifest
Warning::
No name or short_name
Add a name field to identify the app.
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name ✗192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓
Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 2 fail WCAG AA
REVIEW

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

18 pass 2 fail WCAG AA 1 pass AA only
h2 Biennale Teatro 2026
2.61:1
#000000
on
#505051
needs 3.0:1 (large text)
24px · mid-page
h2 Biennale Danza 2026
2.02:1
#000000
on
#3F4041
needs 3.0:1 (large text)
24px · mid-page
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Homepage10.40:13.0:1
#000000
#B8B6B6
Pass
h2 La Biennale on Air7.66:13.0:1
#000000
#9B9CA0
Pass
h2 Biennale Arte 20263.19:13.0:1
#000000
#5D5D5E
Pass
h2 Biennale Teatro 20262.61:13.0:1
#000000
#505051
Fail
h2 Biennale Danza 20262.02:13.0:1
#000000
#3F4041
Fail
h2 Biennale Cinema 202613.62:13.0:1
#000000
#D0D0D0
Pass
h2 Biennale Musica 202617.46:13.0:1
#000000
#EAEAEA
Pass
h2 Acquista online18.10:13.0:1
#000000
#EEEEEE
Pass
h2 La Biennale on Air18.10:13.0:1
#000000
#EEEEEE
Pass
h2 Biennale Arte 202618.10:13.0:1
#000000
#EEEEEE
Pass
h2 News18.10:13.0:1
#000000
#EEEEEE
Pass
h2 Sfoglia l’album18.10:13.0:1
#000000
#EEEEEE
Pass
h2 Agenda18.10:13.0:1
#000000
#EEEEEE
Pass
h2 Biennale Storia18.10:13.0:1
#000000
#EEEEEE
Pass
h2 Focus On18.10:13.0:1
#000000
#EEEEEE
Pass
h2 Biennale Channel18.10:13.0:1
#000000
#EEEEEE
Pass
h2 Cosa Accade18.10:13.0:1
#000000
#EEEEEE
Pass
h2 Settori18.10:13.0:1
#000000
#EEEEEE
Pass
h2 La Biennale di Venez…18.10:13.0:1
#000000
#EEEEEE
Pass
h2 La Biennale di Venez…18.10:13.0:1
#000000
#EEEEEE
Pass

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

A+
Heading Hierarchy
31 headings
PASS
31 headings
Info::
Single H1 present
  • H1 Homepage
  • H2 La Biennale on Air
  • H2 Biennale Arte 2026
  • H2 Biennale Teatro 2026
  • H2 Biennale Danza 2026
  • H2 Biennale Cinema 2026
  • H2 Biennale Musica 2026
  • H2 Acquista online
  • H2 La Biennale on Air
  • H2 Biennale Arte 2026
  • H2 News
  • H2 Sfoglia l’album
  • H2 Agenda
  • H3 Biennale Educational
  • H3 Acquista online
  • H2 Biennale Storia
  • H3 2009
  • H4 György Kurtág  Leone d’oro alla carriera 27 settembre 2009, Teatro alle Tese
  • H2 Focus On
  • H3 Storia della Biennale di Venezia
  • H3 La Biennale on Air
  • H3 Biennale College 2026
  • H2 Biennale Channel
  • H2 Cosa Accade
  • H2 Settori
  • H2 La Biennale di Venezia
  • H2 La Biennale di Venezia
  • H2 Contatti
  • H2 Press
  • H2 Newsletter
  • H2 Seguici su
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="s">
Info::
1 control(s) properly labeled
2 controls
1 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
#edit-qstextDigita cosa stai cercandofor/id
stext(Cerca)placeholder only

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

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

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