The European Accessibility Act applies to a defined list of products and services, and whether it reaches a particular industrial website is a question for qualified legal counsel to confirm.
Whatever that answer turns out to be, the Act is a useful prompt to review the accessibility of product information, technical documents, filters, forms and the core buyer journeys on an industrial B2B site.
Accessibility is a website quality and governance question before it is a legal one. Whether a specific organisation, product or service falls within the scope of the European Accessibility Act depends on what is being sold, how the website supports that sale, and the national law implementing the directive in each market — so applicability should be confirmed by qualified legal counsel rather than inferred from a web checklist. What follows covers what the Act is aimed at, where industrial websites tend to fail, and how to run accessibility as an operating discipline instead of a pre-launch scan.
The European Accessibility Act is an EU directive intended to improve access to a defined list of products and services, with e-commerce among the services the European Commission identifies. It is a directive rather than a regulation, and that distinction has practical consequences: it takes legal effect through each member state’s own implementing law, so obligations, enforcement routes and exemptions can differ between the markets an industrial exporter sells into.
Two things follow for an industrial group. Scope is a legal question answered market by market and entity by entity, rather than settled once at group level. And the technical target the Act points at is the harmonised European standard for ICT accessibility, EN 301 549, which incorporates the WCAG success criteria most development teams already build to — so the engineering work is well defined even while the legal position is still being confirmed.
A brochure site that describes machinery and routes enquiries to a regional sales team sits in a different position from a platform where a distributor configures a product, checks availability and places an order. The closer a website comes to being the place a transaction or a self-service task is completed, the stronger the argument for scope becomes. On a typical industrial estate of sites that puts distributor portals, spare-part ordering, product configurators and authenticated account areas ahead of the corporate brochure.
That is a way of ordering the work, not a legal determination. Have counsel confirm applicability for each entity and market, and use the ranking above to decide where accessibility budget goes while that advice is being obtained.
Waiting for a scope opinion before improving anything is usually a poor trade. Usable heading structure, labelled form fields, keyboard-operable filters, readable specification tables and documents that assistive technology can parse improve the site for every buyer regardless of how the legal question resolves — and they are the same changes a positive scope opinion would require anyway.
The reverse holds too. A published accessibility statement should describe what has been tested and what is known to be outstanding. It should not assert a compliance position that has not been established, and no supplier should offer a compliance guarantee on a site that has not been assessed against the applicable national law.
Industrial websites rarely fail on the marketing pages. They fail on the interfaces and the documents that carry the technical content, because those are the parts built for density rather than for interaction.
Data sheets, declarations of performance, certificates and installation manuals hold the information a specifying engineer needs. A file exported straight from a drawing package or a desktop publishing tool typically arrives with no tag structure, no defined reading order and no alternative text on diagrams; a scanned certificate may carry no text layer at all. A screen-reader user reaches that document and stops there, on a site that is otherwise well built.
Remediating an entire document library at once is rarely realistic, and treating it as one indivisible task is how the work stalls. A defensible approach ranks documents by the journeys they support, remediates the ones a buyer needs in order to specify or order, and publishes the decision-critical figures as structured content on the page so the document supplements the information rather than being the only route to it.
Faceted filtering, comparison tables and configurators are where an industrial site earns its keep, and they are the components most often built mouse-first. The recurring failures are checkboxes and range sliders that cannot be reached or operated from the keyboard, result counts that update without being announced, focus that is lost when a panel closes, and error or availability states signalled by colour alone.
These are design-system problems rather than page problems. Fixing the component fixes every page that uses it, which is why an audit is worth far more when its findings are mapped back to components and templates than when they arrive as a list of URLs.
An automated scan is a reasonable first pass and a poor final answer. Tooling reliably catches contrast ratios, missing alternative text, unlabelled controls and structural errors in markup. It cannot judge whether alternative text is meaningful, whether a reading order makes sense, whether an error message tells a user how to recover, or whether the language attribute matches the language on the page.
A review worth acting on covers the templates rather than every URL, and tests the tasks buyers perform: find a product, filter a range, read a specification, download a document, submit an enquiry, sign into a portal. Each task should be attempted with the keyboard alone and with a screen reader, on desktop and on mobile. Findings should come back prioritised by the journey they block, not by the severity label a tool assigned to them.
Most of what an audit finds was introduced by a template, a component or an editorial habit. Remediating the pages without changing what produced them buys a clean scan and a slow return to the same state. The durable version fixes the design system, adds accessibility acceptance criteria to the definition of done, and gives editors guidance specific to the content they publish — how to write alternative text for a technical diagram, how to structure a specification table, when a PDF needs an accessible equivalent on the page.
Ownership has to be explicit across three groups: product and technical teams for the accuracy and structure of source content, marketing for editorial quality, and development for templates and components. See industrial website accessibility for how that work is scoped, and the accessibility checklist for what to test first.
No. The Act covers a defined list of products and services and takes effect through each member state’s implementing law, so applicability depends on what your organisation sells, how the website supports that sale, and which markets it operates in. Sites that complete transactions or self-service tasks are the most likely to be argued into scope. Treat that as a way of ordering the work, and have qualified legal counsel confirm applicability for each entity and market.
In practice, the harmonised European standard for ICT accessibility, EN 301 549, which incorporates the WCAG success criteria most development teams already build to. Testing against those criteria gives a stable technical target even while the legal position differs between markets. It also keeps the findings useful if a scope opinion later concludes the Act does not reach a particular property, because the same criteria describe a site that is simply easier for a buyer to use.
Cover the templates rather than every URL: navigation, product discovery and filtering, specification tables, forms, documents, video and any authenticated distributor or partner area. Combine automated checks with manual keyboard and screen-reader testing of the tasks buyers perform, on desktop and on mobile. The output should be a prioritised remediation plan tied to components and journeys, so that one fix in the design system resolves the same defect everywhere it appears.
Because they usually hold the decision-critical content: specifications, declarations of performance, certificates and installation instructions. Files exported from drawing or publishing tools commonly lack tag structure, reading order and alternative text, and scanned documents may carry no text layer at all. When those files cannot be read, a well-built website still blocks the journey. Rank documents by the journeys they support and publish the figures that drive a decision as structured content on the page.
No. Automated tools are worth running and catch a real class of defects: contrast, missing alternative text, unlabelled controls, structural markup errors. They cannot judge whether alternative text is meaningful, whether a reading order makes sense, whether an error message helps a user recover, or whether a filter can be operated without a mouse. A scan with no findings is evidence that the automatable checks pass, and no more than that.
No, and an offer to do so is a reason for caution. Compliance is determined against the national law implementing the directive in each relevant market, against the organisation’s own circumstances, and by the authorities that enforce it. What a supplier can commit to is testing against a stated standard, a documented remediation plan, evidence of what was tested, and an accessibility statement that records known gaps plainly. Qualified legal counsel confirms the rest.
We can assess the templates, components, technical documents and publishing process behind your industrial B2B website, and return a remediation plan ordered by the buyer journeys it unblocks.