Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

3 PASS 4 REVIEW 6 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-1upat0

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.

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://openclipart.org/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://openclipart.org/manifest.json

Manifest contains invalid JSON.

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.

Got: #ffffff

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 ✗

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.

Heading Hierarchy

Action

3 headings, 1 skip(s)

REVIEW

3 headings, 1 skip(s)

No H1 heading found

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

Heading level skipped: H2 → H4 (missing H3)

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

H5 Log into OpenClipart
H2 185,014 clipart by 8,231 artists. 21 clipart by 2 artists today.
H4 For questions, please email support@openclipart.org skipped

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

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

Form Accessibility

Action

3 of 4 controls have issues

REVIEW

3 of 4 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="submit" name="submit">

2 control(s) rely on placeholder only

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

Got: <input type="text" name="username">; <input type="password" name="password">

1 control(s) properly labeled

4 controls

1 labeled

2 placeholder only

1 unlabeled

Control	Type	Label	Method
query	text	Search Openclipart	aria-label
password	password	(Password)	placeholder only
username	text	(Username or Email)	placeholder only
submit	submit	(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

Favicon & Branding

Action

13 icon(s) detected

REVIEW

13 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

Apple touch icon present

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 19 fail WCAG AA

REVIEW

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

1 pass 19 fail WCAG AA 1 pass AA only

h2 185,014 clipart by 8,231 artists. 21 cli…

1.47:1

#000000

#003300

needs 3.0:1 (large text)

24px · above the fold

title Openclipart - Clipping Culture

1.47:1

#000000

#003300

needs 4.5:1 (normal text)

16px · top of page (header area)

span OPENCLIPART

1.47:1

#000000

#003300

needs 4.5:1 (normal text)

16px · top of page (header area)

a Login

1.47:1

#000000

#003300

needs 4.5:1 (normal text)

16px · top of page (header area)

a Join & Become Member

1.47:1

#000000

#003300

needs 4.5:1 (normal text)

16px · top of page (header area)

p Email

1.47:1

#000000

#003300

needs 4.5:1 (normal text)

16px · above the fold

a support@openclipart.org

1.47:1

#000000

#003300

needs 4.5:1 (normal text)

16px · above the fold

p for Lost Password or Account Issues. Tha…

1.47:1

#000000

#003300

needs 4.5:1 (normal text)

16px · above the fold

p Don't have an account?

1.47:1

#000000

#003300

needs 4.5:1 (normal text)

16px · above the fold

a Join & Become Member

1.47:1

#000000

#003300

needs 4.5:1 (normal text)

16px · above the fold

button Search

1.47:1

#000000

#003300

needs 4.5:1 (normal text)

16px · above the fold

a Random

1.47:1

#000000

#003300

needs 4.5:1 (normal text)

16px · above the fold

a Improve Openclipart by Becoming a Member

1.47:1

#000000

#003300

needs 4.5:1 (normal text)

16px · mid-page

a Browse Latest Clipart

1.47:1

#000000

#003300

needs 4.5:1 (normal text)

16px · mid-page

a support@openclipart.org

3.66:1

#000000

#666666

needs 4.5:1 (normal text)

16px · mid-page

a FAQ

3.66:1

#000000

#666666

needs 4.5:1 (normal text)

16px · mid-page

a Privacy

3.66:1

#000000

#666666

needs 4.5:1 (normal text)

16px · mid-page

a License

3.66:1

#000000

#666666

needs 4.5:1 (normal text)

16px · mid-page

a Membership

3.66:1

#000000

#666666

needs 4.5:1 (normal text)

16px · mid-page

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 185,014 clipart by 8…	1.47:1	3.0:1	#000000	#003300	Fail
title Openclipart - Clippi…	1.47:1	4.5:1	#000000	#003300	Fail
span OPENCLIPART	1.47:1	4.5:1	#000000	#003300	Fail
a Login	1.47:1	4.5:1	#000000	#003300	Fail
a Join & Become Member	1.47:1	4.5:1	#000000	#003300	Fail
p Email	1.47:1	4.5:1	#000000	#003300	Fail
a support@openclipart.…	1.47:1	4.5:1	#000000	#003300	Fail
p for Lost Password or…	1.47:1	4.5:1	#000000	#003300	Fail
p Don't have an accoun…	1.47:1	4.5:1	#000000	#003300	Fail
a Join & Become Member	1.47:1	4.5:1	#000000	#003300	Fail
button Search	1.47:1	4.5:1	#000000	#003300	Fail
a Random	1.47:1	4.5:1	#000000	#003300	Fail
a Improve Openclipart …	1.47:1	4.5:1	#000000	#003300	Fail
a Browse Latest Clipar…	1.47:1	4.5:1	#000000	#003300	Fail
h4 For questions, pleas…	3.66:1	3.0:1	#000000	#666666	Pass
a support@openclipart.…	3.66:1	4.5:1	#000000	#666666	Fail
a FAQ	3.66:1	4.5:1	#000000	#666666	Fail
a Privacy	3.66:1	4.5:1	#000000	#666666	Fail
a License	3.66:1	4.5:1	#000000	#666666	Fail
a Membership	3.66:1	4.5:1	#000000	#666666	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.

A+

Alt Text Quality

All 33 images OK

PASS

All 33 images OK

33 image(s) with good alt text

33 images 33 good alt text

All images have appropriate alt text.

A+

Link & Button Quality

47 links, 3 buttons — all OK

PASS

47 links, 3 buttons — all OK

47 link(s) with descriptive text

47 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

50 links and buttons have descriptive text

A+

Lighthouse Accessibility Audits

Score 95/100 — 2 failing, 28 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.

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
Join & Become Member `div.ml-auto > div#logged > span > a.btn`
Search `form#search > div.input-group > div.input-group-append > button#button-search`
Random `form#search > div.input-group > div.input-group-append > a#button-random`
Improve Openclipart by Becoming a Member `body > div#content > center > a.btn`
Browse Latest Clipart `body > div#content > p.text-center > a#browse`
Learn more `div.fc-dialog-content > div.fc-dialog-scrollable-content > button.fc-faq-header > span.fc-faq-label`
List of partners. `div.fc-dialog-scrollable-content > div.fc-footer > p > a.fc-vendors-list-dialog`

These are opportunities to improve the legibility of your content.

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
For questions, please email support@openclipart.org `body > div#footer > div#forfooter > h4#support`

These are opportunities to improve keyboard navigation in your application.

○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

●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

●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

●Document has a `<title>` element

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

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

○`[accesskey]` values are unique

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

○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

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

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

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

○Identical links have the same purpose.

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