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 4 REVIEW 4 FIX

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.

Got: #00549e

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.

Landmark Structure

2 landmarks

REVIEW

2 landmarks

<main> landmark present

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

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

Could not test

REVIEW

Could not test

404 page could not be tested

The 404 page check encountered an error. This may be due to a timeout or network issue.

404 page quality check not available.

Favicon & Branding

7 icon(s) detected

REVIEW

7 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

SVG favicon detected — scales perfectly to any size

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✓ SVG Favicon Present

✗ Manifest Icons Missing

✓ Multiple Sizes Present

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

h1 Terms of Use

1.10:1

#000000

#020F23

needs 3.0:1 (large text)

32px · bottom of viewport

h2 1. Acceptance of the Terms of Use

1.10:1

#000000

#020F23

needs 3.0:1 (large text)

24px · bottom of viewport

h2 2. Changes to These Terms of Use

1.10:1

#000000

#020F23

needs 3.0:1 (large text)

24px · bottom of viewport

h2 3. Accessing the Website and Account Sec…

1.10:1

#000000

#020F23

needs 3.0:1 (large text)

24px · bottom of viewport

h2 4. Our Copyrights

1.10:1

#000000

#020F23

needs 3.0:1 (large text)

24px · bottom of viewport

h2 5. Our Trademarks

1.10:1

#000000

#020F23

needs 3.0:1 (large text)

24px · bottom of viewport

h2 6.Prohibited Uses

1.10:1

#000000

#020F23

needs 3.0:1 (large text)

24px · bottom of viewport

h2 7.User Contributions

1.10:1

#000000

#020F23

needs 3.0:1 (large text)

24px · bottom of viewport

h2 8. Monitoring and Enforcement; Terminati…

1.10:1

#000000

#020F23

needs 3.0:1 (large text)

24px · bottom of viewport

h2 9. Content Standards

1.10:1

#000000

#020F23

needs 3.0:1 (large text)

24px · bottom of viewport

h2 10. Intellectual Property Infringement P…

1.10:1

#000000

#020F23

needs 3.0:1 (large text)

24px · bottom of viewport

h2 11. Reliance on Information Posted

1.10:1

#000000

#020F23

needs 3.0:1 (large text)

24px · bottom of viewport

h2 12. Changes to the Website

1.10:1

#000000

#020F23

needs 3.0:1 (large text)

24px · bottom of viewport

h2 13. Information About You and Your Visit…

1.10:1

#000000

#020F23

needs 3.0:1 (large text)

24px · bottom of viewport

h2 14. Linking to the Website and Interacti…

1.10:1

#000000

#020F23

needs 3.0:1 (large text)

24px · bottom of viewport

h2 15. Links from the Website

1.10:1

#000000

#020F23

needs 3.0:1 (large text)

24px · bottom of viewport

h2 16. International Users

1.10:1

#000000

#020F23

needs 3.0:1 (large text)

24px · bottom of viewport

h2 17. Disclaimer of Warranties

1.10:1

#000000

#020F23

needs 3.0:1 (large text)

24px · bottom of viewport

h2 18. Limitation on Liability

1.10:1

#000000

#020F23

needs 3.0:1 (large text)

24px · bottom of viewport

h2 19. Indemnification

1.10:1

#000000

#020F23

needs 3.0:1 (large text)

24px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Terms of Use	1.10:1	3.0:1	#000000	#020F23	Fail
h2 1. Acceptance of the…	1.10:1	3.0:1	#000000	#020F23	Fail
h2 2. Changes to These …	1.10:1	3.0:1	#000000	#020F23	Fail
h2 3. Accessing the Web…	1.10:1	3.0:1	#000000	#020F23	Fail
h2 4. Our Copyrights	1.10:1	3.0:1	#000000	#020F23	Fail
h2 5. Our Trademarks	1.10:1	3.0:1	#000000	#020F23	Fail
h2 6.Prohibited Uses	1.10:1	3.0:1	#000000	#020F23	Fail
h2 7.User Contributions	1.10:1	3.0:1	#000000	#020F23	Fail
h2 8. Monitoring and En…	1.10:1	3.0:1	#000000	#020F23	Fail
h2 9. Content Standards	1.10:1	3.0:1	#000000	#020F23	Fail
h2 10. Intellectual Pro…	1.10:1	3.0:1	#000000	#020F23	Fail
h2 11. Reliance on Info…	1.10:1	3.0:1	#000000	#020F23	Fail
h2 12. Changes to the W…	1.10:1	3.0:1	#000000	#020F23	Fail
h2 13. Information Abou…	1.10:1	3.0:1	#000000	#020F23	Fail
h2 14. Linking to the W…	1.10:1	3.0:1	#000000	#020F23	Fail
h2 15. Links from the W…	1.10:1	3.0:1	#000000	#020F23	Fail
h2 16. International Us…	1.10:1	3.0:1	#000000	#020F23	Fail
h2 17. Disclaimer of Wa…	1.10:1	3.0:1	#000000	#020F23	Fail
h2 18. Limitation on Li…	1.10:1	3.0:1	#000000	#020F23	Fail
h2 19. Indemnification	1.10:1	3.0:1	#000000	#020F23	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+

Heading Hierarchy

28 headings

PASS

28 headings

Single H1 present

H3 Trending
H1 Terms of Use
H2 1. Acceptance of the Terms of Use
H2 2. Changes to These Terms of Use
H2 3. Accessing the Website and Account Security
H2 4. Our Copyrights
H2 5. Our Trademarks
H2 6.Prohibited Uses
H2 7.User Contributions
H2 8. Monitoring and Enforcement; Termination
H2 9. Content Standards
H2 10. Intellectual Property Infringement Policy
H2 11. Reliance on Information Posted
H2 12. Changes to the Website
H2 13. Information About You and Your Visits to the Website
H2 14. Linking to the Website and Interactive Features
H2 15. Links from the Website
H2 16. International Users
H2 17. Disclaimer of Warranties
H2 18. Limitation on Liability
H2 19. Indemnification
H2 20. Governing Law and Jurisdiction
H2 21. Dispute Resolution for Users Not in the United States or Canada
H2 22. Special Arbitration Provision - Dispute Resolution for Users in the United States or Canada
H2 23. Time Limit to Bring Any Claims
H2 24. Waiver and Severability
H2 25. Entire Agreement
H2 26. Your Comments and Concerns

A+

Heading Text Quality

All 28 heading(s) have substantive, well-formed text

PASS

All 28 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

Alt Text Quality

7 of 7 images have issues

PASS

7 of 7 images have issues

7 image(s) with generic alt text

7 images 7 generic

Issue	Count
generic	7 image(s)

Form Accessibility

1 of 3 controls have issues

PASS

1 of 3 controls have issues

1 control(s) rely on placeholder only

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

Got: <input type="text" name="tags" id="tags">

2 control(s) properly labeled

3 controls

2 labeled

1 placeholder only

0 unlabeled

Control	Type	Label	Method
#tos-age-checkbox	checkbox	I am 18 years of age or older.	for/id
#tos-terms-checkbox	checkbox	I have read and accept the Terms of Use.	for/id
#tags	text	(Search posts by tag)	placeholder only

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

A+

Link & Button Quality

1 issue(s) across 37 links and 4 buttons

PASS

1 issue(s) across 37 links and 4 buttons

1 link(s) with generic text

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

Got: /static/site_map ("More")

36 link(s) with descriptive text

37 links

0 empty

1 generic text

0 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/static/site_map	More	generic text	Replace with descriptive text
Before: More Suggested: Site Map

40 links and buttons have descriptive text

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

/static/site_map ("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

A+

Form Input Types

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

PASS

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

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

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

A+

Form Input Quality

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

PASS

3 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 229 visible text node(s) render at >= 12 CSS pixels

PASS

All 229 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

Browser-chrome `theme-color` meta tag present

The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.

A+

Lighthouse Accessibility Audits

Score 96/100 — 1 failing, 25 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
jessabelle's father (happyroadkill) `div.rising-left > div.rising-item > a.tag-type-4 > span.rising-link`

These are opportunities to improve the legibility of your content.

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

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

●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

●Touch targets have sufficient size and spacing.

●`[lang]` attributes have a valid value

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Uses ARIA roles only on compatible elements

○`[accesskey]` values are unique

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

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

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

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