Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

2 PASS 5 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

Form Accessibility

Action

10 of 10 controls have issues

FIX

10 of 10 controls have issues

4 control(s) without accessible label

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

Got: <input type="checkbox" name="someData">; <input type="image" id="fb-reg">; <input type="checkbox" name="someData">; <input type="image" id="fb-reg">

6 control(s) rely on placeholder only

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

Got: <input type="text" name="name">; <input type="text" name="email" id="ca-email">; <input type="password" name="password">; <input type="text" name="name">; <input type="text" name="email" id="ca-email">; <input type="password" name="password">

10 controls

0 labeled

6 placeholder only

4 unlabeled

Control	Type	Label	Method
name	text	(username)	placeholder only
#ca-email	text	(email address)	placeholder only
password	password	(password)	placeholder only
name	text	(username)	placeholder only
#ca-email	text	(email address)	placeholder only
password	password	(password)	placeholder only
#fb-reg	image	(none)	none
someData	checkbox	(none)	none
someData	checkbox	(none)	none
#fb-reg	image	(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

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 ✗

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.

Alt Text Quality

5 of 8 images have issues

REVIEW

5 of 8 images have issues

1 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

4 image(s) with filename as alt text

3 image(s) with good alt text

8 images 3 good alt text 4 generic 1 missing

Issue	Count
missing	1 image(s)
filename	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

404 Error Page

HTTP 404, custom page

REVIEW

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

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Wikidot - Free and Pro Wiki Hosting ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Favicon & Branding

Action

5 icon(s) detected

REVIEW

5 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, 17 fail WCAG AA

REVIEW

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

3 pass 17 fail WCAG AA 1 pass AA only

title Wikidot - Free and Pro Wiki Hosting

1.32:1

#000000

#222222

needs 4.5:1 (normal text)

16px · top of page (header area)

span Toggle navigation

1.32:1

#000000

#222222

needs 4.5:1 (normal text)

16px · top of page (header area)

div your place on the web

1.32:1

#000000

#222222

needs 4.5:1 (normal text)

16px · top of page (header area)

a Create account

1.40:1

#000000

#002A3F

needs 4.5:1 (normal text)

16px · top of page (header area)

a Sign in

1.43:1

#000000

#002C3F

needs 4.5:1 (normal text)

16px · above the fold

a Features

1.48:1

#000000

#002F40

needs 4.5:1 (normal text)

16px · above the fold

a Opinions

1.53:1

#000000

#003240

needs 4.5:1 (normal text)

16px · above the fold

a Pricing

1.57:1

#000000

#003440

needs 4.5:1 (normal text)

16px · above the fold

a Advertising

1.64:1

#000000

#003841

needs 4.5:1 (normal text)

16px · above the fold

span Please leave this checkbox blank

2.43:1

#000000

#514C34

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

button Sign up

1.35:1

#000000

#1D2621

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

div By creating an account you accept our

2.15:1

#000000

#2F4941

needs 4.5:1 (normal text)

16px · mid-page

a Terms of Service

2.49:1

#000000

#465043

needs 4.5:1 (normal text)

16px · mid-page

div and

2.45:1

#000000

#494E42

needs 4.5:1 (normal text)

16px · mid-page

a Privacy Policy

1.27:1

#000000

#0F221F

needs 4.5:1 (normal text)

16px · mid-page · over background image/gradient

p Wikidot does not modify your Facebook pr…

2.32:1

#000000

#4D4935

needs 4.5:1 (normal text)

16px · mid-page

span What is Wikidot?

3.11:1

#F24747

#3C3B2D

needs 4.5:1 (normal text)

16px · mid-page

3 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Create account	3.45:1	3.0:1	#000000	#66634C	Pass
h1 Create account	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 You control your pri…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Wikidot - Free and P…	1.32:1	4.5:1	#000000	#222222	Fail
span Toggle navigation	1.32:1	4.5:1	#000000	#222222	Fail
div your place on the we…	1.32:1	4.5:1	#000000	#222222	Fail
a Create account	1.40:1	4.5:1	#000000	#002A3F	Fail
a Sign in	1.43:1	4.5:1	#000000	#002C3F	Fail
a Features	1.48:1	4.5:1	#000000	#002F40	Fail
a Opinions	1.53:1	4.5:1	#000000	#003240	Fail
a Pricing	1.57:1	4.5:1	#000000	#003440	Fail
a Advertising	1.64:1	4.5:1	#000000	#003841	Fail
span Please leave this ch…	2.43:1	4.5:1	#000000	#514C34	Fail
button Sign up	1.35:1	4.5:1	#000000	#1D2621	Fail
div By creating an accou…	2.15:1	4.5:1	#000000	#2F4941	Fail
a Terms of Service	2.49:1	4.5:1	#000000	#465043	Fail
div and	2.45:1	4.5:1	#000000	#494E42	Fail
a Privacy Policy	1.27:1	4.5:1	#000000	#0F221F	Fail
p Wikidot does not mod…	2.32:1	4.5:1	#000000	#4D4935	Fail
span What is Wikidot?	3.11:1	4.5:1	#F24747	#3C3B2D	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 76/100 — 5 failing, 16 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.

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
Sign in `nav.navbar > div.navbar-header > div.loginStatus > a.login-status-sign-in`
Sign up `div.path > div.ca-form > form#createaccount-forme0dd531b2700b947778f0466863cb9b3 > button.button`
Sign up `div.path > div.ca-form > form#createaccount-form30540a8a19c0923d4ad336fcb548b57b > button.button`

These are opportunities to improve the legibility of your content.

Names and labels

When an image is being used as an `<input>` button, providing alternative text can help screen reader users understand the purpose of the button. Learn about input image alt text.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
div.login-paths > div.path > div.fb-connect-start > input#fb-reg `div.login-paths > div.path > div.fb-connect-start > input#fb-reg`
div.login-paths > div.path > div.fb-connect-start > input#fb-reg `div.login-paths > div.path > div.fb-connect-start > input#fb-reg`

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
form#createaccount-forme0dd531b2700b947778f0466863cb9b3 > div.form-group > div.input-group > input `form#createaccount-forme0dd531b2700b947778f0466863cb9b3 > div.form-group > div.input-group > input`
form#createaccount-form30540a8a19c0923d4ad336fcb548b57b > div.form-group > div.input-group > input `form#createaccount-form30540a8a19c0923d4ad336fcb548b57b > div.form-group > div.input-group > input`

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
nav.navbar > div.navbar-header > div.site-name > a.navbar-brand `nav.navbar > div.navbar-header > div.site-name > a.navbar-brand`

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

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

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

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

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

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

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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

●Deprecated ARIA roles were not used

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

○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

○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

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

○Input buttons have discernible 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.

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

Heading Hierarchy

6 headings

PASS

6 headings

Multiple H1 headings (5 found)

A page should have only one H1. Multiple H1s dilute the document outline.

H1 Create account
H1 or duplicate H1
H1 What is Wikidot? duplicate H1
H1 Create account duplicate H1
H1 or duplicate H1
H2 You control your privacy

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

Link & Button Quality

1 issue(s) across 31 links and 5 buttons

PASS

1 issue(s) across 31 links and 5 buttons

1 link(s) with no accessible text

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

Got: /

1 link(s) open in new tab without warning

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

Got: https://nitropay.com

29 link(s) with descriptive text

31 links

1 empty

0 generic text

1 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/	(empty)	empty	Add link text or aria-label
https://nitropay.com	NitroPay	new tab	Add '(opens in new tab)' to text

34 links and buttons have descriptive text

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

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://nitropay.com

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

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