Web accessibility (WCAG 2.2 / EN 301 549)
WCAG 2.2 AA accessibility for web & software — the conformance the EU Accessibility Act makes you self-declare.
Vælg de regimer, dit repository skal svare på. Hvert af dem kører efter samme ærlige mønster: Watchdog dokumenterer den automatiserbare del, spærrer for det, den fangede som fejlende, og et navngivet menneske erklærer resten. Hvert kort viser den tredelte fordeling — værktøjsdokumenteret, evidens-assisteret og menneskelig attestering — før du slår noget til. For tilgængelighed (WCAG 2.2 / EN 301 549) driver vi det så langt, det ærligt kan komme: statiske tjek dokumenterer med værktøjer det, de kan, og for repositories med frameworket slået til tilføjer et sandboxet rendered-axe-gennemløb og LLM-rådgivning runtime-/assisteret evidens — så den menneskelige del er det minimum, standarden reelt kræver, at et menneske vurderer.
Selvvurdér ethvert framework på enhver plan. Signering & eksport af det manipulationssikre artefakt er en del af compliance-modulet. Vi måler; du erklærer. Vi certificerer aldrig.
2 frameworks
WCAG 2.2 AA accessibility for web & software — the conformance the EU Accessibility Act makes you self-declare.
The full EU ICT accessibility standard — WCAG 2.1 AA for the web clause (per v3.2.1), plus the non-web ICT clauses you declare.
3 frameworks
Cyber risk-management measures for essential & important entities — the technical slice of Article 21(2).
Product cybersecurity for products with digital elements (EU CRA) — the repository-visible security properties are tool-evidenced; conformity is the manufacturer's.
A preparation/readiness tool for ISO/IEC 27001 Annex A:2022 — all 93 controls. Gather the technical evidence a scan produces toward certification; only the Technological theme (A.8) is tool-evidenced. Not a certificate.
1 framework
ICT operational-resilience for EU financial entities — five pillars plus the RTS technical measures. Opt-in.
1 framework
Tamper-resistant build & source integrity (SLSA v1.2) — provenance and source-control attestations across Build L1–L3 and Source L1–L4.
2 frameworks
Secure software development practices (NIST SP 800-218) — secure coding & vulnerability response are tool-evidenced; governance is attested.
Application-security verification (OWASP ASVS v5.0.0, full 345-requirement set) — injection, crypto, transport, config, dependencies & logging are tool-evidenced; the rest is verified by testing.
1 framework
The technical measures of GDPR Art. 32 & Art. 25 only (encryption, secrets, vulnerabilities, resilience) — not GDPR compliance.
Hvert framework er Automatisk / Til / Fra pr. repository · ærlighedsmodellen i dybden · priser