Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

1 REVIEW 6 FIX

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

Soft 404: server returns HTTP 200 for non-existent pages

The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.

Got: Status: 200 for /beavercheck-404-test-1of54l

404 Page Quality ✗ Soft 404 (HTTP 200)

Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

Favicon & Branding

Action

No icons detected

FIX

No icons detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

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

No favicon or icon links detected

Your site will show the browser's generic page icon in tabs, bookmarks, and home screens.

✗ favicon.ico Missing

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

Lighthouse Accessibility Audits

Action

Score 78/100 — 6 failing, 20 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

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
183 DÍAS 00 HORAS 35 MINUTOS 56 SEGUNDOS SIN APLICAR LA LEY DE FINANCIAMIENTO … `body.modal-open > div#popupContador182`

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
FACULTADES Y CARRERAS `div.row > div.col-12 > a.stretched-link > h2`
COLEGIOS `div.row > div.col-12 > a.stretched-link > h2`
POSGRADOS `div.row > div.col-12 > a.stretched-link > h2`
INVESTIGACIÓN `div.row > div.col-12 > a.stretched-link > h2`
COMUNIDAD UBA `div.col-md-6 > a.stretched-link > div.f-blanco > h1`
UNIVERSIDAD Y SOCIEDAD `div.col-md-6 > a.stretched-link > div.f-blanco > h1`
UBA NOTICIAS `div.container-fluid > div.d-flex > div.me-auto > h2`
JORNADA DE VISIBILIZACIÓN `div.col > div.card > div.card-body > h5`
EVITAR LA PROGRESIÓN `div.col > div.card > div.card-body > h5`
CREANDO CONCIENCIA `div.col > div.card > div.card-body > h5`
UBA CIENCIA `div.container-fluid > div.d-flex > div.me-auto > h2`
VER MÁS `div.row > div.col-12 > div.position-absolute > a.btn-uba`
Por más graduad@s `div.col-12 > a.stretched-link > div.f-blanco > h1.f-blanco`
Donar aquí Para las Becas Sarmiento `a.stretched-link > div.f-blanco > h6.f-blanco > p`
00 `div.modal-body > div.contador-tiempo-grid > div.contador-tiempo-item > div#contadorHoras`
HORAS `div.modal-body > div.contador-tiempo-grid > div.contador-tiempo-item > div.contador-tiempo-label`
35 `div.modal-body > div.contador-tiempo-grid > div.contador-tiempo-item > div#contadorMinutos`
MINUTOS `div.modal-body > div.contador-tiempo-grid > div.contador-tiempo-item > div.contador-tiempo-label`
56 `div.modal-body > div.contador-tiempo-grid > div.contador-tiempo-item > div#contadorSegundos`
SEGUNDOS `div.modal-body > div.contador-tiempo-grid > div.contador-tiempo-item > div.contador-tiempo-label`
LEY DE FINANCIAMIENTO UNIVERSITARIO. `div.modal-body > div.contador-texto > p.mb-4 > span.texto-amarillo`
CUIDEMOS LO QUE FUNCIONA. `div.modal-content > div.modal-body > div.contador-texto > p.texto-amarillo-2`

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
Derechos Humanos `div.carousel-item > div.caja > div > h4.mt-4`
JORNADA DE VISIBILIZACIÓN `div.col > div.card > div.card-body > h5`
EVITAR LA PROGRESIÓN `div.col > div.card > div.card-body > h5`
CREANDO CONCIENCIA `div.col > div.card > div.card-body > h5`
Donar aquí Para las Becas Sarmiento `div.col-12 > a.stretched-link > div.f-blanco > h6.f-blanco`

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
body.modal-open > header#inicio > nav.navbar > a.navbar-toggler `body.modal-open > header#inicio > nav.navbar > a.navbar-toggler`
div.container-fluid > div.d-flex > div.ms-auto > a.f-blanco `div.container-fluid > div.d-flex > div.ms-auto > a.f-blanco`
div.container-fluid > div.d-flex > div.ms-auto > a.f-blanco `div.container-fluid > div.d-flex > div.ms-auto > a.f-blanco`
div.row > ul.nav > li > a `div.row > ul.nav > li > a`
div.row > ul.nav > li.ms-2 > a `div.row > ul.nav > li.ms-2 > a`
div.row > ul.nav > li.ms-2 > a `div.row > ul.nav > li.ms-2 > a`
div.row > ul.nav > li.ms-2 > a `div.row > ul.nav > li.ms-2 > a`
div.row > ul.nav > li.ms-2 > a `div.row > ul.nav > li.ms-2 > a`
div.row > ul.nav > li.ms-2 > a `div.row > ul.nav > li.ms-2 > a`
div.row > ul.nav > li.ms-2 > a `div.row > ul.nav > li.ms-2 > 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.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
seguinos!!!! `footer.px-md-3 > div.col-12 > div.row > ul.nav`

These are opportunities to improve the experience of reading tabular or list data using 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

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●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

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

●Document has a main landmark.

●Deprecated ARIA roles were not used

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

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

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

○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

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