Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

16 PASS 3 REVIEW 5 FIX

Mobile-Readable Font Sizes

Action

51% of visible text renders at >= 12 CSS px (80 below threshold)

FIX

51% of visible text renders at >= 12 CSS px (80 below threshold)

80 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: <div> 11.5px ("Account"); <span> 11.0px ("Arcade"); <span> 11.5px ("Yesterday"); <span> 11.5px ("Yesterday"); <span> 11.0px ("Action").

Web Manifest

Action

Not found

FIX

Not found

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.

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: #13161b

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

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

Form Accessibility

Action

3 of 10 controls have issues

REVIEW

3 of 10 controls have issues

3 control(s) without accessible label

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

Got: <input type="submit" name="wp-submit" id="wp-submit">; <input type="submit" id="wp-submit-register">; <input type="submit" id="wp-submit-lost">

7 control(s) properly labeled

10 controls

7 labeled

0 placeholder only

3 unlabeled

Control	Type	Label	Method
s	search	Search apps and games	aria-label
#user_login	text	Username or Email	for/id
#user_pass	password	Password	for/id
#rememberme	checkbox		none
user_login	text	Username	none
user_email	email	Email	none
user_login	text	Username or Email	none
#wp-submit-register	submit	(none)	none
#wp-submit	submit	(none)	none
#wp-submit-lost	submit	(none)	none

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

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

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 Missing

✓ Multiple Sizes Present

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 iO A Physics Platformer

1.09:1

#000000

#0B0F14

needs 3.0:1 (large text)

32px · bottom of viewport · over background image/gradient

h2 Top developers

1.09:1

#000000

#0B0F14

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Applications

1.09:1

#000000

#0B0F14

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Games

1.09:1

#000000

#0B0F14

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Game categories

1.09:1

#000000

#0B0F14

needs 3.0:1 (large text)

24px · bottom of viewport

h2 App categories

1.09:1

#000000

#0B0F14

needs 3.0:1 (large text)

24px · bottom of viewport

h2 DroidCove

1.09:1

#000000

#0B0F14

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Log in to DroidCove

1.09:1

#000000

#0B0F14

needs 3.0:1 (large text)

19px · above the fold

h3 Create your account

1.09:1

#000000

#0B0F14

needs 3.0:1 (large text)

19px · above the fold

h3 Reset your password

1.09:1

#000000

#0B0F14

needs 3.0:1 (large text)

19px · mid-page

title DroidCove - Mod APKs for Android Apps & …

1.09:1

#000000

#0A0F14

needs 4.5:1 (normal text)

16px · top of page (header area)

span Close

1.09:1

#000000

#0A0F14

needs 4.5:1 (normal text)

16px · top of page (header area)

a Games

1.09:1

#000000

#0A0F14

needs 4.5:1 (normal text)

16px · top of page (header area)

a Applications

1.09:1

#000000

#0A0F14

needs 4.5:1 (normal text)

16px · top of page (header area)

a Top apps

1.09:1

#000000

#0B0E14

needs 4.5:1 (normal text)

16px · above the fold

a Top games

1.14:1

#000000

#101419

needs 4.5:1 (normal text)

16px · above the fold

label Username or Email

1.09:1

#000000

#0B0F14

needs 4.5:1 (normal text)

16px · above the fold

label Password

1.09:1

#000000

#0B0F14

needs 4.5:1 (normal text)

16px · above the fold

label Remember Me

1.09:1

#000000

#0B0F14

needs 4.5:1 (normal text)

16px · above the fold

a Lost your password?

1.09:1

#000000

#0B0F14

needs 4.5:1 (normal text)

16px · above the fold

1 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 iO A Physics Platfor…	1.09:1	3.0:1	#000000	#0B0F14	Fail
h2 Top developers	1.09:1	3.0:1	#000000	#0B0F14	Fail
h2 Applications	1.09:1	3.0:1	#000000	#0B0F14	Fail
h2 Games	1.09:1	3.0:1	#000000	#0B0F14	Fail
h2 Game categories	1.09:1	3.0:1	#000000	#0B0F14	Fail
h2 App categories	1.09:1	3.0:1	#000000	#0B0F14	Fail
h2 DroidCove	1.09:1	3.0:1	#000000	#0B0F14	Fail
h3 Log in to DroidCove	1.09:1	3.0:1	#000000	#0B0F14	Fail
h3 Create your account	1.09:1	3.0:1	#000000	#0B0F14	Fail
h3 Reset your password	1.09:1	3.0:1	#000000	#0B0F14	Fail
title DroidCove - Mod APKs…	1.09:1	4.5:1	#000000	#0A0F14	Fail
span Close	1.09:1	4.5:1	#000000	#0A0F14	Fail
a Games	1.09:1	4.5:1	#000000	#0A0F14	Fail
a Applications	1.09:1	4.5:1	#000000	#0A0F14	Fail
a Top apps	1.09:1	4.5:1	#000000	#0B0E14	Fail
a Top games	1.14:1	4.5:1	#000000	#101419	Fail
label Username or Email	1.09:1	4.5:1	#000000	#0B0F14	Fail
label Password	1.09:1	4.5:1	#000000	#0B0F14	Fail
label Remember Me	1.09:1	4.5:1	#000000	#0B0F14	Fail
a Lost your password?	1.09:1	4.5:1	#000000	#0B0F14	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.

Landmark Structure

6 landmarks

PASS

6 landmarks

<main> landmark present

2 <nav> landmark(s) found

All <nav> elements are properly labeled

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

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

10 headings

PASS

10 headings

Single H1 present

H3 Log in to DroidCove
H3 Create your account
H3 Reset your password
H1 iO A Physics Platformer
H2 Top developers
H2 Applications
H2 Games
H2 Game categories
H2 App categories
H2 DroidCove

A+

Heading Text Quality

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

PASS

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

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

A+

Alt Text Quality

All 86 images OK

PASS

All 86 images OK

4 decorative image(s) correctly marked

82 image(s) with good alt text

86 images 82 good alt text 4 decorative

All images have appropriate alt text.

A+

Link & Button Quality

140 links, 7 buttons — all OK

PASS

140 links, 7 buttons — all OK

140 link(s) with descriptive text

140 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

147 links and buttons have descriptive text

Form Input Types

2 input(s) using type=text where a specific type would help

PASS

2 input(s) using type=text where a specific type would help

Input "log" should use type="email" (currently type="text")

Field name "log" suggests type="email". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="email">.

Input "user_login" should use type="email" (currently type="text")

Field name "user_login" suggests type="email". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="email">.

Form Input Quality

1 input-semantic issue(s) across 10 form control(s)

PASS

1 input-semantic issue(s) across 10 form control(s)

1 login form field(s) missing `autocomplete=username` (or `email`)

On a page with a password input, the matching username / email field needs `autocomplete="username"` or `autocomplete="email"` -- otherwise the password manager can't identify which field carries the login identifier and silently skips autofill on the whole form. Sample: <input type="text" name="user_login">.

A+

Mobile Keyboard & Autofill

No autofill-eligible form controls

PASS

No autofill-eligible form controls

No autofill-eligible form controls (no name/email/tel/address fields)

A+

Document Language

Lang attribute set to "en-US"

PASS

Lang attribute set to "en-US"

<html lang="en-US"> is set and valid

Got: en-US

A+

Tabindex Anti-Patterns

No explicit tabindex attributes found

PASS

No explicit tabindex attributes found

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

404 Error Page

HTTP 404, custom page

PASS

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

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page Not Found - DroidCove ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

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

A+

Lighthouse Accessibility Audits

Score 100/100 — 0 failing, 23 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

●Form elements have associated labels

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

●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

●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

○Links are distinguishable without relying on color.

○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

○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

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

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