Demos · Developers

Quickstart

Ask for the tracks that exist for your content. Render them over your own player. That is the whole integration.

Request sandbox keys

1. Ask what exists

Identify the content (a fingerprint, a URL, or your own ID). Optionally filter by language. Sign languages use their own ISO 639-3 codes — there is no universal sign language — for example ase American Sign Language, bfi British Sign Language, ssp Spanish Sign Language, lsf French Sign Language, jsl Japanese Sign Language, bzs Brazilian Sign Language.

Illustrative request and response. The shape is stable in spirit; field names are confirmed with your sandbox keys.

Request: every track that exists for one piece of content
GET https://api.a11y.media/v1/tracks?content=sha256:7f3a…   # add &lang=ssp to filter
Authorization: Bearer sk_sandbox_…
Response: every track the community has made for it
{
  "content": "sha256:7f3a…",
  "tracks": [
    {
      "type": "sign-language",
      "lang": "ssp",
      "creator": { "name": "…", "credit": "Deaf creator" },
      "sync": "timeline",
      "stream": "https://…/manifest.m3u8"
    },
    { "type": "sign-language", "lang": "ase", "creator": { "name": "…" }, "stream": "https://…/manifest.m3u8" },
    { "type": "captions", "lang": "es", "format": "webvtt", "url": "https://…/es.vtt" },
    { "type": "audio-description", "lang": "en", "stream": "https://…/ad-en.m3u8" }
  ]
}

2. Render over your player

Sign language plays as a picture-in-picture layer synchronised to your timeline. Captions load as a normal text track. Audio description is an alternate audio track. Your content never leaves your player.

  • Keep the signer's frame whole — waist-up, hands never cropped.
  • Let the viewer move and resize the signer window.
  • Offer more than one interpreter when the community has made them.
  • Never autoplay the signer; the viewer chooses the modality.

3. Go live

Sandbox keys are free. We review the first integration with you — including a keyboard and screen-reader pass on your player, because the access layer is only as good as the player it sits in.

Request sandbox keys

Rate limits, webhooks for new tracks, and content fingerprinting are documented with your keys. Nothing here requires re-hosting your content.