Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

1 PASS 5 REVIEW 7 FIX

Link & Button Quality

Action

15 issue(s) across 63 links and 15 buttons

FIX

15 issue(s) across 63 links and 15 buttons

10 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: #popup:myform; #popup:myform; #popup:myform; #popup:myform; a (#712 on page); #popup:myform; #popup:myform; a (#867 on page); a (#1033 on page); a (#1052 on page)

2 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: #popup:myform ("Read more"); #popup:myform ("Read more")

10 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://maps.app.goo.gl/X1qicT6qjsdPm4ci9; https://www.instagram.com/icetraycsc/; https://www.facebook.com/profile.php?id=61576620540150&rdid=XuM9zWBBCJkEXWUO&…; https://maps.app.goo.gl/X1qicT6qjsdPm4ci9; https://www.instagram.com/icetraycsc/; https://www.facebook.com/profile.php?id=61576620540150&rdid=XuM9zWBBCJkEXWUO&…; https://maps.app.goo.gl/AnwvaHxLYPzWG3ZX8; https://www.facebook.com/share/1Ah8rQmy5Q/; https://www.instagram.com/icetraycsc/; https://www.tiktok.com/@ice.tray.weed.clu?_t=ZN-8wyfC7VeK62&_r=1

3 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.t824__btn (#1180 on page); button.t824__mobile-close (#1189 on page); button.t824__popup-close (#1202 on page)

41 link(s) with descriptive text

63 links

10 empty

2 generic text

10 new tab

3 empty buttons

Element	Text	Issue	Suggested Fix
https://maps.app.goo.gl/X1qicT6qjsdPm4ci…	Location	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/icetraycsc/	instagram	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/profile.php?id=…	facebook	new tab	Add '(opens in new tab)' to text
https://maps.app.goo.gl/X1qicT6qjsdPm4ci…	Location	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/icetraycsc/	instagram	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/profile.php?id=…	facebook	new tab	Add '(opens in new tab)' to text
#popup:myform	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: #Popup:Myform
#popup:myform	(empty)	empty	Add link text or aria-label
#popup:myform	(empty)	empty	Add link text or aria-label
#popup:myform	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: #Popup:Myform
#popup:myform	(empty)	empty	Add link text or aria-label
#popup:myform	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
#popup:myform	(empty)	empty	Add link text or aria-label
#popup:myform	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
https://maps.app.goo.gl/AnwvaHxLYPzWG3ZX…	Carrer d'Aragó, 209, L'Eixamp…	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/share/1Ah8rQmy5…	facebook	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/icetraycsc/	instagram	new tab	Add '(opens in new tab)' to text
https://www.tiktok.com/@ice.tray.weed.cl…	tiktok	new tab	Add '(opens in new tab)' to text
https://tilda.cc/	Made on Tilda	img no alt	Add alt attribute to the image
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

53 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

#popup:myform; #popup:myform; #popup:myform; #popup:myform; a (#712 on page); #popup:myform; #popup:myform; a (#867 on page); a (#1033 on page); a (#1052 on page)

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Generic link text like 'click here' doesn't describe the destination.

#popup:myform ("Read more"); #popup:myform ("Read more")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

Add '(opens in new tab)' to link text or aria-label.

https://maps.app.goo.gl/X1qicT6qjsdPm4ci9; https://www.instagram.com/icetraycsc/; https://www.facebook.com/profile.php?id=61576620540150&rdid=XuM9zWBBCJkEXWUO&…; https://maps.app.goo.gl/X1qicT6qjsdPm4ci9; https://www.instagram.com/icetraycsc/; https://www.facebook.com/profile.php?id=61576620540150&rdid=XuM9zWBBCJkEXWUO&…; https://maps.app.goo.gl/AnwvaHxLYPzWG3ZX8; https://www.facebook.com/share/1Ah8rQmy5Q/; https://www.instagram.com/icetraycsc/; https://www.tiktok.com/@ice.tray.weed.clu?_t=ZN-8wyfC7VeK62&_r=1

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

Icon-only buttons need an aria-label so screen readers can announce them.

button.t824__btn (#1180 on page); button.t824__mobile-close (#1189 on page); button.t824__popup-close (#1202 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

404 Error Page

Action

HTTP 404, bare page

FIX

HTTP 404, bare page

Correct 404 status code returned

Got: HTTP 404

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 ✓Page Title Tilda ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

favicon.ico present at site root

HTML icon links detected

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

Web Manifest

Action

Not found

FIX

Not found

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.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Landmark Structure

Action

4 landmarks

REVIEW

4 landmarks

No <main> landmark found

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

2 <nav> landmark(s) found

2 of 2 <nav> elements are unlabeled

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

Skip navigation link present

Page Structure — as a screen reader sees it

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

Heading Hierarchy

No headings

REVIEW

No headings

No headings found

Headings (H1-H6) create the document outline for screen reader navigation.

No headings found

Headings create the document outline for screen reader navigation.

Headings (H1-H6) create the document outline for screen reader navigation.

Why this matters

A page with zero headings is unnavigable by assistive tech and reads as one undifferentiated wall of text.

Learn more ▾

Screen reader users navigate by jumping between H1-H6 elements. A page with no headings has no skip targets — users have to read every word linearly. Adding a heading hierarchy (one H1, then H2 sections, optional H3 subsections) makes the page skimmable for both AT and human readers.

Source: WCAG 1.3.1 / W3C WAI

Form Accessibility

Action

7 of 7 controls have issues

REVIEW

7 of 7 controls have issues

1 control(s) without accessible label

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

Got: <textarea>

6 control(s) rely on placeholder only

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

Got: <input type="email" name="Email" id="input_4228215262380">; <input type="text" name="Name" id="input_4229215262381">; <input type="tel" name="Phone" id="input_4229215262382">; <input type="email" name="Email" id="input_8210690378160">; <input type="text" name="Name" id="input_8210690378161">; <input type="tel" name="Phone" id="input_8210690378162">

7 controls

0 labeled

6 placeholder only

1 unlabeled

Control	Type	Label	Method
#input_4228215262380	email	(Email)	placeholder only
#input_4229215262381	text	(Name)	placeholder only
#input_4229215262382	tel	(Phone)	placeholder only
#input_8210690378160	email	(Email)	placeholder only
#input_8210690378161	text	(Name)	placeholder only
#input_8210690378162	tel	(Phone)	placeholder only
textarea	textarea	(none)	none

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

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

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

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

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

title IceTray

1.09:1

#000000

#0E0E0E

needs 4.5:1 (normal text)

16px · top of page (header area)

a To main content

1.08:1

#000000

#0D0D0D

needs 4.5:1 (normal text)

16px · top of page (header area)

div Registration

1.08:1

#000000

#0D0D0D

needs 4.5:1 (normal text)

16px · top of page (header area)

div Just type your contacts

1.08:1

#000000

#0D0D0D

needs 4.5:1 (normal text)

16px · top of page (header area)

span Submit

1.08:1

#000000

#0D0D0D

needs 4.5:1 (normal text)

16px · above the fold

div It's totally free

1.07:1

#000000

#0C0C0C

needs 4.5:1 (normal text)

16px · above the fold

a Events

1.07:1

#000000

#0C0C0C

needs 4.5:1 (normal text)

16px · above the fold

a Activities

1.07:1

#000000

#0C0C0C

needs 4.5:1 (normal text)

16px · above the fold

a Services

1.07:1

#000000

#0C0C0C

needs 4.5:1 (normal text)

16px · above the fold

a Location

1.07:1

#000000

#0C0C0C

needs 4.5:1 (normal text)

16px · above the fold

div Private Weed Club in Barcelona.

1.07:1

#000000

#0B0B0B

needs 4.5:1 (normal text)

16px · above the fold

a Icetray weed club

1.07:1

#000000

#0B0B0B

needs 4.5:1 (normal text)

16px · above the fold

span Become a member

1.07:1

#000000

#0B0B0B

needs 4.5:1 (normal text)

16px · above the fold

a About

1.07:1

#000000

#0B0B0B

needs 4.5:1 (normal text)

16px · mid-page

a Events

1.06:1

#000000

#0A0A0A

needs 4.5:1 (normal text)

16px · mid-page

a Photo

1.06:1

#000000

#0A0A0A

needs 4.5:1 (normal text)

16px · mid-page

a Contact

1.06:1

#000000

#0A0A0A

needs 4.5:1 (normal text)

16px · mid-page

a ICETRAY WEED CLUB

1.05:1

#000000

#090909

needs 4.5:1 (normal text)

16px · mid-page

span BECOME A MEMBER

1.06:1

#000000

#09090C

needs 4.5:1 (normal text)

16px · mid-page

div 2021

1.06:1

#000000

#09090A

needs 4.5:1 (normal text)

16px · mid-page

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
title IceTray	1.09:1	4.5:1	#000000	#0E0E0E	Fail
a To main content	1.08:1	4.5:1	#000000	#0D0D0D	Fail
div Registration	1.08:1	4.5:1	#000000	#0D0D0D	Fail
div Just type your conta…	1.08:1	4.5:1	#000000	#0D0D0D	Fail
span Submit	1.08:1	4.5:1	#000000	#0D0D0D	Fail
div It's totally free	1.07:1	4.5:1	#000000	#0C0C0C	Fail
a Events	1.07:1	4.5:1	#000000	#0C0C0C	Fail
a Activities	1.07:1	4.5:1	#000000	#0C0C0C	Fail
a Services	1.07:1	4.5:1	#000000	#0C0C0C	Fail
a Location	1.07:1	4.5:1	#000000	#0C0C0C	Fail
div Private Weed Club in…	1.07:1	4.5:1	#000000	#0B0B0B	Fail
a Icetray weed club	1.07:1	4.5:1	#000000	#0B0B0B	Fail
span Become a member	1.07:1	4.5:1	#000000	#0B0B0B	Fail
a About	1.07:1	4.5:1	#000000	#0B0B0B	Fail
a Events	1.06:1	4.5:1	#000000	#0A0A0A	Fail
a Photo	1.06:1	4.5:1	#000000	#0A0A0A	Fail
a Contact	1.06:1	4.5:1	#000000	#0A0A0A	Fail
a ICETRAY WEED CLUB	1.05:1	4.5:1	#000000	#090909	Fail
span BECOME A MEMBER	1.06:1	4.5:1	#000000	#09090C	Fail
div 2021	1.06:1	4.5:1	#000000	#09090A	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.

Lighthouse Accessibility Audits

Score 83/100 — 4 failing, 21 passed

REVIEW

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
footer#t-footer > div#rec1085752261 > div.t824 > button.t824__btn `footer#t-footer > div#rec1085752261 > div.t824 > button.t824__btn`

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.t396 > div.t396__artboard > div.t396__elem > a.tn-atom `div.t396 > div.t396__artboard > div.t396__elem > a.tn-atom`
div.t396__artboard > div.t396__elem > div#sbs-1066279996-1697696121745 > a.tn-atom `div.t396__artboard > div.t396__elem > div#sbs-1066279996-1697696121745 > a.tn-atom`
div.t396 > div.t396__artboard > div.t396__elem > a.tn-atom `div.t396 > div.t396__artboard > div.t396__elem > a.tn-atom`
div.t396__artboard > div.t396__elem > div#sbs-1074577381-1697696121745 > a.tn-atom `div.t396__artboard > div.t396__elem > div#sbs-1074577381-1697696121745 > a.tn-atom`
div.t396 > div.t396__artboard > div.t396__elem > a.tn-atom `div.t396 > div.t396__artboard > div.t396__elem > a.tn-atom`
div.t396__artboard > div.t396__elem > div#sbs-1066280041-1697709563193 > a.tn-atom `div.t396__artboard > div.t396__elem > div#sbs-1066280041-1697709563193 > a.tn-atom`

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
+34 613 47-71-16 `div.t554__card > div.t-text > strong > a`
Carrer d'Aragó, 209, L'Eixample, 08011 Barcelona `div.t554__card > div.t-text > strong > a`
Made on `div#tildacopy > a.t-tildalabel__link > div.t-tildalabel__wrapper > div.t-tildalabel__txtleft`
Tilda `div#tildacopy > a.t-tildalabel__link > div.t-tildalabel__wrapper > div.t-tildalabel__txtright`

These are opportunities to improve the legibility of your content.

Internationalization and localization

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

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

○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

●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

●`[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

●`[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

●Document has a `<title>` element

●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.

●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

○`[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

○Heading elements appear in a sequentially-descending order

○`<html>` element has a valid value for its `[lang]` attribute

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○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.

○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.

○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 33 images OK

PASS

All 33 images OK

33 decorative image(s) correctly marked

33 images 33 decorative

All images have appropriate alt text.

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