Skip to content
https://unicen.edu.ar

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
79
GRADE
C
FIX
5
REVIEW
5
PASS
14
INFO
0
Checks
24
14 PASS 5 REVIEW 5 FIX
D
404 Error Page
Action
HTTP 404, custom page
FIX
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
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::
3 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 3 <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
Heading Hierarchy
Action
36 headings
REVIEW
36 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
2 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H2 (empty)
  • H3 (empty)
  • H2 INFORMATION FOR STUDENTS
  • H2 UNIVERSITY LIFE
  • H2 Institutional
  • H3 What are you going to do in 2027? UNICEN invites you to explore its training programs.
  • H2 Latest news
  • H3 Faculty of Economic Sciences of Unicen: 171st Graduation Ceremony – Part 2
  • H3 Successful Field Day at the Farm of the Faculty of Agronomy of UNICEN
  • H3 UNICEN is hosting the III National Conference on Disability in the Faculties of Veterinary Sciences
  • H3 The Faculty of Law invites you to the 2nd Congress on Local and Regional Identity in Azul
  • H3 Artificial intelligence: UNICEN proposes a critical reflection on the challenges of AI
  • H3 UNICEN's Specialization in Childhood and Youth celebrates its 20th anniversary
  • H2 Institutional Management
  • H2 Career Offerings
  • H3 Facultad de Agronomía
  • H3 Facultad de Arte
  • H3 Facultad de Ciencias de la Salud
  • H3 Facultad de Ciencias Económicas
  • H3 Facultad de Ciencias Exactas
  • H3 Facultad de Ciencias Humanas
  • H3 Facultad de Ciencias Sociales
  • H3 Facultad de Ciencias Veterinarias
  • H3 Facultad de Derecho
  • H3 Facultad de Ingeniería
  • H3 Unidad de Enseñanza Universitaria de Quequen
  • H2 UNICEN Media
  • H3 Conference «Neither technobobos nor technophobes
  • H3 Claudio Martínez at UNICEN
  • H3 University March Conference
  • H3 University Radio
  • H3 UNICEN Institutional
  • H3 FACSO Productions
  • H3 ABRATV
  • H2 Featured Access
  • H2 Links of interest

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

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

B
Favicon & Branding
4 icon(s) detected
REVIEW
4 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 6 fail WCAG AA
REVIEW

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

14 pass 6 fail WCAG AA 11 pass AA only
title UNICEN
1.99:1
#000000
on
#004171
needs 4.5:1 (normal text)
16px · top of page (header area)
font INSTITUTION
1.99:1
#000000
on
#004171
needs 4.5:1 (normal text)
16px · top of page (header area)
font Statute
1.99:1
#000000
on
#004171
needs 4.5:1 (normal text)
16px · above the fold
font Government
3.68:1
#000000
on
#49698B
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
font Headquarters and Sub-headquarters
1.72:1
#000000
on
#34353B
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
font Secretariats
1.17:1
#000000
on
#19170A
needs 4.5:1 (normal text)
16px · above the fold

2 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)
ElementRatioRequiredFGBGResult
h3 Facultad de Agronom…4.40:13.0:1
#000000
#587D35
Pass
h3 Facultad de Arte4.40:13.0:1
#000000
#587D35
Pass
h3 Facultad de Ciencias…4.40:13.0:1
#000000
#587D35
Pass
h3 Facultad de Ciencias…4.40:13.0:1
#000000
#587D35
Pass
h3 Facultad de Ciencias…4.40:13.0:1
#000000
#587D35
Pass
h3 Facultad de Ciencias…4.40:13.0:1
#000000
#587D35
Pass
h3 Facultad de Ciencias…4.40:13.0:1
#000000
#587D35
Pass
h3 Facultad de Ciencias…4.40:13.0:1
#000000
#587D35
Pass
h3 Facultad de Derecho4.40:13.0:1
#000000
#587D35
Pass
h3 Facultad de Ingenier…4.40:13.0:1
#000000
#587D35
Pass
h3 Unidad de Enseñanza…4.40:13.0:1
#000000
#587D35
Pass
title UNICEN1.99:14.5:1
#000000
#004171
Fail
font Agents9.62:14.5:1
#000000
#99B3C6
Pass
font Telephones21.00:14.5:1
#000000
#FFFFFF
Pass
font INSTITUTION1.99:14.5:1
#000000
#004171
Fail
font Historical overview7.73:14.5:1
#000000
#81A1B9
Pass
font Statute1.99:14.5:1
#000000
#004171
Fail
font Government3.68:14.5:1
#000000
#49698B
Fail
font Headquarters and Sub…1.72:14.5:1
#000000
#34353B
Fail
font Secretariats1.17:14.5:1
#000000
#19170A
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.

B
Lighthouse Accessibility Audits
Score 88/100 — 3 failing, 22 passed
REVIEW
88

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
Read full article div.noticia-destacada-contenido > span.leer-mas > font > font
Read full article div.novedad-contenido > span.leer-mas > font > font
Read full article div.novedad-contenido > span.leer-mas > font > font
Read full article div.novedad-contenido > span.leer-mas > font > font
Read full article div.novedad-contenido > span.leer-mas > font > font
Read full article div.novedad-contenido > span.leer-mas > font > font
Read full article div.novedad-contenido > span.leer-mas > font > font

These are opportunities to improve the legibility of your content.

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
section.carrusel-unidades > div.unidades-grid > div.unidad-card > a section.carrusel-unidades > div.unidades-grid > div.unidad-card > a
section.carrusel-unidades > div.unidades-grid > div.unidad-card > a section.carrusel-unidades > div.unidades-grid > div.unidad-card > a
section.carrusel-unidades > div.unidades-grid > div.unidad-card > a section.carrusel-unidades > div.unidades-grid > div.unidad-card > a
section.carrusel-unidades > div.unidades-grid > div.unidad-card > a section.carrusel-unidades > div.unidades-grid > div.unidad-card > a
section.carrusel-unidades > div.unidades-grid > div.unidad-card > a section.carrusel-unidades > div.unidades-grid > div.unidad-card > a
section.carrusel-unidades > div.unidades-grid > div.unidad-card > a section.carrusel-unidades > div.unidades-grid > div.unidad-card > a
section.carrusel-unidades > div.unidades-grid > div.unidad-card > a section.carrusel-unidades > div.unidades-grid > div.unidad-card > a
section.carrusel-unidades > div.unidades-grid > div.unidad-card > a section.carrusel-unidades > div.unidades-grid > div.unidad-card > a
section.carrusel-unidades > div.unidades-grid > div.unidad-card > a section.carrusel-unidades > div.unidades-grid > div.unidad-card > a
section.carrusel-unidades > div.unidades-grid > div.unidad-card > a section.carrusel-unidades > div.unidades-grid > div.unidad-card > a
section.carrusel-unidades > div.unidades-grid > div.unidad-card > a section.carrusel-unidades > div.unidades-grid > div.unidad-card > a
div.footer-contenido > div.footer-col > div.footer-redes > a div.footer-contenido > div.footer-col > div.footer-redes > a
div.footer-contenido > div.footer-col > div.footer-redes > a div.footer-contenido > div.footer-col > div.footer-redes > a
div.footer-contenido > div.footer-col > div.footer-redes > a div.footer-contenido > div.footer-col > div.footer-redes > a
div.footer-contenido > div.footer-col > div.footer-redes > a div.footer-contenido > div.footer-col > div.footer-redes > 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 require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
INSTITUTION div#menu-abierto > nav.menu-hamburguesa-nav > div.hamburguesa-items > li.menu-item
STUDIES div#menu-abierto > nav.menu-hamburguesa-nav > div.hamburguesa-items > li.menu-item
INVESTIGATION div#menu-abierto > nav.menu-hamburguesa-nav > div.hamburguesa-items > li.menu-item
EXTENSION div#menu-abierto > nav.menu-hamburguesa-nav > div.hamburguesa-items > li.menu-item

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

○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
●`button`, `link`, and `menuitem` elements have accessible names
●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
●`<frame>` or `<iframe>` elements have a title
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●All heading elements contain content.
○`[accesskey]` values are unique
○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
○`<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.
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○The document does not use `<meta http-equiv="refresh">`
○`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
○`<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>`.
○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
9 landmarks
PASS
9 landmarks
Info::
<main> landmark present
Info::
3 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
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 Menu" MAIN CONTENTINFO footer

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
Info::
3 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: 3 all-caps heading(s)
A+
Alt Text Quality
All 127 images OK
PASS
All 127 images OK
Info::
23 decorative image(s) correctly marked
Info::
104 image(s) with good alt text
127 images 104 good alt text 23 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 6 controls labeled
PASS
All 6 controls labeled
Info::
6 control(s) properly labeled
6 controls
6 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#onetap-box-vision-impaired-modecheckboxnone
#onetap-box-seizure-safe-profilecheckboxnone
#onetap-box-adhd-friendly-modecheckboxnone
#onetap-box-blindness-modecheckboxnone
#onetap-box-epilepsy-safe-modecheckboxnone
#skip-content-selectselectSkip to contentfor/id
A+
Form Input Types
6 form control(s) checked, no type mismatches
PASS
6 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
6 form control(s) checked, no input-semantic issues
PASS
6 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
No autofill-eligible form controls (no name/email/tel/address fields)
A+
Document Language
Lang attribute set to "en"
PASS
Lang attribute set to "en"
Info::
<html lang="en"> is set and valid
Got: en
A
Tabindex Anti-Patterns
0 positive, 3 -1-on-focusable
PASS
0 positive, 3 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <input id="only-for-this-session">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <input id="only-for-24-hours">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <input id="only-for-a-week">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
A+
Iframe Accessibility
All 1 iframe(s) have descriptive titles
PASS
All 1 iframe(s) have descriptive titles
Info::
All 1 iframe(s) have title attributes
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
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
Mobile-Readable Font Sizes
All 87 visible text node(s) render at >= 12 CSS pixels
PASS
All 87 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
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.

Send Feedback