Skip to content
https://ufmg.br

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
52
GRADE
F
FIX
6
REVIEW
4
PASS
3
INFO
0
Checks
13
3 PASS 4 REVIEW 6 FIX
F
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
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-zeyuql
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.

F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://ufmg.br/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://ufmg.br/manifest.json

Manifest contains invalid JSON.

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::
5 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
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 5 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
8 landmarks
REVIEW
8 landmarks
Info::
<main> landmark present
Info::
5 <nav> landmark(s) found
Warning::
5 of 5 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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 CONTENTINFO footer

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

C
Form Accessibility
Action
3 of 3 controls have issues
REVIEW
3 of 3 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="range" id="player-volume">
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="s">; <input type="text" name="nome">
3 controls
0 labeled
2 placeholder only
1 unlabeled
ControlTypeLabelMethod
stext(Buscar)placeholder only
nometext(Buscar curso de graduação)placeholder only
#player-volumerange(none)none

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

<input type="range" id="player-volume">

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.

<input type="text" name="s">; <input type="text" name="nome">

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

C
Favicon & Branding
Action
4 icon(s) detected
REVIEW
4 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 20 fail WCAG AA
REVIEW

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

0 pass 20 fail WCAG AA
h1 Universidade Federal de Minas Gerais
1.08:1
#000000
on
#190806
needs 3.0:1 (large text)
32px · top of page (header area) · over background image/gradient
h1 Universidade Federal de Minas Gerais
1.77:1
#000000
on
#243A48
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Pesquisa vai traçar perfil socioeconôm…
1.77:1
#000000
on
#243A48
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Pesquisa avalia benefícios do treinamen…
1.77:1
#000000
on
#243A48
needs 3.0:1 (large text)
24px · bottom of viewport
h2 UFMG contra o assédio
1.77:1
#000000
on
#243A48
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Com suporte da psicanálise, pesquisa va…
1.77:1
#000000
on
#243A48
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Sobre a UFMG
1.77:1
#000000
on
#243A48
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Cursos
1.77:1
#000000
on
#243A48
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Formação Cidadã
1.77:1
#000000
on
#243A48
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Calendário Escolar
1.77:1
#000000
on
#243A48
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Eventos
1.77:1
#000000
on
#243A48
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Últimas notícias
1.77:1
#000000
on
#243A48
needs 3.0:1 (large text)
24px · bottom of viewport
h2 UFMG nas redes
1.77:1
#000000
on
#243A48
needs 3.0:1 (large text)
24px · bottom of viewport
h2 TV UFMG
1.77:1
#000000
on
#243A48
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Rádio UFMG Educativa
1.77:1
#000000
on
#243A48
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Cidadania
1.77:1
#000000
on
#243A48
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Oportunidades
1.77:1
#000000
on
#243A48
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Nossa UFMG
1.77:1
#000000
on
#243A48
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Ensino
1.77:1
#000000
on
#243A48
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Pesquisa e Inovação
1.77:1
#000000
on
#243A48
needs 3.0:1 (large text)
19px · bottom of viewport

1 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
h1 Universidade Federal…1.08:13.0:1
#000000
#190806
Fail
h1 Universidade Federal…1.77:13.0:1
#000000
#243A48
Fail
h2 Pesquisa vai traçar…1.77:13.0:1
#000000
#243A48
Fail
h2 Pesquisa avalia bene…1.77:13.0:1
#000000
#243A48
Fail
h2 UFMG contra o asséd…1.77:13.0:1
#000000
#243A48
Fail
h2 Com suporte da psica…1.77:13.0:1
#000000
#243A48
Fail
h2 Sobre a UFMG1.77:13.0:1
#000000
#243A48
Fail
h2 Cursos1.77:13.0:1
#000000
#243A48
Fail
h2 Formação Cidadã1.77:13.0:1
#000000
#243A48
Fail
h2 Calendário Escolar1.77:13.0:1
#000000
#243A48
Fail
h2 Eventos1.77:13.0:1
#000000
#243A48
Fail
h2 Últimas notícias1.77:13.0:1
#000000
#243A48
Fail
h2 UFMG nas redes1.77:13.0:1
#000000
#243A48
Fail
h2 TV UFMG1.77:13.0:1
#000000
#243A48
Fail
h2 Rádio UFMG Educativ…1.77:13.0:1
#000000
#243A48
Fail
h2 Cidadania1.77:13.0:1
#000000
#243A48
Fail
h2 Oportunidades1.77:13.0:1
#000000
#243A48
Fail
h2 Nossa UFMG1.77:13.0:1
#000000
#243A48
Fail
h3 Ensino1.77:13.0:1
#000000
#243A48
Fail
h3 Pesquisa e Inovaçã…1.77:13.0:1
#000000
#243A48
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.

A
Heading Hierarchy
41 headings
PASS
41 headings
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H1 Universidade Federal de Minas Gerais
  • H2 Pesquisa vai traçar perfil socioeconômico e cultural de estudantes de graduação das universidades federais
  • H2 Pesquisa avalia benefícios do treinamento físico para o controle da diabetes
  • H2 UFMG contra o assédio
  • H2 Com suporte da psicanálise, pesquisa vai propor novo protocolo para lidar com a exploração infantil pelo tráfico
  • H2 Sobre a UFMG
  • H3 Ensino
  • H3 Pesquisa e Inovação
  • H3 Extensão
  • H2 Cursos
  • H2 Formação Cidadã
  • H2 Calendário Escolar
  • H2 Eventos
  • H3 Colóquio na Fale discute obra da poeta portuguesa Fátima Maldonado
  • H3 Aprendizado de máquinas é tema de curso on-line oferecido pelo Departamento de Estatística
  • H3 Abertas inscrições para curso de produção de cerveja artesanal
  • H3 Planetário promove sessões especiais sobre a astronomia da China Antiga
  • H3 Bibliografia Viva homenageia Danilo Romeu Streck, referência em educação popular e mediações pedagógicas da educação
  • H2 Últimas notícias
  • H3 UFMG regulamenta estruturação de seu fundo patrimonial
  • H3 Reitor, professores e servidora da UFMG são agraciados com a Medalha da Inconfidência
  • H3 Espaços parentais em universidades acendem debate sobre cuidados do poder público com a primeira infância
  • H2 UFMG nas redes
  • H3 Cantinhos da Escola de Arquitetura e Design
  • H3 Apresentando o curso de Engenharia Mecânica
  • H3 A UFMG concedeu o título póstumo de Doutor Honoris Causa a Pepe Mujica.
  • H3 Alessandro Fernandes Moreira tomou posse como novo reitor da UFMG
  • H2 TV UFMG
  • H3 Mercado em Conexão: estudantes e empresas discutem carreiras na UFMG
  • H3 Ubuntu nos negócios: perfil dos empreendedores negros no Brasil
  • H3 Tem cacau no seu chocolate?
  • H3 CULTURA MOVIMENTA #4: arte urbana, identidade e território
  • H2 Rádio UFMG Educativa
  • H3 Próximos Programas
  • H3 Celso Tádhei conta a história do teatro brasileiro no romance ‘A Casa da Ópera de Manoel Luiz’
  • H3 Bom dia UFMG – edição do dia 22/04/26
  • H3 8 – Luíza B.
  • H1 Universidade Federal de Minas Gerais duplicate H1
  • H2 Cidadania
  • H2 Oportunidades
  • H2 Nossa UFMG

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

A+
Alt Text Quality
All 19 images OK
PASS
All 19 images OK
Info::
16 decorative image(s) correctly marked
Info::
3 image(s) with good alt text
19 images 3 good alt text 16 decorative
All images have appropriate alt text.
A
Lighthouse Accessibility Audits
Score 93/100 — 2 failing, 26 passed
PASS
93

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
2026 div.space-y-9 > div.space-y-6 > time.flex > span
2026 div.space-y-9 > div.space-y-6 > time.flex > span
2026 div.space-y-9 > div.space-y-6 > time.flex > span
2026 div.space-y-9 > div.space-y-6 > time.flex > span
Futuros div.space-y-8 > div#events-home > div.flex > button#future
2 horas atrás div.flex > a.basis-full > div.space-y-4 > time.block
23 horas atrás div.flex > a.basis-full > div.space-y-4 > time.block
17 de abril de 2026 div.flex > a.basis-full > div.space-y-4 > time.block
14 abr li.pb-9 > a.flex > div.space-y-3 > time.block
02 abr li.pb-9 > a.flex > div.space-y-3 > time.block
31 mar li.pb-9 > a.flex > div.space-y-3 > time.block

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
div.space-y-3 > ul.md:hidden > li > a.text-[1.25rem] div.space-y-3 > ul.md:hidden > li > a.text-[1.25rem]
div.space-y-3 > ul.md:hidden > li > a.text-[1.25rem] div.space-y-3 > ul.md:hidden > li > a.text-[1.25rem]
div.space-y-3 > ul.md:hidden > li > a.text-[1.25rem] div.space-y-3 > ul.md:hidden > li > a.text-[1.25rem]
div.space-y-3 > ul.md:hidden > li > a.text-[1.25rem] div.space-y-3 > ul.md:hidden > li > a.text-[1.25rem]

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.

○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
●Form elements have associated labels
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●`[accesskey]` values are unique
●ARIA attributes are used as specified for the element's role
●ARIA input fields have accessible names
●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
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○`[aria-hidden="true"]` elements do not contain focusable descendents
○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
○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.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○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.

Send Feedback