• 14 Posts
  • 24 Comments
Joined 1 year ago
cake
Cake day: June 30th, 2025

help-circle











  • I’m not an expert, but based on anecdotal evidence as well as what I was told by a specialist as a kid, Dyslexia technically is just the symptom of having difficulties with reading and/or writing. People will often have multiple “dys” conditions (not sure of the names in English, but difficulties speaking, with math/numbers, with orientation, with one’s understanding of their position in space, etc.).

    I forget why, but we often bunch all that together and put it under the dyslexia for ease of use when it concerns language/learning. And it’s a clearly identified condition at that stage; that can be transmitted genetically (mostly by the father IIRC).

    On one extreme, I’ve met people who could barely read at all, and were totally unable to write with a pen because of dyslexia; but I also know people who technically have common issues linked to it (slow reading, confusing similar letters, etc.) but would not qualify for a proper diagnosis because it is too mild to affect their life in an adverse way. So yeah, it’s one of these things that falls on a spectrum.

    As for OpenDyslexic, I find it too “wonky” and lopsided. It almost feels like the letters aren’t sticking to their line. To be fair, that’s how I write, but it doesn’t mean I want to read wobbly text.

    Atkinson Hyperlegible, on the other hand, helps a lot with things like l,p,q,i,j,I all having clear distinctions that help make words easier to understand.














  • I went with a stack pattern and priorities.

    Within a priority the last “layer” to activate is the only one to receive inputs. The priority system just means that if a layer from a lower priority gets activated, it doesn’t take over until the upper layer is empty.

    It’s a bit stricter (only one layer active at all times), but you can always subscribe to inputs from multiple layers to achieve what you were describing.

    The main advantage here was that you can safely rely on enabling/disabling layers without ever getting a conflict… If some popup comes in over your menu, the popup is in charge until it’s closed. No need for them to communicate, and you reliably know that inputs will eventually return to the menu properly, even if something else gets interposed.

    And since it’s tacked onto the existing system, you can always have parts of the code that ignore the layer system entirely if necessary (like a mute button that has to work across all systems/menus for example).