Slovenia ZDSMA accessibility API

Run a Slovenian public-sector technical profile from the publishing system that owns the asset. The API connects repeat scans, national mapping lineage, and unresolved human work without representing a single result as complete ZDSMA conformity.

For Slovenian public bodies and suppliers maintaining web and document estates

API profilesi-zdsma-current@2026.3

Check a website free Book a demo

Illustrative request202 Accepted

POST /v1/scans
Idempotency-Key: digital-services-office

{
  "asset": {
    "type": "url",
    "url": "https://obcina.example/e-vloge"
  },
  "profiles": [
    "si-zdsma-current@2026.3"
  ],
  "metadata": {
    "service_owner": "digital-services-office"
  }
}

queuedid: scn_01J…profile resolved

Scope: Public-sector web and supported documents
Mapping: Current Slovenian technical profile
Operations: Owner, history, and open review retained

Compare product accessibility evidence without flattening the review boundary.

The delta identifies changed technical work while product usability and national requirements remain explicitly assigned.

Baseline: Approved product build
Current: Candidate product build

New machine failures2

Resolved findings5

Recurring findings8

Open human checks4

Illustrative result: technical review required

Connect the scan to the operating model around it.

A durable program needs more than findings: it needs named ownership, comparable history, and clear boundaries between automation and organizational obligations.

Ownership

Name the responsible service

Keep internal owner, supplier, project, and asset IDs in tenant-safe metadata.

Continuity

Compare repeated publication states

Use stable fingerprints and pinned profiles to identify new, recurring, and resolved work.

Boundary

Record what remains outside the scan

Queue manual testing, statement work, feedback handling, and legal review separately.

Let the API strengthen evidence without overstating it.

The national profile organizes technical inspection. Complete public-sector accessibility remains a broader service responsibility.

Returned by the API

Versioned national and technical mappings
Source-locatable web or document findings
Coverage and unresolved manual checks
Report history and baseline comparison

Maintained by the organization

Complete service and mobile-app evaluation
Accessibility statement and feedback mechanism
Procurement, supplier, and remediation governance
Applicability, exceptions, and conformity decisions

Inspect the policy behind the API profile.

Before Slovenia ZDSMA becomes a production gate, review its source mapping, supported input, automation boundary, and required human checks.

Read the Slovenia ZDSMA profile ZDSMA in the Slovenian legal information system Government of Slovenia accessibility guidance

Put the Slovenia ZDSMA API in the path you already own.

Start with one asset flow, pin the profile, and keep evidence and unresolved human work attached to every result.

Check a website free Create an account

Automated preflight is not an accessibility certification or legal determination.