Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

2 PASS 4 REVIEW 7 FIX

Form Accessibility

Action

13 of 18 controls have issues

FIX

13 of 18 controls have issues

8 control(s) without accessible label

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

Got: <input type="submit">; <input type="submit">; <input type="submit">; <input type="submit" name="submit" id="ibrcw">; <input type="tel" name="telefono-cf7it-national">; <input type="submit">; <input type="submit">; <input type="submit">

5 control(s) rely on placeholder only

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

Got: <input type="email" name="esfpx_email" id="esfpx_email_5a87e7b8238918">; <input type="text" name="nombre">; <input type="text" name="empresa">; <input type="email" name="email">; <textarea name="mensaje">

5 control(s) properly labeled

18 controls

5 labeled

5 placeholder only

8 unlabeled

Control	Type	Label	Method
s	text	Search	aria-label
s	text	Search	aria-label
s	text	Search	aria-label
s	text	Search	aria-label
s	text	Search	aria-label
empresa	text	(Empresa o Razón Social)	placeholder only
email	email	(Correo electrónico)	placeholder only
mensaje	textarea	(Ingresa aquí su mensaje...)	placeholder only
#esfpx_email_5a87e7b8238918	email	(Correo electrónico)	placeholder only
nombre	text	(Nombre completo)	placeholder only
telefono-cf7it-national	tel	(none)	none
input	submit	(none)	none
#ibrcw	submit	(none)	none
input	submit	(none)	none
input	submit	(none)	none
input	submit	(none)	none
input	submit	(none)	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

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

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

404 Error Page

Action

HTTP 503, bare page

FIX

HTTP 503, bare page

Unexpected status code: HTTP 503

Expected HTTP 404 but received 503. This may confuse search engine crawlers.

Got: HTTP 503

Bare server default 404 page

The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.

404 Page Quality Default 404 Page

Status Code HTTP 503 ✗Page Title 503 Service Unavailable ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗

Favicon & Branding

Action

1 icon(s) detected

FIX

1 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

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 Missing

✓ PNG Icons Present

✗ 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

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: #006fd3

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 ✗

Heading Hierarchy

Action

20 headings, 2 skip(s)

REVIEW

20 headings, 2 skip(s)

Multiple H1 headings (8 found)

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

Heading level skipped: H1 → H3 (missing H2)

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

Heading level skipped: H1 → H3 (missing H2)

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

1 empty heading(s)

Empty headings appear in the document outline but provide no information.

H1 SOLUCIONES IA
H3 Análisis de video con IA skipped
H3 Agentes IA
H3 Asistentes IA
H3 IA privada
H3 Robótica
H3 Innovaciones
H1 La Ventaja de Build-tech duplicate H1
H3 Excelencia skipped
H3 Reduce los Tiempos
H3 Precisión de Respuesta
H3 Incremento de Productividad
H1 Obtenga el valor de AI duplicate H1
H1 100 duplicate H1
H1 99 duplicate H1
H1 40 duplicate H1
H1 +100 duplicate H1
H1 Newsletter BUILD-TECH duplicate H1
H2 Su Carrito de Productos
H3 (empty)

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

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 ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

Link & Button Quality

Action

10 issue(s) across 81 links and 15 buttons

REVIEW

10 issue(s) across 81 links and 15 buttons

10 link(s) with no accessible text

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

Got: a.search-icon (#232 on page); a.submit (#234 on page); a.search-icon (#274 on page); a.submit (#276 on page); a.search-icon (#308 on page); a.submit (#310 on page); a.search-icon (#2293 on page); a.submit (#2295 on page); a.search-icon (#2328 on page); a.submit (#2330 on page)

4 link(s) open in new tab without warning

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

Got: #; #; #; #

67 link(s) with descriptive text

81 links

10 empty

0 generic text

4 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
https://build-tech.ai/productos/analisis…	Análisis de video con IA Una …	img no alt	Add alt attribute to the image
https://build-tech.ai/productos/agentes-…	Agentes IA Sistemas autónomos…	img no alt	Add alt attribute to the image
https://build-tech.ai/productos/asistent…	Asistentes IA Chatbots intelig…	img no alt	Add alt attribute to the image
https://build-tech.ai/productos/ia-priva…	IA privada Soluciones diseñad…	img no alt	Add alt attribute to the image
https://build-tech.ai/productos/robotica…	Robótica Tecnología que se m…	img no alt	Add alt attribute to the image
https://build-tech.ai/productos/innovaci…	Innovaciones En nuestra tienda…	img no alt	Add alt attribute to the image
#	Facebook page opens in new win…	new tab	Add '(opens in new tab)' to text
#	X page opens in new window	new tab	Add '(opens in new tab)' to text
#	YouTube page opens in new wind…	new tab	Add '(opens in new tab)' to text
#	Instagram page opens in new wi…	new tab	Add '(opens in new tab)' to text
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label

82 links and buttons have descriptive text

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

a.search-icon (#232 on page); a.submit (#234 on page); a.search-icon (#274 on page); a.submit (#276 on page); a.search-icon (#308 on page); a.submit (#310 on page); a.search-icon (#2293 on page); a.submit (#2295 on page); a.search-icon (#2328 on page); a.submit (#2330 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

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

#; #; #; #

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

Color Contrast (Screenshot)

Action

20 text elements analyzed, 12 fail WCAG AA

REVIEW

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

8 pass 12 fail WCAG AA 4 pass AA only

h1 SOLUCIONES IA

1.32:1

#000000

#102336

needs 3.0:1 (large text)

32px · bottom of viewport

h1 La Ventaja de Build-tech

1.32:1

#000000

#102336

needs 3.0:1 (large text)

32px · bottom of viewport

h2 Su Carrito de Productos

1.32:1

#000000

#102336

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Análisis de video con IA

1.32:1

#000000

#102336

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Agentes IA

1.32:1

#000000

#102336

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Asistentes IA

1.32:1

#000000

#102336

needs 3.0:1 (large text)

19px · bottom of viewport

h3 IA privada

1.32:1

#000000

#102336

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Robótica

1.32:1

#000000

#102336

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Innovaciones

1.32:1

#000000

#102336

needs 3.0:1 (large text)

19px · bottom of viewport

title Build-tech – Robótica e Innovaciones …

1.21:1

#000000

#101B25

needs 4.5:1 (normal text)

16px · top of page (header area)

a Skip to content

1.15:1

#000000

#0B1623

needs 4.5:1 (normal text)

16px · top of page (header area)

div Build-tech

1.15:1

#000000

#091624

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 SOLUCIONES IA	1.32:1	3.0:1	#000000	#102336	Fail
h1 La Ventaja de Build-…	1.32:1	3.0:1	#000000	#102336	Fail
h1 Obtenga el valor de …	15.96:1	3.0:1	#FFFFFF	#102336	Pass
h1 100	15.96:1	3.0:1	#FFFFFF	#102336	Pass
h1 +100	15.96:1	3.0:1	#FFFFFF	#102336	Pass
h1 Newsletter BUILD-TEC…	15.96:1	3.0:1	#FFFFFF	#102336	Pass
h2 Su Carrito de Produc…	1.32:1	3.0:1	#000000	#102336	Fail
h3 Análisis de video c…	1.32:1	3.0:1	#000000	#102336	Fail
h3 Agentes IA	1.32:1	3.0:1	#000000	#102336	Fail
h3 Asistentes IA	1.32:1	3.0:1	#000000	#102336	Fail
h3 IA privada	1.32:1	3.0:1	#000000	#102336	Fail
h3 Robótica	1.32:1	3.0:1	#000000	#102336	Fail
h3 Innovaciones	1.32:1	3.0:1	#000000	#102336	Fail
h3 Excelencia	3.20:1	3.0:1	#006FD3	#102336	Pass
h3 Reduce los Tiempos	3.20:1	3.0:1	#006FD3	#102336	Pass
h3 Precisión de Respue…	3.20:1	3.0:1	#006FD3	#102336	Pass
h3 Incremento de Produc…	3.20:1	3.0:1	#006FD3	#102336	Pass
title Build-tech – Robó…	1.21:1	4.5:1	#000000	#101B25	Fail
a Skip to content	1.15:1	4.5:1	#000000	#0B1623	Fail
div Build-tech	1.15:1	4.5:1	#000000	#091624	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.

Lighthouse Accessibility Audits

Score 84/100 — 5 failing, 24 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

When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body#the7-body > div.joinchat > div.joinchat__button `body#the7-body > div.joinchat > div.joinchat__button`

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
© Copyright 2025, www.build-tech.ai `div#bottom-bar > div.wf-wrap > div.wf-container-bottom > div.wf-float-left`
Diseño y Desarrollado por: www.hosstiger.com `div.wf-container-bottom > div.wf-float-right > div.bottom-text-block > p`
www.hosstiger.com `div.wf-float-right > div.bottom-text-block > p > a`

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
ANÁLISIS DE VIDEO CON IA `a > div.page_image > div.page_title > h3`
Excelencia `div#Info-box-wrap-5539 > div.aio-ibd-block > div.aio-icon-header > h3.aio-icon-title`

These are opportunities to improve keyboard navigation in your application.

Names and labels

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.mobile-mini-widgets > div.mini-search > form.searchform > a.submit `div.mobile-mini-widgets > div.mini-search > form.searchform > a.submit`

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

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`

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

●Image elements have `[alt]` attributes

●Input buttons have discernible text.

●Form elements have associated labels

●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

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

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

○Buttons have an accessible name

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

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

Landmark Structure

8 landmarks

PASS

8 landmarks

<main> landmark present

1 <nav> landmark(s) found

Skip navigation link present

Page Structure — as a screen reader sees it

A+

Alt Text Quality

All 14 images OK

PASS

All 14 images OK

7 decorative image(s) correctly marked

7 image(s) with good alt text

14 images 7 good alt text 7 decorative

All images have appropriate alt text.

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