The WCAG (Web Content Accessibility Guidelines) is an international standard developed by the W3C consortium as part of the WAI (Web Accessibility Initiative) initiative – a set of principles aimed at designing websites and web applications accessible to people with various disabilities. The first version of WCAG 1.0 was published in 1999, and subsequent updates (2.0, 2.1, currently 2.2) have gradually expanded the scope of requirements. The WAI initiative at W3C has been operating since the 1990s, creating accessibility standards and supporting their implementation – thanks to this, the WCAG principles have become a widely recognized framework solution for ensuring that websites are "for everyone".
WCAG guidelines are gradually becoming law in the EU and its member states. Of key importance here is the European Accessibility Act (EAA) – an EU directive (2019/882), in force since 28 June 2025. It introduces a requirement for the accessibility of selected digital products and services, including websites and online applications, e-commerce stores and other digital systems (e.g. payment applications, e-books). This act covers EU companies generating at least EUR 2 million per year and employing at least 10 employees – thus laying off micro-enterprises.
E-commerce Obligations: Online stores are subject to these regulations, which is why owners of e-commerce platforms must implement accessibility requirements (at least AA level, usually associated with WCAG) by the aforementioned deadline. This also applies to Shopify stores operating on the EU market. Failure to implement appropriate changes may result in financial sanctions – it is estimated that the penalties may reach up to 10% of annual turnover. In practice, this means that all online businesses in the EU should ensure that their websites are compliant with WCAG 2.2 (once implemented into law) – from small to large, excluding only the smallest microenterprises.
WCAG 2.2 was published in December 2022 as a supplement to version 2.1. It introduces 9 new success criteria (at levels A and AA) and withdraws one outdated one (criterion 4.1.1 "Code correctness"). The new requirements respond to modern technological challenges and increase support primarily for people with cognitive and motor difficulties. The most important changes include:
To sum up, WCAG 2.2 extends existing rules with elements that facilitate navigation, readability and use on new devices. It increases the focus on the needs of older people and people with learning disabilities, while maintaining backward compatibility with earlier criteria.
Implementing WCAG in practice requires reviewing specific elements of an online store. Typical areas requiring attention include:
<label> element). It is also important to clearly communicate errors (e.g. missing fields) so that the user knows what to fix. You need to avoid “keyboard traps” – each step should be possible without blocking keyboard navigation.All of these examples usually require corrections in the page template - CSS changes (colors, element size), adding ARIA/HTML attributes to components, or corrections in form templates. Some actions (such as alt text description or simple contrast increase) can be performed independently with minimal technical knowledge, others (e.g. deeper changes to the page code or complex interfaces) may require the help of a specialist.
For many stores based on Shopify, the simplest mode is to configure accessibility yourself, using the platform's built-in tools and tips. Shopify has dedicated materials on the accessibility of templates and stores. For example:
Additionally, the platform offers applications and tools for accessibility testing (e.g. automatic audits, widgets that improve contrast or a text reader). Many changes - especially stylistic ones - can be made independently without programming. However, more advanced tasks (e.g. extensive modifications to the theme code, implementation of ARIA or specialist scripts for accessibility) should be entrusted to accessibility experts. A professional WCAG auditor will help identify imperfections, and the developer can make corrections without violating the store's logic. Investing in such an audit often proves justified, as the lack of accessibility may result not only in image problems, but also in legal sanctions.
Digital accessibility is not only a matter of legal compliance. From a business perspective, improving accessibility brings tangible benefits. Firstly – it broadens the reach of the store. A website accessible to all Internet users, including people with disabilities, means a larger potential group of customers. A good user experience builds a positive image of the company and loyalty of buyers. Secondly – accessible websites usually benefit from SEO. Internet search engines prefer user-friendly websites (e.g. they index content with well-described images or headings faster). The UX effect is also beneficial for all users - even people without disabilities appreciate the clear layout, clear buttons and legible graphics.
Generally: investing in accessibility means better experiences (UX) and a wider business reach. By providing equal opportunities to use the store to all customers, the company builds a reputation as a responsible and innovative entrepreneur. At the same time, meeting EU requirements (EAA) minimizes the risk of financial penalties. Therefore, compliance with WCAG 2.2 should be treated as both an obligation and an opportunity to strengthen the store's position on the web - improving accessibility is a benefit for customers, brand and SEO results
