Accessibility is not a check that can be completed once at the end of a project. It depends on HTML structure, content, interactive components, apps, theme updates and the real journeys people use.
This page explains how I work on ifgecommerce.com and which references I use. It is not a certification of compliance and does not replace legal analysis or a formal audit of the entire website.
The technical reference: WCAG 2.2
I use the W3C Web Content Accessibility Guidelines (WCAG) 2.2 as the main technical reference for design and verification. WCAG 2.2 is a W3C Recommendation and organizes accessibility around four principles: perceivable content, operable interfaces, understandable information and robust implementation.
Following WCAG does not automatically prove every legal obligation that may apply. A technical standard and a legal requirement are separate layers and need to be reconciled with the operator, service, market and applicable law.
The European and Italian framework
Directive (EU) 2019/882, commonly known as the European Accessibility Act, sets accessibility requirements for specific products and services. In Italy it was transposed through Legislative Decree 27 May 2022, No. 82, which applies to covered products and services placed on the market or provided from June 28, 2025.
Article 4(5) of the Directive also exempts microenterprises providing services from the accessibility requirements covered by that Directive. That fact alone does not determine every accessibility obligation that may be relevant to a specific website: applicability still needs to be assessed against the actual operator and service.
What I check on the website
1. Semantic structure
I check that headings, landmarks, lists, links, buttons and controls use elements and roles that match their real function. A page can look correct visually and still be confusing to assistive technologies if the underlying structure does not represent what is on screen.
2. Keyboard navigation and focus
Menus, modals, filters, selectors, forms and other interactive components should work without a mouse where required. I check tab order, visible focus, opening and closing behavior and focus return across important interactions.
3. Text, contrast and resizing
I evaluate contrast, readability, typographic hierarchy and behavior when text is enlarged or the viewport becomes narrow. Content should not become unusable simply because someone zooms in or uses a small screen.
4. Images and non-text content
Informative images need useful text alternatives; decorative images should not add noise for screen-reader users. Alternative text is written according to the image’s function in context, rather than copied automatically from a filename or product title.
5. Forms, errors and states
I check labels, instructions, error messages, required fields and state changes. An error should not be communicated by color alone, and a completed action should provide feedback that remains understandable without relying exclusively on visual cues.
6. Shopify components and third-party apps
On Shopify, accessibility issues do not come only from the theme. Search, product options, cart drawers, popups, reviews, cookie banners and app embeds can introduce components with incorrect semantics or focus behavior. The review therefore needs to cover what third parties inject or update as well.
Automation and manual testing are both necessary
Automated scanners are useful for finding categories of errors quickly, but they cannot prove on their own that a journey is accessible. Many issues require real interaction: whether focus moves to the right place, whether a label makes sense, whether a modal manages keyboard focus correctly or whether reading order is understandable.
I therefore combine automated checks with manual testing of important journeys and, when appropriate, checks with assistive technologies.
Accessibility can change over time
A site that does not show an issue today can introduce one tomorrow through a new app, a theme change, editorial content, a video without an alternative or an update to an external component. I therefore treat accessibility as a maintenance practice, not a permanent state achieved by a single test.
Historical content, documents, integrations and third-party components may need dedicated checks and are not automatically considered conforming just because the main template has been corrected.
Current status of ifgecommerce.com
I do not claim full website compliance without a complete and current formal audit of the full public surface. I progressively correct observed issues and treat reported barriers as findings to be verified in their real context.
Report an accessibility barrier
If you find content or functionality that is difficult to use, email info@ifgecommerce.com. To make verification faster, include the relevant URL, what you were trying to do, your device/browser and, when relevant, the assistive technology used.
References
- W3C — Web Content Accessibility Guidelines (WCAG) 2.2;
- EUR-Lex — Directive (EU) 2019/882;
- Normattiva — Italian Legislative Decree 27 May 2022, No. 82.
Last updated: September 20, 2026.
