Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

15 PASS 7 REVIEW 2 FIX

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

3 navigation landmark(s) detected

Hamburger menu detected (responsive design)

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 3 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

Landmark Structure

13 landmarks

REVIEW

13 landmarks

<main> landmark present

3 <nav> landmark(s) found

1 of 3 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

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

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

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

Mobile-Readable Font Sizes

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

REVIEW

98% 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: <span> 10.0px ("New").

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 RobuxKinun - Cheap & Safe Robux in Bangladesh ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Favicon & Branding

6 icon(s) detected

REVIEW

6 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✓ Manifest Icons Present

✓ Multiple Sizes Present

Web Manifest

Valid manifest

REVIEW

Valid manifest

Name present: RobuxKinun

No 192x192 icon

A 192px icon is required for PWA installation.

512x512 icon present

Display mode: standalone

PWA Install Criteria Not Installable

Name RobuxKinun ✓192×192 icon ✗512×512 icon ✓Start URL / ✓Display Mode standalone ✓

Name RobuxKinun Display Mode standalone Theme Color #14161D Background Color #14161D Icons 2 icon(s)

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

color-scheme meta tag present

The site declares support for light and dark color schemes via <meta name='color-scheme'>.

Got: dark

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: #14161d

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark Mode✓ Dark Mode Supported

color-scheme meta dark ✓Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

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 Games

1.00:1

#000000

needs 3.0:1 (large text)

24px · mid-page

h2 Gift Cards

1.13:1

#000000

#111318

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Best sellers

1.13:1

#000000

#111318

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Your order in

1.13:1

#000000

#111318

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Player Reviews

1.13:1

#000000

#111318

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Why choose

1.13:1

#000000

#111318

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Before you buy.

1.13:1

#000000

#111318

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Shops

1.13:1

#000000

#111318

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Support

1.13:1

#000000

#111318

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Legal

1.13:1

#000000

#111318

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Blox Fruits

1.15:1

#000000

#13151C

needs 3.0:1 (large text)

19px · mid-page

h3 Rivals

1.15:1

#000000

#13151C

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Murder Mystery 2

1.13:1

#000000

#111318

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Choose a game

1.13:1

#000000

#111318

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Complete payment

1.13:1

#000000

#111318

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Get it delivered

1.13:1

#000000

#111318

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Instant Delivery

1.13:1

#000000

#111318

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Safe for Your Account

1.13:1

#000000

#111318

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Best Prices in Bangladesh

1.13:1

#000000

#111318

needs 3.0:1 (large text)

19px · bottom of viewport

h3 24/7 Support

1.13:1

#000000

#111318

needs 3.0:1 (large text)

19px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Games	1.00:1	3.0:1	#000000	#000000	Fail
h2 Gift Cards	1.13:1	3.0:1	#000000	#111318	Fail
h2 Best sellers	1.13:1	3.0:1	#000000	#111318	Fail
h2 Your order in	1.13:1	3.0:1	#000000	#111318	Fail
h2 Player Reviews	1.13:1	3.0:1	#000000	#111318	Fail
h2 Why choose	1.13:1	3.0:1	#000000	#111318	Fail
h2 Before you buy.	1.13:1	3.0:1	#000000	#111318	Fail
h2 Shops	1.13:1	3.0:1	#000000	#111318	Fail
h2 Support	1.13:1	3.0:1	#000000	#111318	Fail
h2 Legal	1.13:1	3.0:1	#000000	#111318	Fail
h3 Blox Fruits	1.15:1	3.0:1	#000000	#13151C	Fail
h3 Rivals	1.15:1	3.0:1	#000000	#13151C	Fail
h3 Murder Mystery 2	1.13:1	3.0:1	#000000	#111318	Fail
h3 Choose a game	1.13:1	3.0:1	#000000	#111318	Fail
h3 Complete payment	1.13:1	3.0:1	#000000	#111318	Fail
h3 Get it delivered	1.13:1	3.0:1	#000000	#111318	Fail
h3 Instant Delivery	1.13:1	3.0:1	#000000	#111318	Fail
h3 Safe for Your Accoun…	1.13:1	3.0:1	#000000	#111318	Fail
h3 Best Prices in Bangl…	1.13:1	3.0:1	#000000	#111318	Fail
h3 24/7 Support	1.13:1	3.0:1	#000000	#111318	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+

Heading Hierarchy

34 headings

PASS

34 headings

Single H1 present

H1 Robux in Minutes.Pay Your Way.
H2 Games
H3 Blox Fruits
H3 Rivals
H3 Murder Mystery 2
H2 Gift Cards
H3 Roblox Gift Card $10
H3 Roblox Gift Card $25
H3 Roblox Gift Card $50
H2 Best sellers
H3 Kitsune
H3 Dragon
H3 Buddha
H3 2x Drop Chance
H2 Your order in three easy steps.
H3 1.Choose a game
H3 2.Complete payment
H3 3.Get it delivered
H2 Player Reviews
H2 Why choose RobuxKinun?
H3 Instant Delivery
H3 Safe for Your Account
H3 Best Prices in Bangladesh
H3 24/7 Support
H2 Before you buy.
H3 What is RobuxKinun?
H3 Is it safe for my account? Do you need my password?
H3 How long does delivery take?
H3 How does group payout work?
H3 How can I pay?
H3 Why are your prices cheaper than Roblox?
H2 Shops
H2 Support
H2 Legal

A+

Heading Text Quality

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

PASS

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

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

A+

Alt Text Quality

All 19 images OK

PASS

All 19 images OK

11 decorative image(s) correctly marked

8 image(s) with good alt text

19 images 8 good alt text 11 decorative

All images have appropriate alt text.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

Link & Button Quality

47 links, 11 buttons — all OK

PASS

47 links, 11 buttons — all OK

6 link(s) open in new tab without warning

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

Got: https://wa.me/8801; https://www.facebook.com/robuxkinun; https://www.instagram.com/robuxkinun; https://discord.gg/robuxkinun; https://www.youtube.com/@robuxkinun; https://wa.me/8801

41 link(s) with descriptive text

47 links

0 empty

0 generic text

6 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/robux	RobuxGet Robux at the best pri…	img no alt	Add alt attribute to the image
/games/blox-fruits	Blox FruitsFruits and gamepass…	img no alt	Add alt attribute to the image
https://wa.me/8801	Open chat	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/robuxkinun	Facebook	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/robuxkinun	Instagram	new tab	Add '(opens in new tab)' to text
https://discord.gg/robuxkinun	Discord	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/@robuxkinun	YouTube	new tab	Add '(opens in new tab)' to text
/robux	Robux	img no alt	Add alt attribute to the image
https://wa.me/8801	Chat with support	new tab	Add '(opens in new tab)' to text

52 links and buttons have descriptive text

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

https://wa.me/8801; https://www.facebook.com/robuxkinun; https://www.instagram.com/robuxkinun; https://discord.gg/robuxkinun; https://www.youtube.com/@robuxkinun; https://wa.me/8801

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

A+

Form Input Types

No form controls on this page

PASS

No form controls on this page

A+

Form Input Quality

No form controls on this page

PASS

No form controls on this page

A+

Mobile Keyboard & Autofill

No form controls -- mobile keyboard check is N/A

PASS

No form controls -- mobile keyboard check is N/A

No form controls on this page

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

1 explicit tabindex attribute(s) checked, no anti-patterns

PASS

1 explicit tabindex attribute(s) checked, no anti-patterns

No tabindex anti-patterns detected

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

1 PWA signal(s) surfaced

PASS

1 PWA signal(s) surfaced

Manifest has no maskable icon

Android 12+ Adaptive Icons crop non-maskable icons to a circle or squircle -- frequently hiding important parts of the logo. Add at least one icon entry with `"purpose": "maskable"` (or `"any maskable"`) and a maskable-aware design (16% safe-zone padding around the inner mark).

A+

Mobile UX Depth

3 mobile-depth signal(s) detected

PASS

3 mobile-depth signal(s) detected

Browser-chrome `theme-color` meta tag present

The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.

iOS auto-link for phone numbers disabled (`format-detection: telephone=no`)

The page sets `<meta name="format-detection" content="telephone=no">`, which prevents iOS Safari from auto-converting phone-number-shaped strings into clickable `tel:` links. Common reason: the auto-detection rewrites mid-paragraph DOM and breaks CSS selectors / JS that depended on the specific text. If you want clickable phone numbers, declare them with explicit `<a href="tel:+1234567890">` and keep auto-detection disabled.

Viewport `viewport-fit=cover` -- supports notched / dynamic-island devices

The viewport meta declares `viewport-fit=cover`, which lets the page draw into the safe-area edges (notch, dynamic island, home indicator) on iPhone X+ devices. Pair with `env(safe-area-inset-*)` CSS to keep critical UI inside the inset rectangle while letting backgrounds extend edge-to-edge.

A+

Lighthouse Accessibility Audits

Score 100/100 — 0 failing, 26 passed

PASS

100

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.

○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

●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

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

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Image elements do not have `[alt]` attributes that are redundant text.

●Identical links have the same purpose.

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

○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

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