{"id":9393,"date":"2025-12-19T12:15:00","date_gmt":"2025-12-19T12:15:00","guid":{"rendered":"https:\/\/halkoo.com\/?p=9393"},"modified":"2025-12-12T11:30:19","modified_gmt":"2025-12-12T11:30:19","slug":"accessibilita-digitale-cosa-cambia-per-siti-web-e-commerce-e-applicazioni","status":"publish","type":"post","link":"https:\/\/halkoo.com\/en\/digital-accessibility-what-changes-for-websites-e-commerce-and-applications\/","title":{"rendered":"Digital accessibility: what changes for websites, e-commerce and applications"},"content":{"rendered":"

For years, accessibility was treated as a 'nice to have': useful, right, but often postponed because it was perceived as expensive or complex. Today, this is no longer the case. In Europe, accessibility is becoming a market requirement, with clear deadlines and obligations, and closely concerns not only institutional sites, but also online shops, customer portals, reserved areas, web management, CRM, CMS and business applications<\/strong>.<\/p>\n\n\n\n

The aim is simple: to enable people with disabilities (but also elderly users, with temporary limitations, or in 'difficult' conditions of use such as strong light, small screens, slow connections) to navigate, understand and complete actions<\/strong> without barriers.<\/p>\n\n\n\n

The 'new law' in brief: the European and Italian frameworks<\/h2>\n\n\n\n

The central reference is theEuropean Accessibility Act (EU Directive 2019\/882)<\/strong>which establishes accessibility requirements for a number of products and services<\/strong> in the European market. The directive became fully applicable from 28 June 2025<\/strong>.<\/p>\n\n\n\n

In Italy, transposition took place with the Legislative Decree No. 82 of 27 May 2022<\/strong>which regulates the accessibility requirements for the relevant products and services placed on the market as of the planned date.<\/p>\n\n\n\n

One practical aspect to be aware of: the Italian decree provides a targeted exemption for the micro-companies providing services<\/strong> (in a nutshell: less than 10 employees and annual turnover within 2 million), but this does not mean that it is 'not convenient' to adapt - it means that the obligation may change depending on the service provider and the context.<\/p>\n\n\n\n

What 'accessible' really means (beyond the graphic theme)<\/h2>\n\n\n\n

When we talk about accessibility, we are talking about the ability of a digital service to be:<\/p>\n\n\n\n

    \n
  • perceptible<\/strong>: content usable even without seeing well or hearing (alternative texts, subtitles, contrast, etc.).<\/li>\n\n\n\n
  • usable<\/strong>all functions must be reachable and completable (even only from the keyboard, with screen reader, with adequate time)<\/li>\n\n\n\n
  • understandable<\/strong>language, labels, errors and messages should help the user understand what is happening and how to solve a problem<\/li>\n\n\n\n
  • robust<\/strong>: the code must 'support' assistive technologies and different navigation modes<\/li>\n<\/ul>\n\n\n\n

    These principles are consistent with the most internationally cited standard: the WCAG (Web Content Accessibility Guidelines)<\/strong>today in the version 2.2<\/strong> published as a W3C standard.<\/p>\n\n\n\n

    \n

    Important: it is not just 'put a bigger button' or 'increase contrast'. Accessibility is a set of choices of design, content, development and quality control<\/strong>.<\/p>\n<\/blockquote>\n\n\n\n

    Where accessibility has the greatest impact: shops, portals and web apps<\/h2>\n\n\n\n

    In the real world, the most costly (and most frequent) problems arise when the user has to complete an action. Some typical examples:<\/p>\n\n\n\n

      \n
    • E-commerce<\/strong>: unreadable filters, variants that cannot be selected from the keyboard, modals that trap focus, unclear checkout errors, CAPTCHA or OTP not handled correctly<\/li>\n\n\n\n
    • Reserved areas and customer portals<\/strong>complex menu navigation, non-interpretable tables, graphics without text alternatives, inaccessible document downloads<\/li>\n\n\n\n
    • CRM \/ management \/ CMS web<\/strong>dense interfaces, undocumented shortcuts, custom UI components not compatible with assistive technologies, notifications and status changes 'invisible' to screen readers<\/li>\n<\/ul>\n\n\n\n

      In other words: the more 'application' the product, the more accessibility becomes a structural requirement, not a finishing touch.<\/p>\n\n\n\n

      Common sense' rules that almost always make a difference<\/h2>\n\n\n\n

      Without going into endless technical checklists, there are some general rules that, consistently applied, cover a large part of the problems:<\/p>\n\n\n\n

        \n
      • Full keyboard navigation<\/strong>everything must be reachable, in a logical order, without 'traps'.<\/li>\n\n\n\n
      • Focus always visible<\/strong>: the user must understand where he or she is while navigating<\/li>\n\n\n\n
      • Contrast and readability<\/strong>: readable text, appropriate size, no information relying solely on colour<\/li>\n\n\n\n
      • Clear labels and instructions<\/strong>: form fields, buttons and actions must also be understandable out of context<\/li>\n\n\n\n
      • Useful errors<\/strong>: if a form fails, the error must explain what to correct and where<\/li>\n\n\n\n
      • Semantic structure<\/strong>: titles, lists, tables and landmarks used correctly (not just 'div everywhere')<\/li>\n\n\n\n
      • Accessible media content<\/strong>textual alternatives, subtitles, usable controls<\/li>\n\n\n\n
      • Accessible dynamic components<\/strong>menus, modals, tooltips, dropdowns, AJAX carts must communicate state changes in an accessible manner<\/li>\n<\/ul>\n\n\n\n

        The idea is to design for the real user: the one who does not use a mouse, the one who zooms in at 200%, the one who navigates with a screen reader, the one who needs more time or more explicit messages.<\/p>\n\n\n\n

        It's not just 'technical': we need process (and accountability)<\/h2>\n\n\n\n

        Accessibility cannot be solved once. It needs a process:<\/p>\n\n\n\n

          \n
        • clear requirements already at the design stage<\/li>\n\n\n\n
        • development with consistent and tested components<\/li>\n\n\n\n
        • quality control before releases (especially on checkouts and critical flows)<\/li>\n\n\n\n
        • maintenance over time (new content, new pages, new features)<\/li>\n<\/ul>\n\n\n\n

          For the public sector in Italy, for example, there is also the concept of Declaration of accessibility<\/strong> as a transparency tool on the status of the digital service.
          In the private sector, the picture may vary depending on the type of service and applicable obligations, but the logic remains the same: measure, report, improve.<\/p>\n\n\n\n

          Accessibility = less risk, more conversions, better product<\/h2>\n\n\n\n

          Compliance is not just 'compliance'. In practice, it often means:<\/p>\n\n\n\n

            \n
          • fewer drop-outs<\/strong> (especially on mobile and checkout)<\/li>\n\n\n\n
          • fewer tickets<\/strong> support (login, account recovery, incomprehensible forms)<\/li>\n\n\n\n
          • cleaner interfaces<\/strong> and clearer content<\/li>\n\n\n\n
          • a more robust and easier to evolve product<\/li>\n<\/ul>\n\n\n\n

            And, above all, it reduces the risk of having to 'run for cover' when adaptation becomes urgent.<\/p>\n\n\n\n

            Do you want to understand whether your site, shop or management system is compliant?<\/h2>\n\n\n\n

            If you want a concrete opinion on your case (showcase site, e-commerce, reserved area, CRM\/web management, custom CMS), write to me: we can make a initial assessment<\/strong> and understand what the priority interventions are to make your project aligned with accessibility legislation<\/strong> and, above all, easier for everyone to use.<\/p>","protected":false},"excerpt":{"rendered":"

            Per anni l\u2019accessibilit\u00e0 \u00e8 stata trattata come un \u201cnice to have\u201d: utile, giusto, ma spesso rimandato perch\u00e9 percepito come costoso o complesso. […]<\/p>","protected":false},"author":1,"featured_media":9394,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"inline_featured_image":false,"footnotes":""},"categories":[91],"tags":[87,36,89,56,44,88,47],"class_list":["post-9393","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-news","tag-accessibilita","tag-joomla","tag-prestashop","tag-shopify","tag-shopware","tag-web","tag-wordpress"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/halkoo.com\/en\/wp-json\/wp\/v2\/posts\/9393","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/halkoo.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/halkoo.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/halkoo.com\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/halkoo.com\/en\/wp-json\/wp\/v2\/comments?post=9393"}],"version-history":[{"count":1,"href":"https:\/\/halkoo.com\/en\/wp-json\/wp\/v2\/posts\/9393\/revisions"}],"predecessor-version":[{"id":9395,"href":"https:\/\/halkoo.com\/en\/wp-json\/wp\/v2\/posts\/9393\/revisions\/9395"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/halkoo.com\/en\/wp-json\/wp\/v2\/media\/9394"}],"wp:attachment":[{"href":"https:\/\/halkoo.com\/en\/wp-json\/wp\/v2\/media?parent=9393"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/halkoo.com\/en\/wp-json\/wp\/v2\/categories?post=9393"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/halkoo.com\/en\/wp-json\/wp\/v2\/tags?post=9393"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}