Skip to content
https://saldoxpres.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
45
GRADE
F
FIX
6
REVIEW
7
PASS
0
INFO
0
Checks
13
7 REVIEW 6 FIX
F
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
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-9tit5d
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.

F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
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'>.
✗ favicon.ico Missing
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://saldoxpres.com/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://saldoxpres.com/manifest.json

Manifest contains invalid JSON.

D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
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: rgba(30, 32, 34, 1)
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 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.

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
Landmark Structure
Action
3 landmarks
REVIEW
3 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
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 (missing!) CONTENTINFO footer

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

B
Heading Hierarchy
33 headings
REVIEW
33 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H3 🔥 TRENDING
  • H2 Magic Chess : Go Go
  • H2 PUBG Mobile
  • H2 Free Fire
  • H2 Mobile Legends
  • H3 Top Up Game
  • H2 Call of Duty MOBILE
  • H2 Ace Racer
  • H2 Genshin Impact
  • H2 Magic Chess : Go Go
  • H2 PUBG Mobile
  • H2 Free Fire
  • H2 Mobile Legends
  • H2 Ragnarok M Eternal Love
  • H2 Valorant
  • H2 Point Blank
  • H2 Arena of Valor
  • H2 Blood Strike
  • H2 Dana
  • H2 Roblox
  • H2 Alight Motion Premium
  • H2 Canva Pro
  • H2 CapCut Pro
  • H2 Bstation Premium
  • H2 Amazon Prime Video
  • H2 Spotify Premium
  • H2 FREE FIRE MAX
  • H3 Artikel Terbaru & Berita Game
  • H2 Footer
  • H3 Peta Situs
  • H3 Kemitraan
  • H3 Dukungan
  • H3 Legalitas

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

C
Alt Text Quality
Action
7 of 36 images have issues
REVIEW
7 of 36 images have issues
Critical::
3 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Warning::
4 image(s) with generic alt text
Info::
1 image(s) with alt text over 125 characters
Info::
1 decorative image(s) correctly marked
Info::
27 image(s) with good alt text
36 images 27 good alt text 1 decorative 4 generic 3 missing
IssueCount
missing3 image(s)
generic4 image(s)
too long1 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

B
Form Accessibility
2 of 2 controls have issues
REVIEW
2 of 2 controls have issues
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" id="searchInputDesktop">; <input type="text" id="searchInputMobile">
2 controls
0 labeled
2 placeholder only
0 unlabeled
ControlTypeLabelMethod
#searchInputDesktoptext(Cari Game atau Voucher)placeholder only
#searchInputMobiletext(Cari Game atau Voucher)placeholder only

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

<input type="text" id="searchInputDesktop">; <input type="text" id="searchInputMobile">

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

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
h2 Magic Chess : Go Go
1.16:1
#000000
on
#13161C
needs 3.0:1 (large text)
24px · mid-page
h2 PUBG Mobile
1.16:1
#000000
on
#13161C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Free Fire
1.16:1
#000000
on
#13161C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Mobile Legends
1.16:1
#000000
on
#13161C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Call of Duty MOBILE
1.16:1
#000000
on
#13161C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Ace Racer
1.16:1
#000000
on
#13161C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Genshin Impact
1.16:1
#000000
on
#13161C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Magic Chess : Go Go
1.16:1
#000000
on
#13161C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 PUBG Mobile
1.16:1
#000000
on
#13161C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Free Fire
1.16:1
#000000
on
#13161C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Mobile Legends
1.16:1
#000000
on
#13161C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Ragnarok M Eternal Love
1.16:1
#000000
on
#13161C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Valorant
1.16:1
#000000
on
#13161C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Point Blank
1.16:1
#000000
on
#13161C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Arena of Valor
1.16:1
#000000
on
#13161C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Blood Strike
1.16:1
#000000
on
#13161C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Dana
1.16:1
#000000
on
#13161C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Roblox
1.16:1
#000000
on
#13161C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Alight Motion Premium
1.16:1
#000000
on
#13161C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Canva Pro
1.16:1
#000000
on
#13161C
needs 3.0:1 (large text)
24px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Magic Chess : Go Go1.16:13.0:1
#000000
#13161C
Fail
h2 PUBG Mobile1.16:13.0:1
#000000
#13161C
Fail
h2 Free Fire1.16:13.0:1
#000000
#13161C
Fail
h2 Mobile Legends1.16:13.0:1
#000000
#13161C
Fail
h2 Call of Duty MOBILE1.16:13.0:1
#000000
#13161C
Fail
h2 Ace Racer1.16:13.0:1
#000000
#13161C
Fail
h2 Genshin Impact1.16:13.0:1
#000000
#13161C
Fail
h2 Magic Chess : Go Go1.16:13.0:1
#000000
#13161C
Fail
h2 PUBG Mobile1.16:13.0:1
#000000
#13161C
Fail
h2 Free Fire1.16:13.0:1
#000000
#13161C
Fail
h2 Mobile Legends1.16:13.0:1
#000000
#13161C
Fail
h2 Ragnarok M Eternal L…1.16:13.0:1
#000000
#13161C
Fail
h2 Valorant1.16:13.0:1
#000000
#13161C
Fail
h2 Point Blank1.16:13.0:1
#000000
#13161C
Fail
h2 Arena of Valor1.16:13.0:1
#000000
#13161C
Fail
h2 Blood Strike1.16:13.0:1
#000000
#13161C
Fail
h2 Dana1.16:13.0:1
#000000
#13161C
Fail
h2 Roblox1.16:13.0:1
#000000
#13161C
Fail
h2 Alight Motion Premiu…1.16:13.0:1
#000000
#13161C
Fail
h2 Canva Pro1.16:13.0:1
#000000
#13161C
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.

C
Lighthouse Accessibility Audits
Action
Score 72/100 — 7 failing, 19 passed
REVIEW
72

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.

ARIA

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Games Emoney Streaming Pulsa div.relative > div.flex > div.container > div

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.border-b > div.container > div.flex > button.inline-flex div.border-b > div.container > div.flex > button.inline-flex
div.container > div.flex > div.block > button.inline-flex div.container > div.flex > div.block > button.inline-flex
div > div.flex > div.block > button.inline-flex div > div.flex > div.block > button.inline-flex
div > div.flex > div.block > button.inline-flex div > div.flex > div.block > button.inline-flex

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.swiper > div#swiper-wrapper-46a6df7bfcec10d310 > div.swiper-slide > img.rounded-3xl div.swiper > div#swiper-wrapper-46a6df7bfcec10d310 > div.swiper-slide > img.rounded-3xl
div.swiper > div#swiper-wrapper-46a6df7bfcec10d310 > div.swiper-slide > img.rounded-3xl div.swiper > div#swiper-wrapper-46a6df7bfcec10d310 > div.swiper-slide > img.rounded-3xl

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.my-8 > div.container > div#berita-container > a.group div.my-8 > div.container > div#berita-container > a.group

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.

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
Games div > div.flex > div#tabScrollContainer > button.tab

These are opportunities to improve the legibility of your content.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Call of Duty MOBILE Garena Ace Racer NetEase Genshin Impact HoYoverse Mag… div.flex > div.container > div > ul.my-8

These are opportunities to improve the experience of reading tabular or list data using 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.dark html.dark

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-*]` 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
●`[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
●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.
●Heading elements appear in a sequentially-descending order
●Deprecated ARIA roles were not used
●Elements with visible text labels have matching accessible names.
○`[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
○`[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
○Form elements have associated labels
○Links are distinguishable without relying on color.
○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.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○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.

Send Feedback