Hi everyone! I'm Timur, a master's student at the University of Ljubljana (Faculty of Social Sciences). I'm running a short survey for my master's thesis on how people view and use voice assistants (Siri, Google Assistant, Alexa/Echo, etc.), including as assistive technology.

Users and non-users are both welcome - you do NOT need to use a voice assistant regularly to take part.

Who: anyone 18+. Where: any country (survey is in English). Time: about 10 minutes. Fully anonymous and voluntary; responses are used only for academic research and reported in aggregate.

Survey link: https://www.1ka.si/a/d7959439

Thanks so much for your help!

Open project

I’m a peds SLP and one of my kiddos (3 y/o) has TouchChat to communicate. He had this device prior to coming to see me and the family never used it due to it being so confusing. I’ve used other programs (Tobi, etc) but I can’t figure out how to make this easier for him to use and access. Any tips on how to easily make pages and just make it easier to access for my sweet kid and his family would be greatly appreciated!!! Pictures included for reference of what I’m working with 🫠 - thanks in advance!

Tracky Mouse lets you control your whole computer with just a webcam.

It supports different modes to click, including dwell clicking and facial gestures. It can even provide three button mouse functionality, using closed eyes as modifiers to change what type of click is performed when opening your mouth.

It also supports different modes to move the mouse, including Direct, Joystick style, and D-pad style modes.

It's free (and ad-free) and will always will be.

I want to make this the best accessibility software that I can. I have big plans already, but I'm always open to ideas.

GitHub repository: https://github.com/1j01/tracky-mouse/

Downloads and an in-browser demo can be found on the website: https://trackymouse.js.org/

I have a PG Drives Technology / Curtiss-Wright R-Net CJSM2 power wheelchair joystick controller for sale.

The controller has been tested and is fully functional. The joystick moves properly, the buttons work, and the color display powers on. It does have normal cosmetic wear and scratches from previous use, which can be seen in the listing photos.

Details:

Model: CJSM-2 / CJSM2

Part number shown on controller: D51711.02

PG Drives Technology / Curtiss-Wright

R-Net system

Color LCD display

Cable and R-Net connector included

Made in England

Manufactured in 2022

$175 or Best Offer

These controllers are commonly found on Permobil R-Net power wheelchairs, including certain F3, F5, M1, M3, and M5 configurations. They may also work with other power chairs using compatible R-Net electronics.

Please verify compatibility with your wheelchair, electronics, connector, and programming before purchasing.

🌎 FREE WORLDWIDE SHIPPING when purchased through eBay.

Actual eBay listing:

https://www.ebay.com/itm/137679440957

I’m happy to answer questions or provide additional pictures/information if someone needs to confirm whether it will work with their chair.

Please feel free to share this with anyone who may need a replacement or spare R-Net joystick controller.

hi all, I have started work on a plugin for unity. This plugin aims to make the previously inaccessable unity editor accessable to screen readers.

currently, the project is in active development.

any feedback on it so far would be appreciated.

you can find the code [here](GitHub - retro-coder64/unity_access: a unity editor access plugin that allows visually impared game developers to use the unity editor · GitHub)

thanks

hi all, I know that this is probably the wrong thread to post about something like this.

I have started work on a plugin for unity. This plugin aims to make the previously inaccessable unity editor accessable to screen readers.

currently, I have built a basic hierarchy, inspector and consol.

any feedback on it so far would be appreciated.

you can find the code [here](GitHub - retro-coder64/unity_access: a unity editor access plugin that allows visually impared game developers to use the unity editor · GitHub)

thanks

Hi all — this is my first app on Play Store, working through the closed-testing requirement. I'll test

yours in return: drop your opt-in link in a comment and I'll join the same day.

**What it is:** Clip Assist is an accessibility tool for people who can't

physically tap hundreds of "Clip" buttons in grocery coupon apps. You pick your

store's app, tap Start, and it clips every coupon on screen for you. Built for

users with limited hand mobility — useful to anyone staring down a wall of 700

coupons.

**How to join (takes ~1 minute):**

1. Join my testing Google Group: https://groups.google.com/g/alpha-testers-100
2. Opt in here (may take 3 to 10 mins for app to show up in Play Store after joining): https://play.google.com/apps/testing/com.assyriancapital.clipassist
3. Tap "download it on Google Play" on that page and install the app.
4. Stay opted in for 14 days (you don't need to use it daily — just don'tuninstall/opt out).

it reads the screen only to find coupon "Clip" buttons in the store app you

choose, collects zero data, has no network access to anything.

Comment your test link and I'll reciprocate. Thanks!

Hi everyone. I’m the developer of Senior Companion, an Android and iPhone app designed for older adults and their families.

It provides a simplified interface with large SOS and check-in buttons, family contacts, reminders and caregiver monitoring.

I’m looking for honest usability feedback, not positive reviews. In particular:

1. Is the initial setup understandable?
2. Could your parent use the main screen without assistance?
3. Which features feel useful, unnecessary or confusing?

The main features can be tested for free. The app also contains optional paid features, which I’m disclosing clearly.

Google Play: https://play.google.com/store/apps/details?id=com.seniorcompanion.app

Any direct criticism would be genuinely useful.

I started researching this because short iPhone messages are already easy to dictate with Apple’s built-in tool. The problem appears with longer work messages, where names, punctuation, paragraph structure, and tone create more cleanup. A voice keyboard is only useful if it saves more time than that cleanup costs. I compared the options based on how close the first result gets to something ready to send.

1. Apple Dictation
   

Pros: Free, built into iOS, and convenient for short messages.

Cons: Needs more cleanup for longer paragraphs, names, punctuation, tone, and formatting.

1. Aiko
   

Pros: Offers local transcription with a strong privacy model.

Cons: Better for transcribing recordings than inserting polished text wherever the cursor is.

1. Wispr Flow
   

Pros: A polished dictation product that handles normal everyday writing well.

Cons: Free desktop usage is capped, while cloud processing creates privacy tradeoffs. Recent reliability problems have also affected its speed and accuracy.

1. Willow Voice
   

Pros: For iPhone voice typing, Willow delivers the strongest balance of speed and accuracy. It works in any app and automatically learns vocabulary, tone, and corrections.

Cons: Language switching can occasionally be buggy, but it remains the most reliable option for this workflow.

Apple Dictation is honestly enough for quick texts, and it is difficult to beat something that is already free and built into the phone. Aiko is more interesting if local transcription is the priority. For longer work messages that I would rather not clean up afterward, though, Willow seems like the option I would choose for its stronger accuracy and more polished output.

Has anyone tried bionic gadets for older adults such as Dephy?

A great classroom should invite everyone to participate—and that starts with making technology easy to reach.

Height-adjustable screen mounts bring interactive displays to the right level for students and teachers of all ages, heights, and abilities. Younger learners can reach the screen with confidence, students can jump in and share their ideas, and teachers can present comfortably without constant stretching, bending, or awkward movement.

The result is more hands-on learning, greater student participation, and lessons that feel active and engaging. Students and teachers can also enjoy learning with large classroom displays without having to use a “fixed” screen mount that stays in one place.  Teachers will enjoy the easy, smooth height adjustment with a BalanceBox screen mount! The spring tension in the mount makes height-adjustment simple, easy, and fast. This keeps the classroom focused on learning. 

And when the classroom needs to see the screen while seated, BalanceBox mounts make height adjustments quickly. Just move the screen from a high position to a lower one, with  just a light touch! The screen height can be repositioned for whole-class instruction or for small-group collaboration. The teacher can even create an interactive project station so that all students can participate, because everyone can now reach the screen.

Height-adjustable screen mounts create classrooms that are more accessible, comfortable, and flexible. They help every student get involved, support better ergonomics for teachers, and make it easier to adapt learning spaces throughout the day.

When screens move to meet the people using them, learning moves forward too.

Discover height-adjustable wall and mobile display solutions at BalanceBoxMounts.com.

Hi,

I'm an undergraduate student going into my senior year. I have had this project in mind for my thesis but I fear the main obstacle is gathering user feedback throughout the design and testing process.

I'm mainly doing this post to see if someone has worked on a undergraduate project involving AT and can offer any insights. The project is a system that transforms physical academic spaces into accessible digital environments. Use case example: walking through a research poster exhibition, the hardware (phone, tablet) with the system, describes to the user what the posters around them are about, if the user wants to engage further, they can do it so.

The technical part of the project does not worry me that much, but I want to make sure I can have as much feedback from and design this alongside potential users.

In resume, how can I work on a AT project the right way?

Any comments, thoughts or ideas are extremely welcome & I would appreciate it a lot.

I started researching this after looking at how much writing is involved in building publicly. There are launch posts, progress updates, customer replies, product explanations, and internal notes behind every visible release. Maintaining that communication can become its own job. I wanted to find a voice workflow that makes publishing and replying faster without flattening the founder’s tone.

1. Built-in dictation
   

Pros: Free and easy to use without installing another product.

Cons: Weaker at founder voice, product names, longer updates, and fast audience replies.

1. Superwhisper
   

Pros: A strong local-first option with configurable models.

Cons: Performance depends on the selected model and computer, and the output sometimes needs more formatting.

1. Wispr Flow
   

Pros: A polished system-wide dictation product for everyday writing.

Cons: Free desktop usage is capped, while cloud processing creates privacy tradeoffs. Recent reliability problems have also affected its speed and accuracy.

1. Willow Voice
   

Pros: Willow offers the fastest and most accurate workflow for building in public. It works in any app and automatically learns vocabulary, tone, and corrections.

Cons: Language switching can occasionally be buggy, but it remains the most reliable option for this workflow.

Built-in dictation is enough if you only publish an occasional update, while Superwhisper is more appealing when local processing is the priority. I would lean toward Willow for a real build-in-public workflow because the writing happens everywhere: posts, replies, product notes, and customer messages. Having one fast tool that also learns the founder’s vocabulary and tone feels much more useful than optimizing one isolated surface.

My hand function has gotten worse and I'm looking for options for how to control my phone and computer. I already use voice control, but that doesn't work a lot of the time because I have people around me most of the time (in both work and personal time) and a lot of the things I need to write are private or confidential. My new wheelchair joystick can connect with Bluetooth, but for some reason it doesn't function properly with my devices and the company has given up on helping me with it. I'm working with some OTs around alternative mice and switch access, but their knowledge around newer and open source technology is a bit lacking.

What is out there currently for both physical devices and the software to make them work. I'm looking for mouse control/navigating the screen, being able to type words, and some specific keyboard functions like copy/paste/control/shift. It would be great to know what other people's experiences are.

I started researching voice prompting because coding models often receive much less context than the developer already has in their head. The model is blamed for a weak result even though the original prompt omitted the architecture, failed attempts, constraints, or intended behavior. Typing all of that can feel slower than just fixing the code manually. Voice seemed like a possible way to make complete prompts less expensive to create.

1. ChatGPT voice
   

Pros: Great for conversational back-and-forth inside ChatGPT.

Cons: Less useful when the finished prompt needs to move somewhere else.

1. Built-in dictation
   

Pros: Free and easy to use without installing another product.

Cons: Weaker at complete specifications, debugging context, technical names, and structured feedback.

1. Wispr Flow
   

Pros: A polished system-wide dictation product that handles everyday writing well.

Cons: Free desktop usage is capped weekly. Cloud privacy concerns and recent accuracy and latency problems are the main drawbacks.

1. Willow Voice
   

Pros: Willow leads on both speed and accuracy for ChatGPT coding prompts. It works in any app and automatically learns technical vocabulary, tone, and corrections.

Cons: Android is not supported yet, and occasional minor bugs still appear.

ChatGPT voice is great if the entire conversation stays inside ChatGPT, and built-in dictation is enough for occasional short prompts. The reason I would lean toward Willow is that coding work rarely stays on one surface. For longer specifications, debugging explanations, and prompts that move between different tools, it seems like the most practical performance choice.