Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

13 PASS 3 REVIEW 8 FIX

Heading Hierarchy

Action

19 headings, 3 skip(s)

FIX

19 headings, 3 skip(s)

Multiple H1 headings (8 found)

A page should have only one H1. Multiple H1s dilute the document outline.

Heading level skipped: H1 → H5 (missing H2)

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

Heading level skipped: H1 → H3 (missing H2)

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

Heading level skipped: H1 → H4 (missing H2)

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

1 empty heading(s)

Empty headings appear in the document outline but provide no information.

H1 (empty)
H2 Primary Navigation
H2 Bun venit la
H1 Rodizio duplicate H1
H5 GATA SA TE SERVIM skipped
H2 Conceptul
H1 Rodizio duplicate H1
H2 Conceptul
H1 Churrasco duplicate H1
H3 Vezi meniul RODIZIO aici skipped
H2 Retete
H1 Delicioase duplicate H1
H2 Descopera
H1 Meniul duplicate H1
H2 The perfect
H1 Blend duplicate H1
H2 Vinuri
H1 Alese duplicate H1
H4 Despre Rodizio CLuj skipped

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

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 ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

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 ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

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

Link & Button Quality

Action

8 issue(s) across 19 links and 1 buttons

FIX

8 issue(s) across 19 links and 1 buttons

7 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: a#recipes; https://rodizio.ro/site/wp-content/uploads/2020/09/filetto.jpg; https://rodizio.ro/site/wp-content/uploads/2020/09/t-bon2.jpg; https://rodizio.ro/site/wp-content/uploads/2020/09/tomahawk.jpg; https://rodizio.ro/site/wp-content/uploads/2020/09/cube-roll-wagyu-1.jpg; a#reservation; #

3 link(s) open in new tab without warning

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

Got: https://www.instagram.com/rodizio.ro/; https://www.facebook.com/rodizio.ro; https://visteria.ro

1 button(s) with no accessible text

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

Got: button.nav-trigger (#119 on page)

9 link(s) with descriptive text

19 links

7 empty

0 generic text

3 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
https://www.instagram.com/rodizio.ro/	instagram	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/rodizio.ro	facebook	new tab	Add '(opens in new tab)' to text
	(empty)	empty	Add link text or aria-label
https://rodizio.ro/site/wp-content/uploa…	(empty)	empty	Add link text or aria-label
https://rodizio.ro/site/wp-content/uploa…	(empty)	empty	Add link text or aria-label
https://rodizio.ro/site/wp-content/uploa…	(empty)	empty	Add link text or aria-label
https://rodizio.ro/site/wp-content/uploa…	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
https://visteria.ro	VISTERIA	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label

9 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

a#recipes; https://rodizio.ro/site/wp-content/uploads/2020/09/filetto.jpg; https://rodizio.ro/site/wp-content/uploads/2020/09/t-bon2.jpg; https://rodizio.ro/site/wp-content/uploads/2020/09/tomahawk.jpg; https://rodizio.ro/site/wp-content/uploads/2020/09/cube-roll-wagyu-1.jpg; a#reservation; #

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

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

https://www.instagram.com/rodizio.ro/; https://www.facebook.com/rodizio.ro; https://visteria.ro

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.nav-trigger (#119 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

404 Error Page

Action

HTTP 500, custom page

FIX

HTTP 500, custom page

Unexpected status code: HTTP 500

Expected HTTP 404 but received 500. This may confuse search engine crawlers.

Got: HTTP 500

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 500 ✗Page Title Database Error ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

1 navigation landmark(s) detected

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 1 <nav> element(s)

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.

Lighthouse Accessibility Audits

Action

Score 66/100 — 6 failing, 12 passed

FIX

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
div.container > div.flexbox > div.flexbox__item > button.nav-trigger `div.container > div.flexbox > div.flexbox__item > button.nav-trigger`

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#gallery-1 > figure.gallery-item > div.gallery-icon > a `div#gallery-1 > figure.gallery-item > div.gallery-icon > a`
div#gallery-1 > figure.gallery-item > div.gallery-icon > a `div#gallery-1 > figure.gallery-item > div.gallery-icon > a`
div#gallery-1 > figure.gallery-item > div.gallery-icon > a `div#gallery-1 > figure.gallery-item > div.gallery-icon > a`
div#gallery-1 > figure.gallery-item > div.gallery-icon > a `div#gallery-1 > figure.gallery-item > div.gallery-icon > a`
footer.site-footer > div.copyright-area > div.btn--top > a.btn--top_text `footer.site-footer > div.copyright-area > div.btn--top > a.btn--top_text`

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.

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
Termenul RODIZIO se referă la un restaurant tip steakhouse brazilian. `div.elementor-widget-container > div.pixcode > div.island > p`
Termenul CHURRASCO ia naștere în țările vorbitoare de spaniolă și portugheză du… `div.elementor-widget-container > div.pixcode > div.island > p`
Când vorbim de Churrasco nu ne referim la o simplă carne la grătar ci de un sim… `div.elementor-widget-container > div.pixcode > div.island > p`
VEZI MENIUL RODIZIO AICI `div.pixcode > div.island > h3 > a`
DESPRE NOI `div.pixcode > div.island > p > a.pixcode`
VEZI ÎNTREGUL MENIU `div.pixcode > div.island > p > a.pixcode`
VEZI COLECȚIA DE VINURI `div.pixcode > div.island > p > a.pixcode`
DESPRE RODIZIO CLUJ `div.footer-widget-area > aside.sidebar > div#text-4 > h4.widget__title`
✻ Rodizio este un restaurant cu specific brazilian, unicat în România din câte … `div.footer-widget-area > aside.sidebar > div#text-4 > div.textwidget`
VISTERIA `div.container > div.footer-container > div.copyright-text > a`

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
VISTERIA `div.container > div.footer-container > div.copyright-text > a`

These are opportunities to improve the legibility of your content.

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
GATA SA TE SERVIM `div.c-hero__wrapper > hgroup.article__headline > div.headline__description > h5`
VEZI MENIUL RODIZIO AICI `div.elementor-widget-container > div.pixcode > div.island > h3`
DESPRE RODIZIO CLUJ `div.footer-widget-area > aside.sidebar > div#text-4 > h4.widget__title`

These are opportunities to improve keyboard navigation in your application.

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`

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

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

●Image elements have `[alt]` 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

●Touch targets have sufficient size and spacing.

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

○`[aria-*]` attributes match their roles

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

○ARIA attributes are used as specified for the element's role

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○`[aria-hidden="true"]` elements do not contain focusable descendents

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements use only permitted 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

○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

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

○Skip links are focusable.

○No element has a `[tabindex]` value greater than 0

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

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

Landmark Structure

Action

7 landmarks

REVIEW

7 landmarks

No <main> landmark found

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

1 <nav> landmark(s) found

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

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

Favicon & Branding

Action

3 icon(s) detected

REVIEW

3 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 8 fail WCAG AA

REVIEW

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

12 pass 8 fail WCAG AA

h1 Rodizio

1.11:1

#000000

#1E0C09

needs 3.0:1 (large text)

32px · above the fold

h2 Primary Navigation

1.08:1

#000000

#100D0A

needs 3.0:1 (large text)

24px · top of page (header area) · over background image/gradient

h2 un venit la

1.04:1

#000000

#0F0503

needs 3.0:1 (large text)

24px · above the fold

title RODIZIO - Restaurant brazilian

1.16:1

#000000

#1D150C

needs 4.5:1 (normal text)

16px · top of page (header area)

a Politici de confidențialitate

1.22:1

#000000

#221A12

needs 4.5:1 (normal text)

16px · top of page (header area) · over background image/gradient

a Cookie-uri

1.30:1

#000000

#271F1E

needs 4.5:1 (normal text)

16px · top of page (header area) · over background image/gradient

a Contact

1.30:1

#000000

#281F1D

needs 4.5:1 (normal text)

16px · above the fold

a Starters

1.33:1

#000000

#2E1F1C

needs 4.5:1 (normal text)

16px · above the fold · 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)

Element	Ratio	Required	FG	BG	Result
h1 Rodizio	1.11:1	3.0:1	#000000	#1E0C09	Fail
h1 Rodizio	19.46:1	3.0:1	#000000	#FAF5F6	Pass
h1 Churrasco	19.46:1	3.0:1	#000000	#FAF5F6	Pass
h1 Delicioase	19.46:1	3.0:1	#000000	#FAF5F6	Pass
h1 Meniul	19.46:1	3.0:1	#000000	#FAF5F6	Pass
h1 Blend	19.46:1	3.0:1	#000000	#FAF5F6	Pass
h1 Alese	19.46:1	3.0:1	#000000	#FAF5F6	Pass
h2 Primary Navigation	1.08:1	3.0:1	#000000	#100D0A	Fail
h2 un venit la	1.04:1	3.0:1	#000000	#0F0503	Fail
h2 onceptul	6.98:1	3.0:1	#000000	#979494	Pass
h2 onceptul	19.46:1	3.0:1	#000000	#FAF5F6	Pass
h2 etete	19.46:1	3.0:1	#000000	#FAF5F6	Pass
h2 escopera	19.46:1	3.0:1	#000000	#FAF5F6	Pass
h2 he perfect	19.46:1	3.0:1	#000000	#FAF5F6	Pass
h2 inuri	19.46:1	3.0:1	#000000	#FAF5F6	Pass
title RODIZIO - Restaurant…	1.16:1	4.5:1	#000000	#1D150C	Fail
a Politici de confiden…	1.22:1	4.5:1	#000000	#221A12	Fail
a Cookie-uri	1.30:1	4.5:1	#000000	#271F1E	Fail
a Contact	1.30:1	4.5:1	#000000	#281F1D	Fail
a Starters	1.33:1	4.5:1	#000000	#2E1F1C	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 Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

1 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: 1 all-caps heading(s)

A+

Alt Text Quality

All 12 images OK

PASS

All 12 images OK

5 decorative image(s) correctly marked

7 image(s) with good alt text

12 images 7 good alt text 5 decorative

All images have appropriate alt text.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

A+

Form Input Types

No form controls on this page

PASS

No form controls on this page

A+

Form Input Quality

No form controls on this page

PASS

No form controls on this page

A+

Mobile Keyboard & Autofill

No form controls -- mobile keyboard check is N/A

PASS

No form controls -- mobile keyboard check is N/A

No form controls on this page

A+

Document Language

Lang attribute set to "en-US"

PASS

Lang attribute set to "en-US"

<html lang="en-US"> is set and valid

Got: en-US

A+

Tabindex Anti-Patterns

No explicit tabindex attributes found

PASS

No explicit tabindex attributes found

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

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

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

Mobile-Readable Font Sizes

All 37 visible text node(s) render at >= 12 CSS pixels

PASS

All 37 visible text node(s) render at >= 12 CSS pixels

All text uses legible mobile font sizes (>= 12 CSS px)

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

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.