Build1 distinct publisher3 min readUpdated
A vendor of European Accessibility Act tooling says most of his own market is exempt, and that the exemption covers the accessibility statement and documentation, not just the technical requirements.
The Engineer · Build desk
Compiled by The EngineerSomething wrong?How this is made
A vendor who sells European Accessibility Act compliance tooling has published, on dev.to, the sentence his own funnel depends on not saying: most of the people currently being sold tools like his do not have to comply with anything [1]. The reason is worth more than the confession, because the exemption in Article 4(5) of Directive (EU) 2019/882 does not stop at the technical requirements [2]. The text reads: "Microenterprises providing services shall be exempt from complying with the accessibility requirements referred to in paragraph 3 of this Article and any obligations relating to the compliance with those requirements" [2]. The second clause is the one that matters if you are holding a quote. According to the author, it takes in the accessibility statement, the Annex V information and the documentation [3]. That is precisely the artefact most of this tooling is sold to generate. Then the definition, from Article 3: an enterprise employing fewer than 10 persons and with annual turnover not exceeding EUR 2 million or an annual balance sheet total not exceeding EUR 2 million [4]. The conjunctions carry the whole test. Headcount is an and, and it is mandatory [5]; nine people with EUR 30 million of turnover is not a microenterprise [6]. The money is an or: one of the two figures under two million, not both [7]. The author says he has seen it written as two thresholds you must clear together, which is stricter than the directive and pushes people into obligations they do not have [8]. On the directive's own wording, a nine-person firm with EUR 5 million turnover and a EUR 1.8 million balance sheet total is exempt [9]. Two limits before you file the saving. The exemption covers microenterprises providing services and does not exempt microenterprises placing products on the market [10]. For most readers that is academic, since a website is a service and e-commerce services are explicitly in scope under Article 2(2), alongside consumer banking, e-books, passenger transport, electronic communications and audiovisual media access services [11]. But if you also manufacture, import or distribute self-service terminals, e-readers, or consumer terminal equipment with interactive computing capability, microenterprise status does not release you from the products half [12]. Separately, the EAA is a directive transposed into 27 national laws, and Member States had room to move [13]; national equality and anti-discrimination law is separate and generally older [14]; the ADA is a different question with an active litigation industry attached [15]; and public sector bodies and their suppliers sit under Directive 2016/2102, which is where the familiar five-heading statement template originates [16]. The sharper operational point is what not to do with the exemption. Publishing a conformity claim you never owed converts a non-obligation into a public, written, verifiable assertion about your own product, and the author's argument is that never having had to make it is not a defence if it is inaccurate [17]. He points to the FTC's 2025 action against accessiBe, which turned on claims: that the product made sites WCAG compliant, that it kept them compliant, and how the company's own promotional articles were presented [18]. He also reports fixing his own tool. The statement generator asserted compliance for anyone who clicked through, including people who owed nothing, until he added a microenterprise question ahead of everything else; it now stops asserting conformity, cites Article 4(5), and frames whatever you publish as voluntary [19]. None of this changes the users. The share of people who need captions, keyboard operation or sufficient contrast is exactly what it was before anyone read Article 4(5) [20], and the people who cannot complete your checkout are still not completing it [21].
Follow any of these and your For You feed starts watching them — no settings page required.
Ranked by verification strength, evidence, and original report placement.
Article 3 defines 'microenterprise' as an enterprise which employs fewer than 10 persons and which has an annual turnover not exceeding EUR 2 million or an annual balance sheet total not exceeding EUR 2 million.
The headcount condition is an 'and': fewer than 10 persons is mandatory.
Nine people and EUR 30 million of turnover is not a microenterprise.
The financial condition is an 'or': turnover under EUR 2 million or balance sheet total under EUR 2 million, not both.
The author, who sells a tool that helps with European Accessibility Act compliance, writes that most of the people currently being sold tools like his do not have to comply with anything.
Article 4(5) of Directive (EU) 2019/882 states: 'Microenterprises providing services shall be exempt from complying with the accessibility requirements referred to in paragraph 3 of this Article and any obligations relating to the compliance with those requirements.'
Evidence-backed comparisons of source perspectives and observed adoption signals. Read the methodology
Which Builder, Operator, and Investor concerns the observed source mix emphasized—not a truth score.
Evidence, demonstrated adoption, hype gap, incentives, and confidence are assessed independently, each on its own current evidence. How these are measured.
Primary legal text quoted, interpretation uncorroborated
The load-bearing facts are verbatim quotations of Article 4(5) and the Article 3 microenterprise definition plus a scope citation to Article 2(2), which are checkable against the directive itself and give the cluster a solid factual floor. What is not evidenced inside the cluster is the interpretive leap that 'any obligations relating to the compliance with those requirements' cancels the accessibility statement and Annex V documentation, the extent of national transposition variance, and the claim that a 'very large share' of the marketed base is exempt. One publisher, one self-described non-lawyer author.
One self-reported vendor product change
The only adoption signal is the author changing his own statement generator to gate on microenterprise status and stop asserting conformity, disclosed by the vendor himself. There is no data in the cluster on how many businesses rely on the exemption, whether other vendors surface it, or whether exempt firms have stopped publishing conformity statements, so adoption is measurable only at the scale of a single tool.
Slight over-generalisation inside an against-interest piece
The framing runs against the author's commercial interest and carries its own caveats, which suppresses hype. The residual overstatement is in the generalising headline ('if you employ fewer than 10 people, probably not') and in extending the exemption to the statement and documentation as settled, when that step is a single non-lawyer's reading and the piece itself concedes 27 transpositions, linked-enterprise rules and separate equality law could change the answer. Net effect is close to aligned, tilted marginally toward overstated.
Incentives disclosed and cut against the author's own sales
Incentive structure is unusually legible: the author states up front that he sells EAA compliance tooling while arguing most of that market owes nothing, names the vendor incentive to omit the exemption ('the honest answer costs the sale'), admits his own generator previously asserted conformity for exempt users, and cites a 2025 FTC claims-based action against another accessibility vendor. The residual incentive risk is that the post still markets the author's revised tool and scanner.
Checkable text, single non-expert publisher
Confidence is held up by quotable primary law and clear self-disclosure, and held down by the cluster having exactly one publisher, an author who disclaims legal expertise, no regulator or counsel corroboration, and the acknowledged dependence on Member State transposition and linked-enterprise rules. Readers can verify the quotations quickly; they cannot verify the interpretive conclusion from this cluster alone.
build
"Follow the same standard" is how mobile accessibility debt gets onto the books1 distinct publisher
build
Force the tool call, then hand Lightsail a long-lived key1 distinct publisher
build
AI-written code fails the same four ways, and every gate you own reports green1 distinct publisher
build
CSA's 2026 threat list is a flat line, so ask which threats a config snapshot can prove1 distinct publisher
Distinct publishers with included, body-backed reporting in this cluster.
dev.to
1 article · August 19, 2026