Skip to content
https://rotarydrobeta.org

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
75
GRADE
C
FIX
7
REVIEW
4
PASS
13
INFO
0
Checks
24
13 PASS 4 REVIEW 7 FIX
D
Landmark Structure
Action
5 landmarks
FIX
5 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
2 <nav> landmark(s) found
Warning::
1 of 2 <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 (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

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

D
Form Accessibility
Action
6 of 7 controls have issues
FIX
6 of 7 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="text" name="honeypot" id="form_honeypot">; <input type="submit">
Warning::
4 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="pirate-forms-contact-name" id="pirate-forms-contact-name">; <input type="email" name="pirate-forms-contact-email" id="pirate-forms-contact-email">; <input type="text" name="pirate-forms-contact-subject" id="pirate-forms-contact-subject">; <textarea name="pirate-forms-contact-message" id="pirate-forms-contact-message">
Info::
1 control(s) properly labeled
7 controls
1 labeled
4 placeholder only
2 unlabeled
ControlTypeLabelMethod
#adminbar-searchtextCautăfor/id
#pirate-forms-contact-emailemail(Emailul tău)placeholder only
#pirate-forms-contact-subjecttext(Subiect)placeholder only
#pirate-forms-contact-messagetextarea(Mesajul tău)placeholder only
#pirate-forms-contact-nametext(Numele tău)placeholder only
#form_honeypottext(none)none
inputsubmit(none)none

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

<input type="text" name="honeypot" id="form_honeypot">; <input type="submit">

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="pirate-forms-contact-name" id="pirate-forms-contact-name">; <input type="email" name="pirate-forms-contact-email" id="pirate-forms-contact-email">; <input type="text" name="pirate-forms-contact-subject" id="pirate-forms-contact-subject">; <textarea name="pirate-forms-contact-message" id="pirate-forms-contact-message">

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

F
Favicon & Branding
Action
No icons detected
FIX
No icons 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::
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'>.
Critical::
No favicon or icon links detected
Your site will show the browser's generic page icon in tabs, bookmarks, and home screens.
✗ favicon.ico Missing
✗ PNG Icons Missing
✗ 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::
2 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 2 <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
Tabindex Anti-Patterns
1 positive, 4 -1-on-focusable
REVIEW
1 positive, 4 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <input id="incredere">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <input id="corectitudine">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <input id="prietenie">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <input id="utilitate">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Warning::
Positive tabindex on <a>: tabindex=1
Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 3 fail WCAG AA
REVIEW

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

17 pass 3 fail WCAG AA
title Rotary Club Drobeta Turnu Severin Contin…
1.32:1
#000000
on
#1D2327
needs 4.5:1 (normal text)
16px · top of page (header area)
span Comută navigarea
1.18:1
#000000
on
#15181B
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
a Sari la conținut
1.05:1
#000000
on
#080808
needs 4.5:1 (normal text)
16px · top of page (header area)

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 Rotary Club Drobeta …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Obiectivele noastre21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Despre noi21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Sponsorii noştri21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Proiecte21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Ultimele ştiri21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Contactaţi-ne21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Vocaţional21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Comunitatea21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Internaţional21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Noua generaţie21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Donaţi pentru copii…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Google21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Google21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Google21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Google21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Redirecţionaţi 2% …21.00:13.0:1
#000000
#FFFFFF
Pass
title Rotary Club Drobeta …1.32:14.5:1
#000000
#1D2327
Fail
span Comută navigarea1.18:14.5:1
#000000
#15181B
Fail
a Sari la conținut1.05:14.5:1
#000000
#080808
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 88/100 — 4 failing, 28 passed
REVIEW
88

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

When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
HAI LA FILM! Vino sa descoperi viața de licean, cu povești de iubire, cu pasiu… section#latestnews > div.container > div#carousel-homepage-latestnews > div.carousel-inner

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.

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
Vino sa descoperi viața de licean, cu povești de iubire, cu pasiuni dar și deza… div.item > div.col-sm-3 > div.latesnews-content > p
UPDATE 19 DECEMBRIE 2025 Cea de-a doua etapa a proiectului O cana de fericire s… div.item > div.col-sm-3 > div.latesnews-content > p
UPDATE 14 noiembrie 2025 Festivitatea de premiere Cupa Rotary Drobeta ediția a … div.item > div.col-sm-3 > div.latesnews-content > p
Promenada 2024! Pe o vreme nu foarte prielnică, cu in suflet, ne-am întâlnit, s… div.item > div.col-sm-3 > div.latesnews-content > p
Zerif Lite developed by ThemeIsle footer#footer > div.container > div.col-md-3 > div.zerif-copyright-box

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
Read more about Hai la film! […] div.col-sm-3 > div.latesnews-content > p > a
Read more about O cană de fericire, ediția a 2-a, decembrie 2025 […] div.col-sm-3 > div.latesnews-content > p > a
Read more about Cupa Rotary la șah, Ediția a III-a […] div.col-sm-3 > div.latesnews-content > p > a
ThemeIsle div.container > div.col-md-3 > div.zerif-copyright-box > a.zerif-copyright

These are opportunities to improve the legibility of your content.

Navigation

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Sari la bara de unelte body.home-page > div#wpadminbar > a.screen-reader-shortcut

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
●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
●`[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.
●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
●ARIA toggle fields have accessible names
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links have a discernible name
●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.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with the `role=text` attribute do not have focusable descendents.
○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
○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.
○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.
A+
Heading Hierarchy
25 headings
PASS
25 headings
Info::
Single H1 present
  • H1 Rotary Club Drobeta Turnu Severin Continental, Romania
  • H2 Obiectivele noastre
  • H3 Vocaţional
  • H3 Comunitatea
  • H3 Internaţional
  • H3 Noua generaţie
  • H3 Donaţi pentru copiii din Drobeta Turnu Severin şi judeţul Mehedinţi
  • H2 Despre noi
  • H2 Sponsorii noştri
  • H3 Google
  • H3 Google
  • H3 Google
  • H3 Google
  • H2 Proiecte
  • H3 Redirecţionaţi 2% din impozitul pe venit pentru acţiuni caritabile
  • H2 Ultimele ştiri
  • H3 Hai la film!
  • H3 O cană de fericire, ediția a 2-a, decembrie 2025
  • H3 Cupa Rotary la șah, Ediția a III-a
  • H3 Promenada inimilor 2024
  • H3 O cană de fericire (final)
  • H3 O cană de fericire (5)
  • H3 O cană de fericire (4)
  • H3 O cană de fericire (3)
  • H2 Contactaţi-ne
A+
Heading Text Quality
All 25 heading(s) have substantive, well-formed text
PASS
All 25 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
All 22 images OK
PASS
All 22 images OK
Info::
9 decorative image(s) correctly marked
Info::
13 image(s) with good alt text
22 images 13 good alt text 9 decorative
All images have appropriate alt text.
A+
Form Input Types
1 input(s) using type=text where a specific type would help
PASS
1 input(s) using type=text where a specific type would help
Info::
Input "s" should use type="search" (currently type="text")
Field name "s" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
A+
Form Input Quality
7 form control(s) checked, no input-semantic issues
PASS
7 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
No autofill-eligible form controls (no name/email/tel/address fields)
A+
Document Language
Lang attribute set to "ro-RO"
PASS
Lang attribute set to "ro-RO"
Info::
<html lang="ro-RO"> is set and valid
Got: ro-RO
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
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
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
Mobile-Readable Font Sizes
All 138 visible text node(s) render at >= 12 CSS pixels
PASS
All 138 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
A
404 Error Page
HTTP 404, custom page
PASS
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
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Nu am găsit pagina – Rotary Club Drobeta Turnu Severin Continental ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
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.

Send Feedback