Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

7 PASS 1 REVIEW 5 FIX

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

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 ✗

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

h2 Utility Menu

2.20:1

#000000

#364B2F

needs 3.0:1 (large text)

24px · top of page (header area)

h2 Donate Menu

1.55:1

#000000

#00352C

needs 3.0:1 (large text)

24px · mid-page

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Utility Menu	2.20:1	3.0:1	#000000	#364B2F	Fail
h2 Global Menu	8.87:1	3.0:1	#000000	#A9AC7A	Pass
h2 Donate Menu	1.55:1	3.0:1	#000000	#00352C	Fail
h2 Global Menu	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Global Menu	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Donate Menu	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Protect baby seals	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Changing the world f…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 A Humane World blog	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 End experiments on d…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Latest stories	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Shop to help animals	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Did you see us on TV…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Footer menu	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Global - Social Menu	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Global - Legal Menu	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Notice	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Advocate	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Volunteer	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Learn	21.00:1	3.0:1	#000000	#FFFFFF	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.

Landmark Structure

17 landmarks

PASS

17 landmarks

<main> landmark present

11 <nav> landmark(s) found

1 of 11 <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

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

A+

Heading Hierarchy

22 headings

PASS

22 headings

Single H1 present

H2 Utility Menu
H2 Global Menu
H2 Donate Menu
H2 Global Menu
H2 Global Menu
H2 Donate Menu
H1 Help rescued animals
H2 Protect baby seals
H2 Changing the world for animals
H3 Advocate
H3 Volunteer
H3 Learn
H2 A Humane World blog
H2 End experiments on dogs
H2 Latest stories
H2 Shop to help animals
H2 Did you see us on TV?
H3 Your gift can do so much for animals in need
H2 Footer menu
H2 Global - Social Menu
H2 Global - Legal Menu
H2 Notice

A+

Alt Text Quality

All 20 images OK

PASS

All 20 images OK

1 image(s) with alt text over 125 characters

19 image(s) with good alt text

20 images 19 good alt text

Issue	Count
too long	1 image(s)

A+

Form Accessibility

All 2 controls labeled

PASS

All 2 controls labeled

2 control(s) properly labeled

2 controls

2 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#hw-search-keys	search	Search humaneworld.org	for/id
#edit-query	text	Search:	for/id

Link & Button Quality

156 links, 31 buttons — all OK

PASS

156 links, 31 buttons — all OK

13 link(s) open in new tab without warning

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

Got: https://hsi.org.au/; https://give.humaneworld.org/campaign/653479/donate; https://humanepro.org; https://hsi.org.au/; https://hsi.org.au/; https://twitch.tv/humaneworldforanimals; https://www.instagram.com/humaneworldforanimals; https://x.com/humaneworldorg; https://www.facebook.com/humaneworldforanimals; https://bsky.app/profile/humaneworldorg.bsky.social (+3 more)

143 link(s) with descriptive text

156 links

0 empty

0 generic text

13 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://hsi.org.au/	Australia	new tab	Add '(opens in new tab)' to text
https://give.humaneworld.org/campaign/65…	Start a fundraiser	new tab	Add '(opens in new tab)' to text
https://humanepro.org	HumanePro for animal care prof…	new tab	Add '(opens in new tab)' to text
https://hsi.org.au/	Australia	new tab	Add '(opens in new tab)' to text
https://hsi.org.au/	Australia	new tab	Add '(opens in new tab)' to text
https://twitch.tv/humaneworldforanimals	Twitch	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/humaneworldfor…	Instagram	new tab	Add '(opens in new tab)' to text
https://x.com/humaneworldorg	Twitter X	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/humaneworldfora…	Facebook	new tab	Add '(opens in new tab)' to text
https://bsky.app/profile/humaneworldorg.…	bluesky	new tab	Add '(opens in new tab)' to text
https://linkedin.com/company/humaneworld…	LinkedIn	new tab	Add '(opens in new tab)' to text
https://www.tiktok.com/@humaneworldforan…	tiktok	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/user/hsus	YouTube	new tab	Add '(opens in new tab)' to text

174 links and buttons have descriptive text

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

https://hsi.org.au/; https://give.humaneworld.org/campaign/653479/donate; https://humanepro.org; https://hsi.org.au/; https://hsi.org.au/; https://twitch.tv/humaneworldforanimals; https://www.instagram.com/humaneworldforanimals; https://x.com/humaneworldorg; https://www.facebook.com/humaneworldforanimals; https://bsky.app/profile/humaneworldorg.bsky.social (+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

404 Error Page

HTTP 404, custom page

PASS

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title 404 | Humane World for Animals ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓

A+

Lighthouse Accessibility Audits

Score 100/100 — 0 failing, 31 passed

PASS

100

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.

○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

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

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

●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

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<frame>` or `<iframe>` elements have a title

●`<html>` element has a `[lang]` attribute

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

●Links are distinguishable without relying on color.

●Links have a discernible name

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

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

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

○Form elements have associated labels

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

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

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