Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

6 PASS 2 REVIEW 5 FIX

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

favicon.ico present at site root

No apple-touch-icon detected

iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.

✓ favicon.ico Present

✗ PNG Icons Missing

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

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

No dark mode signals

FIX

No dark mode signals

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

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 ✗

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

404 Page Quality ✓ Custom 404 Page

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

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 Reinventa tu negocio del futuro

1.00:1

#000000

needs 3.0:1 (large text)

32px · bottom of viewport

h2 Premios y reconocimientos

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Cada día, abrimos paso al cambio y crea…

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Un líder empresarial ético

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Un gran lugar para trabajar

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Una innovadora influyente

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Desarrolla una carrera profesional que s…

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

title España | Let There Be Change | Accentur…

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

a Skip to main content

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

a Skip to footer

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

div Menu

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

div Close Menu

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

div Qué hacemos

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

div Back

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

div Qué hacemos

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

button Capacidades

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

span Capacidades

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

a Cloud

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

a Servicios de Atención al Cliente

3.69:1

#000000

#686668

needs 4.5:1 (normal text)

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

a Ciberseguridad

1.01:1

#000000

#030005

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 Reinventa tu negocio…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Premios y reconocimi…	1.00:1	3.0:1	#000000	#000000	Fail
h3 Cada día, abrimos p…	1.00:1	3.0:1	#000000	#000000	Fail
h3 Un líder empresaria…	1.00:1	3.0:1	#000000	#000000	Fail
h3 Un gran lugar para t…	1.00:1	3.0:1	#000000	#000000	Fail
h3 Una innovadora influ…	1.00:1	3.0:1	#000000	#000000	Fail
h3 Desarrolla una carre…	1.00:1	3.0:1	#000000	#000000	Fail
title España \| Let There …	1.00:1	4.5:1	#000000	#000000	Fail
a Skip to main content	1.00:1	4.5:1	#000000	#000000	Fail
a Skip to footer	1.00:1	4.5:1	#000000	#000000	Fail
div Menu	1.00:1	4.5:1	#000000	#000000	Fail
div Close Menu	1.00:1	4.5:1	#000000	#000000	Fail
div Qué hacemos	1.00:1	4.5:1	#000000	#000000	Fail
div Back	1.00:1	4.5:1	#000000	#000000	Fail
div Qué hacemos	1.00:1	4.5:1	#000000	#000000	Fail
button Capacidades	1.00:1	4.5:1	#000000	#000000	Fail
span Capacidades	1.00:1	4.5:1	#000000	#000000	Fail
a Cloud	1.00:1	4.5:1	#000000	#000000	Fail
a Servicios de Atenci�…	3.69:1	4.5:1	#000000	#686668	Fail
a Ciberseguridad	1.01:1	4.5:1	#000000	#030005	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.

A+

Landmark Structure

5 landmarks

PASS

5 landmarks

<main> landmark present

1 <nav> landmark(s) found

Skip navigation link present

Page Structure — as a screen reader sees it

Heading Hierarchy

14 headings, 1 skip(s)

PASS

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

3 hidden heading(s) (aria-hidden)

H1 Reinventa tu negocio del futuro
H3 Cada día, abrimos paso al cambio y creamos valor para todos nuestros grupos de interés en cualquier lugar del mundo. skipped
H4 Alimentar al mundo de forma sostenible
H4 Prada personaliza un clásico de culto
H4 Pensamiento creativo para las operaciones globales
H2 Premios y reconocimientos
H3 Un líder empresarial ético hidden
H4 17 años consecutivos entre las empresas más éticas del mundo
H3 Un gran lugar para trabajar hidden
H4 Puesto nº 10 en la lista de World's Best Workplaces
H3 Una innovadora influyente hidden
H4 Julie Sweet, nuestra presidenta y CEO, es una de las 100 personas más influyentes del TIME100 de 2024.
H3 Desarrolla una carrera profesional que sea tan emocionante como el mundo al que estamos dando forma
H4 Abriendo paso al cambio

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 13 images OK

PASS

All 13 images OK

11 decorative image(s) correctly marked

2 image(s) with good alt text

13 images 2 good alt text 11 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 1 controls labeled

PASS

All 1 controls labeled

1 control(s) properly labeled

1 controls

1 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#carousel-slider-id	range	Carousel slider control	for/id

Link & Button Quality

162 links, 40 buttons — all OK

PASS

162 links, 40 buttons — all OK

3 link(s) open in new tab without warning

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

Got: https://www.linkedin.com/company/accenture; https://www.facebook.com/accenture; https://www.instagram.com/accenture/

159 link(s) with descriptive text

162 links

0 empty

0 generic text

3 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.linkedin.com/company/accentu…	linkedin	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/accenture	facebook	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/accenture/	instagram	new tab	Add '(opens in new tab)' to text

199 links and buttons have descriptive text

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

https://www.linkedin.com/company/accenture; https://www.facebook.com/accenture; https://www.instagram.com/accenture/

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

A+

Lighthouse Accessibility Audits

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

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
Cada día, abrimos paso al cambio y creamos valor para todos nuestros grupos de … `main.container > div#main > div.rad-360-value-title > h3.rad-360-value-title__sub-header`

These are opportunities to improve keyboard navigation in your application.

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
Centro de preferencias `div.rad-footer__links-container > ul.rad-footer__links-column > li.rad-footer__link-item > a.rad-footer__link`
Política de cookies/Configuración `div.rad-footer__links-container > ul.rad-footer__links-column > li.rad-footer__link-item > a.rad-footer__link`

○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

●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

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

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

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

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