Skip to content
https://ufsc.br

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
51
GRADE
F
FIX
7
REVIEW
4
PASS
2
INFO
0
Checks
13
2 PASS 4 REVIEW 7 FIX
D
Alt Text Quality
Action
58 of 82 images have issues
FIX
58 of 82 images have issues
Critical::
58 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
1 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
1 image(s) with alt text over 125 characters
Info::
8 decorative image(s) correctly marked
Info::
15 image(s) with good alt text
82 images 15 good alt text 8 decorative 58 missing
IssueCount
missing58 image(s)
too long1 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 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::
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'>.
✗ favicon.ico Missing
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
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::
1 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 1 <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.
D
Lighthouse Accessibility Audits
Action
Score 50/100 — 9 failing, 10 passed
FIX
50

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.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.pikachoose > div.pika-stage > div.pika-aniwrap > img div.pikachoose > div.pika-stage > div.pika-aniwrap > img

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#ytc-wrapper > div.ytc-pslb > div.embed-responsive > iframe#ytcplayer1 div#ytc-wrapper > div.ytc-pslb > div.embed-responsive > iframe#ytcplayer1

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#content > div#slideshow > div.item > a div#content > div#slideshow > div.item > a
section#home > div.fotos > div.galeria > a#flickr_holder section#home > div.fotos > div.galeria > a#flickr_holder
div.galeria > div.pikachoose > div.pika-stage > a div.galeria > div.pikachoose > div.pika-stage > 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.

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
Safatle: A importância das universidades contra o autoritarismo #shorts #ufsc div.ytc-pslb > div.ytc-row > div.ytc-column > h5.ytctitle

These are opportunities to improve keyboard navigation in your application.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.js html.js

These are opportunities to improve the interpretation of your content by users in different locales.

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
Acesso à Informação Carta de Serviços Consulta de Processos Perguntas frequente… body > footer#footer > div.section > li#linkcat-83
Redes Sociais Facebook Instagram RSS Twitter YouTube body > footer#footer > div.section > li#linkcat-47648
UFSC Concursos Egressos Identidade Visual Notícias Oportunidades internacionais… body > footer#footer > div.section > li#linkcat-125

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

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
ENGLISH div > ul#topbar > li > a.language
ACESSIBILIDADE div > ul#topbar > li > a.accessibility
ALTO CONTRASTE div > ul#topbar > li > a#contrast
MAPA DO SITE div > ul#topbar > li > a.accessibility
Imprensa div#menu-nav > ul > li#menu-link-nav-imprensa > a
Telefones div#menu-nav > ul > li#menu-link-nav-telefones > a
Ouvidoria div#menu-nav > ul > li#menu-link-nav-ouvidoria > a
Acesso à Informação div#menu-nav > ul > li#menu-link-nav-acessoinformacao > a
Contato div#menu-nav > ul > li#menu-link-nav-contato > a
Conheça o PIAPE/UFSC div.ytc-row > div.ytc-column > h5.ytctitle > a.ytclink
UFSC 65 anos div.ytc-row > div.ytc-column > h5.ytctitle > a.ytclink
Extensão li.clearfix > div.news_categories > span.news_category > a
Geral li.clearfix > div.news_categories > span.news_category > a
Geral li.clearfix > div.news_categories > span.news_category > a
Ensino li.clearfix > div.news_categories > span.news_category > a
Gestão li.clearfix > div.news_categories > span.news_category > a
Pesquisa li.clearfix > div.news_categories > span.news_category > a
Pesquisa li.clearfix > div.news_categories > span.news_category > a
Pesquisa li.clearfix > div.news_categories > span.news_category > a
Consulta de Processos li#linkcat-83 > ul.xoxo > li > a
Perguntas frequentes li#linkcat-83 > ul.xoxo > li > a
Facebook li#linkcat-47648 > ul.xoxo > li > a
Instagram li#linkcat-47648 > ul.xoxo > li > a
Twitter li#linkcat-47648 > ul.xoxo > li > a
YouTube li#linkcat-47648 > ul.xoxo > li > a
Concursos li#linkcat-125 > ul.xoxo > li > a
Egressos li#linkcat-125 > ul.xoxo > li > a

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.js html.js

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-hidden="true"]` is not present on the document `<body>`
●Form elements have associated labels
●`[accesskey]` values are unique
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
○`[aria-*]` attributes match their roles
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA attributes are used as specified for the element's role
○Deprecated ARIA roles were not used
○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 use only permitted ARIA attributes
○`[role]`s have all required `[aria-*]` attributes
○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
○`[role]` values are valid
○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
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○Buttons have an accessible name
○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 a valid value for its `[lang]` attribute
○`<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.
○Skip links are focusable.
○No element has a `[tabindex]` value greater than 0
○`<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.
○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.
C
Landmark Structure
Action
3 landmarks
REVIEW
3 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
1 <nav> landmark(s) found
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 (missing!) CONTENTINFO footer

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

B
Heading Hierarchy
33 headings, 1 skip(s)
REVIEW
33 headings, 1 skip(s)
Warning::
Multiple H1 headings (4 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H2 Institucional
  • H2 Comunidade
  • H2 Ensino
  • H2 Ingresso
  • H2 Estudante
  • H2 Portais
  • H2 Estrutura
  • H3 UFSC prepara transição com apresentação do nome de Amir e Felipa ao Conselho Universitário
  • H3 Amir e Felipa vencem consulta informal para a Reitoria da UFSC
  • H3 Fenômeno raro deixa ostras esverdeadas e mais saborosas; pesquisadores da UFSC explicam
  • H3 Filósofo Vladimir Safatle faz palestra sobre fascismo na aula magna da UFSC
  • H3 3,5 milhões de brasileiros com 60 anos ou mais podem ter alto risco de quedas, diz estudo
  • H3 Propesq entrega prêmio Mulheres na Ciência a dez pesquisadoras da UFSC
  • H3 UFSC recebe 180 estudantes para o primeiro café da manhã no campus da Trindade
  • H3 UFSC aprova projeto de internacionalização em edital da Capes
  • H2 Destaques
  • H1 Conselho Universitário divulga inscritos para compor as listas tríplices para a Reitoria
  • H1 Cuidoteca lança edital para seleção de crianças que terão acolhimento em período noturno duplicate H1
  • H1 Comissão divulga edital para inscrição de interessados em compor a lista tríplice para reitor duplicate H1
  • H1 Mestranda da UFSC representa SC no Programa Brasileiro de Professores no CERN, na Suíça duplicate H1
  • H2 Últimos Vídeos
  • H5 Safatle: A importância das universidades contra o autoritarismo #shorts #ufsc skipped
  • H5 Conheça o PIAPE/UFSC
  • H5 UFSC 65 anos
  • H5 Karine de Souza Silva - Mulheres na Ciência - Cientistas Negras #ufsc #novembronegro #shorts
  • H2 Ingresso
  • H2 Gestão
  • H2 Campanhas
  • H2 Notícias
  • H2 Fotos
  • H2 Acesso à Informação
  • H2 Redes Sociais
  • H2 UFSC

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

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

B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Universidade Federal de Santa Catarina ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
A
Form Accessibility
1 of 1 controls have issues
PASS
1 of 1 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="q" id="s">
1 controls
0 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
#stext(Buscar no portal)placeholder only

Placeholder text disappears on focus and is not a reliable label.

<input type="text" name="q" id="s">

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

A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

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

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Conselho Universitá…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Cuidoteca lança edi…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Comissão divulga ed…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Mestranda da UFSC re…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Institucional21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Comunidade21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Ensino21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Ingresso21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Estudante21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Portais21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Estrutura21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Destaques21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Últimos Vídeos21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Ingresso21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Gestão21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Campanhas21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Notícias21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Fotos21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Acesso à Informaç…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Redes Sociais21.00:13.0:1
#000000
#FFFFFF
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.

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

Send Feedback