npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@ariada-org/statement-generator

v0.1.0

Published

EAA / WCAG accessibility-statement generator — Directive 2016/2102 art. 7-style statement pages in HTML or MDX. Nordic 4 + English locales. Open source under EUPL-1.2.

Readme

@ariada-org/statement-generator

EAA / WCAG accessibility-statement generator — Directive 2016/2102 art. 7-style statement pages in HTML or MDX, Nordic 4 + English locales.

License: EUPL-1.2 CI

Quick-start

npm install @ariada-org/statement-generator
import { generateStatement } from "@ariada-org/statement-generator";
import type { Violation, ReportMeta } from "@ariada-org/evidence-emitter";

const violations: Violation[] = [
  /* axe-core results normalized */
];
const meta: ReportMeta = {
  productName: "Example Web App",
  productVersion: "2.5.0",
  evaluator: "Audit Team",
  evaluationDate: "2026-05-16",
  scope: "https://example.com/checkout",
};

const statement = generateStatement(violations, meta, {
  locale: "sv",
  jurisdiction: "SE",
  organisation: "Example AB",
  authorityEmail: "[email protected]",
  feedbackUrl: "https://example.se/kontakt",
  format: "html",
  conformance: "partial",
});

// statement.body — HTML or MDX document ready to drop into /accessibility/

Node ≥ 22. Single workspace dependency: @ariada-org/evidence-emitter (re-uses the Violation + ReportMeta types).

What this package does

Renders an accessibility-statement page that satisfies the disclosure structure mandated by Directive (EU) 2016/2102 art. 7 and mirrored by the EAA Annex I §I.1 obligation for in-scope private-sector services. The output covers the six required disclosures: publication date, scope, conformance status, non-conformances, feedback mechanism, and enforcement procedure (per-jurisdiction authority contact).

The generator is locale-aware (English + Swedish + Norwegian Bokmål + Danish + Finnish) and jurisdiction-aware (SE / NO / DK / FI Nordic enforcement track). Strings live in a single i18n catalogue (STATEMENT_MESSAGES) so additional locales can be added without touching the rendering logic. Output is either standalone HTML (drop directly at /accessibility/) or MDX (compatible with Astro / Next.js content collections).

The function is deterministic: same input → same output. No network calls, no template fetching, no third-party CDN.

What this package does NOT do

It does not scan for violations, host the rendered page, sign the statement, or notify enforcement authorities. It does not produce VPAT-JSON or EN 301 549 §11 conformance reports — see @ariada-org/evidence-emitter for those formats. Locale and jurisdiction coverage is currently limited to the Nordic 4 + English; other EU locales are not yet shipped.

API summary

| Export | Signature | Returns | | ------------------------------------------- | --------------------------------------------------------------------------- | ------------------------------------------------ | | generateStatement(violations, meta, opts) | (Violation[], ReportMeta, GenerateStatementOptions) => GeneratedStatement | { body, format, locale, jurisdiction } | | STATEMENT_MESSAGES | Record<Locale, StatementMessages> | i18n catalogue (5 locales × all surface strings) |

Types: GeneratedStatement, GenerateStatementOptions, StatementJurisdiction ('SE' | 'NO' | 'DK' | 'FI'), StatementConformance ('full' | 'partial' | 'non-conformant'), StatementFormat ('html' | 'mdx'), StatementMessages, Locale.

Regulatory mapping

Tests + verification

80 tests across 2 files (vitest), including 3 property-based suites via fast-check that verify locale + jurisdiction round-trips and HTML / MDX structural invariants. Run with pnpm test; coverage via pnpm test:coverage.

Sibling packages

License

EUPL-1.2 — see LICENSE.