It could certainly detect borders, colors and style changes.
When it comes to gum, it's up to you what you want to display. Don't want ASCII borders? That's fine.
It could certainly detect borders, colors and style changes.
When it comes to gum, it's up to you what you want to display. Don't want ASCII borders? That's fine.
@AutumnMeowMeow @loke @antijingoist @fribbledom 1. accessibility is not important
2. it’s the terminal isn’t it accessibile automatically?
3. accessibility isn’t as important as usability (they’re the same thing)
so i saw gum being allllmost there, almost the right kind of thing to be accessible AND easy to code but then just not bothering? so weird
@AutumnMeowMeow @loke @antijingoist @fribbledom
i am loving the problem solving here.in retrospect my posts sound a bit crabby but i was *just* thinking about something similar to gum , but in the context of how easy and important it is to have an accessibility mode for TUI apps.
i get a bit irritated by dismissive attitudes that say
@loke @antijingoist @fribbledom @zens DA1 is the standard VT100/VT220/etc. Device Attributes query (also called Primary DA). The response from the terminal is a list of numbers, each of which has a specific feature meaning.
@AutumnMeowMeow @antijingoist @fribbledom @zens that could be an alternative indeed. If you you want to go that route, then one could define an entire extension protocol that allows a terminal to render things in an accessible manner.
But how does da1 work? I don't see it defined in terminfo, so you're suggesting hardcoding an extension to xterm?
@loke @antijingoist @fribbledom @zens Better than terminfo (which isn't portable, and can't traverse ssh/telnet et al interactive links) would be a device attributes (DA1) response that indicates the terminal can support whatever new feature.
Problem may be also that accessibility is almost always an afterthought, and anyone implementing this in a workplace is not going to go out of their way to pick accessible options over the flashy ones. Very rarely is something done correctly in the field vs quickly.
(otherwise I think this looks fantastic atm. To the point where if I knew go I’d try to add any necessary pieces found in a pull reqst.)
@antijingoist @fribbledom @zens Perhaps there should be a terminfo field that indicates that accessible options are preferred. Then anyone wanting that could set TERM to this special terminal and programs such as gum could adjust its settings to make it easier to use with a braille terminal for example.
@zens @AutumnMeowMeow @loke @antijingoist
Ufff, you seem to have no idea how many hours we sunk into this to be as accessible as possible. I'm sorry we don't live up to your standards, but then I'm starting to wonder which software does.
@zens @AutumnMeowMeow @loke @antijingoist
I never said we didn't bother. I pointed out that given the right environment variables it should be as accessible as it's currently possible, given the limits of terminals and screen reader software.
Sadly they are in a really dire state and the truth is a lot has to happen for the terminal to become truly accessible. That's nothing we can fix in the scope of gum, tho. GUIs are far ahead in that regard.
@fribbledom @AutumnMeowMeow @loke @antijingoist i don’t know if it lives up to my standards or not that’s why i asked. why didn’t you tell me about those hundreds of hours in the first place?
what you told me was you didn’t bother and it was fine it’s not important.
i think not being dismissive of this question isn’t a high standard
@fribbledom @AutumnMeowMeow @loke @antijingoist i think you worded it a lot better this time, i misunderstood what you meant
@zens @AutumnMeowMeow @loke @antijingoist
I'm sorry about that and am glad I could clarify that part a bit. I'm honestly trying to be anything but dismissive when it comes to accessibility and have been actively trying to improve the situation in open-source software for the better part of my life now (mostly working on GUI toolkits like Qt however).
@fribbledom @AutumnMeowMeow @loke @antijingoist maybe get rid of “that’s sad to hear, but…” from your repertoir. that made it seem to me like you were hearing this for the first time… BUT didn’t think it was very important. so even tho the correct, information followed it sounded like excuses
@zens @AutumnMeowMeow @loke @antijingoist
I don't know what to say 😆 I get your point, but the state of accessibility in terminal(-software) is quite simply that: sad.
Bobinas P4G is a social network. It runs on GNU social, version 2.0.1-beta0, available under the GNU Affero General Public License.
All Bobinas P4G content and data are available under the Creative Commons Attribution 3.0 license.