Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

5 PASS 4 REVIEW 4 FIX

Landmark Structure

Action

4 landmarks

FIX

4 landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

2 <nav> landmark(s) found

2 of 2 <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

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

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

404 Error Page

Action

HTTP 404, custom page

FIX

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

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

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

Link & Button Quality

Action

3 issue(s) across 280 links and 7 buttons

REVIEW

3 issue(s) across 280 links and 7 buttons

8 link(s) open in new tab without warning

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

Got: https://kids.poki.com; https://www.tiktok.com/@poki_games; https://www.instagram.com/poki__games; https://www.youtube.com/@Poki; https://about.poki.com; https://developers.poki.com; https://kids.poki.com; https://jobs.poki.com

3 button(s) with no accessible text

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

Got: button#profile-btn; button.buttonReset (#118 on page); button.buttonReset (#899 on page)

272 link(s) with descriptive text

280 links

0 empty

0 generic text

8 new tab

3 empty buttons

Element	Text	Issue	Suggested Fix
https://kids.poki.com	Poki Kids	new tab	Add '(opens in new tab)' to text
https://www.tiktok.com/@poki_games	Poki TikTok	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/poki__games	Poki Instagram	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/@Poki	Poki YouTube	new tab	Add '(opens in new tab)' to text
https://about.poki.com	About	new tab	Add '(opens in new tab)' to text
https://developers.poki.com	Poki for Developers	new tab	Add '(opens in new tab)' to text
https://kids.poki.com	Poki Kids	new tab	Add '(opens in new tab)' to text
https://jobs.poki.com	Jobs	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

276 links and buttons have descriptive text

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

https://kids.poki.com; https://www.tiktok.com/@poki_games; https://www.instagram.com/poki__games; https://www.youtube.com/@Poki; https://about.poki.com; https://developers.poki.com; https://kids.poki.com; https://jobs.poki.com

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#profile-btn; button.buttonReset (#118 on page); button.buttonReset (#899 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

Favicon & Branding

9 icon(s) detected

REVIEW

9 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

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: only light

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: #83ffe7

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 only light ✓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, 10 fail WCAG AA

REVIEW

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

10 pass 10 fail WCAG AA 2 pass AA only

h1 Free Online Games

1.55:1

#000000

#222C53

needs 3.0:1 (large text)

32px · bottom of viewport

h2 Our game selection

1.55:1

#000000

#222C53

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Explore a world of game categories

1.55:1

#000000

#222C53

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Who we are

1.55:1

#000000

#222C53

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Create the next big hit at Poki

1.55:1

#000000

#222C53

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Exclusive games only on Poki

1.55:1

#000000

#222C53

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Most popular games right now

1.55:1

#000000

#222C53

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Popular game categories

1.55:1

#000000

#222C53

needs 3.0:1 (large text)

19px · bottom of viewport

a Shooting Games

1.85:1

#000000

#5A2F10

needs 4.5:1 (normal text)

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

a Roblox Games

1.76:1

#000000

#532E0D

needs 4.5:1 (normal text)

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

2 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 Free Online Games	1.55:1	3.0:1	#000000	#222C53	Fail
h2 Our game selection	1.55:1	3.0:1	#000000	#222C53	Fail
h2 Explore a world of g…	1.55:1	3.0:1	#000000	#222C53	Fail
h2 Who we are	1.55:1	3.0:1	#000000	#222C53	Fail
h2 Create the next big …	1.55:1	3.0:1	#000000	#222C53	Fail
h3 Exclusive games only…	1.55:1	3.0:1	#000000	#222C53	Fail
h3 Most popular games r…	1.55:1	3.0:1	#000000	#222C53	Fail
h3 Popular game categor…	1.55:1	3.0:1	#000000	#222C53	Fail
title Free Online Games at…	14.38:1	4.5:1	#000000	#B4DCEB	Pass
button What are you playing…	8.96:1	4.5:1	#000000	#8CB1A7	Pass
a 2 Player Games	11.56:1	4.5:1	#000000	#C2C2A6	Pass
a Car Games	7.53:1	4.5:1	#000000	#CD8F03	Pass
a Shooting Games	1.85:1	4.5:1	#000000	#5A2F10	Fail
a Roblox Games	1.76:1	4.5:1	#000000	#532E0D	Fail
a Action Games	10.58:1	4.5:1	#000000	#F3A860	Pass
a Minecraft Games	10.07:1	4.5:1	#000000	#EBA55D	Pass
a Skill Games	12.17:1	4.5:1	#000000	#F8B971	Pass
a Multiplayer Games	5.28:1	4.5:1	#000000	#BE6A25	Pass
a .io Games	6.51:1	4.5:1	#000000	#A18B7E	Pass
a Adventure Games	16.11:1	4.5:1	#000000	#EAE0D4	Pass

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

9 headings, 1 skip(s)

PASS

9 headings, 1 skip(s)

Single H1 present

Heading level skipped: H2 → H6 (missing H3)

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

H1 Free Online Games
H2 Our game selection
H3 Exclusive games only on Poki
H3 Most popular games right now
H2 Explore a world of game categories
H3 Popular game categories
H2 Who we are
H2 Create the next big hit at Poki
H6 Select your language skipped

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+

Alt Text Quality

All 241 images OK

PASS

All 241 images OK

241 image(s) with good alt text

241 images 241 good alt text

All images have appropriate alt text.

Form Accessibility

1 of 1 controls have issues

PASS

1 of 1 controls have issues

1 control(s) rely on placeholder only

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

Got: <input type="search">

1 controls

0 labeled

1 placeholder only

0 unlabeled

Control	Type	Label	Method
input	search	(What are you playing today?)	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

A+

Web Manifest

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: Poki

192x192 icon present

512x512 icon present

Display mode: minimal-ui

PWA Install Criteria ✓ Installable

Name Poki ✓192×192 icon ✓512×512 icon ✓Start URL ./?utm_source=web_app_manifest ✓Display Mode minimal-ui ✓

Name Poki Display Mode minimal-ui Theme Color #009cff Background Color #83ffe7 Icons 2 icon(s)

A+

Lighthouse Accessibility Audits

Score 98/100 — 2 failing, 23 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.

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 `html`

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
What are you playing today? `div#app-root > nav#nav > div.NuKVRCDKjJRkfpgoOKXi > button.buttonReset`
Let the world play `div.B3Ykv32PAQzAWDm8ZLxP > div.gYKLsrGper0lDtd1Jh5L > div.NsUjvfZGYVJuaFFoj8UT > button.buttonReset`
English `div.gYKLsrGper0lDtd1Jh5L > div.NsUjvfZGYVJuaFFoj8UT > div.OpF4NXmnwNP6RxPvobuQ > button.buttonReset`

○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

●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 are distinguishable without relying on color.

●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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Deprecated ARIA roles were not used

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

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

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

○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

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