Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

5 PASS 5 REVIEW 3 FIX

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.

Navigation UX

Action

2 navigation pattern(s)

FIX

2 navigation pattern(s)

Search functionality detected

Got: role-search

Skip navigation link detected

4 navigation landmark(s) detected

Breadcrumbs

Search role='search' landmark

Skip Link Skip link detected

Labeled Navigation 4 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.

Alt Text Quality

1 of 7 images have issues

REVIEW

1 of 7 images have issues

1 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

1 image-in-link without alt text

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

6 image(s) with good alt text

7 images 6 good alt text 1 missing

Issue	Count
missing	1 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

Link & Button Quality

Action

4 issue(s) across 30 links and 7 buttons

REVIEW

4 issue(s) across 30 links and 7 buttons

8 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: http://www.dri.ufrj.br/index.php/en/our-team; https://clac.letras.ufrj.br/; http://siarq.ufrj.br/index.php/boletim-ufrj/; https://acessibilidade.ufrj.br/; https://internacional.ufrj.br/; http://www.ouvidoria.ufrj.br; https://www.gov.br/acessoainformacao/pt-br; https://ufrj.br/comunicacao/

4 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.toggle (#82 on page); button.toggle (#96 on page); button.btncontrast (#111 on page); button.toggle (#116 on page)

22 link(s) with descriptive text

30 links

0 empty

0 generic text

8 new tab

4 empty buttons

Element	Text	Issue	Suggested Fix
https://ufrj.br/en	Universidade Federal do Rio de…	img no alt	Add alt attribute to the image
http://www.dri.ufrj.br/index.php/en/our-…	students officer	new tab	Add '(opens in new tab)' to text
https://clac.letras.ufrj.br/	CLAC	new tab	Add '(opens in new tab)' to text
http://siarq.ufrj.br/index.php/boletim-u…	Boletim Oficial da UFRJ	new tab	Add '(opens in new tab)' to text
https://acessibilidade.ufrj.br/	Acessibilidade e Inclusão	new tab	Add '(opens in new tab)' to text
https://internacional.ufrj.br/	Internacional	new tab	Add '(opens in new tab)' to text
http://www.ouvidoria.ufrj.br	Logo da ouvidoria da Universid…	new tab	Add '(opens in new tab)' to text
https://www.gov.br/acessoainformacao/pt-…	Logo e-sic	new tab	Add '(opens in new tab)' to text
https://ufrj.br/comunicacao/	Logo da coordenadoria de comun…	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

25 links and buttons have descriptive text

Add '(opens in new tab)' to link text or aria-label.

http://www.dri.ufrj.br/index.php/en/our-team; https://clac.letras.ufrj.br/; http://siarq.ufrj.br/index.php/boletim-ufrj/; https://acessibilidade.ufrj.br/; https://internacional.ufrj.br/; http://www.ouvidoria.ufrj.br; https://www.gov.br/acessoainformacao/pt-br; https://ufrj.br/comunicacao/

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

Icon-only buttons need an aria-label so screen readers can announce them.

button.toggle (#82 on page); button.toggle (#96 on page); button.btncontrast (#111 on page); button.toggle (#116 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

Favicon & Branding

4 icon(s) detected

REVIEW

4 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 19 fail WCAG AA

REVIEW

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

1 pass 19 fail WCAG AA

h1 UFRJ is an institution of excellence in …

2.52:1

#000000

#514E43

needs 3.0:1 (large text)

32px · mid-page · over background image/gradient

title Universidade Federal do Rio de Janeiro �…

1.67:1

#000000

#003366

needs 4.5:1 (normal text)

16px · top of page (header area)

a Skip to the content

1.67:1

#000000

#003366

needs 4.5:1 (normal text)

16px · top of page (header area)

p Universidade Federal do Rio de Janeiro

1.67:1

#000000

#003366

needs 4.5:1 (normal text)

16px · top of page (header area)

a Português

2.69:1

#000000

#5A5141

needs 4.5:1 (normal text)

16px · top of page (header area)

a English

1.56:1

#000000

#352E18

needs 4.5:1 (normal text)

16px · above the fold

a Español

1.34:1

#000000

#272318

needs 4.5:1 (normal text)

16px · above the fold

a Français

1.31:1

#000000

#252118

needs 4.5:1 (normal text)

16px · above the fold

span Search for:

2.07:1

#000000

#48412F

needs 4.5:1 (normal text)

16px · above the fold

span Close search

2.48:1

#000000

#524C46

needs 4.5:1 (normal text)

16px · above the fold

span Close Menu

3.06:1

#000000

#5C5A59

needs 4.5:1 (normal text)

16px · above the fold

a Português

2.47:1

#000000

#4F4C4D

needs 4.5:1 (normal text)

16px · above the fold

a English

1.75:1

#000000

#32392A

needs 4.5:1 (normal text)

16px · above the fold

a Español

1.81:1

#000000

#3C3835

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

a Français

2.14:1

#000000

#4C4236

needs 4.5:1 (normal text)

16px · mid-page

div Scroll Down

1.81:1

#000000

#3C3838

needs 4.5:1 (normal text)

16px · mid-page · over background image/gradient

em *Extension means reaching findings of kn…

2.07:1

#000000

#46403F

needs 4.5:1 (normal text)

16px · mid-page

p UFRJ’s history dates back to the begin…

1.26:1

#000000

#211D1E

needs 4.5:1 (normal text)

16px · mid-page

p century and is filled with remarkable sc…

1.54:1

#000000

#302D2B

needs 4.5:1 (normal text)

16px · mid-page

3 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)

Element	Ratio	Required	FG	BG	Result
h1 UFRJ is an instituti…	2.52:1	3.0:1	#000000	#514E43	Fail
h3 Exchange program	19.89:1	3.0:1	#000000	#F7F9FA	Pass
title Universidade Federal…	1.67:1	4.5:1	#000000	#003366	Fail
a Skip to the content	1.67:1	4.5:1	#000000	#003366	Fail
p Universidade Federal…	1.67:1	4.5:1	#000000	#003366	Fail
a Português	2.69:1	4.5:1	#000000	#5A5141	Fail
a English	1.56:1	4.5:1	#000000	#352E18	Fail
a Español	1.34:1	4.5:1	#000000	#272318	Fail
a Français	1.31:1	4.5:1	#000000	#252118	Fail
span Search for:	2.07:1	4.5:1	#000000	#48412F	Fail
span Close search	2.48:1	4.5:1	#000000	#524C46	Fail
span Close Menu	3.06:1	4.5:1	#000000	#5C5A59	Fail
a Português	2.47:1	4.5:1	#000000	#4F4C4D	Fail
a English	1.75:1	4.5:1	#000000	#32392A	Fail
a Español	1.81:1	4.5:1	#000000	#3C3835	Fail
a Français	2.14:1	4.5:1	#000000	#4C4236	Fail
div Scroll Down	1.81:1	4.5:1	#000000	#3C3838	Fail
em *Extension means rea…	2.07:1	4.5:1	#000000	#46403F	Fail
p UFRJ’s history dat…	1.26:1	4.5:1	#000000	#211D1E	Fail
p century and is fille…	1.54:1	4.5:1	#000000	#302D2B	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.

Lighthouse Accessibility Audits

Score 84/100 — 4 failing, 23 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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
header#site-header > div.header-inner > div.header-titles-wrapper > button.toggle `header#site-header > div.header-inner > div.header-titles-wrapper > button.toggle`
header#site-header > div.header-inner > div.header-titles-wrapper > button.toggle `header#site-header > div.header-inner > div.header-titles-wrapper > button.toggle`

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.header-titles > a.site-brand > figure.site-logo > img `div.header-titles > a.site-brand > figure.site-logo > img`

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.header-inner > div.header-titles-wrapper > div.header-titles > a.site-brand `div.header-inner > div.header-titles-wrapper > div.header-titles > a.site-brand`

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
Rio de Janeiro `article#post-2284 > div#post-inner > div.entry-content > h3.wp-block-heading`

These are opportunities to improve keyboard navigation in your application.

○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

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

●Links are distinguishable without relying on color.

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●Touch targets have sufficient size and spacing.

●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○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

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

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

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

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

○`<td>` elements in a large `<table>` have one or more table headers.

A+

Landmark Structure

10 landmarks

PASS

10 landmarks

<main> landmark present

4 <nav> landmark(s) found

All <nav> elements are properly labeled

Skip navigation link present

Search landmark present

Page Structure — as a screen reader sees it

Heading Hierarchy

6 headings, 1 skip(s)

PASS

6 headings, 1 skip(s)

Single H1 present

Heading level skipped: H1 → H3 (missing H2)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H1 UFRJ is an institution of excellence in teaching, research, and extension
H3 Rio de Janeiro skipped
H3 Exchange program
H3 Academic calendar
H3 Courses
H3 Portuguese language proficiency

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

Form Accessibility

1 of 2 controls have issues

PASS

1 of 2 controls have issues

1 control(s) without accessible label

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

Got: <input type="submit">

1 control(s) properly labeled

2 controls

1 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
#search-form-1	search	Search for:	none
input	submit	(none)	none

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

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

404 Error Page

HTTP 404, custom page

PASS

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Página não encontrada – Universidade Federal do Rio de Janeiro ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓

A+

Print Stylesheet

Print styles detected

PASS

Print styles detected

External print stylesheet detected

Got: https://ufrj.br/wp-content/themes/twentytwenty/print.css?ver=0.2

Print Stylesheet ✓ Print Optimized

Print stylesheet https://ufrj.br/wp-content/themes/twentytwenty/print.css?ver=0.2 ✓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.