Accessibility Audit Report

fotando.global

Completed27 Jun 2026, 12:17viewport 756 × 413

Accessibility score

F42 / 100

Critical issues

Weighted by issue severity and affected elements.

Affected elements by severity

Critical0

Serious3

Moderate26

Minor0

Rule violations

Affected elements

Passed checks

Manual review

Executive summary

fotando.global scored 42/100 — a failing grade driven by issues that block core functionality for people with disabilities.

Across the page, automated checks flagged 5 distinct rule violations affecting 29 elements: 3 serious and 26 moderate.

A further 2 checks could not be evaluated automatically and require manual review, while 34 checks passed. Remediating the most frequent serious issue — links must have discernible text — will clear the highest-impact barriers first.

Methodology

Scanned against WCAG 2.0 / 2.1 success criteria at a 756 × 413 viewport, with the results mapped to practical EN 301 549 and European Accessibility Act readiness. Automated testing detects only part of WCAG risk; pair it with manual keyboard and assistive-technology testing for full coverage.

Legal compliance risk

Digital Accessibility Act readiness

Since 28 June 2025, the European Accessibility Act (Directive (EU) 2019/882) has applied to covered digital services across the EU market. Many organizations refer to this as the Digital Accessibility Act in procurement and compliance work. In practice, websites, apps, e-commerce, banking, transport, media and support journeys should align with EN 301 549 and WCAG AA expectations.

Non-compliance can trigger formal complaints, corrective orders, national authority investigations, financial penalties in EUR, reputational harm, contract loss, and restrictions on placing or keeping a non-conforming service in the market. This audit found 5 accessibility issues that may expose your organization to this risk and should be remediated promptly.

Priority implication: treat critical checkout, booking, account, payment and support barriers as commercial and compliance risks, not only technical defects. Remediation evidence can help demonstrate due diligence if customers, public buyers or regulators request proof of accessibility work.

Findings

5 rule violations, grouped by severity.

Serious2 rules · 3 elements

Moderate3 rules · 26 elements

Serious

2 rules · 3 elements

Seriouslink-name

elements

Links must have discernible text

Ensure links have discernible text

WCAG 2.0 AWCAG 2.4.4WCAG 4.1.2

Why it matters

Causes significant barriers for assistive-technology users. Should be fixed soon.

How to fix

→Element does not have text that is visible to screen readers
→aria-label attribute does not exist or is empty
→aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
→Element has no title attribute
→Element is in tab order and does not have accessible text

Where — sample elements

.ftnd-footer__logo

<a href="/" aria-current="page" class="ftnd-footer__logo w-inline-block w--current"><img src="https://cdn.prod.website-files.com/650b2a76fde940fccd85293f/675e1487321ce7c46749afe1_footer-logo.png" loading="lazy" width="Auto" alt="" class="ftnd-footer__logo-image"></a>

.ftnd-footer__social-item-link

<a href="https://www.linkedin.com/in/ovsvlad/" class="ftnd-footer__social-item-link w-inline-block"><img src="https://cdn.prod.website-files.com/650b2a77fde940fccd852a21/675e21b29fc96480c93bd93a_icon-linkedIn.png" loading="lazy" alt="" class="ftnd-footer__social-item-icon"></a>

Learn more ↗

Serioushtml-has-lang

element

<html> element must have a lang attribute

Ensure every HTML document has a lang attribute

WCAG 2.0 AWCAG 3.1.1

Why it matters

Causes significant barriers for assistive-technology users. Should be fixed soon.

How to fix

→The <html> element does not have a lang attribute

Where — sample elements

html

<html data-wf-domain="www.fotando.global" data-wf-page="675db093716db936a46e4a1b" data-wf-site="650b2a76fde940fccd85293f" class="w-mod-js w-mod-ix wf-albertsans-n5-active wf-albertsans-n7-active wf-albertsans-n4-active wf-albertsans-n6-active wf-albertsans-n3-active wf-active">

Learn more ↗

Moderate

3 rules · 26 elements

Moderateregion

elements

All page content should be contained by landmarks

Ensure all page content is contained by landmarks

Best practice

Why it matters

Creates friction and a degraded experience for some users.

How to fix

→Some page content is not contained by landmarks

Where — sample elements

.ftnd-hero__content

<div class="ftnd-hero__content">

.ftnd-column-flex-child-tablet-w100.ftnd-column-flex-child-w50 > .ftnd-container-horiz-wauto > .button-group > .button-wrapper__ftnd-hero.button-wrapper:nth-child(1) > .is-icon.button[target="_blank"] > .button-inner > .button_text

<div class="button_text">Book a 30-Minute Call</div>

.ftnd-section_data

<div class="ftnd-section ftnd-section_black ftnd-section_data">

+ 20 more affected elements

Learn more ↗

Moderateheading-order

elements

Heading levels should only increase by one

Ensure the order of headings is semantically correct

Best practice

Why it matters

Creates friction and a degraded experience for some users.

How to fix

→Heading order invalid

Where — sample elements

.ftnd-hero__slogan

<h4 class="heading-style-h4 ftnd-hero__slogan">We help CEOs and COOs at 100-500 person companies scale 2-5x — by diagnosing the one thing blocking growth and building a working AI solution in 2-4 weeks. Not a roadmap. A working solution.</h4>

.ftnd-workflow__item.ftnd-container-flex-parent-horiz-w100:nth-child(1) > .ftnd-workflow__item-description > .ftnd-workflow__item-number

<h4 class="heading-style-h4 ftnd-workflow__item-number"><strong class="bold-text-3">01</strong></h4>

Learn more ↗

Moderatelandmark-one-main

element

Document should have one main landmark

Ensure the document has a main landmark

Best practice

Why it matters

Creates friction and a degraded experience for some users.

How to fix

→Document does not have a main landmark

Where — sample elements

html

<html data-wf-domain="www.fotando.global" data-wf-page="675db093716db936a46e4a1b" data-wf-site="650b2a76fde940fccd85293f" class="w-mod-js w-mod-ix wf-albertsans-n5-active wf-albertsans-n7-active wf-albertsans-n4-active wf-albertsans-n6-active wf-albertsans-n3-active wf-active">

Learn more ↗

Needs manual review

2 checks could not be decided automatically and should be verified by a person.

aria-valid-attr-value1

ARIA attributes must conform to valid values

Ensure all ARIA attributes have valid values

color-contrast2

Elements must meet minimum color contrast ratio thresholds

Ensure the contrast between foreground and background colors meets WCAG 2 AA minimum contrast ratio thresholds

Passed checks34

Automated checks that returned no violations on this page.

aria-allowed-attr
aria-allowed-role
aria-command-name
aria-conditional-attr
aria-deprecated-role
aria-hidden-body
aria-prohibited-attr
aria-required-attr
aria-required-children
aria-required-parent
aria-roles
aria-valid-attr-value
aria-valid-attr
avoid-inline-spacing
bypass
color-contrast

+ 18 more passed checks

Choose Your Path to Compliance

Select the option that works best for you

AI-Powered Fix Instructions

Get detailed, step-by-step instructions with AI assistance to fix issues yourself

✓Code examples and solutions
✓Priority-based guidance
✓Instant access

Full Manual Audit by Expert

Order a comprehensive manual audit from accessibility specialists

✓Expert human review
✓Detailed remediation report
✓Priority support