Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

11 PASS 7 REVIEW 6 FIX

Mobile Keyboard & Autofill

Action

1/1 eligible field(s) missing autocomplete or inputmode

FIX

1/1 eligible field(s) missing autocomplete or inputmode

1 field(s) missing recommended autocomplete attribute

WCAG 1.3.5 (Level AA): inputs whose purpose maps to a Common Input Purpose value should declare it via `autocomplete=`. Required for password managers, browser autofill, and assistive tech that customizes inputs (e.g., simplified keyboards). Mobile autofill in particular cuts form-completion time by 30-50% when these are present. Affected purposes: current-password.

Got: <input type="password">

Favicon & Branding

Action

3 icon(s) detected

FIX

3 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

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 ✗

Landmark Structure

3 landmarks

REVIEW

3 landmarks

<main> landmark present

No <nav> landmark found

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

Form Accessibility

Action

3 of 3 controls have issues

REVIEW

3 of 3 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="password">

2 control(s) rely on placeholder only

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

Got: <input type="text">; <input type="text" name="domain">

3 controls

0 labeled

2 placeholder only

1 unlabeled

Control	Type	Label	Method
input	text	(Your login...)	placeholder only
domain	text	(Website, DOI or URL of the Wikipedia article...)	placeholder only
input	password	(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

Link & Button Quality

2 issue(s) across 218 links and 8 buttons

REVIEW

2 issue(s) across 218 links and 8 buttons

2 link(s) with no accessible text

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

Got: #; https://twitter.com/bestrefnet

216 link(s) with descriptive text

218 links

2 empty

0 generic text

0 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
#	(empty)	empty	Add link text or aria-label
https://www.wikipedia.org/	Wikipedia	img no alt	Add alt attribute to the image
https://twitter.com/bestrefnet	(empty)	empty	Add link text or aria-label
#header	Go to top	img no alt	Add alt attribute to the image

224 links and buttons have descriptive text

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

#; https://twitter.com/bestrefnet

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

Form Input Quality

2 input-semantic issue(s) across 3 form control(s)

REVIEW

2 input-semantic issue(s) across 3 form control(s)

1 password field(s) missing or with invalid `autocomplete`

Password managers fill / save passwords only when `autocomplete` is exactly `current-password` (login) or `new-password` (registration / change). Empty, `off`, `password`, or other values silently disable the manager UX. Sample: <input type="password">.

1 login form field(s) missing `autocomplete=username` (or `email`)

On a page with a password input, the matching username / email field needs `autocomplete="username"` or `autocomplete="email"` -- otherwise the password manager can't identify which field carries the login identifier and silently skips autofill on the whole form. Sample: <input type="text">.

Mobile-Readable Font Sizes

99% of visible text renders at >= 12 CSS px (1 below threshold)

REVIEW

99% of visible text renders at >= 12 CSS px (1 below threshold)

1 text node(s) render below 12 CSS pixels on mobile

Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <p> 11.0px ("Search").

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.

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 The best information sources of Wikipedi…

1.31:1

#000000

#232121

needs 3.0:1 (large text)

32px · bottom of viewport

title The best information sources of the The …

1.17:1

#000000

#23130F

needs 4.5:1 (normal text)

16px · top of page (header area)

a Home

1.13:1

#000000

#1D100D

needs 4.5:1 (normal text)

16px · top of page (header area) · over background image/gradient

a Languages

1.23:1

#000000

#2B1611

needs 4.5:1 (normal text)

16px · top of page (header area) · over background image/gradient

a Topics

2.60:1

#000000

#6C4738

needs 4.5:1 (normal text)

16px · top of page (header area) · over background image/gradient

a About

1.29:1

#000000

#2E1B1B

needs 4.5:1 (normal text)

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

button Login

1.12:1

#000000

#160F18

needs 4.5:1 (normal text)

16px · above the fold

button Sign in

1.07:1

#000000

#0C0C0D

needs 4.5:1 (normal text)

16px · above the fold

button Login

1.12:1

#000000

#121212

needs 4.5:1 (normal text)

16px · above the fold

button Sign in

4.04:1

#000000

#876824

needs 4.5:1 (normal text)

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

a Home

1.69:1

#000000

#3E3317

needs 4.5:1 (normal text)

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

a Languages

1.21:1

#000000

#1B1A1A

needs 4.5:1 (normal text)

16px · above the fold

a Topics

1.30:1

#000000

#222020

needs 4.5:1 (normal text)

16px · above the fold

a About

1.31:1

#000000

#232121

needs 4.5:1 (normal text)

16px · above the fold

span Sign In

1.30:1

#000000

#222020

needs 4.5:1 (normal text)

16px · mid-page

button Connect with Facebook

1.30:1

#000000

#222020

needs 4.5:1 (normal text)

16px · mid-page

button Connect with Google

1.30:1

#000000

#222020

needs 4.5:1 (normal text)

16px · mid-page

p Login

1.31:1

#000000

#232121

needs 4.5:1 (normal text)

16px · mid-page

p Password

1.30:1

#000000

#222020

needs 4.5:1 (normal text)

16px · mid-page

a Forgot Password ?

1.28:1

#000000

#211F1F

needs 4.5:1 (normal text)

16px · mid-page

6 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 The best information…	1.31:1	3.0:1	#000000	#232121	Fail
title The best information…	1.17:1	4.5:1	#000000	#23130F	Fail
a Home	1.13:1	4.5:1	#000000	#1D100D	Fail
a Languages	1.23:1	4.5:1	#000000	#2B1611	Fail
a Topics	2.60:1	4.5:1	#000000	#6C4738	Fail
a About	1.29:1	4.5:1	#000000	#2E1B1B	Fail
button Login	1.12:1	4.5:1	#000000	#160F18	Fail
button Sign in	1.07:1	4.5:1	#000000	#0C0C0D	Fail
button Login	1.12:1	4.5:1	#000000	#121212	Fail
button Sign in	4.04:1	4.5:1	#000000	#876824	Fail
a Home	1.69:1	4.5:1	#000000	#3E3317	Fail
a Languages	1.21:1	4.5:1	#000000	#1B1A1A	Fail
a Topics	1.30:1	4.5:1	#000000	#222020	Fail
a About	1.31:1	4.5:1	#000000	#232121	Fail
span Sign In	1.30:1	4.5:1	#000000	#222020	Fail
button Connect with Faceboo…	1.30:1	4.5:1	#000000	#222020	Fail
button Connect with Google	1.30:1	4.5:1	#000000	#222020	Fail
p Login	1.31:1	4.5:1	#000000	#232121	Fail
p Password	1.30:1	4.5:1	#000000	#222020	Fail
a Forgot Password ?	1.28:1	4.5:1	#000000	#211F1F	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

3 headings, 1 skip(s)

PASS

3 headings, 1 skip(s)

Single H1 present

Heading level skipped: H1 → H4 (missing H2)

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

H1 The best information sources of Wikipedia
H4 BestRef.net (ver. 1.03) skipped
H4 Usefull links

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

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

PASS

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

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

A+

Alt Text Quality

All 11 images OK

PASS

All 11 images OK

10 decorative image(s) correctly marked

1 image(s) with good alt text

11 images 1 good alt text 10 decorative

All images have appropriate alt text.

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 "domain" should use type="url" (currently type="text")

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

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+

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 92/100 — 2 failing, 14 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
BESTREF.NET (VER. 1.03) `div.footer__info > div.footer__nav > div.footer__info--site > h4.footer__nav--mainTitle`

These are opportunities to improve keyboard navigation in your application.

Names and labels

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
div.container > div.footer__bottom > div.footer__social > a `div.container > div.footer__bottom > div.footer__social > a`

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.

○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

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

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

●Document has a main landmark.

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

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