Skip to content
https://trendmicro.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
52
GRADE
F
FIX
5
REVIEW
6
PASS
2
INFO
0
Checks
13
2 PASS 6 REVIEW 5 FIX
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
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 Present
Apple Touch Missing
SVG Favicon Missing
Manifest Icons Missing
Multiple Sizes Missing
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
4 landmarks
REVIEW
4 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
Info::
No contentinfo (footer) 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 header NAV MAIN (missing!) CONTENTINFO (missing!)

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
Alt Text Quality
Action
26 of 50 images have issues
REVIEW
26 of 50 images have issues
Critical::
26 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
24 image(s) with good alt text
50 images 24 good alt text 26 missing
IssueCount
missing26 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

B
Form Accessibility
2 of 3 controls have issues
REVIEW
2 of 3 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" id="checkbox">
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="search">
Info::
1 control(s) properly labeled
3 controls
1 labeled
1 placeholder only
1 unlabeled
ControlTypeLabelMethod
domaintextyourdomain.comaria-label
searchtext(Search)placeholder only
#checkboxcheckbox(none)none

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

<input type="checkbox" id="checkbox">

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="text" name="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
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 404 | Trend Micro (US) Custom Styling Navigation Homepage Link Search Form
C
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 Avanzando en seguridad nativa para la IA…
2.12:1
#000000
on
#464244
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Presentamos TrendAI™
2.12:1
#000000
on
#464244
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Lidera el futuro en
2.12:1
#000000
on
#464244
needs 3.0:1 (large text)
32px · bottom of viewport
h2 comienza aquí
2.12:1
#000000
on
#464244
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Prevea, prevenga, detecte y responda a l…
2.12:1
#000000
on
#464244
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Proteja, adapte y defienda con confianza…
2.12:1
#000000
on
#464244
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Escanee su superficie de ataque en segun…
2.12:1
#000000
on
#464244
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Escanee su superficie de ataque en segun…
2.12:1
#000000
on
#464244
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Escanee su superficie de ataque en segun…
2.12:1
#000000
on
#464244
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Escanee su superficie de ataque en segun…
2.12:1
#000000
on
#464244
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Protección de la IA en la arquitectura …
2.12:1
#000000
on
#464244
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Protección con velocidad y precisión
2.12:1
#000000
on
#464244
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Líneas de fallo en el ecosistema de IA
2.12:1
#000000
on
#464244
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Actualización: el estado de la IA crimi…
2.12:1
#000000
on
#464244
needs 3.0:1 (large text)
19px · bottom of viewport
h3 La ficción de IA de las ciberamenazas
2.12:1
#000000
on
#464244
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Protección de la IA en la arquitectura …
2.12:1
#000000
on
#464244
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Protección con velocidad y precisión
2.12:1
#000000
on
#464244
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Líneas de fallo en el ecosistema de IA
2.12:1
#000000
on
#464244
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Actualización: el estado de la IA crimi…
2.12:1
#000000
on
#464244
needs 3.0:1 (large text)
19px · bottom of viewport
h3 La ficción de IA de las ciberamenazas
2.12:1
#000000
on
#464244
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Avanzando en segurid…2.12:13.0:1
#000000
#464244
Fail
h1 Presentamos TrendAI…2.12:13.0:1
#000000
#464244
Fail
h1 Lidera el futuro en2.12:13.0:1
#000000
#464244
Fail
h2 comienza aquí2.12:13.0:1
#000000
#464244
Fail
h2 Prevea, prevenga, de…2.12:13.0:1
#000000
#464244
Fail
h2 Proteja, adapte y de…2.12:13.0:1
#000000
#464244
Fail
h3 Escanee su superfici…2.12:13.0:1
#000000
#464244
Fail
h3 Escanee su superfici…2.12:13.0:1
#000000
#464244
Fail
h3 Escanee su superfici…2.12:13.0:1
#000000
#464244
Fail
h3 Escanee su superfici…2.12:13.0:1
#000000
#464244
Fail
h3 Protección de la IA…2.12:13.0:1
#000000
#464244
Fail
h3 Protección con velo…2.12:13.0:1
#000000
#464244
Fail
h3 Líneas de fallo en …2.12:13.0:1
#000000
#464244
Fail
h3 Actualización: el e…2.12:13.0:1
#000000
#464244
Fail
h3 La ficción de IA de…2.12:13.0:1
#000000
#464244
Fail
h3 Protección de la IA…2.12:13.0:1
#000000
#464244
Fail
h3 Protección con velo…2.12:13.0:1
#000000
#464244
Fail
h3 Líneas de fallo en …2.12:13.0:1
#000000
#464244
Fail
h3 Actualización: el e…2.12:13.0:1
#000000
#464244
Fail
h3 La ficción de IA de…2.12:13.0:1
#000000
#464244
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
Heading Hierarchy
47 headings
PASS
47 headings
Warning::
Multiple H1 headings (3 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H1 Avanzando en seguridad nativa para la IA con Anthropic
  • H1 Presentamos TrendAI™ duplicate H1
  • H1 Lidera el futuro en Spark 2026 duplicate H1
  • H2 La seguridad proactiva comienza aquí
  • H2 Prevea, prevenga, detecte y responda a las amenazas más rápido con la única plataforma de ciberseguridad empresarial diseñada para una seguridad completa y proactiva.
  • H3 Escanee su superficie de ataque en segundos
  • H4 Eche un vistazo a su estado
  • H3 Escanee su superficie de ataque en segundos
  • H3 Escanee su superficie de ataque en segundos
  • H4 Resultados para
  • H3 Escanee su superficie de ataque en segundos
  • H4 Resultados para
  • H4 Estado de riesgo:
  • H2 Proteja, adapte y defienda con confianza.
  • H3 Protección de la IA en la arquitectura de software moderna
  • H3 Protección con velocidad y precisión
  • H3 Líneas de fallo en el ecosistema de IA
  • H3 Actualización: el estado de la IA criminal
  • H3 La ficción de IA de las ciberamenazas
  • H3 Protección de la IA en la arquitectura de software moderna
  • H3 Protección con velocidad y precisión
  • H3 Líneas de fallo en el ecosistema de IA
  • H3 Actualización: el estado de la IA criminal
  • H3 La ficción de IA de las ciberamenazas
  • H3 Refuerce todos los aspectos de su seguridad  conTrend Vision One
  • H4 Crear resiliencia al riesgo
  • H4 Optimice las operaciones de seguridad
  • H4 Elimine puntos ciegos
  • H4 Transforme la seguridad en un catalizador de innovación
  • H4 Céntrese en lo que más importa
  • H4 Cerrar brechas de seguridad
  • H3 Experimente el futuro de la ciberseguridad proactiva ahora
  • H3 La seguridad proactiva empieza por conocer las amenazas del mundo real
  • H3 Defensa más inteligente con información sobre amenazas de élite
  • H4 Innovación inigualable
  • H4 Mantener la seguridad, estar a la vanguardia
  • H4 Liderando el camino con un rendimiento demostrado líder en la industria.
  • H4 Líder en seguridad de endpoints
  • H4 Líder en seguridad en la nube
  • H4 Líder en seguridad de red
  • H4 Máximo rendimiento en ciberseguridad de extremo a extremo
  • H4 ¿Está listo para transformar su estrategia de ciberseguridad?
  • H4 Trend Vision One - Proactive Security Starts Here
  • H3 Recursos
  • H3 Soporte
  • H3 Acerca de Trend
  • H3 Sede en el país

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
Lighthouse Accessibility Audits
Score 93/100 — 3 failing, 27 passed
PASS
93

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

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Menu nav > div.header-bar > div.inner-nav-wrapper > div.hamburger

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.

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
Go to slide 1 div#background-wrapper-fc74137b-1807-4eae-b585-a102c8f8bf53 > div.tile-bento-box-slider > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 2 div#background-wrapper-fc74137b-1807-4eae-b585-a102c8f8bf53 > div.tile-bento-box-slider > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 3 div#background-wrapper-fc74137b-1807-4eae-b585-a102c8f8bf53 > div.tile-bento-box-slider > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 4 div#background-wrapper-fc74137b-1807-4eae-b585-a102c8f8bf53 > div.tile-bento-box-slider > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 5 div#background-wrapper-fc74137b-1807-4eae-b585-a102c8f8bf53 > div.tile-bento-box-slider > div.swiper-pagination > span.swiper-pagination-bullet

These items highlight common accessibility best practices.

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
El stack inteligente Protección de la IA en la arquitectura de software modern… div#background-wrapper-fc74137b-1807-4eae-b585-a102c8f8bf53 > div.tile-bento-box-slider > div#swiper-wrapper-4e97825aaf5b699d > a#s3a-tile-intelligent-stack-b9b9cd
Fábrica de IA segura Protección con velocidad y precisión Trend, NVIDIA y Del… div#background-wrapper-fc74137b-1807-4eae-b585-a102c8f8bf53 > div.tile-bento-box-slider > div#swiper-wrapper-4e97825aaf5b699d > a#s3b-tile-security-ai-factory-e242c6
Español (ESP) expand_more div.footer > div.country-selection > div.dropup > button#countryMenu
Learn more div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a.ot-cookie-policy-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.
`button`, `link`, and `menuitem` elements have accessible names
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
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
Heading elements appear in a sequentially-descending order
Document has a main landmark.
Deprecated ARIA roles were not used
Uses ARIA roles only on compatible elements
`[accesskey]` values are unique
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.
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.
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.

Send Feedback