Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

12 PASS 7 REVIEW 5 FIX

Heading Hierarchy

Action

17 headings, 4 skip(s)

FIX

17 headings, 4 skip(s)

No H1 heading found

Every page should have one H1 that describes the page content.

Heading level skipped: H2 → H6 (missing H3)

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

Heading level skipped: H2 → H5 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H6 (missing H3)

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

H4 ¡Bienvenido!
H2 ¿Por qué elegirnos?
H6 La forma más eficiente de aprender inglés skipped
H2 APRENDE DONDE Y CUANDO QUIERAS
H5 Conversaciones inmersivas skipped
H5 Comentarios en tiempo real
H5 Personalización
H5 Clases presenciales
H5 Cursos empresariales
H5 Cursos virtuales en vivo
H2 ¡Empieza a hablar inglés sin miedo!
H4 Nuestra Comunidad Bilingüe skipped
H2 Contacto
H6 Bello Horizonte skipped
H6 Cristo Rey
H6 Teléfonos
H2 Enlaces rápidos

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

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

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

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

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 ✗

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.

Link & Button Quality

1 issue(s) across 23 links and 1 buttons

REVIEW

1 issue(s) across 23 links and 1 buttons

1 link(s) with no accessible text

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

Got: https://www.harmonhall.talisis.com/solicitar-informacion

7 link(s) open in new tab without warning

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

Got: https://aulavirtual.nationalenglishinstitute.com; https://aulavirtual.nationalenglishinstitute.com; https://nationalenglishinstitute.com/contact-3/; #; #; #;

15 link(s) with descriptive text

23 links

1 empty

0 generic text

7 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://nationalenglishinstitute.com/	National English Institute	img no alt	Add alt attribute to the image
https://aulavirtual.nationalenglishinsti…	Aula Virtual	new tab	Add '(opens in new tab)' to text
https://aulavirtual.nationalenglishinsti…	Aula Virtual	new tab	Add '(opens in new tab)' to text
https://nationalenglishinstitute.com/	National English Institute	img no alt	Add alt attribute to the image
https://nationalenglishinstitute.com/con…	Solicitar información	new tab	Add '(opens in new tab)' to text
https://www.harmonhall.talisis.com/solic…	(empty)	empty	Add link text or aria-label
#	Facebook	new tab	Add '(opens in new tab)' to text
#	Twitter	new tab	Add '(opens in new tab)' to text
#	YouTube	new tab	Add '(opens in new tab)' to text
	TikTok	new tab	Add '(opens in new tab)' to text

16 links and buttons have descriptive text

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

https://www.harmonhall.talisis.com/solicitar-informacion

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.

https://aulavirtual.nationalenglishinstitute.com; https://aulavirtual.nationalenglishinstitute.com; https://nationalenglishinstitute.com/contact-3/; #; #; #;

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

Tap Target Adequacy

3 tap target(s) too small or too close together

REVIEW

3 tap target(s) too small or too close together

3 tap target(s) too small or too close to neighbors

WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.

Mobile-Readable Font Sizes

94% of visible text renders at >= 12 CSS px (2 below threshold)

REVIEW

94% of visible text renders at >= 12 CSS px (2 below threshold)

2 text node(s) render below 12 CSS pixels on mobile

Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <div> 11.9px ("nuestros cursos"); <a> 11.9px ("Solicitar info").

404 Error Page

Action

Could not test

REVIEW

Could not test

404 page could not be tested

The 404 page check encountered an error. This may be due to a timeout or network issue.

404 page quality check not available.

Favicon & Branding

Action

3 icon(s) detected

REVIEW

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

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

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

title National English Institute - National En…

1.24:1

#000000

#181C2C

needs 4.5:1 (normal text)

16px · top of page (header area)

a Ir al contenido

1.36:1

#000000

#1F2435

needs 4.5:1 (normal text)

16px · top of page (header area)

a Inicio

1.26:1

#000000

#1A1D2D

needs 4.5:1 (normal text)

16px · top of page (header area)

a Cursos

1.25:1

#000000

#181D2C

needs 4.5:1 (normal text)

16px · top of page (header area)

a Contacto

1.52:1

#000000

#242D3F

needs 4.5:1 (normal text)

16px · above the fold

div Aula Virtual

1.52:1

#000000

#242D3F

needs 4.5:1 (normal text)

16px · above the fold

a Aula Virtual

1.23:1

#000000

#121C2F

needs 4.5:1 (normal text)

16px · above the fold

a Inicio

1.43:1

#000000

#1D283E

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 ¿Por qué elegirnos…	18.31:1	3.0:1	#000000	#ECF0F2	Pass
h2 APRENDE DONDE Y CUAN…	18.31:1	3.0:1	#000000	#ECF0F2	Pass
h2 ¡Empieza a hablar i…	18.31:1	3.0:1	#000000	#ECF0F2	Pass
h2 Contacto	18.31:1	3.0:1	#000000	#ECF0F2	Pass
h2 Enlaces rápidos	18.31:1	3.0:1	#000000	#ECF0F2	Pass
title National English Ins…	1.24:1	4.5:1	#000000	#181C2C	Fail
a Ir al contenido	1.36:1	4.5:1	#000000	#1F2435	Fail
a Inicio	1.26:1	4.5:1	#000000	#1A1D2D	Fail
a Cursos	1.25:1	4.5:1	#000000	#181D2C	Fail
a Contacto	1.52:1	4.5:1	#000000	#242D3F	Fail
div Aula Virtual	1.52:1	4.5:1	#000000	#242D3F	Fail
a Aula Virtual	1.23:1	4.5:1	#000000	#121C2F	Fail
a Inicio	1.43:1	4.5:1	#000000	#1D283E	Fail
a Cursos	18.31:1	4.5:1	#000000	#ECF0F2	Pass
a Contacto	18.31:1	4.5:1	#000000	#ECF0F2	Pass
h4 ¡Bienvenido!	18.31:1	3.0:1	#000000	#ECF0F2	Pass
p Enseñanza de Inglé…	18.31:1	4.5:1	#000000	#ECF0F2	Pass
div nuestros cursos	18.31:1	4.5:1	#000000	#ECF0F2	Pass
strong En National English …	18.31:1	3.0:1	#000000	#ECF0F2	Pass
a Solicitar informaci�…	18.31:1	4.5:1	#000000	#ECF0F2	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.

Lighthouse Accessibility Audits

Score 87/100 — 4 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.

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
Clases presenciales `div.wp-block-columns > div.wp-block-column > div.wp-block-group > h5.wp-block-heading`
Cursos empresariales `div.entry-content > div.wp-block-columns > div.wp-block-column > h5.wp-block-heading`
Cursos virtuales en vivo `div.entry-content > div.wp-block-columns > div.wp-block-column > h5.wp-block-heading`
SOLICITAR INFO `div.wp-block-group > div.wp-block-buttons > div.wp-block-button > a.wp-block-button__link`

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
La forma más eficiente de aprender inglés `div.uagb-infobox-margin-wrapper > div.uagb-ifb-content > div.uagb-ifb-title-wrap > h6.uagb-ifb-title-prefix`
Conversaciones inmersivas `div.uagb-infobox-margin-wrapper > div.uagb-ifb-content > div.uagb-ifb-title-wrap > h5.uagb-ifb-title`
Nuestra Comunidad Bilingüe `main#main > article#post-2523 > div.entry-content > h4.wp-block-heading`
Bello Horizonte `aside.footer-widget-area > section#text-2 > div.textwidget > h6.wp-block-heading`

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.entry-content > div.wp-block-group > p.has-text-align-center > a `div.entry-content > div.wp-block-group > p.has-text-align-center > 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.

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
Aula Virtual `nav.menu-aula-virtual-container > ul#menu-aula-virtual > li#menu-item-2747 > a.menu-link`
Cursos `nav.menu-aula-virtual-container > ul#menu-aula-virtual > li#menu-item-2426 > a.menu-link`
Contáctanos `nav.menu-aula-virtual-container > ul#menu-aula-virtual > li#menu-item-2514 > a.menu-link`

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

●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

●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

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Uses ARIA roles only on compatible elements

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

○Links are distinguishable without relying on color.

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

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

Landmark Structure

9 landmarks

PASS

9 landmarks

<main> landmark present

3 <nav> landmark(s) found

All <nav> elements are properly labeled

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

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

A+

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

1 heading(s) are all-uppercase (excluding short acronyms)

Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.

Got: 1 all-caps heading(s)

A+

Alt Text Quality

All 15 images OK

PASS

All 15 images OK

15 decorative image(s) correctly marked

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

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

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

PASS

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

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.

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