Accessibility
· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.DAlt Text QualityAction8 of 21 images have issuesFIX
| Issue | Count |
|---|---|
| missing | 4 image(s) |
| filename | 4 image(s) |
Images without alt text are invisible to screen readers.
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
DForm AccessibilityAction5 of 9 controls have issuesFIX
| Control | Type | Label | Method |
|---|---|---|---|
| s | text | Enter your search | aria-label |
| input | submit | Search | aria-label |
| #wt-cli-checkbox-necessary | checkbox | Necessary | for/id |
| #wt-cli-checkbox-non-necessary | checkbox | Non-necessary | for/id |
| s | text | (Enter your search) | placeholder only |
| name | text | (Introdu numele) | placeholder only |
| text | (Introdu adresa de email aici) | placeholder only | |
| submit | submit | (none) | none |
| input | submit | (none) | none |
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
<input type="submit" name="submit">; <input type="submit">
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="name">; <input type="text" name="email">; <input type="text" name="s">
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
FLink & Button QualityAction9 issue(s) across 96 links and 5 buttonsFIX
| Element | Text | Issue | Suggested Fix |
|---|---|---|---|
| https://wa.me/40752888816?text=Salut%2C%… | AI Agent… | new tab | Add '(opens in new tab)' to text |
| https://forum.muffingroup.com/betheme/ | Support forum | new tab | Add '(opens in new tab)' to text |
| https://themeforest.net/item/betheme-res… | Buy it now | new tab | Add '(opens in new tab)' to text |
| https://www.macaraledeinchiriat.eu/cerer… | CERE OFERTĂ | new tab | Add '(opens in new tab)' to text |
| https://macaraledeinchiriat.eu/macarale-… | Read more | generic text | Replace with descriptive text |
Before: Read more Suggested: Macara Automontanta Smh 321 2 | |||
| https://macaraledeinchiriat.eu/macarale-… | Read more | generic text | Replace with descriptive text |
Before: Read more Suggested: Macara Automontanta Smh 260 | |||
| https://macaraledeinchiriat.eu/macarale-… | Read more | generic text | Replace with descriptive text |
Before: Read more Suggested: Macara Automontanta Simma Gta 62 | |||
| https://macaraledeinchiriat.eu/macarale-… | Read more | generic text | Replace with descriptive text |
Before: Read more Suggested: Macara Automontanta Dalbe 2025 Hs 251 | |||
| https://macaraledeinchiriat.eu/disponibi… | Read more | generic text | Replace with descriptive text |
Before: Read more Suggested: Macara Automontanta Neofin Ght 2460 | |||
| https://macaraledeinchiriat.eu/macarale-… | Read more | generic text | Replace with descriptive text |
Before: Read more Suggested: Macara Turn Raimondi Mr75 | |||
| https://macaraledeinchiriat.eu/wp-conten… | (empty) | empty | Add link text or aria-label |
| https://www.fortza.ro | FORTZA | new tab | Add '(opens in new tab)' to text |
| https://www.baboon.ro | Baboon.ro | new tab | Add '(opens in new tab)' to text |
| https://www.macaraledeinchiriat.eu/cerer… | CERE OFERTĂ | new tab | Add '(opens in new tab)' to text |
| # | (empty) | empty | Add link text or aria-label |
| https://www.macaraledeinchiriat.eu/polit… | Vezi mai multe detalii | new tab | Add '(opens in new tab)' to text |
| <input> | (empty) | empty | Add button text or aria-label |
Links without text are announced as raw URLs by screen readers.
https://macaraledeinchiriat.eu/wp-content/uploads/2025/05/20-de-ani-de-experi…; #
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
Generic link text like 'click here' doesn't describe the destination.
https://macaraledeinchiriat.eu/macarale-automontante-autoridicatoare/macara-a… ("Read more"); https://macaraledeinchiriat.eu/macarale-automontante-autoridicatoare/macara-a… ("Read more"); https://macaraledeinchiriat.eu/macarale-automontante-autoridicatoare/macara-a… ("Read more"); https://macaraledeinchiriat.eu/macarale-automontante-autoridicatoare/macara-a… ("Read more"); https://macaraledeinchiriat.eu/disponibile/macara-automontanta-neofin-ght-2460/ ("Read more"); https://macaraledeinchiriat.eu/macarale-turn/macara-turn-raimondi-mr75/ ("Read more")
Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.
Learn more ▾ ▴
Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.
Source: WCAG 2.4.4 / Google Search Central
Add '(opens in new tab)' to link text or aria-label.
https://wa.me/40752888816?text=Salut%2C%20ma%20intereseaza%20o%20oferta%20pen…; https://forum.muffingroup.com/betheme/; https://themeforest.net/item/betheme-responsive-multipurpose-wordpress-theme/…; https://www.macaraledeinchiriat.eu/cerere-oferta-macara; https://www.fortza.ro; https://www.baboon.ro; https://www.macaraledeinchiriat.eu/cerere-oferta-macara; https://www.macaraledeinchiriat.eu/politica-de-confidentialitate/
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.
input[type="submit"].display-none (#676 on page)
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
DMobile Keyboard & AutofillAction2/2 eligible field(s) missing autocomplete or inputmodeFIX
F404 Error PageActionHTTP 500, custom pageFIX
FFavicon & BrandingAction1 icon(s) detectedFIX
DWeb ManifestActionNot foundFIX
No web manifest found.
DPrint StylesheetActionNo print stylesFIX
CLandmark StructureAction17 landmarksREVIEW
A page should have only one <main> landmark.
Multiple <main> elements violate the spec — there must be exactly one per page.
Learn more ▾ ▴
HTML5 spec: 'authors must not include more than one main element' visible to AT at the same time. Multiple <main>s confuse AT and break the 'jump to main content' shortcut. Refactor to a single <main> with nested <section>/<article>.
Source: HTML5 spec
Multiple navigations need aria-label to distinguish them for screen readers.
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.
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
CHeading HierarchyAction22 headings, 2 skip(s)REVIEW
- H1 MACARALE DE ÎNCHIRIAT SAU DE VÂNZARE
- H1 Macarale de închiriat sau de vânzare pentru businessul tău duplicate H1
- H3 Macara turn skipped
- H3 Macara automontanta
- H3 Montaj macarale
- H3 Transport macarale
- H3 Service macarale
- H3 Accesorii macara
- H2 Sună pentru a afla lista de Macarale disponibile
- H2 Macara automontanta SMH 321
- H2 Macara automontanta SMH 260
- H2 Macara Automontanta Simma GTA 62
- H2 Macara Automontanta Dalbe 2025 HS 251
- H2 Închiriere macara automontantă Neofin GHT 2460
- H2 Închiriere Macara turn Raimondi MR75
- H2 Probabil găseşti la noi cam tot ce ai nevoie pe şantierul tău.
- H4 Noutăţi despre macarale pe email skipped
- H2 Macarale de închiriat sau de vânzare în toată România
- H2 Despre noi
- H2 Servicii & Produse
- H3 FORTZA.RO SRL
- H4 Privacy Overview
A page should have only one H1. Multiple H1s dilute the document outline.
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.
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.
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
CTap Target AdequacyAction7 tap target(s) too small or too close togetherREVIEW
BMobile-Readable Font Sizes95% of visible text renders at >= 12 CSS px (4 below threshold)REVIEW
BDark Mode SupportDark mode detectedREVIEW
Detection limited to meta tags and inline styles.
BColor Contrast (Screenshot)20 text elements analyzed, 0 fail WCAG AAREVIEW
Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.
Show all checked elements (20)
| Element | Ratio | Required | FG | BG | Result |
|---|---|---|---|---|---|
| h1 MACARALE DE ÎNCHIRI… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h1 Macarale de închiri… | 5.24:1 | 3.0:1 | #000000 | #7F7F7F | Pass |
| h2 Sună pentru a afla … | 5.24:1 | 3.0:1 | #000000 | #7F7F7F | Pass |
| h2 Probabil găseşti l… | 5.24:1 | 3.0:1 | #000000 | #7F7F7F | Pass |
| h2 Macarale de închiri… | 5.24:1 | 3.0:1 | #000000 | #7F7F7F | Pass |
| h2 Despre noi | 5.24:1 | 3.0:1 | #000000 | #7F7F7F | Pass |
| h2 Servicii & Produse | 5.24:1 | 3.0:1 | #000000 | #7F7F7F | Pass |
| h3 Macara turn | 5.24:1 | 3.0:1 | #000000 | #7F7F7F | Pass |
| h3 Macara automontanta | 5.24:1 | 3.0:1 | #000000 | #7F7F7F | Pass |
| h3 Montaj macarale | 5.24:1 | 3.0:1 | #000000 | #7F7F7F | Pass |
| h3 Transport macarale | 5.24:1 | 3.0:1 | #000000 | #7F7F7F | Pass |
| h3 Service macarale | 5.24:1 | 3.0:1 | #000000 | #7F7F7F | Pass |
| h3 Accesorii macara | 5.24:1 | 3.0:1 | #000000 | #7F7F7F | Pass |
| h3 FORTZA.RO SRL | 5.24:1 | 3.0:1 | #000000 | #7F7F7F | Pass |
| title Închiriere macara |… | 5.24:1 | 4.5:1 | #000000 | #7F7F7F | Pass |
| div Ai nevoie de ajutor?… | 5.24:1 | 4.5:1 | #000000 | #7F7F7F | Pass |
| div Contactează-ne — … | 4.82:1 | 4.5:1 | #000000 | #797979 | Pass |
| span Agent AI WhatsApp | 4.82:1 | 4.5:1 | #000000 | #797979 | Pass |
| span Răspunde instant 24… | 4.82:1 | 4.5:1 | #000000 | #797979 | Pass |
| span Sună-ne acum | 5.10:1 | 4.5:1 | #000000 | #7D7D7D | 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.
CLighthouse Accessibility AuditsActionScore 70/100 — 9 failing, 19 passedREVIEW
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
Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Toggle submenu nav#menu > ul#menu-main-menu > li#menu-item-62 > a.menu-toggle |
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
+40 269 838 450 div.column > div.mcb-column-inner > a.button > span.button_label |
aside#wp_subscribe-3 > div#wp-subscribe > form#wp-subscribe-form-1 > input.regular-text aside#wp_subscribe-3 > div#wp-subscribe > form#wp-subscribe-form-1 > input.regular-text |
aside#wp_subscribe-3 > div#wp-subscribe > form#wp-subscribe-form-1 > input.regular-text aside#wp_subscribe-3 > div#wp-subscribe > form#wp-subscribe-form-1 > input.regular-text |
Vom trimite doar mesaje despre oferta de macarale şi nimic altceva. Maxim un me… div.mcb-column-inner > aside#wp_subscribe-3 > div#wp-subscribe > p.footer-text |
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
FORTZA div.column > div.mcb-column-inner > div.copyright > a |
Baboon.ro div.column > div.mcb-column-inner > div.copyright > 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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Macara turn div.icon_box > a > div.desc_wrapper > h3.title |
NOUTĂŢI DESPRE MACARALE
PE EMAIL div.mcb-column-inner > aside#wp_subscribe-3 > div#wp-subscribe > h4.title |
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.image_frame > div.image_wrapper > div.image_links > a.zoom div.image_frame > div.image_wrapper > div.image_links > a.zoom |
div.image_frame > div.image_wrapper > div.image_links > a.link div.image_frame > div.image_wrapper > div.image_links > a.link |
div.image_frame > div.image_wrapper > div.image_links > a.zoom div.image_frame > div.image_wrapper > div.image_links > a.zoom |
div.image_frame > div.image_wrapper > div.image_links > a.link div.image_frame > div.image_wrapper > div.image_links > a.link |
div.image_frame > div.image_wrapper > div.image_links > a.zoom div.image_frame > div.image_wrapper > div.image_links > a.zoom |
div.image_frame > div.image_wrapper > div.image_links > a.link div.image_frame > div.image_wrapper > div.image_links > a.link |
div.image_frame > div.image_wrapper > div.image_links > a.zoom div.image_frame > div.image_wrapper > div.image_links > a.zoom |
div.image_frame > div.image_wrapper > div.image_links > a.link div.image_frame > div.image_wrapper > div.image_links > a.link |
div.image_frame > div.image_wrapper > div.image_links > a.zoom div.image_frame > div.image_wrapper > div.image_links > a.zoom |
div.image_frame > div.image_wrapper > div.image_links > a.link div.image_frame > div.image_wrapper > div.image_links > a.link |
div.image_frame > div.image_wrapper > div.image_links > a.zoom div.image_frame > div.image_wrapper > div.image_links > a.zoom |
div.image_frame > div.image_wrapper > div.image_links > a.link div.image_frame > div.image_wrapper > div.image_links > a.link |
div.mcb-column-inner > aside#block-10 > figure.wp-block-image > a div.mcb-column-inner > aside#block-10 > figure.wp-block-image > 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.
Tables and lists
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
CUI: 9947416
Str. Gării nr. 10, 551010, Mediaş – SB
+40 269 838 450
office@fo… div.column > div.mcb-column-inner > aside#block-9 > ul.contact-list |
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Str. Gării nr. 10, 551010, Mediaş – SB aside#block-9 > ul.contact-list > a.link-footer > li |
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.
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Macara automontanta SMH 321 div.post-desc > div.post-title > h2.entry-title > a |
Macara automontanta SMH 260 div.post-desc > div.post-title > h2.entry-title > a |
Macara Automontanta Simma GTA 62 div.post-desc > div.post-title > h2.entry-title > a |
Macara Automontanta Dalbe 2025 HS 251 div.post-desc > div.post-title > h2.entry-title > a |
+40 269 838 450 aside#block-9 > ul.contact-list > li > a |
office@fortza.ro aside#block-9 > ul.contact-list > li > a |
www.fortza.ro aside#block-9 > ul.contact-list > li > a |
These items highlight common accessibility best practices.