Skip to content
https://bluestacks.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
48
GRADE
F
FIX
6
REVIEW
6
PASS
1
INFO
0
Checks
13
1 PASS 6 REVIEW 6 FIX
F
Alt Text Quality
Action
13 of 145 images have issues
FIX
13 of 145 images have issues
Critical::
12 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
8 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Warning::
1 image(s) with generic alt text
Info::
132 image(s) with good alt text
145 images 132 good alt text 1 generic 12 missing
IssueCount
missing12 image(s)
generic1 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

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

D
Web Manifest
Action
Not found
FIX
Not found
Info::
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.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
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 ModeNo Dark Mode Detected
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

C
Heading Hierarchy
Action
69 headings, 3 skip(s)
REVIEW
69 headings, 3 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H2 Escolha um método para instalar o aplicativo BlueStacks Mobile no seu celular
  • H1 O Emulador Android mais rápido e leve para jogar jogos Android no PC
  • H3 BlueStacks Air para Mac skipped
  • H3 BlueStacks Store
  • H3 Desempenho imbatível
  • H3 Mais de 2 milhões de jogos Android
  • H3 Apoiado por
  • H2 Jogos para todos. Vamos jogar.
  • H2 Descubra mais de 2 milhões de jogos
  • H2 Jogue jogos no PC, Mac ou na nuvem.
  • H2 Nuvem híbrida ou PC local. Jogue como quiser.
  • H2 ÚLTIMOS E PRÓXIMOS JOGOS
  • H3 MU Immortal
  • H3 Slayer: Crimson Legacy
  • H3 Renegade Immortal
  • H3 Business Dynasty: Zero to Hero
  • H3 Magicmon: World
  • H3 Spirit Summoners
  • H3 Dominion: The Iron Throne
  • H3 Ragnarok Monster Kitchen
  • H3 Last Fiefdom
  • H3 Larva Survival: K-Ani Hunters
  • H3 Larva Sky
  • H3 Arknights: Endfield
  • H3 Dragon Traveler
  • H3 MU: Dark Awakening
  • H3 Stickman GO
  • H3 Eternal Sword Pact
  • H3 RAID: Shadow Legends
  • H3 Legend of Mushroom
  • H3 Azur Lane
  • H3 Blood Strike – FPS for all
  • H3 Whiteout Survival
  • H3 CookieRun: Kingdom
  • H3 Blue Archive
  • H3 Isekai:Slow Life
  • H3 Lords Mobile: Kingdom Wars
  • H3 Standoff 2
  • H3 Free Fire: Tesouro Perdido
  • H3 Call of Duty®: Mobile
  • H3 Age of Empires Mobile
  • H3 Plants vs Zombies™ 2
  • H3 Echocalypse: Scarlet Covenant
  • H3 Zombieland: Doomsday Survival
  • H3 King of Fighting
  • H3 Command & Conquer™: Legions
  • H3 MetaCity M
  • H3 Azure Tale
  • H3 Chess Rumble: PVP Card Battle
  • H3 Supremacy: Warhammer 40,000
  • H3 Goddess Paradise
  • H3 NTE: Neverness to Everness
  • H3 Movie Cinema Simulator
  • H3 Corrida de quebra de tijolos
  • H3 Missão de Ordenar Água
  • H3 Dragon Rider Idle
  • H3 Jewels Town : Match 3
  • H3 Match Puzzle Blast
  • H3 Pixel Quest: Rogue Legend
  • H3 Skill Blitz
  • H2 As Melhores Estratégias de Jogo
  • H4 BlueStacks Prime no Mac e no PC: jogabilidade sem anúncios, economia extra em jogos exclusivos e muito mais! skipped
  • H4 Standoff 2 – Guia Épico de Casos/Caixas Fable: probabilidades, melhor estratégia e vale a pena?
  • H4 Standoff 2 – Itens épicos que você pode criar com fragmentos épicos
  • H2 Principais vídeos do nosso canal
  • H2 Descubra uma ótima jogabilidade e recompensas exclusivas no PC ou Mac.
  • H5 BlueStacks é uma plataforma para PC. skipped
  • H5 Desculpe, BlueStacks é apenas para PC ou Mac
  • H5 BlueStacks

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

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

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

C
Form Accessibility
Action
4 of 4 controls have issues
REVIEW
4 of 4 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="checkbox" name="terms-and-condition">
Warning::
3 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="search">; <input type="text">; <input type="search">
4 controls
0 labeled
3 placeholder only
1 unlabeled
ControlTypeLabelMethod
inputsearch(Pesquisar)placeholder only
inputtext(Digite seu endereço de e-mail)placeholder only
inputsearch(Pesquisar)placeholder only
terms-and-conditioncheckbox(none)none

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

<input type="checkbox" name="terms-and-condition">

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

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

<input type="search">; <input type="text">; <input type="search">

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

B
Favicon & Branding
4 icon(s) detected
REVIEW
4 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 8 fail WCAG AA
REVIEW

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

12 pass 8 fail WCAG AA
title BlueStacks: jogue no PC e Mac, emulador …
1.33:1
#000000
on
#1B2331
needs 4.5:1 (normal text)
16px · top of page (header area)
span We value your privacy
1.33:1
#000000
on
#1B2330
needs 4.5:1 (normal text)
16px · top of page (header area)
div We and our
1.33:1
#000000
on
#1C232E
needs 4.5:1 (normal text)
16px · top of page (header area)
button partners
1.35:1
#000000
on
#1D242F
needs 4.5:1 (normal text)
16px · top of page (header area)
div store and/or access information on a dev…
1.35:1
#000000
on
#1D242F
needs 4.5:1 (normal text)
16px · above the fold
span MORE OPTIONS
1.33:1
#000000
on
#1D232E
needs 4.5:1 (normal text)
16px · above the fold
span AGREE
1.33:1
#000000
on
#1C232E
needs 4.5:1 (normal text)
16px · above the fold
a Recursos
1.34:1
#000000
on
#1C242F
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 O Emulador Android m…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Escolha um método p…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Jogos para todos. Va…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Descubra mais de 2 m…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Jogue jogos no PC, M…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Nuvem híbrida ou PC…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Jogue como quiser.21.00:13.0:1
#000000
#FFFFFF
Pass
h2 ÚLTIMOS E PRÓXIMOS…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 As Melhores Estraté…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Principais vídeos d…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Descubra uma ótima …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Apoiado por21.00:13.0:1
#000000
#FFFFFF
Pass
title BlueStacks: jogue no…1.33:14.5:1
#000000
#1B2331
Fail
span We value your privac…1.33:14.5:1
#000000
#1B2330
Fail
div We and our1.33:14.5:1
#000000
#1C232E
Fail
button partners1.35:14.5:1
#000000
#1D242F
Fail
div store and/or access …1.35:14.5:1
#000000
#1D242F
Fail
span MORE OPTIONS1.33:14.5:1
#000000
#1D232E
Fail
span AGREE1.33:14.5:1
#000000
#1C232E
Fail
a Recursos1.34:14.5:1
#000000
#1C242F
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.

B
Lighthouse Accessibility Audits
Score 82/100 — 5 failing, 22 passed
REVIEW
82

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.

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
header.header-wrapper > div.container > div.right-section > button.nav-menu-opner header.header-wrapper > div.container > div.right-section > button.nav-menu-opner
div.hero-search-wrapper > div.container-autocomplete > form.flex > button div.hero-search-wrapper > div.container-autocomplete > form.flex > button
body.experiment_variant > div#modals > button.close-modal body.experiment_variant > div#modals > button.close-modal

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
li.strategy-item > a.strategy-link > figure > img.lazy li.strategy-item > a.strategy-link > figure > img.lazy
li.strategy-item > a.strategy-link > figure > img.lazy li.strategy-item > a.strategy-link > figure > img.lazy
li.strategy-item > a.strategy-link > figure > img.lazy li.strategy-item > a.strategy-link > figure > img.lazy
body.experiment_variant > footer > section.unlock-banner-section > img.lazy body.experiment_variant > footer > section.unlock-banner-section > img.lazy
ul.socail-ftr > li > a.twitter > img ul.socail-ftr > li > a.twitter > img

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#modals > div.modal-content > div.embed-container > iframe div#modals > div.modal-content > div.embed-container > iframe

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.show-on-mob-deal-for-win > section.bsx-hero-section > div.hero-upper-text > a.flex div.show-on-mob-deal-for-win > section.bsx-hero-section > div.hero-upper-text > a.flex
BlueStacks Logo section.unlock-banner-section > div.container > div.unlock-content > a.play-store-btn
div.follow-us-on > ul.socail-ftr > li > a.discord div.follow-us-on > ul.socail-ftr > li > a.discord
div.follow-us-on > ul.socail-ftr > li > a.Reddit div.follow-us-on > ul.socail-ftr > li > a.Reddit
div.follow-us-on > ul.socail-ftr > li > a.facebook div.follow-us-on > ul.socail-ftr > li > a.facebook
div.follow-us-on > ul.socail-ftr > li > a.twitter div.follow-us-on > ul.socail-ftr > li > a.twitter

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.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Apoiado por div.show-on-mob-deal-for-win > div.section-backed-by > div.container > h3
BlueStacks Prime no Mac e no PC: jogabilidade sem anúncios, economia extra em j… li.strategy-item > a.strategy-link > div.strategy-item-content > h4.blog-title

These are opportunities to improve keyboard navigation in your application.

○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
●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
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●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.
●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.
●Document has a main landmark.
●Deprecated ARIA roles were not used
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements 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
○`<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
○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.
○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.
A
404 Error Page
HTTP 404, custom page
PASS
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page Not Found ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback