Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

10 PASS 4 REVIEW 10 FIX

Alt Text Quality

Action

4 of 62 images have issues

FIX

4 of 62 images have issues

4 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

4 image-in-link without alt text

An image inside a link with no alt creates an empty link.

11 decorative image(s) correctly marked

47 image(s) with good alt text

62 images 47 good alt text 11 decorative 4 missing

Issue	Count
missing	4 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

Form Accessibility

Action

4 of 9 controls have issues

FIX

4 of 9 controls have issues

2 control(s) without accessible label

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

Got: <input type="checkbox" name="newsletter" id="newsletter">; <input type="text" name="q" id="searchI">

2 control(s) rely on placeholder only

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

Got: <input type="email" name="email" id="timesact_bis_email">; <input type="email" name="contact[email]" id="sections--25598215225723__newsletter_kFXWbX_Newsletter_Email">

5 control(s) properly labeled

9 controls

5 labeled

2 placeholder only

2 unlabeled

Control	Type	Label	Method
#search	checkbox	Close search	for/id
#searchMob	text		none
#searchI	text		none
#searchMob	text		none
#email_01M4QNBB2GGBWRNJ6BR0N17SS1	email	Email	aria-label
#sections--25598215225723__newsletter_kFXWbX_Newsletter_Email	email	(Enter your email)	placeholder only
#timesact_bis_email	email	(eg. username@example.com)	placeholder only
#searchI	text	(none)	none
#newsletter	checkbox	(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

Link & Button Quality

Action

16 issue(s) across 179 links and 18 buttons

FIX

16 issue(s) across 179 links and 18 buttons

7 link(s) with no accessible text

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

Got: /; /; https://www.murci.co.uk/customer_authentication/redirect?locale=en&region_cou…; /collections/sample-sale; /collections/denim; /collections/rendezvous; /collections/best-sellers-home-page

13 link(s) open in new tab without warning

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

Got: https://timesact.com; https://www.murci.co.uk/policies/privacy-policy; https://instagram.com/murciuk; https://www.facebook.com/murciofficial; https://www.tiktok.com/@murciuk; https://apps.apple.com/us/app/murci/id6798773508; https://play.google.com/store/apps/details?id=co.app.id_mlykBOwnOL; https://apps.apple.com/us/app/murci/id6798773508; https://play.google.com/store/apps/details?id=co.app.id_mlykBOwnOL; https://www.instagram.com/murciuk (+3 more)

9 button(s) with no accessible text

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

Got: button.timesact_bis_submit_button (#375 on page); button.md-trigger (#391 on page); button.flex (#692 on page); button.flex (#848 on page); button.flex (#1191 on page); button.flex (#1307 on page); button.flex (#1663 on page); button.flex (#1819 on page); button.flex (#3307 on page)

159 link(s) with descriptive text

179 links

7 empty

0 generic text

13 new tab

9 empty buttons

Element	Text	Issue	Suggested Fix
https://timesact.com	by Timesact	new tab	Add '(opens in new tab)' to text
https://www.murci.co.uk/policies/privacy…	Privacy Policy	new tab	Add '(opens in new tab)' to text
/	(empty)	empty	Add link text or aria-label
/	(empty)	empty	Add link text or aria-label
https://www.murci.co.uk/customer_authent…	(empty)	empty	Add link text or aria-label
/collections/sample-sale	(empty)	empty	Add link text or aria-label
/collections/denim	(empty)	empty	Add link text or aria-label
/collections/rendezvous	(empty)	empty	Add link text or aria-label
/collections/best-sellers-home-page	(empty)	empty	Add link text or aria-label
https://instagram.com/murciuk	Instagram	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/murciofficial	Facebook	new tab	Add '(opens in new tab)' to text
https://www.tiktok.com/@murciuk	Tiktok	new tab	Add '(opens in new tab)' to text
https://apps.apple.com/us/app/murci/id67…	Download on the App Store	new tab	Add '(opens in new tab)' to text
https://play.google.com/store/apps/detai…	Get it on Google Play	new tab	Add '(opens in new tab)' to text
https://apps.apple.com/us/app/murci/id67…	Download on the App Store	new tab	Add '(opens in new tab)' to text
https://play.google.com/store/apps/detai…	Get it on Google Play	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/murciuk	Opens @murciuk Instagram profi…	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/murciuk	Opens @murciuk Instagram profi…	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/murciuk	Opens @murciuk Instagram profi…	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/murciuk	Opens @murciuk Instagram profi…	new tab	Add '(opens in new tab)' to text
<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
<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
<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

168 links and buttons have descriptive text

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

/; /; https://www.murci.co.uk/customer_authentication/redirect?locale=en&region_cou…; /collections/sample-sale; /collections/denim; /collections/rendezvous; /collections/best-sellers-home-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

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

https://timesact.com; https://www.murci.co.uk/policies/privacy-policy; https://instagram.com/murciuk; https://www.facebook.com/murciofficial; https://www.tiktok.com/@murciuk; https://apps.apple.com/us/app/murci/id6798773508; https://play.google.com/store/apps/details?id=co.app.id_mlykBOwnOL; https://apps.apple.com/us/app/murci/id6798773508; https://play.google.com/store/apps/details?id=co.app.id_mlykBOwnOL; https://www.instagram.com/murciuk (+3 more)

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.timesact_bis_submit_button (#375 on page); button.md-trigger (#391 on page); button.flex (#692 on page); button.flex (#848 on page); button.flex (#1191 on page); button.flex (#1307 on page); button.flex (#1663 on page); button.flex (#1819 on page); button.flex (#3307 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

Mobile Keyboard & Autofill

Action

4/5 eligible field(s) missing autocomplete or inputmode

FIX

4/5 eligible field(s) missing autocomplete or inputmode

1 field(s) missing recommended autocomplete attribute

WCAG 1.3.5 (Level AA): inputs whose purpose maps to a Common Input Purpose value should declare it via `autocomplete=`. Required for password managers, browser autofill, and assistive tech that customizes inputs (e.g., simplified keyboards). Mobile autofill in particular cuts form-completion time by 30-50% when these are present. Affected purposes: email.

Got: <input type="email" name="email" id="timesact_bis_email">

3 field(s) would benefit from inputmode attribute

Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: email.

Got: <input type="email" name="email" id="timesact_bis_email">, <input type="email" name="contact[email]" id="sections--25598215225723__newsletter_kFXWbX_Newsletter_Email">, <input type="email" name="email" id="email_01M4QNBB2GGBWRNJ6BR0N17SS1">

404 Error Page

Action

HTTP 403, custom page

FIX

HTTP 403, custom page

Unexpected status code: HTTP 403

Expected HTTP 404 but received 403. This may confuse search engine crawlers.

Got: HTTP 403

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 403 ✗Page Title Verifying your connection... ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

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 Missing

✓ 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

Theme color only

FIX

Theme color only

Theme-color present but no dark variant

A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.

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 ModePartial Dark Mode

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 ✗

Heading Hierarchy

20 headings

REVIEW

20 headings

No H1 heading found

Every page should have one H1 that describes the page content.

1 empty heading(s)

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

H3 (empty)
H2 Cookie consent
H3 You may also like
H2 SAMPLE SALE FAVOURITES
H3 CURVE MINI DRESS
H3 JAGGER JUMPSUIT
H3 OPAL CAPRI JUMPSUIT
H3 LEXI MINI DRESS
H2 new in
H3 TORA MAXI DRESS
H3 MARLOWE DENIM MINI DRESS
H3 FARRAH MIDI DRESS
H3 SLOANE DENIM CORSET TOP
H2 BESTSELLERS
H3 SCANDAL MINI DRESS
H3 FATALE MINI DRESS
H3 ISOLA MAXI DRESS
H3 KITTEN MINI DRESS
H2 #MURCIMUSES
H2 10% Off follow Our Design Diary

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

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

Form Input Types

4 input(s) using type=text where a specific type would help

REVIEW

4 input(s) using type=text where a specific type would help

Input "q" should use type="search" (currently type="text")

Field name "q" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.

Input "q" should use type="search" (currently type="text")

Field name "q" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.

Input "q" should use type="search" (currently type="text")

Field name "q" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.

Input "q" should use type="search" (currently type="text")

Field name "q" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.

Color Contrast (Screenshot)

Action

20 text elements analyzed, 1 fail WCAG AA

REVIEW

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

19 pass 1 fail WCAG AA

title Murci

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Cookie consent	5.89:1	3.0:1	#000000	#DB5B8D	Pass
h2 SAMPLE SALE FAVOURIT…	15.41:1	3.0:1	#1A1A1A	#F1F1F1	Pass
h2 new in	15.41:1	3.0:1	#1A1A1A	#F1F1F1	Pass
h2 BESTSELLERS	15.41:1	3.0:1	#1A1A1A	#F1F1F1	Pass
h2 #MURCIMUSES	15.41:1	3.0:1	#1A1A1A	#F1F1F1	Pass
h2 follow Our Design Di…	18.59:1	3.0:1	#000000	#F1F1F1	Pass
h3 You may also like	18.59:1	3.0:1	#000000	#F1F1F1	Pass
h3 CURVE MINI DRESS	18.59:1	3.0:1	#000000	#F1F1F1	Pass
h3 JAGGER JUMPSUIT	18.59:1	3.0:1	#000000	#F1F1F1	Pass
h3 OPAL CAPRI JUMPSUIT	18.59:1	3.0:1	#000000	#F1F1F1	Pass
h3 LEXI MINI DRESS	18.59:1	3.0:1	#000000	#F1F1F1	Pass
h3 TORA MAXI DRESS	18.59:1	3.0:1	#000000	#F1F1F1	Pass
h3 MARLOWE DENIM MINI D…	18.59:1	3.0:1	#000000	#F1F1F1	Pass
h3 FARRAH MIDI DRESS	18.59:1	3.0:1	#000000	#F1F1F1	Pass
h3 SLOANE DENIM CORSET …	18.59:1	3.0:1	#000000	#F1F1F1	Pass
h3 SCANDAL MINI DRESS	18.59:1	3.0:1	#000000	#F1F1F1	Pass
h3 FATALE MINI DRESS	18.59:1	3.0:1	#000000	#F1F1F1	Pass
h3 ISOLA MAXI DRESS	18.59:1	3.0:1	#000000	#F1F1F1	Pass
h3 KITTEN MINI DRESS	18.59:1	3.0:1	#000000	#F1F1F1	Pass
title Murci	1.00:1	4.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.

Lighthouse Accessibility Audits

Action

Score 79/100 — 5 failing, 28 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