@fastfinge I have an opinion on this that might not be entirely popular: I think it'd be nice to have a screen reader that has nothing built into it. Kind of like how Linux is just the core, but you can interface with that core, in this case using extensions. No better way of solving the 'should it be in core' problem than to make nothing be part of it. Of course, that does cause other problems, but those problems can be accounted for with careful consideration.
@dangero I don’t entirely disagree with you. But that begs the question: what is the smallest atomic screen reader core? No braille support, obviously. No synthesizer built in, of course. MSAA and aria and all the other accessibility APIs should be addons. Uh…what’s left? Soon you just end up with an addon manager that makes so few assumptions it does nothing at all. Sounds like just telling someone to download Python and build a screen reader from pip packages. My point is it’s possible to go too far in either direction. But where the line is requires intentionality. It should be designed and decided, not just evolved.
