The Complete Guide to Web Accessibility for 2026

Key Takeaways

  • Slovakia implements the EAA’s service accessibility requirements through Act No. 351/2022 Coll. and Government Regulation No. 283/2023 Coll. WCAG and EN 301 549 provide technical accessibility criteria, but their legal status depends on the applicable legislation and harmonisation.
  • The European Accessibility Act (EAA) has applied since 28 June 2025. It covers defined categories of products and consumer services, not automatically every business website.
  • Slovakia implemented the EAA through Act No. 351/2022 Coll. and Government Regulation No. 283/2023 Coll. Administrative fines range from €200 to 3% of the previous accounting period’s turnover, subject to maximum limits of €6,000, €20,000 or €30,000 depending on the infringement.
  • Micro-enterprises are excluded from the service requirements under Act No. 351/2022 Coll. A micro-enterprise must employ fewer than 10 people and have annual turnover or an annual balance sheet total not exceeding €2 million.
  • Native HTML elements provide built-in semantics and keyboard behaviour, but their accessibility still depends on correct implementation, labelling and interaction handling.
  • ARIA should be used only when native HTML cannot achieve the required functionality. Misused ARIA can harm accessibility.
  • Automated tools catch only a portion of accessibility issues. Manual testing with keyboards, screen readers and real users remains essential.
  • WCAG contrast requirements are 4.5:1 for normal text and 3:1 for large text.
  • EN 301 549 v4.1.1, aligned with WCAG 2.2, was published in September 2026. Its publication does not automatically make it a harmonised standard under the EAA.
  • WCAG 3.0 is a working draft and should not be used as a compliance standard. It is incomplete and will change substantially.

Web accessibility is a fundamental requirement for modern digital products. More than a billion people globally live with some form of disability, meaning that inaccessible websites exclude a significant portion of the population. Beyond legal mandates, accessibility supports inclusion, usability and equal access to information and services.

This guide explains web accessibility through native HTML elements, ARIA roles and attributes, screen readers, colour accessibility, testing practices and the legal framework in Slovakia and the European Union.

Why Web Accessibility Matters

Web accessibility helps make websites and digital services usable by people with different abilities. This includes people with visual, auditory, physical, speech, cognitive, language, learning and neurological disabilities.

Accessibility also overlaps with good information architecture and search engine optimisation. Semantic headings, descriptive links, meaningful text alternatives and clear page structure can improve how people and assistive technologies understand content. These practices can also help search engines interpret a page, although accessibility compliance does not guarantee higher search rankings.

European Accessibility Act (EAA), Directive (EU) 2019/882

The European Accessibility Act (EAA), established by Directive (EU) 2019/882, has applied since 28 June 2025. It introduces harmonised accessibility requirements for specific categories of products and services provided to consumers across the European Union.

The legislation covers defined product and service categories, including consumer financial services, e-books, specialised software, information society services and digital components of specified passenger transport services.

Key principles:

  • Accessibility requirements apply to the products and services covered by the Directive.
  • Service providers must ensure that their services meet the applicable accessibility requirements throughout their provision.
  • Member States implement and enforce these requirements through national legislation.
  • Technical standards help establish and assess accessibility, but publication of a standard does not automatically make it a legally harmonised reference.

A company website is not automatically covered simply because it is publicly accessible. The relevant question is whether the website or application is used to provide a product or service that falls within the legislation’s scope, and whether an exclusion or exemption applies.

Slovak Act No. 351/2022 Coll.

Slovakia transposed the European Accessibility Act through Act No. 351/2022 Coll. on the accessibility of products and services for persons with disabilities. Government Regulation No. 283/2023 Coll. sets out related technical requirements.

The Act establishes accessibility requirements, obligations for service providers, supervisory responsibilities and administrative penalties.

Scope of application

Under §2, the Act covers defined categories of services provided to consumers, including:

  • Passenger transport services: specified websites, mobile applications, electronic ticketing systems, ticket sales and real-time travel information.
  • Financial services provided to consumers.
  • Electronic books and specialised software.
  • Information society services, including online services that fall within the statutory definition.

The Act does not automatically apply to every company website. Its applicability depends on the nature of the product or service, the statutory scope and any applicable exclusions.

Enforcement

The Slovak Trade Inspection (SOI) and other designated supervisory authorities oversee compliance within their respective areas of responsibility.

Penalties

Under §10, administrative fines range from €200 to 3% of the previous accounting period’s turnover, subject to the following maximum amounts:

  • €6,000 for certain accessibility and information-related infringements.
  • €20,000 for certain procedural and corrective-action infringements.
  • €30,000 for failure to provide requested documentation, information or cooperation.

Corrective measures may also be required. The applicable maximum depends on the type of infringement.

Micro-enterprise Exemption

Under §2(3) of Act No. 351/2022 Coll., services provided by micro-enterprises are excluded from the accessibility requirements of this Act.

To qualify as a micro-enterprise, a business must satisfy both of the following conditions:

  • Fewer than 10 employees.
  • Annual turnover not exceeding €2 million or an annual balance sheet total not exceeding €2 million.

Both conditions must be satisfied. The employee threshold is mandatory, but the business can meet either of the two financial thresholds.

The exemption applies to services provided by qualifying micro-enterprises. It is not limited exclusively to e-commerce services.

Existing Services and Transitional Provisions

Act No. 351/2022 Coll. includes specific transitional provisions under §12.

A service provided under a contract concluded by 28 June 2025 may remain exempt from the accessibility requirements until the contract expires, but no later than 28 June 2030.

This does not mean that every website created or launched before 28 June 2025 automatically receives an exemption until 2030.

The Act also excludes certain previously published content from its accessibility requirements, subject to the conditions in the legislation:

  • Pre-recorded time-based media published before 28 June 2025.
  • Office file formats published before 28 June 2025.
  • Websites and mobile applications qualifying as archives, containing only content that has not been updated or edited after 28 June 2025.

These provisions have specific conditions. They should not be interpreted as a general exemption for all existing websites or all content published before the deadline.

Accessibility Information and Provider Obligations

Act No. 351/2022 Coll. imposes obligations that extend beyond the technical accessibility of a website or digital service.

Under §6, service providers must make information about the accessibility of their services publicly available.

This information must be included in the general terms and conditions for providing the service or an equivalent document. It must contain:

  • A general description of the service in accessible formats.
  • Descriptions and explanations necessary to understand how the service works.
  • A description of how the service meets the applicable accessibility requirements.

The information must be available in written and oral formats, including formats accessible to persons with disabilities, throughout the period in which the service is provided.

Providers must also establish procedures to maintain accessibility when the service or applicable accessibility requirements change.

Accessibility compliance therefore involves both the technical implementation of the service and the information and processes maintained by its provider.

WCAG Versions: What You Need to Know in 2026

The Web Content Accessibility Guidelines (WCAG) are published by the World Wide Web Consortium (W3C). They provide testable success criteria for making web content more accessible.

VersionStatusApplication
WCAG 2.1W3C RecommendationIncorporated into EN 301 549 v3.2.1, harmonised under the Web Accessibility Directive for public-sector websites and applications.
WCAG 2.2W3C RecommendationIncorporated into EN 301 549 v4.1.1, published in September 2026. A forward-looking accessibility benchmark.
WCAG 3.0Working DraftIncomplete and not suitable as a compliance standard. It remains under development and may change substantially.

EN 301 549 is the European standard covering accessibility requirements for information and communication technology.

Version 3.2.1 aligns its web accessibility requirements with WCAG 2.1 Level A and AA. It is harmonised under the EU Web Accessibility Directive, which governs public-sector websites and mobile applications.

EN 301 549 v4.1.1 was published in September 2026. It updates the web accessibility requirements to WCAG 2.2 Level A and AA.

However, publication of v4.1.1 does not automatically make it a harmonised standard under the European Accessibility Act. Formal citation in the Official Journal of the European Union is required for that status.

As of 30 October 2026, v4.1.1 had not yet been formally cited as an EAA harmonised standard.

For service providers covered by the EAA, the applicable legal requirements arise from the Directive and its national implementation. In Slovakia, these include Act No. 351/2022 Coll. and Government Regulation No. 283/2023 Coll.

WCAG 2.2 is a sensible technical target for organisations preparing for future accessibility requirements, even while its formal harmonisation status remains pending.

WCAG success criteria are organised into three conformance levels:

  • Level A: The minimum level, addressing fundamental accessibility barriers.
  • Level AA: Addresses a broader range of common barriers and is the conformance level frequently used in accessibility requirements and procurement.
  • Level AAA: The highest level, with more demanding criteria. It is not generally practical or required for every page and type of content.

Native HTML Elements: Accessibility by Design

Native HTML elements provide built-in semantics and keyboard behaviour. They give browsers and assistive technologies information about the purpose and expected behaviour of page components.

However, native elements are not automatically accessible in every implementation. Developers still need to provide appropriate labels, meaningful structure, visible focus, correct states and usable interaction behaviour.

Semantic Landmarks

Semantic HTML elements help assistive technology users identify and navigate the main regions of a page.

ElementPurposeImplementation notes
<main>Primary content of the page.Use for the page’s main content. Avoid multiple visible main landmarks on the same page.
<header>Introductory content for a page or section.A top-level header can provide the banner landmark. A header inside an article or section does not have the same landmark role.
<footer>Footer content for a page or section.A top-level footer can provide the contentinfo landmark. A footer inside an article or section is scoped to that content.
<nav>A major navigation block.Give separate navigation landmarks distinct accessible names when a page has more than one.
<aside>Complementary content related to the surrounding content.Its landmark exposure depends on its context and accessible naming.
<article>Self-contained, independent content.Useful for content that can stand on its own, such as an article, post or comment.
<section>A thematic grouping of related content.Use a heading to identify the section. A section becomes a region landmark when it has an accessible name.

Using <main> instead of <div role="main"> provides native semantics and reduces unnecessary ARIA. The same principle applies to elements such as <nav>, <header> and <footer>, while remembering that their landmark behaviour depends on context.

Form Elements

Native HTML form controls such as <button>, <input>, <select> and <textarea> provide built-in keyboard behaviour and browser interaction patterns.

A native button, for example, can be activated with Enter or Space without custom JavaScript. That does not remove the need to implement accessible labels, instructions, validation messages, error identification and logical focus handling.

Every form control should have an accessible name. Use a visible <label> associated with the relevant control whenever possible. Group related controls with <fieldset> and <legend> where appropriate.

Example: Semantic HTML Structure

The following example shows a basic semantic page structure. The headings identify the content sections, and the navigation landmarks have accessible names.

<header>
  <a href="/" rel="home">Website name</a>

  <nav aria-label="Primary navigation">
    <!-- Primary navigation links -->
  </nav>
</header>

<main>
  <article>
    <h1>Article title</h1>

    <section aria-labelledby="section-one">
      <h2 id="section-one">Section heading</h2>
      <p>Introductory content for this section.</p>

      <section aria-labelledby="subsection-one">
        <h3 id="subsection-one">Subsection heading</h3>
        <p>Content for this subsection.</p>
      </section>
    </section>
  </article>

  <aside aria-labelledby="related-content">
    <h2 id="related-content">Related content</h2>
    <!-- Related links or supplementary information -->
  </aside>
</main>

<footer>
  <!-- Site footer content -->
</footer>

ARIA Roles and Attributes

ARIA (Accessible Rich Internet Applications) provides additional information about roles, names, states and properties to assistive technologies. It is useful when building custom interface components or communicating information that native HTML does not provide.

ARIA does not automatically make a custom component keyboard-accessible. Developers must still implement its interaction model, focus handling, state changes and keyboard behaviour.

When a suitable native HTML element exists, use it instead of recreating its behaviour with generic elements and ARIA.

ARIA Roles

ARIA roles describe the purpose of an element to assistive technologies.

Role categoryPurposeExamples
Document structureDescribes the structure or organisation of content.toolbar, tooltip, presentation
Widget rolesIdentifies interactive interface components.slider, tab, treeitem, switch
Landmark rolesIdentifies important regions of a page.banner, complementary, main, navigation, search
Live region rolesCommunicates dynamic content changes.alert, log, status, timer
Window rolesIdentifies window-like components within a document.alertdialog, dialog
Abstract rolesProvides internal role definitions used by ARIA.Do not use abstract roles directly in HTML.

Many landmark roles have native HTML equivalents. For example, <main> exposes the main landmark, and <nav> exposes a navigation landmark. Adding a redundant role is usually unnecessary. Incorrect role assignments can also change or obscure the semantics that browsers would otherwise expose.

ARIA States and Properties

ARIA states and properties communicate the current state of an element or relationships between elements to assistive technologies.

Common ARIA attributes include:

AttributePurpose
aria-labelProvides an accessible name when visible text does not provide one.
aria-labelledbyReferences another element that supplies the accessible name.
aria-describedbyReferences content that provides additional information or instructions.
aria-expandedIndicates whether a collapsible component is expanded or collapsed.
aria-hiddenRemoves an element and its descendants from the accessibility tree when set to true.
aria-liveIdentifies a region where dynamic content changes may need to be announced.
aria-requiredCommunicates that a form control is required. Native required is preferable for standard form controls.
aria-invalidCommunicates that the current value of a form control is invalid.

ARIA attributes must reflect the actual state of the interface. For example, aria-expanded="true" should only be used while the associated content is expanded.

When to Use ARIA

  • Use ARIA when: A custom component needs an accessible role, name, state or relationship that native HTML does not provide. Examples include custom tabs, dialogs, tree views and specialised controls.
  • Avoid unnecessary ARIA when: A native HTML element already provides the required semantics and behaviour. Redundant or incorrect ARIA can override native semantics or communicate a state that does not match the interface.

Always test custom components with a keyboard and assistive technologies. Adding ARIA attributes alone does not establish that a component works correctly.

Screen Readers

Screen readers are assistive technologies that interpret webpage content and communicate it through speech or braille output. They allow people who are blind or have low vision to navigate content, identify controls and interact with digital services.

Common screen readers include:

  • JAWS (Windows)
  • NVDA (Windows), a free and open-source screen reader
  • VoiceOver (macOS, iOS and iPadOS)
  • TalkBack (Android)

Making Content Screen-Reader Friendly

Use the following practices to make page content easier to understand and navigate:

  1. Use semantic HTML. Semantic elements help screen readers identify headings, landmarks, lists, links, form controls and other content structures.
  2. Provide appropriate text alternatives for images. Describe meaningful images according to their purpose. Use an empty alt attribute for decorative images so they can be ignored by assistive technology.
  3. Maintain a logical heading structure. Use headings from <h1> to <h6> to represent the content hierarchy. Do not choose heading levels only for their visual appearance.
  4. Provide meaningful landmark navigation. Use semantic landmarks and give multiple navigation regions distinct accessible names where needed.
  5. Keep focus indicators visible. Do not remove browser focus outlines unless you provide a visible alternative with sufficient contrast.

Example image markup:

<!-- Meaningful image -->
<img
  src="beach.jpg"
  alt="A sunny beach with palm trees and a clear blue sky"
>

<!-- Decorative image -->
<img src="divider.png" alt="">

Alternative text should communicate the information or function of an image. Avoid describing decorative details that do not help users understand the surrounding content.

Colour Accessibility

Colour accessibility is important for people with colour vision deficiencies and for anyone viewing content in conditions that make colour differences difficult to distinguish.

Designers should avoid relying solely on colour to communicate meaning. They should also ensure sufficient contrast between text, controls, icons and their backgrounds.

Contrast Ratios

WCAG 2.x defines minimum contrast ratios for text:

Text typeMinimum contrast ratio
Normal text4.5:1
Large text (at least 18pt or 14pt bold)3:1

Large text can use the lower contrast ratio because its size and weight make it easier to distinguish. Contrast should be checked for the actual foreground and background colours, including relevant states such as hover and focus.

Tools for checking contrast ratios include:

Avoid Relying Solely on Colour

Colour should not be the only method of conveying information. For example, an error message should not rely only on red text. Include a clear text message and, where useful, an icon or another visual indicator.

<!-- Insufficient: the error is communicated only through colour -->
<span style="color: red;">Invalid email address</span>

<!-- Better: the error is identified with text -->
<span role="alert">
  <span aria-hidden="true">!</span>
  Invalid email address
</span>

For form fields, associate the error message with the relevant control. Use aria-describedby when necessary so assistive technologies can identify the explanation when the user focuses the field. Use live announcements where an error or status change needs to be communicated immediately.

Colour Blindness Simulators

Colour blindness simulators help designers understand how interfaces may appear to people with different types of colour vision deficiencies.

Useful tools include:

  • Color Oracle: Desktop application.
  • WhoCanUse: Web-based colour accessibility preview.
  • Chrome DevTools: Includes colour vision deficiency emulation.

Simulation is useful during design review, but it does not replace contrast measurement or testing with users.

Accessibility obligations depend on the type of organisation, product or service and the legislation that applies. The European Accessibility Act and the Web Accessibility Directive have different scopes. They should not be treated as interchangeable laws.

European Union

LawApplicabilityRequirements
European Accessibility Act (EAA)Providers of products and services within the Directive’s defined scope, subject to exemptions and exclusions.Applicable accessibility requirements under the EAA and national implementing legislation.
Web Accessibility DirectivePublic-sector websites and mobile applications within the Directive’s scope.Accessibility requirements based on the applicable harmonised standard, including EN 301 549.

Slovakia

LawApplicabilityPenalties or requirements
Act No. 351/2022 Coll.Providers of services within the Act’s scope, subject to micro-enterprise exemptions and other statutory exclusions.€200 to 3% of previous accounting period turnover, capped at €6,000, €20,000 or €30,000 depending on the infringement.
Act No. 95/2019 Coll.Public administration information technologies and websites within its scope.Public-sector accessibility obligations under the applicable Slovak rules and technical requirements.

Enforcement in Slovakia is carried out by the Slovak Trade Inspection (SOI) and other designated supervisory authorities within their respective areas of responsibility.

Testing and Validation Tools

Accessibility testing should combine automated checks with manual evaluation. Automated tools can identify many technical issues, but they cannot reliably determine whether every task can be completed with a keyboard or whether content makes sense when read by assistive technology.

ToolPurposePlatform
WAVEVisual accessibility evaluation and identification of common issues.Browser extension and website
axe DevToolsAutomated accessibility testing.Browser extensions for major browsers
LighthouseAccessibility audits alongside performance and SEO checks.Chrome DevTools
NVDAScreen reader testing.Windows
VoiceOverScreen reader testing.macOS and iOS
Colour Contrast AnalyserContrast ratio measurement.Desktop application

Use automated results as a starting point. Follow up with manual keyboard testing, screen reader testing, form completion and checks of interactive states.

Practical Steps for Implementing Accessibility

1. Start with Semantic HTML

Prioritise native HTML elements such as <main>, <header>, <article>, <section>, <nav>, <button> and <label>. They provide standard semantics and interaction behaviour, but still require correct structure, accessible names and implementation.

2. Provide Text Alternatives

Provide appropriate text alternatives for non-text content. Use descriptive alternative text for meaningful images, captions for video with audio, and transcripts where they are needed to make audio content available in text form. Decorative images should generally use an empty alt attribute.

3. Use ARIA Judiciously

Use ARIA when native HTML cannot communicate the role, name, state or relationship required by a custom component. Do not add redundant roles or attributes to native elements. Test custom components with a keyboard and screen reader.

4. Ensure Keyboard Accessibility

All interactive functionality should be operable with a keyboard. Test using Tab, Shift+Tab, Enter, Space and the arrow keys where appropriate. Check that:

  • Interactive elements receive focus in a logical order.
  • Focus is visibly indicated and is not obscured.
  • Every action available by pointer is also available through the keyboard.
  • Custom controls implement the keyboard interaction expected for their role.
  • Modal dialogs manage focus while open and return focus to the invoking control when closed.

5. Test with Real Users

Automated tools catch only a portion of accessibility issues. Testing with people who use assistive technologies can reveal barriers that automated checks and developer-only testing may miss. Include users with different access needs when the scope and resources of the project allow it.

6. Validate Colour Contrast

Check text contrast against its actual background and verify contrast in relevant interface states. Do not rely on visual judgement alone. Use a contrast analyser to verify the required ratios.

7. Provide Captions for Videos

Provide accurate, synchronised captions for prerecorded video content that includes audio. Captions should include relevant spoken dialogue and meaningful sounds. Live video may have separate captioning requirements. Do not rely on automatically generated captions without checking their accuracy.

Use descriptive link text that explains the destination or purpose. Avoid generic labels such as “Click here” or “Read more” when the context is not clear.

Instead of:

Click here to learn more.

Use:

Learn more about our accessibility services.

9. Properly Label Form Fields

Associate every form control with a visible label whenever possible. Do not use placeholder text as the only label. Provide clear instructions, identify errors in text and associate error messages with their corresponding fields.

<label for="email">Email address:</label>
<input
  type="email"
  id="email"
  name="email"
  autocomplete="email"
  required
>

For groups of related controls, use <fieldset> and <legend> where appropriate.

10. Maintain Focus and State Management

After interactions such as form submissions, validation failures and modal closures, ensure that focus remains in a meaningful location. Announce important status changes to assistive technologies when necessary. Keep accessible states, such as aria-expanded and aria-invalid, synchronised with the actual interface.

Conclusion

Creating accessible websites is an important responsibility for developers and designers. Semantic HTML, appropriate ARIA, screen reader support, keyboard operation, readable content and sufficient colour contrast all contribute to a more usable experience.

The European Accessibility Act has applied since 28 June 2025. Slovakia implements its service accessibility requirements through Act No. 351/2022 Coll. and Government Regulation No. 283/2023 Coll. These regulations establish accessibility obligations, provider responsibilities and penalties for non-compliance. EN 301 549 v4.1.1, published in September 2026, introduces WCAG 2.2 as the updated technical benchmark for European ICT accessibility. Its formal harmonisation under the EAA remains a separate regulatory step.

Accessibility should be integrated into the development process from the start, not added as an afterthought. Proper implementation can improve usability, expand access to information and services, and help organisations meet applicable accessibility requirements. It should be maintained as websites, services and technologies change.

Resources

Accessibility standards and technical guidance

European and Slovak legislation

Other international legislation

The following resources concern other jurisdictions. They are useful for international comparisons but do not establish the accessibility obligations that apply in Slovakia:

Playful Sparkle has been engineering digital products since 2004, offering UI/UX & Web Design, Web Development and accessibility consulting services. Our team can help you audit and improve your website’s accessibility against applicable requirements under the European Accessibility Act and Slovak Act No. 351/2022 Coll. Our approach combines technical accessibility testing, practical remediation and forward-looking implementation based on WCAG 2.2. Contact us to discuss how we can help you create a more accessible digital experience.

Was this helpful - Post
Zsolt Oroszlány

Zsolt Oroszlány

Founder & Chief Creative Officer of Playful Sparkle since 2004, combining business leadership, digital strategy, design, and software engineering to help organizations build effective digital solutions. Regularly publishes insights on web development, SEO, design, and emerging technologies.