Skip to content
https://ulisboa.pt

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
61
GRADE
D
FIX
5
REVIEW
5
PASS
3
INFO
0
Checks
13
3 PASS 5 REVIEW 5 FIX
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.

F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
8 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 8 <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.
B
Landmark Structure
32 landmarks
REVIEW
32 landmarks
Info::
<main> landmark present
Info::
8 <nav> landmark(s) found
Warning::
2 of 8 <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 ASIDE 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

B
Heading Hierarchy
20 headings, 1 skip(s)
REVIEW
20 headings, 1 skip(s)
Warning::
Multiple H1 headings (3 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H1 → H6 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H2 Menu de utilizador
  • H1 TERMINEI A
  • H1 LICENCIATURA. duplicate H1
  • H1 E AGORA? duplicate H1
  • H6 Transforma ideias em futuro! skipped
  • H3 ULisboa em Números
  • H3 O que procura?
  • H3 És estudante internacional?
  • H3 Investigação e Inovação
  • H2 ULisboa Research Portal
  • H2 Novidades
  • H2 Agenda
  • H2 Siga-nos:
  • H2 Menu de rodapé
  • H2 Contactos
  • H2 Menu de Rodapé (Secundário)
  • H2 Menu Principal
  • H2 Menu Principal (Secundário)
  • H2 Menu Principal (Auxiliar)
  • H3 Este site utiliza cookies para melhorar a experiência de navegação.

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 Página não encontrada | ULisboa ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 17 fail WCAG AA
REVIEW

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

3 pass 17 fail WCAG AA
h2 Menu de utilizador
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
24px · bottom of viewport
h2 ULisboa Research Portal
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
24px · bottom of viewport · over background image/gradient
h2 Novidades
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Agenda
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Siga-nos:
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Menu de rodapé
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Contactos
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Menu de Rodapé (Secundário)
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Menu Principal
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Menu Principal (Secundário)
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Menu Principal (Auxiliar)
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
24px · bottom of viewport
h3 ULisboa em Números
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
19px · bottom of viewport
h3 O que procura?
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
19px · bottom of viewport
h3 És estudante internacional?
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
19px · bottom of viewport · over background image/gradient
h3 Investigação e Inovação
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
19px · bottom of viewport · over background image/gradient
h3 Este site utiliza cookies para melhorar …
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
19px · bottom of viewport
title Universidade de Lisboa
1.57:1
#000000
on
#2E2F32
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient

4 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 TERMINEI A12.63:13.0:1
#FFFFFF
#333333
Pass
h1 LICENCIATURA.12.63:13.0:1
#FFFFFF
#333333
Pass
h1 E AGORA?12.63:13.0:1
#FFFFFF
#333333
Pass
h2 Menu de utilizador1.66:13.0:1
#000000
#333333
Fail
h2 ULisboa Research Por…1.66:13.0:1
#000000
#333333
Fail
h2 Novidades1.66:13.0:1
#000000
#333333
Fail
h2 Agenda1.66:13.0:1
#000000
#333333
Fail
h2 Siga-nos:1.66:13.0:1
#000000
#333333
Fail
h2 Menu de rodapé1.66:13.0:1
#000000
#333333
Fail
h2 Contactos1.66:13.0:1
#000000
#333333
Fail
h2 Menu de Rodapé (Sec…1.66:13.0:1
#000000
#333333
Fail
h2 Menu Principal1.66:13.0:1
#000000
#333333
Fail
h2 Menu Principal (Secu…1.66:13.0:1
#000000
#333333
Fail
h2 Menu Principal (Auxi…1.66:13.0:1
#000000
#333333
Fail
h3 ULisboa em Números1.66:13.0:1
#000000
#333333
Fail
h3 O que procura?1.66:13.0:1
#000000
#333333
Fail
h3 És estudante intern…1.66:13.0:1
#000000
#333333
Fail
h3 Investigação e Ino…1.66:13.0:1
#000000
#333333
Fail
h3 Este site utiliza co…1.66:13.0:1
#000000
#333333
Fail
title Universidade de Lisb…1.57:14.5:1
#000000
#2E2F32
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 87/100 — 4 failing, 24 passed
REVIEW
87

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
Este site utiliza cookies para melhorar a experiência de navegação. Ao carrega… body.layout-no-sidebars > div#sliding-popup

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.

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
Transforma ideias em futuro! div.layout__region > div.paragraph-align-content--left > div.clearfix > h6

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.content > ul.social-media-links--platforms > li > a.social-media-link-icon--facebook div.content > ul.social-media-links--platforms > li > a.social-media-link-icon--facebook
div.content > ul.social-media-links--platforms > li > a.social-media-link-icon--instagram div.content > ul.social-media-links--platforms > li > a.social-media-link-icon--instagram
div.content > ul.social-media-links--platforms > li > a.social-media-link-icon--youtube div.content > ul.social-media-links--platforms > li > a.social-media-link-icon--youtube
div.content > ul.social-media-links--platforms > li > a.social-media-link-icon--linkedin div.content > ul.social-media-links--platforms > li > a.social-media-link-icon--linkedin
div.content > ul.social-media-links--platforms > li > a.social-media-link-icon--threads div.content > ul.social-media-links--platforms > li > a.social-media-link-icon--threads

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
1 div#slick-807e724d8d4 > ul.slick-dots > li > button
2 div#slick-807e724d8d4 > ul.slick-dots > li.slick-active > button
3 div#slick-807e724d8d4 > ul.slick-dots > li > button
4 div#slick-807e724d8d4 > ul.slick-dots > li > button

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
●Background and foreground colors have a sufficient contrast ratio
●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
●`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[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
○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
○`<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.
○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+
Alt Text Quality
All 28 images OK
PASS
All 28 images OK
Info::
28 image(s) with good alt text
28 images 28 good alt text
All images have appropriate alt text.
A+
Form Accessibility
All 2 controls labeled
PASS
All 2 controls labeled
Info::
2 control(s) properly labeled
2 controls
2 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#edit-s--2textTermos a pesquisarfor/id
#edit-stextTermos a pesquisarfor/id
A+
Print Stylesheet
Print styles detected
PASS
Print styles detected
Info::
External print stylesheet detected
Got: /sites/default/files/css/css_7B1qHZRwfgXtwEK309mi9azYK9mD58HOOafMs5S3i04.css?delta=2&language=pt-pt&theme=ulisboa&include=eJyFUltywyAMvBCBIzECZJtGIA8SSd3TFyd9pHFm-gNiV97xrgQpKUPdHHwVdmpc1QSCj80RQ8p1NoFZRRusPkBrmV1qvIauyvXITdzKEZ2JA9BJdKOXirnAjH6intORLCgyaPGU50WPfOWEJp4xZeXmIUZuKXN1P9XdFdZkBoAuclm5YlWxz1qnU8Ha722p9RXIwhu8_wEe3GP3kfmc0e-alKFGdK9An3CCTmqm8SNwReGC7qG2Vwz7UwzBxl196JkSNqdLQ4xMXjDqsHLgr_yCTVkiX7BtbvgcvCkjHHCMJWCy-4hAFZu5A36f9j7sPZkyVJ5gv2v2gO7rNis0mEdoi3xn8ovYXtceKMuCyTSUkbTkC_o9V_f0tuWW9n9d31vzgCsEGvuSabh46D_dcCOU49kFkFFyzED-5n_sTz2LO0JWFyyjdxPFcv-uDweB4XlxLxmv4m6nLZw64Sdg4kwD
Print Stylesheet ✓ Print Optimized
Print stylesheet /sites/default/files/css/css_7B1qHZRwfgXtwEK309mi9azYK9mD58HOOafMs5S3i04.css?delta=2&language=pt-pt&theme=ulisboa&include=eJyFUltywyAMvBCBIzECZJtGIA8SSd3TFyd9pHFm-gNiV97xrgQpKUPdHHwVdmpc1QSCj80RQ8p1NoFZRRusPkBrmV1qvIauyvXITdzKEZ2JA9BJdKOXirnAjH6intORLCgyaPGU50WPfOWEJp4xZeXmIUZuKXN1P9XdFdZkBoAuclm5YlWxz1qnU8Ha722p9RXIwhu8_wEe3GP3kfmc0e-alKFGdK9An3CCTmqm8SNwReGC7qG2Vwz7UwzBxl196JkSNqdLQ4xMXjDqsHLgr_yCTVkiX7BtbvgcvCkjHHCMJWCy-4hAFZu5A36f9j7sPZkyVJ5gv2v2gO7rNis0mEdoi3xn8ovYXtceKMuCyTSUkbTkC_o9V_f0tuWW9n9d31vzgCsEGvuSabh46D_dcCOU49kFkFFyzED-5n_sTz2LO0JWFyyjdxPFcv-uDweB4XlxLxmv4m6nLZw64Sdg4kwD ✓Inline @media print Not detected ✗
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback