<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Accessibility Doctors – Blog</title>
    <link>https://accessibility.sk/en/</link>
    <atom:link href="https://accessibility.sk/en/feed.xml" rel="self" type="application/rss+xml"/>
    <description>Articles about digital accessibility, legislation and practice.</description>
    <language>en</language>
    <lastBuildDate>Fri, 11 Sep 2026 08:00:00 GMT</lastBuildDate>
    <generator>Eleventy</generator>
    <item>
      <title>A cookie banner that does no harm: focus order, closing it, and the right to change your mind</title>
      <link>https://accessibility.sk/en/blog/accessible-cookie-banner/</link>
      <guid isPermaLink="true">https://accessibility.sk/en/blog/accessible-cookie-banner/</guid>
      <pubDate>Fri, 11 Sep 2026 08:00:00 GMT</pubDate>
      <dc:creator>Accessibility Doctors</dc:creator>
      <description>How to make cookie consent accessible: a region not a modal, Escape as rejection, equal buttons, and a lasting link to change your choice.</description>
      <content:encoded><![CDATA[<p>A cookie banner is the first thing a visitor meets on a website, and in accessibility evaluations it regularly turns out to be the worst part of the entire site. Not because cookie consent is a hard problem, but because almost nobody solves it themselves: a plugin gets dropped in, it renders whatever it renders, and nobody ever checks what that does to keyboard users and screen readers. This article covers the three things that matter most, and explains why a plugin usually fails at all of them.</p>
<h2>1. Focus order: the banner is not a modal window</h2>
<p>Most banners behave like a modal window: as soon as the page loads, they grab keyboard focus, lock scrolling and cover the content. For someone using a keyboard or a screen reader, that means they can only reach the page they actually came for once they've dealt with the banner somehow. That's the wrong order of priorities: cookie consent is not why they came.</p>
<p>A correctly built banner is a <strong>region</strong> with its own heading, placed <strong>early</strong> in the document, right after the skip links, but it <strong>never moves focus onto itself</strong>. A keyboard user finds it after three presses of <kbd>Tab</kbd>; a screen reader user sees it in the list of regions and, on top of that, hears one polite sentence saying the banner exists and where it is. The whole page stays usable even before a decision is made, because until someone decides, nothing beyond the essential is stored.</p>
<p>A modal window only makes sense when you genuinely cannot proceed without a decision. That doesn't apply to cookies: without consent, the analytics and marketing scripts simply don't load. Anyone who insists on a modal window is admitting they want to force consent.</p>
<h2>2. It can always be closed, and rejecting is exactly as easy as accepting</h2>
<p>Two requirements, one technical and one ethical. Technical: the banner must be closable with the <strong><kbd>Escape</kbd> key</strong>, and its content must not be a keyboard trap (criterion 2.1.2). Closing it without a decision counts as rejecting non-essential cookies; that follows from the requirement for consent to be freely given and active.</p>
<p>Ethical: the &quot;Accept all&quot; and &quot;Reject non-essential&quot; buttons must be <strong>equally visible and equally close together</strong>. A greyed-out &quot;Reject&quot; hidden behind a &quot;Settings&quot; button and three clicks away is a dark pattern, which European supervisory authorities — including the Slovak Office for Personal Data Protection and the European Data Protection Board — repeatedly flag as invalid consent. For a user with reduced attention or a cognitive impairment, it's not just an inconvenience, it's a barrier.</p>
<p>Closing also means the banner <strong>must not obscure the focused element</strong> (criterion 2.4.11 in WCAG 2.2). A banner pinned to the bottom of the window covers every button a keyboard user reaches at the end of the page. The fix is simple: while the banner is showing, it writes its height into the document's <code>scroll-padding</code>, and the browser scrolls the focused element above it automatically.</p>
<h2>3. The right to change your mind</h2>
<p>Consent that can't be withdrawn as easily as it was given is not consent. In practice that means a <strong>permanent link or &quot;Change cookie settings&quot; button</strong>, typically in the footer of every page, which opens the same banner with the current choice already set. On closing, focus returns to the button the user came from, exactly as with any other disclosure widget.</p>
<p>Two small things people tend to forget. First, remembering a rejection needs no cookie at all; the browser's local storage is enough. Second, the stored choice should carry a <strong>version</strong>: when a new category or a new tool is added, you bump the version and the banner asks again, instead of the new tool quietly hiding behind old consent.</p>
<h2>Why not to use a plugin</h2>
<p>This isn't dogma; it's experience from audits. Consent management platforms (plugins) regularly have these problems:</p>
<ul>
<li><strong>They load third-party scripts before consent is given.</strong> The plugin itself is often a script from someone else's domain, carrying its own cookies and its own tracking. Cookie consent ends up being collected by a tool that breaches it itself.</li>
<li><strong>Generic ARIA instead of semantics.</strong> A window with no heading, buttons built from <code>div</code> elements, toggles with no labels, <code>aria-hidden</code> slapped on the whole page and forgotten after closing. For a screen reader, the site goes silent.</li>
<li><strong>A focus trap.</strong> Focus gets locked inside the banner, but <kbd>Escape</kbd> doesn't work and the only way out is to give consent.</li>
<li><strong>Content gets covered, with zero support for zooming.</strong> At 400% zoom the banner fills the whole screen and can't be scrolled away.</li>
<li><strong>It can't be checked or fixed.</strong> The code changes without your knowledge, an accessibility evaluation is only valid until the next update, and any bug you find, you can't fix.</li>
<li><strong>Legal risk stays yours.</strong> The duty to obtain consent under Article 5(3) of the ePrivacy Directive (2002/58/EC) as transposed by national law (in Slovakia, § 109(8) of Act No. 452/2021 Coll. on Electronic Communications) and the GDPR's conditions for consent rests with the website operator, not the plugin vendor.</li>
</ul>
<p>A banner you build yourself is a few dozen lines: a region with a heading, three buttons, one group of toggles, and storing the choice. If you need to manage consent for dozens of tools, what you actually need is fewer tools.</p>
<h2>What this looks like in practice</h2>
<p>The <a href="https://accessibility.sk/en/patterns/cookie-banner/">accessible component patterns</a> page has a banner that meets everything above, complete with a keyboard map, screen reader announcements and code to copy. This website doesn't use cookies at all, so the banner is just a demonstration — which makes it all the easier to try out.</p>
<h2>Checklist</h2>
<ul>
<li>The banner is a region with a heading, placed early in the document, with no focus moved onto it after loading.</li>
<li>The page is usable without a decision; nothing non-essential loads before consent.</li>
<li><kbd>Escape</kbd> closes the banner and counts as rejection; keyboard focus can always get out of it.</li>
<li>&quot;Accept&quot; and &quot;Reject&quot; are equal buttons; no categories are pre-checked by default.</li>
<li>The banner doesn't obscure the focused element; the content behind it can still be scrolled into view even at 400% zoom.</li>
<li>The choice can be changed from any page; closing returns focus to the button.</li>
<li>The choice carries a version, and the banner asks again when the categories change.</li>
<li>After saving, a status message sounds, which a screen reader reads without interruption.</li>
</ul>
]]></content:encoded>
    </item>
    <item>
      <title>Just 100 days left…</title>
      <link>https://accessibility.sk/en/blog/100-days-until-the-eaa-applies/</link>
      <guid isPermaLink="true">https://accessibility.sk/en/blog/100-days-until-the-eaa-applies/</guid>
      <pubDate>Thu, 20 Mar 2025 14:01:43 GMT</pubDate>
      <dc:creator>Accessibility Doctors</dc:creator>
      <description>The European Accessibility Act takes effect in 100 days. Find out if it applies to you and get ready for this new legislation.</description>
      <content:encoded><![CDATA[<p>Only 100 days remain until the European Accessibility Act takes effect – <time datetime="2025-06-28">28 June 2025</time> is approaching fast.</p>
<h2>Don't panic…</h2>
<p>First of all, check whether the <strong><a href="https://www.consilium.europa.eu/en/policies/accessibility-goods-services/">European Accessibility Act (EAA)</a></strong> applies to you. But, very briefly: if you run an e-shop, a mobile application, or a website where you offer any kind of service, or if you send electronic invoices to end consumers, the EAA applies to you. If you're not sure, <a href="https://accessibility.sk/en/eaa-check/">check with our test</a>. <strong>B2B is not covered by the EAA</strong>, but if you offer a service that your partners then offer on to their own customers – end consumers – you're simply passing the problem on to them, and either you'll lose those partners, or they'll start passing the responsibility back to you. Take your pick of which is worse… If you also offer services or goods abroad, you'll need to check the local legislation too, since in some countries the EAA may have been implemented more strictly than it has been here.</p>
<p>Why does accessibility matter? Listen to the podcast <a href="https://dennikn.sk/4365396/ako-online-svet-mysli-na-znevyhodnenych-nestacia-krasne-ikonky-kliknut-potrebuju-aj-nevidiaci-ci-ludia-s-trasom-v-rukach/">Denník N</a> recorded with us. We also most recently talked about accessibility for <a href="https://bastadigital.com/podcasty/pristupnost-webu/">Basta Digital</a>.</p>
<p><img src="https://accessibility.sk/assets/img/2025-03-20_14h26_22-2.png" alt="Keep calm and start shipping accessible code. Accessibility.sk"></p>
<p>Accessibility Doctors</p>
<h2>What all needs to be accessible?</h2>
<p>In short? <strong>Everything.</strong> But step by step. It's important to look at the whole spectrum of the service you provide and your communication with customers. Besides your <strong>website</strong>, <strong>mobile application</strong>, <strong>payment processes</strong> and so on, don't forget:</p>
<ul>
<li>published documents, especially contractual or business terms and other legally binding content,</li>
<li>electronic invoices,</li>
<li>instructions or manuals for the products and services you sell,</li>
<li>accessible help and customer support,</li>
<li>electronic communications such as newsletter emails or social media posts,</li>
<li>promotional or informational videos and podcasts.</li>
</ul>
<h2>How do I check accessibility myself?</h2>
<p>You don't need a PhD in information science (although we do have one :-)). To check basic accessibility, all you need to do is… put your mouse aside / turn off the touchpad. It takes some getting used to, but can you reach all the services and functions on your website using only the keyboard? Can you complete the checkout process without a mouse, or send a question through a chat bot? And does the way you move around the page without a mouse make logical sense? Congratulations – you've just checked two very important points: keyboard operability and a meaningful order.</p>
<p>It's only the beginning, but if you've passed this test, the rest will be easier. For example, the <a href="https://wave.webaim.org/extension/">WAVE</a> extension can help you quickly spot:</p>
<ul>
<li>contrast errors,</li>
<li>missing text alternatives for images (unless they're purely decorative or illustrative graphics),</li>
<li>missing labels for form fields,</li>
<li>certain elements that can't be operated using the keyboard.</li>
</ul>
<p>For more thorough testing, you can try <a href="https://accessibilityinsights.io/">Accessibility Insights</a>, which walks you through selected points from the <a href="https://www.w3.org/TR/WCAG21/">WCAG</a> guidelines (the Web Content Accessibility Guidelines – we also helped produce <a href="https://s3.eu-central-1.amazonaws.com/w3c-wcag-2.1-sk/index.html">an unofficial Slovak translation</a> of them). However, no automated tool checks more than 20–30% of the current requirements, and none of them can check accessibility against the EU's applicable standard, <a href="https://www.etsi.org/deliver/etsi_en/301500_301599/301549/03.02.01_60/en_301549v030201p.pdf">EN 301 549 (PDF, 2.2 MB)</a>. They won't verify whether the text alternatives used are accurate, whether users have sufficient instructions before and during form completion and are alerted to errors in a clear and accessible way, whether the reading order through the content is genuinely meaningful, and so on. Just as they miss plenty of real issues, they also frequently report many false positive findings, especially if you use images and background graphics inserted via CSS.</p>
<p>The ultimate test, of course, is using assistive technology, such as <a href="https://www.nvaccess.org/download/">NVDA</a> for Windows, or <a href="https://support.apple.com/en-gb/guide/voiceover/welcome/mac">VoiceOver</a> for macOS. Linux also has its own tool, called <a href="https://help.gnome.org/users/orca/stable/index.html.en">Orca</a>.</p>
<p>To check the accessibility of PDF documents, you can use either the paid version of <a href="https://helpx.adobe.com/acrobat/using/create-verify-pdf-accessibility.html">Adobe Acrobat Pro</a>, or the free <a href="https://pac.pdf-accessibility.org/en">PDF Accessibility Checker PAC 2026</a> (Windows only).</p>
<p>Is this all too much? <strong><a href="https://accessibility.sk/en/services/accessibility-evaluation/">Get in touch and we'll take a look at it together!</a></strong></p>
]]></content:encoded>
    </item>
    <item>
      <title>Accessibility as an opportunity: the path to better UX, higher profits and a stronger brand</title>
      <link>https://accessibility.sk/en/blog/accessibility-as-an-opportunity/</link>
      <guid isPermaLink="true">https://accessibility.sk/en/blog/accessibility-as-an-opportunity/</guid>
      <pubDate>Thu, 06 Mar 2025 10:20:08 GMT</pubDate>
      <dc:creator>Beáta Ďuračová</dc:creator>
      <description>Accessibility improves UX, SEO and business competitiveness, benefits all users and helps meet legislative requirements.</description>
      <content:encoded><![CDATA[<p>Implementing measures to ensure the accessibility of products and services is a legislative obligation that's new to many businesses and companies. It often requires <strong>additional financial resources</strong>, which can be an obstacle for company management – especially where accessibility isn't among their priority areas. Some organisations are willing to <strong>accept the risk of a fine</strong>, because they see investment in accessibility as an extra cost that doesn't bring immediate returns.</p>
<p>When deciding what will or won't be implemented, it's worth also considering the benefits accessibility can bring to a business. There are, in fact, <strong>numerous benefits that can turn accessibility into added value for a company and improve its competitiveness</strong>.</p>
<h2>Accessibility helps you win more customers and strengthen your brand</h2>
<p><strong>More accessible digital solutions mean a larger customer base</strong>, since persons with disabilities, older people, or people with temporary limitations (such as a broken arm or a short-term deterioration in eyesight) will find it easier to use the services and products on offer. By removing barriers, we win their trust and their satisfaction with our products and services. Companies that adapt to the new requirements in good time <strong>minimise the risk of legal disputes and sanctions</strong>, including financial penalties, while also <strong>building a positive image as a socially responsible brand</strong>.</p>
<h2>Accessibility improves the user experience for everyone</h2>
<p><img src="https://accessibility.sk/assets/img/pristupnost-zlepsuje-ux.jpg" alt="Laptop with an open website about the design and development of digital services."></p>
<p>Accessibility isn't just about meeting requirements for persons with disabilities – <strong>it improves the overall user experience (UX) for everyone</strong>. When a website, mobile application or digital product is designed with an emphasis on simplicity, intuitiveness and usability, all users benefit. <strong>What specific improvements does accessibility bring?</strong></p>
<ul>
<li><strong>Clearer navigation</strong> – A clear, consistent menu, a logical content layout, and the ability to operate the site by keyboard or voice command make it easier for everyone to use, not just for persons with disabilities.</li>
<li><strong>Better colour contrast and readability</strong> – Properly set colour contrast, sufficiently large text and clear typography reduce eye strain and improve the readability of content for older people and people with temporarily reduced eyesight (for example, tired eyes when working at night), as well as on screens exposed to direct sunlight or when projected onto a large screen, where poor colour contrast can significantly reduce readability.</li>
<li><strong>Simpler forms and interactions</strong> – Well-designed forms with clear labels, properly flagged errors and the ability to auto-fill data improve efficiency and reduce user frustration.</li>
<li><strong>Clearer content</strong> – Using plain language, short sentences and well-structured text helps not only people with cognitive impairments, but also all users reading on mobile devices or who aren't native speakers of the site's language.</li>
<li><strong>Adaptability across devices</strong> – Accessible design is responsive, meaning it displays correctly on mobiles, tablets and desktops alike. This leads to better user comfort and prevents visitors from leaving the site. Responsive design is also important for SEO, since, from <time datetime="2024-07-05">5 July 2024</time>, the <a href="https://developers.google.com/search/blog/2024/06/mobile-indexing-vlast-final-final.doc">Google crawler only indexes websites that are responsive</a>.</li>
</ul>
<h2>Accessibility and SEO: better visibility in search engines</h2>
<p>One of the less-discussed but very important benefits of accessibility is its <strong>positive impact on SEO (search engine optimisation)</strong>. When a website is accessible, it often also meets key SEO requirements that improve its position in organic search results. <strong>How exactly does accessibility affect SEO?</strong></p>
<ul>
<li><strong>Better content structure</strong> – Using correctly marked-up headings (H1, H2, H3, etc.), a logical hierarchy of information and well-organised sections help search engines better understand the page's content and increase its relevance.</li>
<li><strong>Text alternatives for images</strong> – Search engines can't &quot;see&quot; images, but they can read their text alternatives. Correctly written text alternatives help not only blind users, but also how the page is displayed in search engines.</li>
<li><strong>Faster page loading</strong> – Optimising for accessibility often involves removing unnecessary elements, which speeds up page loading. Google treats loading speed as an important factor when ranking pages in search results.</li>
<li><strong>Mobile accessibility = higher Google ranking</strong> – Since Google enforces <strong>mobile-first indexing</strong> (ranking based on the mobile version of the page), responsive design and accessibility for touch devices can significantly affect your SEO score.</li>
<li><strong>Clearer, more understandable text</strong> – Using plain language and short paragraphs improves readability not only for users, but also for search engines, which can then better understand the page's content.</li>
<li><strong>Meaningful hyperlinks, even out of context</strong> – Descriptive and unambiguous link text (e.g. &quot;Read the overview of WCAG 2.2 changes&quot; instead of &quot;Click here&quot;) improves orientation on the website and helps search engines better understand the connections between pages.</li>
</ul>
<h2>Getting ready for the future of the digital market</h2>
<p>With the EAA's effective date approaching, it's <strong>essential for organisations to start adapting their digital solutions as soon as possible</strong>. Implementing accessibility measures requires thorough planning, testing and a gradual roll-out of changes, especially for large digital platforms. The sooner companies begin this implementation, the easier and more cost-effective it will be for them to adapt to the new standards.</p>
<p>Thorough preparation not only enables companies to meet legal requirements, but also to <strong>gain a competitive advantage and support innovation in the digital environment</strong>. This allows businesses to set themselves apart from the competition and contribute to <strong>building a more inclusive digital society, where everyone has equal access to information and services</strong>.</p>
<p>We can help you prepare and plan the implementation of accessibility requirements – read more in our <a href="https://accessibility.sk/en/services/">Services</a> section.</p>
]]></content:encoded>
    </item>
  </channel>
</rss>
