Website Accessibility (WCAG) for Polish Businesses

November 1, 2025 — Did you know that your website might not comply with current digital accessibility regulations? The European Union directive on website accessibility is already in effect, and Polish regulatory authorities are starting to impose penalties on companies with non-accessible websites.

The Problem: Most small and medium businesses in Poland don’t know that their websites must comply with the WCAG 2.1 standard. Even fewer people know how to check this and what to do to avoid financial penalties.

In this guide, you’ll learn:

• What legal regulations apply in Poland regarding website accessibility
• Penalty amounts for non-accessible websites
• What exactly WCAG 2.1 is and its compliance levels
• 10-point Quick Checklist – check your site in 15 minutes
• Free accessibility testing tools
• When you need a professional WCAG audit

This isn’t a theoretical guide – you’ll find concrete steps, tools, and examples that will help you check and improve your website’s accessibility today.

Key Terms in Simple Words

• WCAG (Web Content Accessibility Guidelines) – international standard for website accessibility
• Digital accessibility – ensuring the site works for people with disabilities (vision, hearing, motor, cognitive)
• Screen Reader – software that reads website content for blind users
• WCAG compliance levels: A (basic), AA (recommended), AAA (highest)
• Alt text – text description of an image for screen readers
• Color contrast – brightness difference between text and background (min. 4.5:1 for AA)
• Keyboard navigation – ability to use the site without a mouse (only Tab, Enter, arrows)

Legal Regulations: Who Must Comply with WCAG and Since When?

EU Digital Accessibility Directive

European Accessibility Act (EAA) and Web Accessibility Directive are two key legal acts that have changed the digital accessibility landscape in Europe.

Who is subject to the requirement:

1. Public sector (since September 23, 2020):

   • All public institutions, offices, schools, hospitals
   • Compliance level: WCAG 2.1 AA
   • Sanctions: financial penalties + obligation to fix

2. Large private companies (since June 28, 2025):

   • E-commerce, banks, insurance, transport, media
   • Companies employing >250 people or turnover >50 million EUR
   • Compliance level: WCAG 2.1 AA

3. SMEs (small and medium enterprises) – in preparation:

   • Planned extension to all commercial sites by 2027-2028
   • Recommended compliance level: WCAG 2.1 AA

Penalties for Non-Accessible Websites in Poland

Polish law provides for specific sanctions:

Public sector:

• Financial penalty: from 5,000 PLN to 50,000 PLN (approximately $1,250-$12,500)
• Immediate correction order
• Publication of information about the violation
• Personal liability of the unit manager

Private sector (large companies):

• Financial penalty: up to 4% of global annual turnover (analogous to GDPR)
• Real cases: penalties of 10,000 - 100,000 PLN ($2,500-$25,000) for EU companies
• Class action lawsuits from organizations representing people with disabilities
• Loss of reputation and customers

Who controls:

• UODO (Personal Data Protection Office) – cooperation with accessibility authorities
• Ombudsman – can initiate proceedings
• Disability organizations – can file complaints
• Individual users – right to file complaint about inaccessible site

Real-world Example (fictional but realistic)

Company X from Silesia, e-commerce (50 employees, 8 million EUR turnover)

• Non-accessible site: no alt text, contrast below 3:1, no keyboard navigation
• Complaint from disabled user: inability to complete purchase
• Authority inspection: confirmed WCAG 2.1 violations
• Penalty: 25,000 PLN + obligation to fix within 30 days
• Additional costs: audit (5,000 PLN) + implementing fixes (15,000 PLN)
• Total cost: 45,000 PLN (~$11,000)

For comparison: Professional WCAG audit + implementing fixes before inspection would cost 8,000 - 15,000 PLN. Prevention is 3x cheaper than fixing after penalty.

What is WCAG 2.1 - 4 Accessibility Principles Explained Simply

WCAG 2.1 is based on 4 fundamental principles, known as POUR:

1. Perceivable - “User Must SEE or HEAR Content”

Content must be presented in a way that the user can perceive with at least one sense.

Key requirements:

✅ Alt text for images

• Every image has an alt="" attribute with description
• Exception: decorative images can have empty alt=""

Example GOOD:

<img src="laptop.jpg" alt="HP EliteBook laptop on desk with open code editor">

Example BAD:

<img src="img001.jpg" alt="image"> <!-- says nothing -->
<img src="hero.jpg"> <!-- no alt! -->

✅ Color contrast minimum 4.5:1 (for normal-sized text)

• Text must be readable also for visually impaired people
• Large text (18pt+ or bold 14pt+): min. 3:1

Example GOOD:

• Black text (#000000) on white background (#FFFFFF) = contrast 21:1 ✅
• Dark gray (#333333) on white = contrast 12.6:1 ✅

Example BAD:

• Light gray (#CCCCCC) on white = contrast 1.6:1 ❌
• Yellow (#FFFF00) on white = contrast 1.1:1 ❌

🔧 How to fix: Use Colour Contrast Analyser tool – you enter background and text color, it shows if it passes WCAG AA.

✅ Captions in video and audio transcripts

• Video on site must have captions (subtitles) for deaf people
• Podcasts / audio should have text transcripts

2. Operable - “User Must INTERACT with Site”

All site functions must be accessible via keyboard (not just mouse).

✅ Keyboard navigation

• Every interactive element must be accessible via Tab
• Logical focus order (top → bottom, left → right)
• Visible focus indicator (border around active element)

30-second test:

1. Go to your site
2. Hide mouse, use only keyboard: Tab (next), Shift+Tab (previous), Enter (click)
3. Can you fill out form? Click buttons? Open menu?

Example BAD:

• Dropdown menu opening only on mouse hover (doesn’t work with keyboard)
• Form where you can’t Tab to “Submit” button
• Focus “jumps” in random order across the page

🔧 How to fix:

• Use semantic HTML (<button>, <a>, <input>) – they have built-in keyboard support
• Add tabindex="0" to custom interactive elements
• Test with real keyboard, not just tools

✅ No “focus traps”

• User can never get “stuck” in an element (e.g., modal dialog without ability to close with Escape)
• All functions accessible without time limit (or with ability to extend)

3. Understandable - “User Must UNDERSTAND Content and Interface”

Content and how the site works must be clear and predictable.

✅ Language declaration

<html lang="en"> <!-- for English -->
<html lang="pl"> <!-- for Polish -->

This allows screen reader to pronounce text with correct accent.

✅ Logical heading structure (H1 → H2 → H3)

• One H1 per page (main title)
• H2 for main sections
• H3 for subsections in H2
• DON’T skip levels (don’t do H1 → H4)

Example GOOD:

<h1>Website Accessibility</h1>
  <h2>Legal Regulations</h2>
    <h3>EU Directive</h3>
    <h3>Penalties in Poland</h3>
  <h2>4 WCAG Principles</h2>
    <h3>Perceivable</h3>
    <h3>Operable</h3>

✅ Form labels connected to inputs

<!-- GOOD -->
<label for="email">Your email:</label>
<input type="email" id="email" name="email">

<!-- BAD -->
Email: <input type="email"> <!-- no connection -->

✅ Error messages clear and helpful

• “Email field is required” instead of “Validation error”
• “Password must have min. 8 characters, 1 digit, 1 capital letter” instead of “Invalid password”

4. Robust - “Site Must WORK in Different Browsers and with Different Assistive Technologies”

HTML code must be correct and compatible with screen readers.

✅ Valid HTML (no validation errors)

• Closed tags
• Unique IDs
• Correct semantic structure

🔧 How to check:

• Paste your site URL into validator.w3.org
• Fix critical errors (red)

✅ ARIA attributes only when needed

• aria-label, aria-describedby, aria-live – for elements without semantic meaning
• Don’t overuse ARIA – better to use semantic HTML

Example:

<!-- ARIA unnecessary (good HTML) -->
<button>Close</button>

<!-- ARIA needed (custom element) -->
<div role="button" aria-label="Close modal" tabindex="0" onclick="closeModal()">×</div>

Quick Win Checklist - 10 Things to Check Now (15 minutes)

Print or save this list and check your site today:

☑️ 1. Do images have alt attribute?

How to check:

• Right-click on image → “Inspect element”
• Check if there’s alt="some description" or alt="" (for decoration)

What to do if missing:

• Add descriptive alt text to all meaningful images
• For icons/decorations use empty alt=""

---

☑️ 2. Is text contrast minimum 4.5:1?

How to check:

• Download Colour Contrast Analyser (free)
• Use eyedropper to click text color and background
• Check result: must be ≥4.5:1 for WCAG AA

What to do if doesn’t pass:

• Change text color to darker or background to lighter
• Simplest: black text (#000) on white (#FFF) = always passes

---

☑️ 3. Can you navigate with keyboard only (Tab + Enter)?

How to check:

1. Go to homepage
2. Hide mouse
3. Press Tab repeatedly – do you see border/focus indicator?
4. Try filling out contact form using only Tab + Enter

What to do if doesn’t work:

• Make sure you use <button>, <a>, <input> (not <div onclick>)
• Add tabindex="0" to custom interactive elements
• Style :focus to be visible (don’t remove outline!)

---

☑️ 4. Do forms have tags?

How to check:

• Inspect form in DevTools
• Check if each <input> has associated <label for="id">

Correct example:

<label for="name">Name:</label>
<input type="text" id="name" name="name">

---

☑️ 5. Do links have descriptive texts (not “click here”)?

How to check:

• Review link texts on site
• Is it clear from link text alone where it leads?

❌ BAD:

• “Click here to learn more”
• “Read more”
• “More…”

✅ GOOD:

• “Read complete WCAG 2.1 guide”
• “Contact through form”
• “Download pricing PDF”

---

☑️ 6. Are headings in logical order (H1→H2→H3)?

How to check:

• Install HeadingsMap extension (Chrome/Firefox)
• Open your site
• Check heading structure – should be hierarchical tree

Correct example:

H1: Homepage
  H2: Our Services
    H3: Business Card Websites
    H3: E-commerce
  H2: About Us
  H2: Contact

---

☑️ 7. Does video have captions (subtitles)?

How to check:

• If you have video on site (YouTube, Vimeo, own)
• Turn on captions/CC – are they available in video language?

What to do if missing:

• YouTube: add captions through YouTube Studio
• Vimeo: upload SRT file with captions
• Own video: use <track> element in HTML5

---

☑️ 8. Does site work at 200% browser zoom?

How to check:

1. Press Ctrl + (or Cmd + on Mac) to zoom page to 200%
2. Check if:
   • Text doesn’t go off screen
   • No need to scroll horizontally
   • Buttons and links still work

What to do if doesn’t work:

• Use responsive CSS (viewport units, media queries)
• Avoid fixed widths in pixels
• Test mobile version – if it works, zoom will too

---

☑️ 9. Is page language declared in HTML?

How to check:

• Right-click → “View page source”
• In first line check if there’s <html lang="en"> (or “pl”)

What to do if missing:

• Add lang="en" to <html> tag
• For multilingual sites: change lang dynamically

---

☑️ 10. Does HTML have validation errors?

How to check:

• Go to validator.w3.org
• Paste your site URL
• Click “Check”

What to do if errors:

• Fix red errors – critical
• Yellow warnings can be skipped if they don’t affect accessibility

---

Results:

• ✅ 8-10 checked – Great! Your site meets basic WCAG requirements
• ⚠️ 5-7 checked – Good start, but gaps to fill
• ❌ Below 5 – Site has serious accessibility problems, you need an audit

Important: This checklist covers ~60% of most common problems. Full WCAG 2.1 AA audit checks 78 success criteria – for that you need a professional auditor or specialized tools.

Free Accessibility Testing Tools

You don’t need to spend money to check basic WCAG compliance. Here are the best free tools:

1. WAVE Browser Extension (best to start)

What it does:

• Shows accessibility problems directly on page
• Colored icons: red (errors), yellow (alerts), green (OK)
• Explains each problem in plain language

How to use:

1. Install WAVE extension for Chrome or Firefox
2. Go to your site
3. Click WAVE icon in extension bar
4. Review red icons – these are critical errors

What it checks:

• Missing alt texts
• Contrast errors
• Missing form labels
• Empty links/buttons
• Heading structure errors

---

2. Lighthouse (built into Chrome)

What it does:

• Comprehensive audit: performance, SEO, accessibility, best practices
• Gives 0-100 score for each category
• List of specific problems to fix

How to use:

1. Open Chrome DevTools (F12)
2. “Lighthouse” tab
3. Check “Accessibility”
4. Click “Analyze page load”
5. After 30 seconds you have report

What it checks:

• 30+ automated WCAG tests
• Color contrast
• ARIA attributes
• Keyboard navigation (partially)
• Semantic HTML

Result:

• 90-100 – Great! Only minor fixes
• 70-89 – Good level, but gaps exist
• 50-69 – Plenty to improve
• Below 50 – Serious problems

---

3. axe DevTools (for developers)

What it does:

• Most advanced free tool
• Finds problems others miss
• Provides code snippets for fixes

How to use:

1. Install axe DevTools for Chrome
2. Open DevTools (F12) → “axe DevTools” tab
3. Click “Scan ALL of my page”
4. Review Issues: Critical, Serious, Moderate, Minor

Advantage: Fewest false positives of all tools.

---

4. Colour Contrast Analyser (desktop app)

What it does:

• Checks color contrast with pixel accuracy
• Shows if it passes WCAG AA and AAA

How to use:

1. Download Colour Contrast Analyser (Windows/Mac)
2. Use eyedropper to click text color
3. Then click background color
4. Check result: Pass/Fail for WCAG AA and AAA

Bonus: You can test colors before implementation (design mockups).

---

5. NVDA Screen Reader (testing like blind person)

What it does:

• Free screen reader for Windows
• Lets you experience how blind people use your site

How to use:

1. Download NVDA (Windows only)
2. Install and run
3. Close your eyes, listen to how NVDA reads your site
4. Try filling out form using only keyboard + NVDA voice

Note: Requires learning, but gives best understanding of accessibility problems.

---

6. W3C HTML Validator (code validation)

What it does:

• Checks if HTML is correct
• HTML errors often cause accessibility problems

How to use:

1. Go to validator.w3.org
2. Paste your site URL
3. Fix red errors

---

Recommended workflow:

1. WAVE – quick scan of basic problems (5 min)
2. Lighthouse – comprehensive audit + score (10 min)
3. axe DevTools – deeper analysis for developers (15 min)
4. Contrast Analyser – checking doubtful colors (5 min)
5. NVDA – test with screen reader (optional, 30 min)

Total time: 35-60 minutes for comprehensive basic test.

When Do You Need a Professional WCAG Audit?

Free tools find 60-70% of problems, but full WCAG 2.1 AA compliance requires manual audit by expert. Here are signals you need professional audit:

Signals You Have a Problem:

✅ You received complaint from disabled user

• Someone reported they can’t use your site
• This is official warning sign before inspection

✅ You’re in mandatory group (public sector, large company)

• You must document compliance with regulations
• You need certificate/compliance report

✅ You have e-commerce with high traffic

• More users = higher complaint risk
• Every % bounce rate is lost revenue

✅ Lighthouse/WAVE shows 10+ critical errors

• Automated tools find only part of problems
• If even auto-tests detect a lot, manual audit will find even more

✅ You’re planning redesign or building new site

• Cheapest is building in accessibility from start
• “Before” audit saves “after” fix costs

✅ You’re applying for certificates/accreditations

• B Corp, ISO, accessibility certificates
• Require documented WCAG compliance

What Does Professional WCAG Audit Look Like?

Audit scope (WCAG 2.1 AA):

1. Automated tests (30% of work):

   • WAVE, axe, Lighthouse, HTML validator
   • Checking all pages + templates

2. Manual tests (50% of work):

   • Keyboard-only navigation through entire site
   • Testing with screen reader (NVDA/JAWS)
   • Checking focus logic and ARIA attributes
   • Testing forms, modals, dropdowns
   • Video/audio content (captions, transcripts)

3. Reporting (20% of work):

   • Detailed report with 78 WCAG 2.1 criteria
   • Prioritization: Critical → High → Medium → Low
   • Cost estimate for fixing each problem
   • Code snippets / screenshots of problems

What you get:

• 📄 PDF Report (30-80 pages) with every found problem
• 📊 Executive Summary – summary for management
• 🛠️ Action Plan – what to fix in what order
• 💰 Fix cost estimate – how much implementation will cost
• ✅ Certificate of Compliance – if site passes (optional)
• 🔄 Re-test after 30 days – checking if fixes worked

Delivery time: 5-10 business days (depending on site size)

Price:

• Small site (10-20 subpages): 1500-3000 PLN (~$375-750)
• Medium site (20-50 subpages): 3000-6000 PLN (~$750-1500)
• Large site (50+ subpages, e-commerce): 6000-15000 PLN (~$1500-3750)

From my experience: I have ISTQB Test Manager certificate and 6+ years experience testing software. WCAG audit is a natural extension of website testing I do for every client. If you want to learn more about automated website testing, read my guide.

Business Benefits of Accessible Website (Not Just Avoiding Penalties)

WCAG compliance isn’t just a “checkbox” to avoid penalty. It’s a real competitive and business advantage:

1. Larger Audience (+15% potential customers)

Facts:

• 15% of population has some form of disability (WHO)
• In Poland that’s 5.7 million people
• Additionally: elderly people (50+), people with temporary limitations (broken arm), parents with children in arms

Accessible site = you can sell to everyone, not just “standard” users.

---

2. Better Google Rankings (SEO boost)

Google rewards accessible sites because:

• Semantic HTML = better content understanding
• Alt texts = additional context for images
• Logical heading structure = easier indexing
• Site speed (often correlates with good code)
• Lower bounce rate (better UX = longer sessions)

Case study:

Company from Silesia, business website:

• Before: Lighthouse Accessibility: 68, average Google position: 15-20
• After WCAG fixes: Lighthouse: 95, average position: 5-8 (+10 positions!)
• Organic traffic: +45% in 3 months

Google explicitly states: “Accessibility is a ranking factor” (especially Core Web Vitals, mobile-first, page experience).

---

3. Lower Bounce Rate and Higher Conversion

Accessible site = easier to use for everyone, not just people with disabilities.

Examples:

• Good text contrast → everyone reads easier (not just visually impaired)
• Clear form labels → fewer filling errors
• Keyboard navigation → power users use shortcuts
• Responsiveness and 200% zoom → seniors don’t need to find glasses

Case study:

E-commerce from Silesia:

• Before accessibility fixes: Conversion 2.1%, bounce rate 68%
• After fixes: Conversion 3.2% (+52%), bounce rate 54% (-20%)
• ROI: Audit cost 4000 PLN, monthly revenue increase +12,000 PLN
• Investment return: 10 days 🚀

---

4. Better Reputation and CSR (Corporate Social Responsibility)

Companies that care about accessibility show they:

• Don’t discriminate against people with disabilities
• Think about all customers, not just “easy” ones
• Are modern and socially aware

Benefits:

• Better PR and media relations
• Distinction in tenders (public sector requires WCAG)
• B Corp, ISO certificates require accessibility
• Better employee opinion (employer branding)

---

5. Compliance with Other Standards (GDPR, ISO, etc.)

WCAG often overlaps with:

• GDPR – transparent forms, clear consents
• ISO 9001 – process and UX quality
• EN 301 549 – European accessibility standard

If you meet WCAG, it’s easier to meet other compliance standards.

---

Benefits summary:

Benefit	Business Impact	ROI
Larger audience	+15% potential customers	Long-term
Better SEO	+20-50% organic traffic	3-6 months
Higher conversion	+30-60% more leads/sales	Immediate
Better reputation	Brand value, media coverage	Long-term
Avoiding penalties	Save 5k-50k PLN	Immediate

FAQ - Most Common Questions About WCAG and Accessibility

Does a small company (10 people) have to comply with WCAG?

Currently (2025): Legal obligation mainly applies to public sector and large companies (250+ employees or 50 million EUR turnover). Small and medium companies don’t have obligation yet, but:

1. Legislative trend: EU plans to extend obligation to SMEs by 2027-2028
2. Legal risk: You can get complaint from disabled user (right to equal treatment)
3. Business benefits: Better SEO, larger customer base, higher conversion (as described above)

Recommendation: Start implementing WCAG gradually (Quick Wins checklist), to be ahead of curve when obligation takes effect.

---

How much does WCAG implementation cost for existing site?

Depends on degree of non-accessibility and site size:

Quick Fixes (basic problems):

• Alt texts, contrast, form labels
• Cost: 500-1500 PLN (~$125-375) (5-10h developer work)
• Effect: Going from Lighthouse 40-60 to 70-85

Medium scope (most problems):

• Above + keyboard navigation, ARIA, HTML structure
• Cost: 2000-5000 PLN (~$500-1250) (15-30h work)
• Effect: Going to 85-95 Lighthouse

Full WCAG 2.1 AA compliance:

• Comprehensive HTML, CSS, JS rebuild
• Manual tests, documentation
• Cost: 5000-15000 PLN (~$1250-3750) (40-100h work)
• Effect: WCAG 2.1 AA compliance certificate

For new site: Building in accessibility from start adds 10-20% project time, but avoids costly fixes later.

From my experience: Sites coded in Astro (like those I create) are by default more accessible than WordPress because:

• Clean, semantic HTML (no bloat from page builders)
• No heavy JS frameworks that break keyboard navigation
• Better control over heading structure and ARIA

Read more about advantages of custom-coded sites vs WordPress.

---

Can WordPress be WCAG compliant?

Yes, but:

• WordPress core is relatively accessible
• Problem: themes and plugins often break WCAG
• Page builders (Elementor, Divi) generate incorrect HTML
• You need to manually test and fix many elements

If you have WordPress:

1. Use accessibility-ready theme (check wordpress.org/themes/tags/accessibility-ready/)
2. Install WP Accessibility plugin
3. Regularly test with WAVE/Lighthouse
4. Avoid heavy page builders

Alternative: Coded sites (Astro, Next.js) give full control over accessibility and are faster. More about modern websites.

---

What if I receive complaint about site non-accessibility?

Action steps:

1. Don’t ignore – respond in 24-48h
2. Ask for details – what exactly doesn’t work?
3. Order immediate WCAG audit – you need problem documentation
4. Present fix plan – “We’ll fix within 30 days”
5. Implement fixes by priority – start with critical problems
6. Inform user about fix – show you took complaint seriously

Important: Most complaints can be resolved amicably if you show good will and quick action.

---

Are video captions mandatory?

For public sector and large companies: YES (WCAG 2.1 AA requires)

For small companies: Currently no legal obligation, but:

• 15% users need captions (deaf, foreign language, watching without sound at work/metro)
• YouTube auto-generated captions are free (though imperfect)
• Captions improve SEO (Google indexes text from captions)

Recommendation: Add captions if video is key to business (product presentation, tutorial). If it’s just “background video” (hero section), not a priority.

---

Is dark mode (dark theme) a WCAG requirement?

No. WCAG doesn’t require dark mode, but requires:

• Contrast ≥4.5:1 regardless of colors (light or dark)
• Ability to adjust – user can change colors in browser/OS

Bonus: If you offer dark mode, it’s a plus for UX and accessibility (some users have photophobia and bright screens hurt them).

Read more about website performance and Core Web Vitals – speed is also an accessibility element.

---

Summary: Accessibility is Investment, Not Cost

Website accessibility (WCAG 2.1) is no longer optional – it’s a legal requirement for many companies and a competitive advantage for all.

Key conclusions:

1. ✅ Regulations already apply – public sector and large companies are obligated, SMEs will be soon
2. ✅ Penalties are real – 5,000 - 50,000 PLN (public sector), up to 4% turnover (large companies)
3. ✅ 4 WCAG Principles: Perceivable, Operable, Understandable, Robust
4. ✅ 10-point Quick Checklist – check basics in 15 minutes (alt texts, contrast, keyboard)
5. ✅ Free tools – WAVE, Lighthouse, axe DevTools are enough to start
6. ✅ Business benefits – better SEO (+20-50% traffic), higher conversion (+30-60%), larger customer base (+15%)

What to do now:

1. Go through Quick Checklist (10 points) – 15 minutes
2. Run WAVE and Lighthouse on your site – 10 minutes
3. Fix Quick Wins (alt texts, contrast, labels) – 1-3 hours work
4. If you have 10+ critical errors or are in mandatory group → order professional WCAG audit

---

Need help with accessibility?

I offer comprehensive accessibility services:

🔍 Quick Audit (free) – I’ll check 10 basic elements of your site and send report in 48h

📊 Full WCAG 2.1 AA Audit – from 1500 PLN (~$375)

• Automated + manual tests
• Report with priorities
• Fix cost estimate
• Compliance certificate (if passes)

🛠️ Implementing Fixes – from 500 PLN (~$125)

• Fixing detected problems
• Re-test after 30 days
• Change documentation

Bonus: Every site I code (from scratch or modernization) is by default tested for WCAG according to ISTQB Test Manager standards. More about my website creation process.

Contact through form or call: +48 697 433 120 (Mon-Fri 9-17, I answer personally).

PS: Accessibility isn’t just “checkbox compliance” – it’s a fundamental part of good UX. Accessible site is easier to use for everyone, not just people with disabilities. It’s an investment that returns many times over through better SEO, larger reach, and higher conversion.