Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

3 PASS 3 REVIEW 7 FIX

Alt Text Quality

Action

2 of 10 images have issues

FIX

2 of 10 images have issues

2 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

2 image-in-link without alt text

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

5 decorative image(s) correctly marked

3 image(s) with good alt text

10 images 3 good alt text 5 decorative 2 missing

Issue	Count
missing	2 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

Link & Button Quality

Action

5 issue(s) across 121 links and 2 buttons

FIX

5 issue(s) across 121 links and 2 buttons

5 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: https://www.facebook.com/viber/; https://twitter.com/Viber; https://www.linkedin.com/company/rakuten-viber; https://www.instagram.com/viber/; a (#341 on page)

5 image-only link(s) without alt text

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

Got: a[href="https://www.viber.com/en/blog/2026-03-09/from-hey-to-we-insights-from-our-ina…"]; a[href="https://www.viber.com/en/blog/2025-12-02/whats-new-on-viber/"]; a[href="https://www.viber.com/en/blog/2025-11-03/why-viber-pay-is-the-best-way-to-sen…"]; a[href="https://www.viber.com/en/blog/2025-09-04/sending-money-home-how-viber-pay-con…"]; a[href="https://www.viber.com/en/blog/2025-09-04/send-money-without-bank-details/"]

9 link(s) open in new tab without warning

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

Got: https://support.viber.com; https://www.viki.com/; https://www.kobo.com/; https://travel.rakuten.com/; https://rakutenmarketing.com/; https://insight.rakuten.com/; https://es.rakuten.tv/?utm_source=viber&utm_medium=homepage; https://global.rakuten.com/corp/about/; https://global.rakuten.com/corp/

102 link(s) with descriptive text

121 links

5 empty

0 generic text

9 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.viber.com/en/blog/2026-03-09…	From “Hey” to “We”: In…	img no alt	Add alt attribute to the image
https://www.viber.com/en/blog/2025-12-02…	What’s New on Viber …	img no alt	Add alt attribute to the image
https://www.viber.com/en/blog/2025-11-03…	Why Viber Pay Is the Best Way …	img no alt	Add alt attribute to the image
https://www.viber.com/en/blog/2025-09-04…	Sending Money Home: How Viber …	img no alt	Add alt attribute to the image
https://www.viber.com/en/blog/2025-09-04…	Viber Pay: Send Money Without …	img no alt	Add alt attribute to the image
https://support.viber.com	Support	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/viber/	(empty)	empty	Add link text or aria-label
https://twitter.com/Viber	(empty)	empty	Add link text or aria-label
https://www.linkedin.com/company/rakuten…	(empty)	empty	Add link text or aria-label
https://www.instagram.com/viber/	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
https://www.viki.com/	Rakuten Viki	new tab	Add '(opens in new tab)' to text
https://www.kobo.com/	Rakuten Kobo	new tab	Add '(opens in new tab)' to text
https://travel.rakuten.com/	Rakuten Travel	new tab	Add '(opens in new tab)' to text
https://rakutenmarketing.com/	Rakuten Marketing	new tab	Add '(opens in new tab)' to text
https://insight.rakuten.com/	Rakuten Insight	new tab	Add '(opens in new tab)' to text
https://es.rakuten.tv/?utm_source=viber&…	Rakuten TV	new tab	Add '(opens in new tab)' to text
https://global.rakuten.com/corp/about/	About Rakuten	new tab	Add '(opens in new tab)' to text
https://global.rakuten.com/corp/	Rakuten	new tab	Add '(opens in new tab)' to text

104 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

https://www.facebook.com/viber/; https://twitter.com/Viber; https://www.linkedin.com/company/rakuten-viber; https://www.instagram.com/viber/; a (#341 on page)

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

a[href="https://www.viber.com/en/blog/2026-03-09/from-hey-to-we-insights-from-our-ina…"]; a[href="https://www.viber.com/en/blog/2025-12-02/whats-new-on-viber/"]; a[href="https://www.viber.com/en/blog/2025-11-03/why-viber-pay-is-the-best-way-to-sen…"]; a[href="https://www.viber.com/en/blog/2025-09-04/sending-money-home-how-viber-pay-con…"]; a[href="https://www.viber.com/en/blog/2025-09-04/send-money-without-bank-details/"]

Why this matters

Image-only links with no alt are unidentifiable to screen-reader users — link's destination is invisible.

Source: WCAG 2.1 SC 2.4.4

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

https://support.viber.com; https://www.viki.com/; https://www.kobo.com/; https://travel.rakuten.com/; https://rakutenmarketing.com/; https://insight.rakuten.com/; https://es.rakuten.tv/?utm_source=viber&utm_medium=homepage; https://global.rakuten.com/corp/about/; https://global.rakuten.com/corp/

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

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

Soft 404: server returns HTTP 200 for non-existent pages

The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.

Got: Status: 200 for /beavercheck-404-test-p43e1l

404 Page Quality ✗ Soft 404 (HTTP 200)

Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://viber.com/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://viber.com/manifest.json

Manifest contains invalid JSON.

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: #ffffff

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

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.

Landmark Structure

6 landmarks

REVIEW

6 landmarks

<main> landmark present

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

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

Favicon & Branding

Action

14 icon(s) detected

REVIEW

14 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Lighthouse Accessibility Audits

Score 83/100 — 5 failing, 22 passed

REVIEW

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.

ARIA

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
This website uses cookies to enhance user experience and to analyze performance… `body.blog > div#onetrust-consent-sdk > div#onetrust-banner-sdk > div`

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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
News `section.widget > a.popular-media > div.popular-media-body > div.popular-widget-category`
News `section.widget > a.popular-media > div.popular-media-body > div.popular-widget-category`
Viber Pay `section.widget > a.popular-media > div.popular-media-body > div.popular-widget-category`
Viber Pay `section.widget > a.popular-media > div.popular-media-body > div.popular-widget-category`
Viber Pay `section.widget > a.popular-media > div.popular-media-body > div.popular-widget-category`
Advertising `aside.sidebar > section.widget > div.tagcloud > a.tag-cloud-link`
Brand Partnerships `aside.sidebar > section.widget > div.tagcloud > a.tag-cloud-link`
channels `aside.sidebar > section.widget > div.tagcloud > a.tag-cloud-link`
chat extensions `aside.sidebar > section.widget > div.tagcloud > a.tag-cloud-link`
chats `aside.sidebar > section.widget > div.tagcloud > a.tag-cloud-link`
coffee `aside.sidebar > section.widget > div.tagcloud > a.tag-cloud-link`
communities `aside.sidebar > section.widget > div.tagcloud > a.tag-cloud-link`
community `aside.sidebar > section.widget > div.tagcloud > a.tag-cloud-link`
create stickers `aside.sidebar > section.widget > div.tagcloud > a.tag-cloud-link`
data `aside.sidebar > section.widget > div.tagcloud > a.tag-cloud-link`
digital advertising `aside.sidebar > section.widget > div.tagcloud > a.tag-cloud-link`
digital marketing `aside.sidebar > section.widget > div.tagcloud > a.tag-cloud-link`
Digital Wallet `aside.sidebar > section.widget > div.tagcloud > a.tag-cloud-link`
express yourself `aside.sidebar > section.widget > div.tagcloud > a.tag-cloud-link`
FC Barcelona `aside.sidebar > section.widget > div.tagcloud > a.tag-cloud-link`
free calls `aside.sidebar > section.widget > div.tagcloud > a.tag-cloud-link`
gdpr `aside.sidebar > section.widget > div.tagcloud > a.tag-cloud-link`
group chats `aside.sidebar > section.widget > div.tagcloud > a.tag-cloud-link`
halloween `aside.sidebar > section.widget > div.tagcloud > a.tag-cloud-link`
happy birthday `aside.sidebar > section.widget > div.tagcloud > a.tag-cloud-link`
happy holidays `aside.sidebar > section.widget > div.tagcloud > a.tag-cloud-link`
instant video messages `aside.sidebar > section.widget > div.tagcloud > a.tag-cloud-link`
international calls `aside.sidebar > section.widget > div.tagcloud > a.tag-cloud-link`
legcat `aside.sidebar > section.widget > div.tagcloud > a.tag-cloud-link`
love `aside.sidebar > section.widget > div.tagcloud > a.tag-cloud-link`
manage community `aside.sidebar > section.widget > div.tagcloud > a.tag-cloud-link`
marketing `aside.sidebar > section.widget > div.tagcloud > a.tag-cloud-link`
messaging `aside.sidebar > section.widget > div.tagcloud > a.tag-cloud-link`
Messaging Apps `aside.sidebar > section.widget > div.tagcloud > a.tag-cloud-link`
polls `aside.sidebar > section.widget > div.tagcloud > a.tag-cloud-link`
privacy `aside.sidebar > section.widget > div.tagcloud > a.tag-cloud-link`
safe `aside.sidebar > section.widget > div.tagcloud > a.tag-cloud-link`
secret chats `aside.sidebar > section.widget > div.tagcloud > a.tag-cloud-link`
security `aside.sidebar > section.widget > div.tagcloud > a.tag-cloud-link`
sticker market `aside.sidebar > section.widget > div.tagcloud > a.tag-cloud-link`
Stickers `aside.sidebar > section.widget > div.tagcloud > a.tag-cloud-link`
unlimited calls `aside.sidebar > section.widget > div.tagcloud > a.tag-cloud-link`
viber `aside.sidebar > section.widget > div.tagcloud > a.tag-cloud-link`
viber communities `aside.sidebar > section.widget > div.tagcloud > a.tag-cloud-link`
viber features `aside.sidebar > section.widget > div.tagcloud > a.tag-cloud-link`
viber out `aside.sidebar > section.widget > div.tagcloud > a.tag-cloud-link`
viber pay `aside.sidebar > section.widget > div.tagcloud > a.tag-cloud-link`
viber stickers `aside.sidebar > section.widget > div.tagcloud > a.tag-cloud-link`
violet `aside.sidebar > section.widget > div.tagcloud > a.tag-cloud-link`
wheel of fortune `aside.sidebar > section.widget > div.tagcloud > a.tag-cloud-link`
VIBER `div.container > div.row > section.widget > h3`
COMPANY `div.container > div.row > section.widget > h3`
DOWNLOAD `div.container > div.row > section.widget > h3`
Rakuten Viki `div.container > div.row > div.col-lg-8 > a`
Rakuten Kobo `div.container > div.row > div.col-lg-8 > a`
Rakuten Travel `div.container > div.row > div.col-lg-8 > a`
Rakuten Marketing `div.container > div.row > div.col-lg-8 > a`
Rakuten Insight `div.container > div.row > div.col-lg-8 > a`
Rakuten TV `div.container > div.row > div.col-lg-8 > a`
About Rakuten `div.container > div.row > div.col-lg-8 > a`
Cookies Settings `body.blog > footer.content-info > button#ot-sdk-btn`
Cookies Settings `div.ot-sdk-row > div#onetrust-button-group-parent > div#onetrust-button-group > button#onetrust-pc-btn-handler`
Accept All Cookies `div.ot-sdk-row > div#onetrust-button-group-parent > div#onetrust-button-group > button#onetrust-accept-btn-handler`

These are opportunities to improve the legibility of your content.

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
POPULAR `aside.sidebar > section.widget > div.widget-heading > h3`

These are opportunities to improve keyboard navigation in your application.

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
footer.content-info > div.barcelona > a > img.optanon-category-C0003 `footer.content-info > div.barcelona > a > img.optanon-category-C0003`

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.row > section.col-6 > div.social-links-footer > a.s-link `div.row > section.col-6 > div.social-links-footer > a.s-link`
div.row > section.col-6 > div.social-links-footer > a.s-link `div.row > section.col-6 > div.social-links-footer > a.s-link`
div.row > section.col-6 > div.social-links-footer > a.s-link `div.row > section.col-6 > div.social-links-footer > a.s-link`
div.row > section.col-6 > div.social-links-footer > a.s-link `div.row > section.col-6 > div.social-links-footer > a.s-link`
body.blog > footer.content-info > div.barcelona > a `body.blog > footer.content-info > div.barcelona > a`

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.

○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

●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

●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

●Touch targets have sufficient size and spacing.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements 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

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

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

Heading Hierarchy

7 headings, 1 skip(s)

PASS

7 headings, 1 skip(s)

Single H1 present

Heading level skipped: H1 → H3 (missing H2)

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

H1 Latest Posts
H3 Popular skipped
H3 Archives
H3 Tags
H3 Viber
H3 Company
H3 Download

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

Form Accessibility

1 of 2 controls have issues

PASS

1 of 2 controls have issues

1 control(s) without accessible label

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

Got: <input type="submit">

1 control(s) properly labeled

2 controls

1 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
#s	search	Search for:	none
input	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

A+

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

PASS

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

20 pass

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Latest Posts	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Popular	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Archives	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Tags	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Viber	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Company	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Download	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Viber	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Home	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Download	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Features	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Communities	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Security	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Viber Out	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Blog	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Business	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Home	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Download	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Features	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Communities	21.00:1	4.5:1	#000000	#FFFFFF	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.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.