Accessibility extension for Magento 2 and Adobe Commerce
Published · 1.2% of French online stores
Magento runs fewer stores than WooCommerce or Shopify, but it powers large catalogues, often sold across several EU countries. These merchants almost always exceed the European Accessibility Act exemption thresholds. The Conformly extension adds an accessibility page to the Magento admin: score, issues ranked by severity and whole-site monitoring.
Download · Conformly Magento 2 / Adobe Commerce
- Version
- 1.0.0
- Requirements
- Magento 2.4.x · PHP 7.4–8.3
- License
- OSL-3.0
- Size
- 42.9 KB
- SHA-256
- 82d2d5870f5843ea4974420189e8052c77f3e020d11181672b52b22f9e0c6fa0
Source code and release notes inside the ZIP (README.md).
Why Magento stores are on the front line
The European Accessibility Act has applied since 28 June 2025 to e-commerce services provided to consumers. Only micro-enterprises providing services are exempt (fewer than ten employees and under EUR 2 million turnover or balance sheet). A Magento store almost always exceeds those thresholds, and often sells in several Member States, each with its own market surveillance authority.
Luma and Hyvä themes, and above all custom themes, show recurring problems: layered navigation unusable with a keyboard, a mini-cart that does not return focus, checkout error messages that are not announced, brand colour contrast.
What the extension does
The Conformly_Accessibility module follows Magento conventions: ACL, system configuration, form key.
- Admin page Content → Elements → Accessibility (Conformly): free scan, accessibility score, table of failing rules with a link to their fix.
- Configuration in Stores → Configuration → Conformly: API key (encrypted field), site ID, badge toggle.
- Connected mode: latest score from continuous monitoring and an on-demand full-site scan, results aggregated per rule.
- Score badge in the storefront footer, off by default.
- Permissions handled by ACL: Conformly_Accessibility::scan and ::config.
What the extension does not do
It does not change the store's themes or layouts, apart from the optional badge, and adds no accessibility overlay. An automated scan covers part of the criteria: it does not replace a full audit, but it detects frequent errors and regressions after a deployment.
To block a regression before it reaches production, combine it with Conformly's CI/CD integration in your deployment pipeline.
Install the Magento 2 extension
- Copy the module. Unzip conformly-magento at the Magento root: the files land in app/code/Conformly/Accessibility.
- Enable the module. Run bin/magento module:enable Conformly_Accessibility, then bin/magento setup:upgrade.
- Compile and flush the cache. In production mode: bin/magento setup:di:compile, setup:static-content:deploy, then bin/magento cache:flush.
- Scan. Admin → Content → Elements → Accessibility (Conformly) → "Run a free scan". With a Pro or Agency plan, enter the API key and site ID in Stores → Configuration → Conformly.
Frequently asked questions
Is the extension compatible with Hyvä?
Yes for the admin, which does not depend on the theme. The optional badge is a plain HTML block added to the footer container; on a heavily customised Hyvä theme, check where it lands.
Where is the API key stored?
In Magento configuration, encrypted with the installation's encryption key, like other secrets (Encrypted backend model).
Can I install it with Composer?
The module ships a composer.json (conformly/module-accessibility). It is not on Packagist yet: install it in app/code or from a local path Composer repository.
Do I need a Conformly account?
Not for the home page scan, which is free and limited to five scans per hour. Monitoring every page and the badge require a Pro or Agency plan.
Related
Other integrations
Monitor accessibility across your whole store
Scheduled scans of every page, regression alerts, accessibility statement and PDF report.
See plans