The text mode lie: why modern TUIs are a nightmare for accessibility — The Inclusive Lens https://xogium.me/the-text-mode-lie-why-modern-tuis-are-a-nightmare-for-accessibility #Accessibility #CLI #TUI
Discussion
Loading...
Im sure this is a wonderful article but reading this is like trying to read a codebase on github where the lines average 200 chars. word wrapping is good.
@WeirdWriter FYI the text in the link doesn't wrap on my phone, although it does on the homepage
Thanks, but this isn't my website. I would try using reader mode and contacting the website developer. @tombrandis
@WeirdWriter @tombrandis thanks for the recommendation to use reader mode, I have the same issue and completely forgot about it
@WeirdWriter @jrdepriest Makes perfect sense.
@WeirdWriter yikes
" Hello! As part of our effort to keep our backlog manageable and focus on the most active issues, we are tidying up older reports. It looks like this > issue hasn't been active for a while, so we are closing it for now.”
This is unacceptable. Closing an accessibility report because the maintainers haven't touched it in months is not “tidying up”; it is hiding evidence. It effectively says that if a bug is ignored long enough, it ceases to exist. It boosts the project's “Closed Issues” metric while leaving the actual software unusable for blind users."
@krupo It happens all the time. I see it happened constantly in mainstream development as well as open source development
@WeirdWriter working in IT audit, I've seen similar persistent issues.
So it's satisfying to be able to wield the audit stick that says "the longer an issue isn't fixed the louder the audit finding is going to get."
I know as well that life isn't that simple, especially when things are "out of scope" for an audit.