Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

16 PASS 1 REVIEW 7 FIX

Landmark Structure

Action

1 landmarks

FIX

1 landmarks

No <main> landmark found

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

1 <nav> landmark(s) found

No banner (header) landmark

No contentinfo (footer) landmark

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

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

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

Soft 404: server returns HTTP 200 for non-existent pages

The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.

Got: Status: 200 for /beavercheck-404-test-22qop9

404 Page Quality ✗ Soft 404 (HTTP 200)

Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

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

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://pictures.loowis.co.uk/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://pictures.loowis.co.uk/manifest.json

Manifest contains invalid JSON.

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

1 navigation landmark(s) detected

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 1 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

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 Loowis Photography

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

a ALL IMAGES

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

a COLLECTIONS

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

a IMAGE MAP

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

button Film

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

button Digital

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

h5 Chimney

1.00:1

#000000

needs 4.5:1 (normal text)

13px · above the fold

h5 Chimney

1.00:1

#000000

needs 4.5:1 (normal text)

13px · above the fold

h5 Dangerous Structure

1.00:1

#000000

needs 4.5:1 (normal text)

13px · above the fold

h5 Dangerous Structure

1.00:1

#000000

needs 4.5:1 (normal text)

13px · above the fold

h5 Roskilde Train Station

1.00:1

#000000

needs 4.5:1 (normal text)

13px · above the fold

h5 Roskilde Train Station

1.00:1

#000000

needs 4.5:1 (normal text)

13px · above the fold

h5 Obelisk

1.00:1

#000000

needs 4.5:1 (normal text)

13px · above the fold

h5 Obelisk

1.00:1

#000000

needs 4.5:1 (normal text)

13px · above the fold

h5 Balmoral Hotel

1.00:1

#000000

needs 4.5:1 (normal text)

13px · mid-page

h5 Balmoral Hotel

1.00:1

#000000

needs 4.5:1 (normal text)

13px · mid-page

h5 Lock No .3

1.00:1

#000000

needs 4.5:1 (normal text)

13px · mid-page

h5 Lock No .3

1.00:1

#000000

needs 4.5:1 (normal text)

13px · mid-page

h5 Hayward Gallery

1.00:1

#000000

needs 4.5:1 (normal text)

13px · mid-page

h5 Hayward Gallery

1.00:1

#000000

needs 4.5:1 (normal text)

13px · mid-page

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
title Loowis Photography	1.00:1	4.5:1	#000000	#000000	Fail
a ALL IMAGES	1.00:1	4.5:1	#000000	#000000	Fail
a COLLECTIONS	1.00:1	4.5:1	#000000	#000000	Fail
a IMAGE MAP	1.00:1	4.5:1	#000000	#000000	Fail
button Film	1.00:1	4.5:1	#000000	#000000	Fail
button Digital	1.00:1	4.5:1	#000000	#000000	Fail
h5 Chimney	1.00:1	4.5:1	#000000	#000000	Fail
h5 Chimney	1.00:1	4.5:1	#000000	#000000	Fail
h5 Dangerous Structure	1.00:1	4.5:1	#000000	#000000	Fail
h5 Dangerous Structure	1.00:1	4.5:1	#000000	#000000	Fail
h5 Roskilde Train Stati…	1.00:1	4.5:1	#000000	#000000	Fail
h5 Roskilde Train Stati…	1.00:1	4.5:1	#000000	#000000	Fail
h5 Obelisk	1.00:1	4.5:1	#000000	#000000	Fail
h5 Obelisk	1.00:1	4.5:1	#000000	#000000	Fail
h5 Balmoral Hotel	1.00:1	4.5:1	#000000	#000000	Fail
h5 Balmoral Hotel	1.00:1	4.5:1	#000000	#000000	Fail
h5 Lock No .3	1.00:1	4.5:1	#000000	#000000	Fail
h5 Lock No .3	1.00:1	4.5:1	#000000	#000000	Fail
h5 Hayward Gallery	1.00:1	4.5:1	#000000	#000000	Fail
h5 Hayward Gallery	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.

Heading Hierarchy

23 headings, 1 skip(s)

PASS

23 headings, 1 skip(s)

Single H1 present

Heading level skipped: H1 → H5 (missing H2)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H1 LOOWIS
H5 Chimney skipped
H5 Chimney
H5 Dangerous Structure
H5 Dangerous Structure
H5 Roskilde Train Station
H5 Roskilde Train Station
H5 Obelisk
H5 Obelisk
H5 Balmoral Hotel
H5 Balmoral Hotel
H5 Lock No .3
H5 Lock No .3
H5 Hayward Gallery
H5 Hayward Gallery
H5 Spikes
H5 Spikes
H5 Costco
H5 Costco
H5 Train Station
H5 Train Station
H5 Edinburgh Castle
H5 Edinburgh Castle

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+

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

1 heading(s) are all-uppercase (excluding short acronyms)

Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.

Got: 1 all-caps heading(s)

A+

Alt Text Quality

All 22 images OK

PASS

All 22 images OK

22 decorative image(s) correctly marked

22 images 22 decorative

All images have appropriate alt text.

Form Accessibility

1 of 1 controls have issues

PASS

1 of 1 controls have issues

1 control(s) without accessible label

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

Got: <input type="search">

1 controls

0 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
input	search	(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

Link & Button Quality

1 issue(s) across 20 links and 14 buttons

PASS

1 issue(s) across 20 links and 14 buttons

1 button(s) with no accessible text

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

Got: button.searchSubmit (#38 on page)

20 link(s) with descriptive text

20 links

0 empty

0 generic text

0 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
/images/7ff85496-ac51-458a-bd84-5dc1669c…	Chimney	img no alt	Add alt attribute to the image
/images/99de73fc-4f85-4418-b6f3-3068bf09…	Dangerous Structure	img no alt	Add alt attribute to the image
/images/b6cbbfa9-b672-430d-808d-c99824dd…	Roskilde Train Station	img no alt	Add alt attribute to the image
/images/19a1ade4-19d4-471c-9340-b9928397…	Obelisk	img no alt	Add alt attribute to the image
/images/67c62d11-57b9-41c8-923d-023de4af…	Balmoral Hotel	img no alt	Add alt attribute to the image
/images/0dc24f13-08af-434c-96cf-9ef4f537…	Lock No .3	img no alt	Add alt attribute to the image
/images/03f67493-a7a4-455a-b197-af9a4b79…	Hayward Gallery	img no alt	Add alt attribute to the image
/images/69f69c80-1c9e-415f-807f-0bf7acc1…	Spikes	img no alt	Add alt attribute to the image
/images/e506084a-2f4f-49da-bd00-49cceb6d…	Costco	img no alt	Add alt attribute to the image
/images/c38d8fdc-7715-4e75-8d85-14f07059…	Train Station	img no alt	Add alt attribute to the image
/images/ea07f6b6-ed92-4069-88a8-87a4b7f0…	Edinburgh Castle	img no alt	Add alt attribute to the image
<button>	(empty)	empty	Add button text or aria-label

33 links and buttons have descriptive text

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

button.searchSubmit (#38 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

A+

Form Input Types

1 form control(s) checked, no type mismatches

PASS

1 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

1 form control(s) checked, no input-semantic issues

PASS

1 form control(s) checked, no input-semantic issues

All form input semantics look correct

A+

Mobile Keyboard & Autofill

No autofill-eligible form controls

PASS

No autofill-eligible form controls

No autofill-eligible form controls (no name/email/tel/address fields)

A+

Document Language

Lang attribute set to "en"

PASS

Lang attribute set to "en"

<html lang="en"> is set and valid

Got: en

A+

Tabindex Anti-Patterns

No explicit tabindex attributes found

PASS

No explicit tabindex attributes found

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

A+

Tap Target Adequacy

All tap targets meet WCAG 2.5.5/2.5.8 sizing

PASS

All tap targets meet WCAG 2.5.5/2.5.8 sizing

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

Mobile-Readable Font Sizes

All 15 visible text node(s) render at >= 12 CSS pixels

PASS

All 15 visible text node(s) render at >= 12 CSS pixels

All text uses legible mobile font sizes (>= 12 CSS px)

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

No `<meta name="theme-color">` -- browser chrome falls back to default

Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.

Lighthouse Accessibility Audits

Score 93/100 — 2 failing, 10 passed

PASS

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.

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
Dangerous Structure `div._filmShow_inv3r_59 > article._imageContainer_to0nm_1 > a._mobileLink_to0nm_13 > h5._thumbnailTitle_to0nm_35`

These are opportunities to improve keyboard navigation in your application.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

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

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●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

●Links have a discernible name

●Touch targets have sufficient size and spacing.

○`[accesskey]` values are unique

○`[aria-*]` attributes match their roles

○`button`, `link`, and `menuitem` elements have accessible names

○ARIA attributes are used as specified for the element's role

○Deprecated ARIA roles were not used

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○`[aria-hidden="true"]` elements do not contain focusable descendents

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements use only permitted ARIA attributes

○`[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]`s are contained by their required parent element

○`[role]` values are valid

○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

○`[aria-*]` attributes have valid values

○`[aria-*]` attributes are valid and not misspelled

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

○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

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

○Identical links have the same purpose.

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

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