Development of Alternative and Augmentative Communication (AAC) Application Programming Interface (API)

Summary

An application programming interface is an interface or communication protocol between different parts of a computer program intended to simplify the implementation and maintenance of software. An API may be for a web-based system, operating system, database system, computer hardware, or software library.

One is required to enable the deployment of AAC symbols, such as Tawasol in different digital settings.

Not Initiated

Target Users

User Journey

NooraAhmed is 18 years old. He is unable to communicate through speech, and relies on reading and activating AAC symbols to communicate. Ahmed is looking to navigate the FIFA World Cup 2022 website using AAC symbols.

1

Ahmed logs on to the FIFA World Cup 2022 Website to find the information written in Arabic. He cannot read the text.

2

Ahmed activates the AAC feature on the website.

3

Once activated, all highlighted content including text and image will be converted it to AAC symbols.

Potential Service Features

  • AAC API
  • Personalized Settings
  • Predictive Insights
  • Issue Resolution

Touch Points

Issue Statement

As a person with cognitive and communication disabilities, Ahmed is unable to access web content during his everyday life. He needs AAC interpretation of content to be able to navigate through a website.

Expected Key Benefits

Web content to AAC symbols

Translate key information that is being delivered to mass audiences websites into AAC symbols, such as Tawasol.

Audience Expansion

Businesses and public sector organizations can use the solution to broadcast contextualized information in AAC symbols, thereby targeting a niche customer base that is not traditionally accessed through conventional advertising mediums.

Implementation Analysis

Implementation Timeline

Timeline Medium

Short

Medium

Long

Technology Commercial Viability

Timeline Short

Available Now

Viable in Short Term

Viable in Long Term

Investment Requirements

Timeline High

Low

Medium

High

Key Implementation Considerations

1

User identification and sign-on

2

Collection and synchronization of real-time data from multiple sources (e.g. transportation schedules, emergency response routes, etc.)

3

Identification and Instant / Real-time sign language translation of relevant data in alternative formats (e.g. text, audio, etc.)

4

Data collection policies

5

Intuitive Graphical User Interface