Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

7 REVIEW 6 FIX

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

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

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.

Favicon & Branding

Action

1 icon(s) detected

FIX

1 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

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

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

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.

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: rgba(30, 32, 34, 1)

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

Action

3 landmarks

REVIEW

3 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

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

Heading Hierarchy

34 headings

REVIEW

34 headings

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 Promo GAS 50% di Bulan Juli
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

Alt Text Quality

Action

7 of 37 images have issues

REVIEW

7 of 37 images have issues

3 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

4 image(s) with generic alt text

1 image(s) with alt text over 125 characters

2 decorative image(s) correctly marked

27 image(s) with good alt text

37 images 27 good alt text 2 decorative 4 generic 3 missing

Issue	Count
missing	3 image(s)
generic	4 image(s)
too long	1 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

Form Accessibility

2 of 3 controls have issues

REVIEW

2 of 3 controls have issues

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

1 control(s) properly labeled

3 controls

1 labeled

2 placeholder only

0 unlabeled

Control	Type	Label	Method
#dontShowAgain	checkbox	Close	aria-label
#searchInputMobile	text	(Cari Game atau Voucher)	placeholder only
#searchInputDesktop	text	(Cari Game atau Voucher)	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

Link & Button Quality

Action

5 issue(s) across 61 links and 14 buttons

REVIEW

5 issue(s) across 61 links and 14 buttons

1 link(s) with no accessible text

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

Got: https://saldoxpres.com/id-id/articles/rilis-hero-baru-marcel-skin-starlight-m…

14 link(s) open in new tab without warning

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

Got: https://saldoxpres.com/id-id/articles; https://saldoxpres.com/id-id/docs; https://saldoxpres.com/id-id/articles; https://saldoxpres.com/id-id/docs; https://saldoxpres.com/id-id/articles/rilis-hero-baru-marcel-skin-starlight-m…; https://saldoxpres.com/id-id/articles; mailto:support@saldoxpres.com; https://www.instagram.com/-; https://t.me/-; https://www.instagram.com/- (+4 more)

4 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.inline-flex (#43 on page); button.inline-flex (#54 on page); button.inline-flex (#368 on page); button.inline-flex (#377 on page)

46 link(s) with descriptive text

61 links

1 empty

0 generic text

14 new tab

4 empty buttons

Element	Text	Issue	Suggested Fix
https://saldoxpres.com/id-id/articles	Artikel	new tab	Add '(opens in new tab)' to text
https://saldoxpres.com/id-id/docs	Dokumentasi API	new tab	Add '(opens in new tab)' to text
https://saldoxpres.com/id-id/articles	Artikel	new tab	Add '(opens in new tab)' to text
https://saldoxpres.com/id-id/docs	Dokumentasi API	new tab	Add '(opens in new tab)' to text
https://saldoxpres.com/id-id/articles/ri…	(empty)	empty	Add link text or aria-label
https://saldoxpres.com/id-id/articles/ri…	Rilis Hero Baru Marcel & Skin …	new tab	Add '(opens in new tab)' to text
https://saldoxpres.com/id-id/articles	Lihat Semua Artikel	new tab	Add '(opens in new tab)' to text
mailto:support@saldoxpres.com	Email	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/-	Instagram	new tab	Add '(opens in new tab)' to text
https://t.me/-	Telegram	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/-	Instagram	new tab	Add '(opens in new tab)' to text
https://www.tiktok.com/@-	Tiktok	new tab	Add '(opens in new tab)' to text
https://wa.me/6287766651424	Whatsapp	new tab	Add '(opens in new tab)' to text
https://wa.me/6287766651424	Whatsapp CS	new tab	Add '(opens in new tab)' to text
mailto:support@saldoxpres.com	Email	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

56 links and buttons have descriptive text

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

https://saldoxpres.com/id-id/articles/rilis-hero-baru-marcel-skin-starlight-m…

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://saldoxpres.com/id-id/articles; https://saldoxpres.com/id-id/docs; https://saldoxpres.com/id-id/articles; https://saldoxpres.com/id-id/docs; https://saldoxpres.com/id-id/articles/rilis-hero-baru-marcel-skin-starlight-m…; https://saldoxpres.com/id-id/articles; mailto:support@saldoxpres.com; https://www.instagram.com/-; https://t.me/-; https://www.instagram.com/- (+4 more)

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

Icon-only buttons need an aria-label so screen readers can announce them.

button.inline-flex (#43 on page); button.inline-flex (#54 on page); button.inline-flex (#368 on page); button.inline-flex (#377 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

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.07:1

#000000

#090B0E

needs 3.0:1 (large text)

24px · mid-page

h2 PUBG Mobile

1.07:1

#000000

#090B0E

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Free Fire

1.07:1

#000000

#0A0C0F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Mobile Legends

1.07:1

#000000

#0A0C0F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Call of Duty MOBILE

1.07:1

#000000

#0A0C0F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Ace Racer

1.07:1

#000000

#0A0C0F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Genshin Impact

1.07:1

#000000

#0A0C0F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Magic Chess : Go Go

1.07:1

#000000

#0A0C0F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 PUBG Mobile

1.07:1

#000000

#0A0C0F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Free Fire

1.07:1

#000000

#0A0C0F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Mobile Legends

1.07:1

#000000

#0A0C0F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Ragnarok M Eternal Love

1.07:1

#000000

#0A0C0F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Valorant

1.07:1

#000000

#0A0C0F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Point Blank

1.07:1

#000000

#0A0C0F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Arena of Valor

1.07:1

#000000

#0A0C0F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Blood Strike

1.07:1

#000000

#0A0C0F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Dana

1.07:1

#000000

#0A0C0F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Roblox

1.07:1

#000000

#0A0C0F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Alight Motion Premium

1.07:1

#000000

#0A0C0F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Canva Pro

1.07:1

#000000

#0A0C0F

needs 3.0:1 (large text)

24px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Magic Chess : Go Go	1.07:1	3.0:1	#000000	#090B0E	Fail
h2 PUBG Mobile	1.07:1	3.0:1	#000000	#090B0E	Fail
h2 Free Fire	1.07:1	3.0:1	#000000	#0A0C0F	Fail
h2 Mobile Legends	1.07:1	3.0:1	#000000	#0A0C0F	Fail
h2 Call of Duty MOBILE	1.07:1	3.0:1	#000000	#0A0C0F	Fail
h2 Ace Racer	1.07:1	3.0:1	#000000	#0A0C0F	Fail
h2 Genshin Impact	1.07:1	3.0:1	#000000	#0A0C0F	Fail
h2 Magic Chess : Go Go	1.07:1	3.0:1	#000000	#0A0C0F	Fail
h2 PUBG Mobile	1.07:1	3.0:1	#000000	#0A0C0F	Fail
h2 Free Fire	1.07:1	3.0:1	#000000	#0A0C0F	Fail
h2 Mobile Legends	1.07:1	3.0:1	#000000	#0A0C0F	Fail
h2 Ragnarok M Eternal L…	1.07:1	3.0:1	#000000	#0A0C0F	Fail
h2 Valorant	1.07:1	3.0:1	#000000	#0A0C0F	Fail
h2 Point Blank	1.07:1	3.0:1	#000000	#0A0C0F	Fail
h2 Arena of Valor	1.07:1	3.0:1	#000000	#0A0C0F	Fail
h2 Blood Strike	1.07:1	3.0:1	#000000	#0A0C0F	Fail
h2 Dana	1.07:1	3.0:1	#000000	#0A0C0F	Fail
h2 Roblox	1.07:1	3.0:1	#000000	#0A0C0F	Fail
h2 Alight Motion Premiu…	1.07:1	3.0:1	#000000	#0A0C0F	Fail
h2 Canva Pro	1.07:1	3.0:1	#000000	#0A0C0F	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 75/100 — 6 failing, 22 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.