https://amiable-company-641562.framer.app

Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

16 PASS 4 REVIEW 4 FIX

Favicon & Branding

Action

3 icon(s) detected

FIX

3 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

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

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

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

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

5 landmarks

REVIEW

5 landmarks

<main> landmark present

3 <nav> landmark(s) found

3 of 3 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

No banner (header) landmark

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

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page Not Found | Framer ✓Custom Styling ✓Navigation ✗Homepage Link ✓Search Form ✗

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

prefers-color-scheme CSS detected in inline styles

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark Mode✓ Dark Mode Supported

color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

Color Contrast (Screenshot)

Action

20 text elements analyzed, 8 fail WCAG AA

REVIEW

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

12 pass 8 fail WCAG AA 7 pass AA only

h2 Cuando el capital llega tarde,

1.80:1

#000000

#293D2C

needs 3.0:1 (large text)

24px · above the fold

h2 pensado para el agro exportador.

1.33:1

#000000

#232229

needs 3.0:1 (large text)

24px · mid-page · over background image/gradient

p Cuéntanos tu operación

3.76:1

#000000

#5B6F2D

needs 4.5:1 (normal text)

16px · top of page (header area)

p Cuéntanos tu operación

2.72:1

#000000

#465926

needs 4.5:1 (normal text)

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

p El desafío

2.71:1

#000000

#44592A

needs 4.5:1 (normal text)

16px · above the fold

span la oportunidad ya pasó.

1.60:1

#000000

#2C331E

needs 4.5:1 (normal text)

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

p Tu empresa ya tiene lo más difícil:

1.47:1

#000000

#212E1E

needs 4.5:1 (normal text)

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

p El mercado

1.53:1

#000000

#283018

needs 4.5:1 (normal text)

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

5 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 Impulsamos el crecim…	14.51:1	3.0:1	#000000	#CAD9E0	Pass
h2 Cuando el capital ll…	1.80:1	3.0:1	#000000	#293D2C	Fail
h2 pensado para el agro…	1.33:1	3.0:1	#000000	#232229	Fail
h2 Soluciones de capita…	4.44:1	3.0:1	#000000	#757370	Pass
h2 De la consulta al ca…	4.44:1	3.0:1	#000000	#757370	Pass
h2 Construyamos juntos …	4.44:1	3.0:1	#000000	#757370	Pass
h3 Alcance global	3.93:1	3.0:1	#000000	#59715A	Pass
h3 Compromiso con el ag…	4.78:1	3.0:1	#000000	#7A7877	Pass
h3 Relaciones de confia…	18.87:1	3.0:1	#000000	#F7F2EC	Pass
h3 Capital de trabajo	4.44:1	3.0:1	#000000	#757370	Pass
h3 Anticipo contra orde…	4.44:1	3.0:1	#000000	#757370	Pass
h3 Estructuras a medida	4.44:1	3.0:1	#000000	#757370	Pass
title Agriconex	18.87:1	4.5:1	#000000	#F7F2EC	Pass
p Aporte de capital pa…	7.84:1	4.5:1	#000000	#95A474	Pass
p Cuéntanos tu operac…	3.76:1	4.5:1	#000000	#5B6F2D	Fail
p Cuéntanos tu operac…	2.72:1	4.5:1	#000000	#465926	Fail
p El desafío	2.71:1	4.5:1	#000000	#44592A	Fail
span la oportunidad ya pa…	1.60:1	4.5:1	#000000	#2C331E	Fail
p Tu empresa ya tiene …	1.47:1	4.5:1	#000000	#212E1E	Fail
p El mercado	1.53:1	4.5:1	#000000	#283018	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.

Heading Hierarchy

19 headings, 1 skip(s)

PASS

19 headings, 1 skip(s)

Single H1 present

Heading level skipped: H2 → H4 (missing H3)

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

H1 Impulsamos el crecimiento del agro exportador
H2 Cuando el capital llega tarde, la oportunidad ya pasó.
H2 Aporte de capital pensado para el agro exportador.
H3 Alcance global
H3 Compromiso con el agro
H3 Relaciones de confianza
H2 Soluciones de capital a la medida de tu empresa
H3 Capital de trabajo
H3 Anticipo contra orden de compra
H3 Estructuras a medida
H2 De la consulta al capital, en un proceso claro.
H4 Cuéntanos tu operación skipped
H4 02
H4 Evaluamos
H4 03
H4 Estructuramos
H4 04
H4 Desembolsamos
H2 Construyamos juntos el futuro de tu empresa.

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

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

3 heading(s) are too short (≤2 characters) to convey meaning

Headings with 2 or fewer characters are almost always emoji / typos / alignment hacks rather than real headings. Screen readers announce the heading level ("heading 2") and then read the content -- a single-character heading conveys no information. Affected: - H4: "02" - H4: "03" - H4: "04"

Got: 3 ≤2-char heading(s)

A+

Alt Text Quality

All 7 images OK

PASS

All 7 images OK

5 decorative image(s) correctly marked

2 image(s) with good alt text

7 images 2 good alt text 5 decorative

All images have appropriate alt text.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

Link & Button Quality

20 links, 0 buttons — all OK

PASS

20 links, 0 buttons — all OK

3 link(s) open in new tab without warning

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

Got: mailto:info@agriconex.com; wa.me:17865537228; https://tocstudio.co

17 link(s) with descriptive text

20 links

0 empty

0 generic text

3 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
./soluciones#capital-de-trabajo	Capital de trabajoLiquidez par…	img no alt	Add alt attribute to the image
./soluciones#anticipo-contra-orden-de-co…	Anticipo contra orden de compr…	img no alt	Add alt attribute to the image
./soluciones#estructuras-a-medida	Estructuras a medidaCada opera…	img no alt	Add alt attribute to the image
mailto:info@agriconex.com	Enviar correo a info@agriconex…	new tab	Add '(opens in new tab)' to text
wa.me:17865537228	Contactar por WhatsApp	new tab	Add '(opens in new tab)' to text
https://tocstudio.co	TOC Studio	new tab	Add '(opens in new tab)' to text

17 links and buttons have descriptive text

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

mailto:info@agriconex.com; wa.me:17865537228; https://tocstudio.co

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+

Form Input Types

No form controls on this page

PASS

No form controls on this page

A+

Form Input Quality

No form controls on this page

PASS

No form controls on this page

A+

Mobile Keyboard & Autofill

No form controls -- mobile keyboard check is N/A

PASS

No form controls -- mobile keyboard check is N/A

No form controls on this page

A+

Document Language

Lang attribute set to "es"

PASS

Lang attribute set to "es"

<html lang="es"> is set and valid

Got: es

A+

Tabindex Anti-Patterns

7 explicit tabindex attribute(s) checked, no anti-patterns

PASS

7 explicit tabindex attribute(s) checked, no anti-patterns

No tabindex anti-patterns detected

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

A+

Tap Target Adequacy

All tap targets meet WCAG 2.5.5/2.5.8 sizing

PASS

All tap targets meet WCAG 2.5.5/2.5.8 sizing

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

Mobile-Readable Font Sizes

All 65 visible text node(s) render at >= 12 CSS pixels

PASS

All 65 visible text node(s) render at >= 12 CSS pixels

All text uses legible mobile font sizes (>= 12 CSS px)

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

No `<meta name="theme-color">` -- browser chrome falls back to default

Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.

Lighthouse Accessibility Audits

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

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
Cuéntanos tu operación `a.framer-X4Wor > div.framer-azy68d > div.framer-r290v > p.framer-text`
Cuéntanos tu operación `a.framer-X4Wor > div.framer-azy68d > div.framer-r290v > p.framer-text`
Conoce nuestras soluciones `a.framer-X4Wor > div.framer-azy68d > div.framer-r290v > p.framer-text`
Cuéntanos tu operación `a.framer-X4Wor > div.framer-azy68d > div.framer-r290v > p.framer-text`
Inicio `div.framer-1jg4ssr > div.framer-n182wh > p.framer-text > a.framer-text`

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
Cuéntanos tu operación `div.framer-1vrhrni > div.framer-1vmu5k0 > div.framer-1cs46l1 > h4.framer-text`

These are opportunities to improve keyboard navigation in your application.

○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

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

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

●Touch targets have sufficient size and spacing.

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

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

○Form elements have associated labels

○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

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

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

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