Skip to content
https://www.bisecthosting.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
74
GRADE
C
FIX
7
REVIEW
5
PASS
12
INFO
0
Checks
24
12 PASS 5 REVIEW 7 FIX
F
Alt Text Quality
Action
31 of 113 images have issues
FIX
31 of 113 images have issues
Critical::
30 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
30 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Warning::
1 image(s) with generic alt text
Info::
82 image(s) with good alt text
113 images 82 good alt text 1 generic 30 missing
IssueCount
missing30 image(s)
generic1 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

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

D
404 Error Page
Action
HTTP 404, custom page
FIX
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
D
Favicon & Branding
Action
4 icon(s) detected
FIX
4 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
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'>.
Info::
SVG favicon detected — scales perfectly to any size
✓ favicon.ico Present
✓ PNG Icons Present
✗ Apple Touch Missing
✓ SVG Favicon Present
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
D
Web Manifest
Action
Not found
FIX
Not found
Info::
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.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
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.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
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 ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
1 navigation landmark(s) detected
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 1 <nav> element(s)
Back to Top
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.
C
Form Accessibility
Action
4 of 9 controls have issues
REVIEW
4 of 9 controls have issues
Critical::
4 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonNecessaryInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonPreferencesInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonStatisticsInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonMarketingInline">
Info::
5 control(s) properly labeled
9 controls
5 labeled
0 placeholder only
4 unlabeled
ControlTypeLabelMethod
#CybotCookiebotDialogBodyLevelButtonNecessarycheckboxNecessaryfor/id
#CybotCookiebotDialogBodyLevelButtonPreferencescheckboxPreferencesfor/id
#CybotCookiebotDialogBodyLevelButtonStatisticscheckboxStatisticsfor/id
#CybotCookiebotDialogBodyLevelButtonMarketingcheckboxMarketingfor/id
#CybotCookiebotDialogBodyContentCheckboxPersonalInformationcheckboxDo not sell or share my personal informationfor/id
#CybotCookiebotDialogBodyLevelButtonPreferencesInlinecheckbox(none)none
#CybotCookiebotDialogBodyLevelButtonStatisticsInlinecheckbox(none)none
#CybotCookiebotDialogBodyLevelButtonMarketingInlinecheckbox(none)none
#CybotCookiebotDialogBodyLevelButtonNecessaryInlinecheckbox(none)none

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

<input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonNecessaryInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonPreferencesInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonStatisticsInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonMarketingInline">

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

B
Tabindex Anti-Patterns
0 positive, 4 -1-on-focusable
REVIEW
0 positive, 4 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <a id="CybotCookiebotDialogPoweredbyCybot">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a id="CybotCookiebotDialogNavDetails">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a id="CybotCookiebotDialogNavAdSettings">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a id="CybotCookiebotDialogNavAbout">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
B
Iframe Accessibility
2/5 iframe(s) missing title; 0 placeholder(s)
REVIEW
2/5 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="https://js.stripe.com/v3/m-outer-3437aaddcdf6922d623e172c2d6f9278.html#url=http…")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
C
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 MINECRAFT SERVER HOSTING
1.02:1
#000000
on
#02030A
needs 3.0:1 (large text)
32px · bottom of viewport
h2 AND 110+ TOP ONLINE GAMES
1.02:1
#000000
on
#02030A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Your
1.02:1
#000000
on
#02030A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Partner
1.02:1
#000000
on
#02030A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Other Games
1.02:1
#000000
on
#02030A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 OUR features
1.02:1
#000000
on
#02030A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 SERVER HOSTING FOR MINECRAFT & TOP GAMES…
1.02:1
#000000
on
#02030A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 WHY BISECTHOSTING?
1.02:1
#000000
on
#02030A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 FREQUENTLY ASKED QUESTIONS
1.02:1
#000000
on
#02030A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 GO BEYOND GAMING
1.02:1
#000000
on
#02030A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 START HERE
1.02:1
#000000
on
#02030A
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Minecraft
1.02:1
#000000
on
#02030A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Wardogs
1.02:1
#000000
on
#02030A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Hytale
1.02:1
#000000
on
#02030A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Valheim
1.02:1
#000000
on
#02030A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Terraria
1.02:1
#000000
on
#02030A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Project Zomboid
1.02:1
#000000
on
#02030A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Palworld
1.02:1
#000000
on
#02030A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Farming Simulator 25
1.02:1
#000000
on
#02030A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 OUR SUPPORT TEAM IS AVAILABLE 24/7/365
1.02:1
#000000
on
#02030A
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 MINECRAFT SERVER HOS…1.02:13.0:1
#000000
#02030A
Fail
h2 AND 110+ TOP ONLINE …1.02:13.0:1
#000000
#02030A
Fail
h2 Your1.02:13.0:1
#000000
#02030A
Fail
h2 Partner1.02:13.0:1
#000000
#02030A
Fail
h2 Other Games1.02:13.0:1
#000000
#02030A
Fail
h2 OUR features1.02:13.0:1
#000000
#02030A
Fail
h2 SERVER HOSTING FOR M…1.02:13.0:1
#000000
#02030A
Fail
h2 WHY BISECTHOSTING?1.02:13.0:1
#000000
#02030A
Fail
h2 FREQUENTLY ASKED QUE…1.02:13.0:1
#000000
#02030A
Fail
h2 GO BEYOND GAMING1.02:13.0:1
#000000
#02030A
Fail
h2 START HERE1.02:13.0:1
#000000
#02030A
Fail
h3 Minecraft1.02:13.0:1
#000000
#02030A
Fail
h3 Wardogs1.02:13.0:1
#000000
#02030A
Fail
h3 Hytale1.02:13.0:1
#000000
#02030A
Fail
h3 Valheim1.02:13.0:1
#000000
#02030A
Fail
h3 Terraria1.02:13.0:1
#000000
#02030A
Fail
h3 Project Zomboid1.02:13.0:1
#000000
#02030A
Fail
h3 Palworld1.02:13.0:1
#000000
#02030A
Fail
h3 Farming Simulator 251.02:13.0:1
#000000
#02030A
Fail
h3 OUR SUPPORT TEAM IS …1.02:13.0:1
#000000
#02030A
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
Landmark Structure
5 landmarks
PASS
5 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Warning::
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
BANNER header NAV MAIN CONTENTINFO footer

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

A+
Heading Hierarchy
36 headings
PASS
36 headings
Info::
Single H1 present
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H1 MINECRAFT SERVER HOSTING
  • H2 AND 110+ TOP ONLINE GAMES
  • H2 Your Ultimate Gaming Partner™
  • H2 Other Games
  • H3 Minecraft
  • H3 Wardogs
  • H3 Hytale
  • H3 Valheim
  • H3 Terraria
  • H3 Project Zomboid
  • H3 Palworld
  • H3 Farming Simulator 25
  • H2 OUR features
  • H2 SERVER HOSTING FOR MINECRAFT & TOP GAMES MADE EASY
  • H3 (empty)
  • H3 Out of stock
  • H2 WHY BISECTHOSTING?
  • H3 OUR SUPPORT TEAM IS AVAILABLE 24/7/365
  • H3 POWERFUL CONTROL PANEL FOR EASY SERVER MANAGEMENT
  • H3 TRUSTED HOST, MINECRAFT COMMUNITY APPROVED
  • H3 MODDED MINECRAFT SERVERS ARE OUR SPECIALTY
  • H3 HOST MORE THAN MINECRAFT SERVERS
  • H3 OUR KNOWLEDGEBASE IS HERE TO HELP
  • H3 Welcome to BisectHosting!
  • H2 FREQUENTLY ASKED QUESTIONS
  • H2 GO BEYOND GAMING
  • H3 Web hosting
  • H3 Voice servers
  • H3 VPS servers
  • H3 Dedicated servers
  • H2 START HERE
  • H3 Company
  • H3 Services
  • H3 Customers
  • H3 Legal
  • H3 Social

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

A+
Heading Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Info::
13 heading(s) are all-uppercase (excluding short acronyms)
Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.
Got: 13 all-caps heading(s)
A+
Form Input Types
9 form control(s) checked, no type mismatches
PASS
9 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
9 form control(s) checked, no input-semantic issues
PASS
9 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
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"
Info::
<html lang="en"> is set and valid
Got: en
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
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
Mobile-Readable Font Sizes
All 127 visible text node(s) render at >= 12 CSS pixels
PASS
All 127 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
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.
A
Lighthouse Accessibility Audits
Score 94/100 — 2 failing, 27 passed
PASS
94

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
Consent div#CybotCookiebotDialogNav > ul#CybotCookiebotDialogNavList > li.CybotCookiebotDialogNavItem > a#CybotCookiebotDialogNavDeclaration
Privacy Policy div#CybotCookiebotDialogBodyContentText > p > a > span

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
110+ games ul.list-none > li.relative > span.ml-2 > a
BisectOne ul.list-none > li.relative > span.ml-2 > a

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
●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
●`[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.
●ARIA attributes are used as specified for the element's role
●`[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 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
●`<object>` elements have alternate text
●No element has a `[tabindex]` value greater than 0
●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
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○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
○Form elements have associated labels
○The document does not use `<meta http-equiv="refresh">`
○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.
○`<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.

Send Feedback