← All use cases 05 · ACCESSIBILITY · PROPOSED WORKFLOW

Useful information for more people and devices.

Provide clear text, descriptions, languages and lighter alternatives as first-class resources.

Who this is for: Public services, schools, publishers and accessibility teams. Illustrative concept, not a deployed OSYNIA capability.

01 · START WITH THE PROBLEM

What problem are we trying to solve?

A rich-media information page can be difficult to use with slow connections, assistive technology or older devices.

A rich-media information page can be difficult to use with slow connections, assistive technology or older devices.

Relevant contracts: OSYNIA-E experience and accessibility contract plus OSYNIA-R resource representations.

EXAMPLE USER REQUEST
“Show the key steps from this training page as clear text that works with my screen reader and limited data.”
BEFORE · COMMON APPROACH
  1. A page may require large media downloads before the essential content is accessible.
  2. Important diagram explanations or captions may be missing.
  3. A user may depend on cloud AI to reconstruct alternative descriptions.
WITH OSYNIA · PROPOSED
  1. The publisher provides validated text, captions and alternative descriptions with the resource.
  2. A client selects an accessible, low-bandwidth representation.
  3. The user can access essential information without continuous AI calls.
  4. Media and detailed visuals remain available on demand.
02 · STEP-BY-STEP USER JOURNEY

From request to a verifiable outcome.

Switch between General and Technical in the header to explore the same journey at two levels.

01

Publish meaningful alternatives

Creators provide text instructions, image descriptions and captions when publishing their material.

Link accessible representations and language variants to canonical resource identities with editorial provenance.

Illustrative output

Text guide, captions and diagram description available

02

Discover available formats

The browser or service learns which versions are available.

Resolve representation metadata for language, modality, size and accessibility semantics.

Illustrative output

Available: plain text, captioned video, diagram description

03

Choose what works

The visitor selects simple text and the language they understand best.

Negotiate language and representation without requiring inference or a paid AI service.

Illustrative output

Low-data text representation selected

04

Deliver the essentials

The page displays meaningful headings, steps and descriptions compatible with assistive technology.

Serve semantic headings, structured text, correct reading order and accessibility-tested controls.

Illustrative output

Readable steps without mandatory video download

05

Verify usability

People using different devices and assistive technology test whether the information is actually usable.

Validate WCAG-related behaviour, keyboard navigation, screen-reader tasks and constrained-network performance.

Illustrative output

Accessibility test results, including failures, recorded

03 · RESPONSE & OUTCOME

What would the person see?

ILLUSTRATIVE SYSTEM RESPONSE

“Here is the text guide, with headings and step-by-step instructions. The full video is optional.”

ILLUSTRATIVE COMPLETION

Example completion: essential training steps are accessible on a lower-bandwidth connection; usability remains subject to testing.

A proposed success message must be backed by actual execution and verification in a real implementation.

04 · UNDER THE HOOD

How the proposed technology fits together.

This example depends on information that explains what it is, trusted links to other information, and clearly described operations when an action is needed.

What must be in place:

  • Publishers must produce and maintain accurate alternatives.
  • Accessibility must be tested with real assistive technologies and users.
  • Translations and generated descriptions need suitable review.
Resources
Canonical content resource with alternate text, timed captions, language variants and media descriptions
Contracts
OSYNIA-E experience and accessibility contract plus OSYNIA-R resource representations

Proposed system sequence

  1. Publish alternate representations
  2. Resolve capabilities and user preference
  3. Select format
  4. Serve structured content
  5. Test task success

Security and governance controls

  • Accessibility QA
  • Editorial versioning
  • Translation review
  • Semantic structure

Illustrative JSON contract

{
  "resourceId": "training:42",
  "representations": [
    {
      "type": "text/html",
      "language": "en",
      "lowBandwidth": true
    },
    {
      "type": "text/vtt",
      "language": "en"
    },
    {
      "type": "video/mp4",
      "optional": true
    }
  ],
  "requiresAi": false
}
RELEVANT OSYNIA SPECIFICATIONS
Experience & AccessibilityResources & MeaningTrust & Governance
Explore proposed specifications →
05 · REAL-WORLD VALIDATION

How would we know it works?

These are proposed measures, not published results.

Task accessibility

Completion rate by keyboard and screen-reader users

Data transfer

Bytes delivered for essential content versus media-first baseline

AI independence

Successful access to essential information with AI disabled

Requirements for adoption

  • Publishers must produce and maintain accurate alternatives.
  • Accessibility must be tested with real assistive technologies and users.
  • Translations and generated descriptions need suitable review.

Limits and trade-offs

  • Metadata does not make an inaccessible user interface automatically accessible.
  • Some media tasks still require bandwidth and assistive adaptations.
  • A valid standard cannot guarantee every implementation meets accessibility requirements.

This page presents research hypotheses, not verified performance improvements, customer results or a live demonstration.