Login
You're viewing the functional.cafe public feed.
  • Nov 16, 2026, 6:55 PM

    My screenreader accessibility plans in my current projects:

    Regarding #merephone: As a phone I'll need to include speakers, so I'll implement a simple Flite-based screenreader for its 2 widgets. Reading the text you've typed, menu title, & menu selection.
    A caveat is that reading the labels for the device's physical controls would prove tiring, so I'll repurpose a toggle button for a font-light to toggle a verbose screenreader mode! Sighted users won't get annoyed by onscreen labels.

    1/4?

    💬 1🔄 2⭐ 0

Replies

  • Nov 16, 2026, 7:05 PM

    Regarding #Alonzo: I have my own UI framework upon which to implement my editor, it is fully keyboard-accessible & I can promise that it'll be fully screenreader accessible too!
    While I haven't integrated with screenreaders yet, I've researched how to & I'm making sure nothing I do will hinder it.

    All my accessibility & internationalization work will also apply to any running Alonzo programs!

    2/4 For broader accessibility

    💬 1🔄 2⭐ 0
  • Nov 16, 2026, 7:21 PM

    For #merephone: I hope the tactility of the controls will make them more usable for pretty much anyone, & I'll offer accessibility settings I won't label as such.

    For #Alonzo: Its hard to draw a clear line between my efforts at accessibility & my efforts to make programming so trivial it is approachable. Notably I've got structural code-editing & navigation in place!

    In both projects there's limits to what I can do, if others don't do their part.

    3/4!

    💬 1🔄 1⭐ 0
  • Nov 16, 2026, 7:35 PM

    One thing that occurs to me: I was going to include a ArduCam in the merephone, to serve as a better-than-nothing camera. This won't give much of anything for the screenreader to describe, so there's a blank spot in the screenreader design.

    This could be an opportunity to add a useful feature specifically for the blind! But I'll want them to design it for themselves, I won't.

    And perhaps others can give advice on what Computer Vision my limited hardware could handle?

    4/4 Fin!

    💬 1🔄 2⭐ 0
  • Nov 16, 2026, 7:40 PM

    @alcinnz the issue is that this is a chicken and egg problem, we can't make a screenreader for something which can't present us information in any way to know what we pressed or did. So, maybe create a pluggable and hookable framework kinda like emacs, and then we can built that stuff without having to modify all components in the system? Yeah, I'm talking about an accessibility API

    💬 1🔄 1⭐ 0
  • Nov 16, 2026, 8:42 PM

    @esoteric_programmer Yeah, fair!

    That said... On a cheap microcontroller I'm not sure how pluggable I can make it, I have no process isolation. No multitasking, all code in ROM.

    I *think* the design of a decent screenreader for most of it is fairly obvious, though I will seek confirmation.

    My biggest question is regarding the device's camera mode? There I'd get JPGs or bitmaps & can verbally output text.

    💬 1🔄 0⭐ 0
  • 💬 1🔄 0⭐ 0
  • Nov 17, 2026, 12:27 AM

    @esoteric_programmer I presumably could...

    I mean neural-nets can be evaluated using software, so as long as it doesn't require much software... I see no reason I couldn't!

    The neural-net itself would probably have to be stored on an attached SD card, given I'm already finding I need to store fonts & hyphenation dictionaries there.

    The specs I've currently got are 48MHz clockspeed with 256KiB Flash & 32KiB SRAM. And I'm adding much needed extra datastorage with that SD card.

    💬 0🔄 0⭐ 0