layout | title | page_title | description | include_nav |
---|---|---|---|---|
page |
Developer Resources |
Developer Resources |
Start thinking about how you can<br/>support AAC in your projects |
false |
- Additional documentation/developer supports at opensymbols.org
- Additional language datasets for the Language Model
- Generative AI for picture symbol libraries
- On-device next-gen speech output
- AAC Effort Score summative metric, and support for additional popular libraries
- Anonymized AAC usage data processing and reporting
- Quantitative data output on knAAC Awards results
- Mobile plugins to support AAC Shim functionality
- Generic libraries for alternative access methods
AAC app development is a noble endeavor, and can provide enormous value to people who can will from technology supports. It is important, when supporting those who use AAC, that you understand the expectations of AAC users, and can build something long-term and robust. We want to help make that happen!
If you are interested in, or planning on, implementing an AAC app, we have collected a list of considerations that you should factor in to your development plans.
Additionally, you will want to review the developer specifications which will make your life easier as you develop an AAC app.
Accessibility is something we are starting to see baked in to more and more projects. If you are developing a web site, a mobile app, or other projects you think AAC users might benefit from, think about how you can make things accessible. From larger buttons/targets to slower timeouts, there are many little things you can do to make things easier on people whose hands shake, or who take longer to read, or who need frequent breaks. Also consider implementing AAC Shim to make it easier for AAC users to access your site.
Additionally, if you are using the cloud at all, please consider the value of publishing a public API. Some users are going to need a very simplified version of your interface that focuses only on the primary tasks. If you don't have the resources to write and maintain such an interface yourself, publishing an API will allow AAC vendors and even families to develop their own simplified interfaces to provide access to valuable, engaging activites and social interactions that are only available via the Internet.
Already bought in? Add an OpenAAC Badge ( or ) to your site or GitHub project! Once you've added it, let us know and we can add you to our
- anyone can embed this badge to support open AAC principles!
// For GitHub embed/Markdown
// Raw HTML
<a href="https://www.openaac.org/advocates.html" target="_blank"><img src="https://www.openacc.org/images/OpenAAC-chat-red.svg" alt='I support OpenAAC'/></a>
- this badge is for projects/groups that have signed the OpenAAC Advocacy Pledge
Once you have filled out the agreemeent we will send you instructions for adding this badge to your project/site.
It's great to see progress in making technology accesssible, from web standards to gaming hardware, there is a lot of exciting work happening! The open source community and even some vendors are starting to open up and share resources so everyone can benefit.
- OpenAAC GitHub Repos
- Language Support Models for AAC - word and inflection rule sets for simpler language-aware support in AAC systems
- OpenSymbols - library of open-licensed icons and symbols that can be used to implement AAC
- AAC Shim - JavaScript utility to make web pages and apps accessible and launchable from within an AAC system
- The Open Board Format - an open file format and parsing libraries to import and export AAC vocabulary or board sets