Loading page…

Integrating WeAccess.Ai Sign Language SDK into iOS Applications

Integrating WeAccess.Ai Sign Language SDK into iOS Applications

Integrating WeAccess.Ai SignForDeaf SDK into Android Applications

This guide explains how to integrate the WeAccess.Ai (SignForDeaf) Mobile Sign Language SDK into an Android application using Kotlin.

Step 1. Add JitPack Repository

Add the JitPack repository to your settings.gradle file:

dependencyResolutionManagement {
    repositoriesMode.set(RepositoriesMode.FAIL_ON_PROJECT_REPOS)
    repositories {
        mavenCentral()
        maven { url 'https://jitpack.io' }
    }
}

Step 2. Add the SDK Dependency

Add the dependency to your app-level build.gradle file:

dependencies {
    implementation 'com.github.signfordeaf:mobile-sign-language-translation-kt:1.0.3'
}

Sync your project after adding the dependency.

Step 3. Add Required Permissions

Ensure that the following permission exists in your app/src/main/AndroidManifest.xml file:

<uses-permission android:name="android.permission.INTERNET" />

Step 4. Initialize and Use the SDK (Kotlin)

Initialize the SDK inside the onCreate method of your AppCompatActivity.

class MainActivity : AppCompatActivity() {

    override fun onCreate(savedInstanceState: Bundle?) {
        super.onCreate(savedInstanceState)
        enableEdgeToEdge()
        setContentView(R.layout.activity_main)

        // Initialize WeAccess.Ai Sign Language SDK
        SignForDeafUtil.initialize(
            apiKey = "YOUR_API_KEY",
            requestUrl = "YOUR_REQUEST_URL"
        )

        // Enable sign language translation for all selectable text
        SignForDeafTranslate.makeAllTextSelectable(this)
    }
}

✅ Android Integration Complete

Your Android application is now successfully integrated with the WeAccess.Ai SignForDeaf SDK, enabling accessible sign language translation and improving digital inclusivity.

Find accessibility issues on your website.

Run a quick accessibility check and discover potential barriers on your website. Automated scanning cannot detect every issue.

Example: www.yourwebsite.com

The accessibility score is based on automated test results. It is not a statement of WCAG or regulatory compliance. A full assessment requires manual testing.

An accessibility scan result screen: a list of detected issues with status indicators.