Skip to content
https://real.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
60
GRADE
D
FIX
5
REVIEW
6
PASS
2
INFO
0
Checks
13
2 PASS 6 REVIEW 5 FIX
D
Alt Text Quality
Action
5 of 64 images have issues
FIX
5 of 64 images have issues
Critical::
5 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
1 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
2 image(s) with alt text over 125 characters
Info::
1 decorative image(s) correctly marked
Info::
56 image(s) with good alt text
64 images 56 good alt text 1 decorative 5 missing
IssueCount
missing5 image(s)
too long2 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.
B
Landmark Structure
3 landmarks
REVIEW
3 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Info::
No banner (header) landmark
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 (missing!) NAV MAIN CONTENTINFO footer

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

B
404 Error Page
HTTP 404, custom page
REVIEW
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
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Watch, save & share videos on any device | RealPlayer Cloud ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
B
Favicon & Branding
6 icon(s) detected
REVIEW
6 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, 13 fail WCAG AA
REVIEW

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

7 pass 13 fail WCAG AA 4 pass AA only
h1 : ¡Repleto de grandes novedades!
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
32px · bottom of viewport
h1 RealPlayer
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
32px · bottom of viewport
h2 ¡Repleto de grandes novedades!
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
a haz clic aquí
2.79:1
#FFFFFF
on
#00A4EC
needs 4.5:1 (normal text)
16px · top of page (header area)
a Política de privacidad
3.14:1
#FFFFFF
on
#009ADF
needs 4.5:1 (normal text)
16px · above the fold
a Sobre RealPlayer
4.35:1
#000000
on
#0178B4
needs 4.5:1 (normal text)
16px · above the fold
a Planes de RealPlayer
4.17:1
#000000
on
#0275AF
needs 4.5:1 (normal text)
16px · above the fold
a Sobre RealPlayer
3.68:1
#000000
on
#076CA3
needs 4.5:1 (normal text)
16px · above the fold
a RealPlayer Mobile
3.38:1
#000000
on
#08669A
needs 4.5:1 (normal text)
16px · above the fold
a StarSearch
3.28:1
#000000
on
#106495
needs 4.5:1 (normal text)
16px · mid-page
a Blog
3.01:1
#000000
on
#105E8E
needs 4.5:1 (normal text)
16px · mid-page
a RealTimes
2.69:1
#000000
on
#125684
needs 4.5:1 (normal text)
16px · mid-page
a RealTimes
2.55:1
#000000
on
#15527F
needs 4.5:1 (normal text)
16px · mid-page
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 : ¡Repleto de grand…1.00:13.0:1
#000000
#000000
Fail
h1 RealPlayer1.00:13.0:1
#000000
#000000
Fail
h2 ¡Repleto de grandes…1.00:13.0:1
#000000
#000000
Fail
title Home to the video pl…21.00:14.5:1
#000000
#FFFFFF
Pass
div Utilizamos cookies p…21.00:14.5:1
#000000
#FFFFFF
Pass
a haz clic aquí2.79:14.5:1
#FFFFFF
#00A4EC
Fail
div . Al seguir en nuest…7.09:14.5:1
#000000
#009FE5
Pass
a Política de privaci…3.14:14.5:1
#FFFFFF
#009ADF
Fail
span Acepto6.15:14.5:1
#000000
#0193D6
Pass
span Alternar navegación5.84:14.5:1
#000000
#018FD0
Pass
a RealPlayer5.35:14.5:1
#000000
#0188C7
Pass
a Planes de RealPlayer4.70:14.5:1
#000000
#017EBB
Pass
a Sobre RealPlayer4.35:14.5:1
#000000
#0178B4
Fail
a Planes de RealPlayer4.17:14.5:1
#000000
#0275AF
Fail
a Sobre RealPlayer3.68:14.5:1
#000000
#076CA3
Fail
a RealPlayer Mobile3.38:14.5:1
#000000
#08669A
Fail
a StarSearch3.28:14.5:1
#000000
#106495
Fail
a Blog3.01:14.5:1
#000000
#105E8E
Fail
a RealTimes2.69:14.5:1
#000000
#125684
Fail
a RealTimes2.55:14.5:1
#000000
#15527F
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 87/100 — 3 failing, 23 passed
REVIEW
87

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
¡Repleto de grandes novedades! div.col-sm-offset-1col-md-offset-1 > div.row > div.col-sm-12 > h2.section-title-mobile
... ADEMÁS de todas las ideas que ya te gustan de RealPlayer div.col-sm-offset-1col-md-offset-1 > div.row > div.col-sm-12 > span.text-white
¡NUEVO! div.col-sm-5 > div.row > div.col-sm-12 > span.new
Descargar RealPlayer div.row > div.col-sm-12 > a > span.dl-rp-text
¡NUEVO! div.col-sm-5 > div.row > div.col-sm-12 > span.new
Descargar RealPlayer div.row > div.col-sm-12 > a > span.dl-rp-text
¡NUEVO! div.col-sm-5 > div.row > div.col-sm-12 > span.new
Descargar RealPlayer div.row > div.col-sm-12 > a > span.dl-rp-text
Descargar RealPlayer div.row > div.col-sm-12 > a > span.dl-rp-text
Asistencia técnica div.col-xs-12 > ul.footer-nav > li > a
Contáctenos div.col-xs-12 > ul.footer-nav > li > a
Términos div.col-sm-12 > ul.terms > li > a
Política de privacidad div.col-sm-12 > ul.terms > li > a
© 2020-2026 RealNetworks, Inc. ul.terms > li.copyright > em > span#copyright

These are opportunities to improve the legibility of your content.

Names and labels

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
div.container-fluid > div.row > div.col-md-12 > img.index-hero-image div.container-fluid > div.row > div.col-md-12 > img.index-hero-image
div.col-sm-offset-1 > div.row > div.col-md-12 > img.img-responsive div.col-sm-offset-1 > div.row > div.col-md-12 > img.img-responsive
div.col-sm-5 > div.row > div.col-md-12 > img.section-img div.col-sm-5 > div.row > div.col-md-12 > img.section-img
div.col-sm-offset-1 > div.row > div.col-md-12 > img.section-img div.col-sm-offset-1 > div.row > div.col-md-12 > img.section-img

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.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Asistencia técnica div.col-xs-12 > ul.footer-nav > li > a
Contáctenos div.col-xs-12 > ul.footer-nav > li > a

These items highlight common accessibility best practices.

○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
●`[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
●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
●Heading elements appear in a sequentially-descending order
●`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
●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
○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
○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.
A
Heading Hierarchy
3 headings
PASS
3 headings
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H1 RealPlayer 25: ¡Repleto de grandes novedades!
  • H1 RealPlayer duplicate H1
  • H2 ¡Repleto de grandes novedades!

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback