I absolutely hate touch screens!
-
@TheQuinbox I wouldn't want a phone with phisical buttons, just my hable for typing is good for me.
@J3317 @TheQuinbox If I may ask, is it that you wouldn't want a phone with physical buttons even if it was a very modern phone, or do you just not want any of the phones with physical buttons which are available now since they're so behind.
-
I absolutely hate touch screens! I love my current phone, a Pixel 9A. It has good battery, good speakers, a flat back, etc. But I am so fucking inefficient on a touch screen, no matter if its iOS or android. Want me to google something? Okay, let me look around for the web browser, double tap on it, explore by touch until I find the address bar which might or might not have been moved or altered in a recent app update, double tap there, type way slower than on a physical keyboard, hit search, switch my rotor/reading control to headings, and very slowly start reading through results. Touch screens are remarklably efficient for people with functioning eyeballs, and I've seen people who can text on a phone almost as fast as I can type on a computer. But for me, a metal slab with a glass screen and way more computing power than I would've ever thought possible, no matter how fucking cool it is that we can drop that in our pockets like its nothing, will never ever be as efficient as win+r, browsername, enter, start typing, enter, press h, boom first result. This is not helped by the mainstream screen readers on both mobile operating systems having agrivating bugs. On Android scrolling locks up your screen reader while it refreshes the screen, because we're apparently still living in 2005, and VO has just started getting worse and worse with every iteration. I see the downsides to this approach, but I'm really starting to think the best solution for mobile devices for blind people is custom hardware/software. There are plenty of examples of getting this wrong, but I think that's mostly due to people not eating their own dog food as opposed to it being an impossible task. Paperback for Android has shown me that you can make as polished of Android software as you want, but there are still no physical buttons on the front of your phone. For a truly efficient reading and usability experience, I'd personally want both blind-centric software and hardware with physical buttons. That's not at all realistic, though. Welcome to being blind in a world made for sighted people.
@TheQuinbox I agree to a point, but I pretty much hate all blindness specific hardware.
-
@TheQuinbox I agree to a point, but I pretty much hate all blindness specific hardware.
@bscross32 I don't think you're disagreeing with @TheQuinbox at all. I, too, hate blindness hardware because... every single example I've seen over the past ten years has been bad. By bad, I mean significantly worse than products doing similar things for the sighted. Usually, much worse. My view is that this is the market, not anything inherent in hardware for the blind, but of course I don't know that for sure.
-
I absolutely hate touch screens! I love my current phone, a Pixel 9A. It has good battery, good speakers, a flat back, etc. But I am so fucking inefficient on a touch screen, no matter if its iOS or android. Want me to google something? Okay, let me look around for the web browser, double tap on it, explore by touch until I find the address bar which might or might not have been moved or altered in a recent app update, double tap there, type way slower than on a physical keyboard, hit search, switch my rotor/reading control to headings, and very slowly start reading through results. Touch screens are remarklably efficient for people with functioning eyeballs, and I've seen people who can text on a phone almost as fast as I can type on a computer. But for me, a metal slab with a glass screen and way more computing power than I would've ever thought possible, no matter how fucking cool it is that we can drop that in our pockets like its nothing, will never ever be as efficient as win+r, browsername, enter, start typing, enter, press h, boom first result. This is not helped by the mainstream screen readers on both mobile operating systems having agrivating bugs. On Android scrolling locks up your screen reader while it refreshes the screen, because we're apparently still living in 2005, and VO has just started getting worse and worse with every iteration. I see the downsides to this approach, but I'm really starting to think the best solution for mobile devices for blind people is custom hardware/software. There are plenty of examples of getting this wrong, but I think that's mostly due to people not eating their own dog food as opposed to it being an impossible task. Paperback for Android has shown me that you can make as polished of Android software as you want, but there are still no physical buttons on the front of your phone. For a truly efficient reading and usability experience, I'd personally want both blind-centric software and hardware with physical buttons. That's not at all realistic, though. Welcome to being blind in a world made for sighted people.
@TheQuinbox I'm sighted but I've been working on making a portable audio based desktop environment for these exact same reasons. I use a one handed keyboard and bluetooth headphones with a single board computer hooked to a portable battery bank. Sadly I found linux screen readers have been too slow to use so I'm designing my own. IMO screen reader first setups could be better than dedicated linux phones if you focus on keyboard access and ignore the rendering entirely.
-
@TheQuinbox I'm sighted but I've been working on making a portable audio based desktop environment for these exact same reasons. I use a one handed keyboard and bluetooth headphones with a single board computer hooked to a portable battery bank. Sadly I found linux screen readers have been too slow to use so I'm designing my own. IMO screen reader first setups could be better than dedicated linux phones if you focus on keyboard access and ignore the rendering entirely.
@mauve Holy shit, this sounds fucking awesome! I'd love to pick your brain about this.
-
I absolutely hate touch screens! I love my current phone, a Pixel 9A. It has good battery, good speakers, a flat back, etc. But I am so fucking inefficient on a touch screen, no matter if its iOS or android. Want me to google something? Okay, let me look around for the web browser, double tap on it, explore by touch until I find the address bar which might or might not have been moved or altered in a recent app update, double tap there, type way slower than on a physical keyboard, hit search, switch my rotor/reading control to headings, and very slowly start reading through results. Touch screens are remarklably efficient for people with functioning eyeballs, and I've seen people who can text on a phone almost as fast as I can type on a computer. But for me, a metal slab with a glass screen and way more computing power than I would've ever thought possible, no matter how fucking cool it is that we can drop that in our pockets like its nothing, will never ever be as efficient as win+r, browsername, enter, start typing, enter, press h, boom first result. This is not helped by the mainstream screen readers on both mobile operating systems having agrivating bugs. On Android scrolling locks up your screen reader while it refreshes the screen, because we're apparently still living in 2005, and VO has just started getting worse and worse with every iteration. I see the downsides to this approach, but I'm really starting to think the best solution for mobile devices for blind people is custom hardware/software. There are plenty of examples of getting this wrong, but I think that's mostly due to people not eating their own dog food as opposed to it being an impossible task. Paperback for Android has shown me that you can make as polished of Android software as you want, but there are still no physical buttons on the front of your phone. For a truly efficient reading and usability experience, I'd personally want both blind-centric software and hardware with physical buttons. That's not at all realistic, though. Welcome to being blind in a world made for sighted people.
@TheQuinbox Oh you do have that kind of.custom phones. Say blindshell and the likes. Only problem olis they are basically a custom shell over android for old people with legacy components inside.
-
@TheQuinbox Oh you do have that kind of.custom phones. Say blindshell and the likes. Only problem olis they are basically a custom shell over android for old people with legacy components inside.
@ragb @TheQuinbox Even those phones, because they have, as you rightly say, "legacy components", are very slow and a serious pain to use for anyone used to a windows machine and its speed. I have a smartvision 3 which I bought used and it was worth less to me than the very low price I spent for it.
-
@mauve Holy shit, this sounds fucking awesome! I'd love to pick your brain about this.
@TheQuinbox Yeah of course! The tl;dr is the Twiddler 4 keyboard and a Khadas Edge 2 glued to a random USB-C powerbank. Orca for screen reader for now but I'm gonna slap together something else. Mostly geares towards jumping around the accessibility tree with fuzzy search. Maybe also speaking live regions in multiple voices to get more data through?
-
I absolutely hate touch screens! I love my current phone, a Pixel 9A. It has good battery, good speakers, a flat back, etc. But I am so fucking inefficient on a touch screen, no matter if its iOS or android. Want me to google something? Okay, let me look around for the web browser, double tap on it, explore by touch until I find the address bar which might or might not have been moved or altered in a recent app update, double tap there, type way slower than on a physical keyboard, hit search, switch my rotor/reading control to headings, and very slowly start reading through results. Touch screens are remarklably efficient for people with functioning eyeballs, and I've seen people who can text on a phone almost as fast as I can type on a computer. But for me, a metal slab with a glass screen and way more computing power than I would've ever thought possible, no matter how fucking cool it is that we can drop that in our pockets like its nothing, will never ever be as efficient as win+r, browsername, enter, start typing, enter, press h, boom first result. This is not helped by the mainstream screen readers on both mobile operating systems having agrivating bugs. On Android scrolling locks up your screen reader while it refreshes the screen, because we're apparently still living in 2005, and VO has just started getting worse and worse with every iteration. I see the downsides to this approach, but I'm really starting to think the best solution for mobile devices for blind people is custom hardware/software. There are plenty of examples of getting this wrong, but I think that's mostly due to people not eating their own dog food as opposed to it being an impossible task. Paperback for Android has shown me that you can make as polished of Android software as you want, but there are still no physical buttons on the front of your phone. For a truly efficient reading and usability experience, I'd personally want both blind-centric software and hardware with physical buttons. That's not at all realistic, though. Welcome to being blind in a world made for sighted people.
@TheQuinbox Honestly sometimes I have thought about looking at Blindshell even though I have been using VO almost exclusively with a touchscreen since 2009, and have gotten reasonably fast with direct touch typing mode. Also like you said web browsing really is a pain in the arse.
-
I absolutely hate touch screens! I love my current phone, a Pixel 9A. It has good battery, good speakers, a flat back, etc. But I am so fucking inefficient on a touch screen, no matter if its iOS or android. Want me to google something? Okay, let me look around for the web browser, double tap on it, explore by touch until I find the address bar which might or might not have been moved or altered in a recent app update, double tap there, type way slower than on a physical keyboard, hit search, switch my rotor/reading control to headings, and very slowly start reading through results. Touch screens are remarklably efficient for people with functioning eyeballs, and I've seen people who can text on a phone almost as fast as I can type on a computer. But for me, a metal slab with a glass screen and way more computing power than I would've ever thought possible, no matter how fucking cool it is that we can drop that in our pockets like its nothing, will never ever be as efficient as win+r, browsername, enter, start typing, enter, press h, boom first result. This is not helped by the mainstream screen readers on both mobile operating systems having agrivating bugs. On Android scrolling locks up your screen reader while it refreshes the screen, because we're apparently still living in 2005, and VO has just started getting worse and worse with every iteration. I see the downsides to this approach, but I'm really starting to think the best solution for mobile devices for blind people is custom hardware/software. There are plenty of examples of getting this wrong, but I think that's mostly due to people not eating their own dog food as opposed to it being an impossible task. Paperback for Android has shown me that you can make as polished of Android software as you want, but there are still no physical buttons on the front of your phone. For a truly efficient reading and usability experience, I'd personally want both blind-centric software and hardware with physical buttons. That's not at all realistic, though. Welcome to being blind in a world made for sighted people.
@TheQuinbox Interesting, with iOS, you can get some fairly consistent behavior. I find the Google app a. little easier for searching though, but navigating by headings through the results helps tremendously. I do prefer the computer overall, but I can use the phone short-term with no problems.
-
@TheQuinbox Interesting, with iOS, you can get some fairly consistent behavior. I find the Google app a. little easier for searching though, but navigating by headings through the results helps tremendously. I do prefer the computer overall, but I can use the phone short-term with no problems.
@hallen @TheQuinbox I'm kinda the same lol.
-
P pixelate@tweesecake.social shared this topic
-
@TheQuinbox I cannot agree more with any of this except for the solution. The solution for me, and it's not a great solution but it does exist, unlike any decent button-based phone, is remote access with a small bluetooth keyboard or game controller. This exists both from iOS https://testflight.apple.com/join/edg8YSeU and from android in several versions. This is not a good solution because it requires constant internet access, because it has issues (the iOS version, for example, has speech problems with eloquence, the android stuff often has problems with the keyboard). Having said that, it is the only solution which really works, which really makes windows+r/site/pressing h and the speed from that possible. Everything else is too slow or impossible. I wish someone would make a better screen reader and a better phone with buttons. It just isn't going to happen. I'm very sorry to think that, but he evidence makes it the only conclusion. Phones can be used for reading and phone/text, and maybe for some apps. They just aren't efficient for much else, in my experience.
@techsinger @TheQuinbox Game controller?
-
I absolutely hate touch screens! I love my current phone, a Pixel 9A. It has good battery, good speakers, a flat back, etc. But I am so fucking inefficient on a touch screen, no matter if its iOS or android. Want me to google something? Okay, let me look around for the web browser, double tap on it, explore by touch until I find the address bar which might or might not have been moved or altered in a recent app update, double tap there, type way slower than on a physical keyboard, hit search, switch my rotor/reading control to headings, and very slowly start reading through results. Touch screens are remarklably efficient for people with functioning eyeballs, and I've seen people who can text on a phone almost as fast as I can type on a computer. But for me, a metal slab with a glass screen and way more computing power than I would've ever thought possible, no matter how fucking cool it is that we can drop that in our pockets like its nothing, will never ever be as efficient as win+r, browsername, enter, start typing, enter, press h, boom first result. This is not helped by the mainstream screen readers on both mobile operating systems having agrivating bugs. On Android scrolling locks up your screen reader while it refreshes the screen, because we're apparently still living in 2005, and VO has just started getting worse and worse with every iteration. I see the downsides to this approach, but I'm really starting to think the best solution for mobile devices for blind people is custom hardware/software. There are plenty of examples of getting this wrong, but I think that's mostly due to people not eating their own dog food as opposed to it being an impossible task. Paperback for Android has shown me that you can make as polished of Android software as you want, but there are still no physical buttons on the front of your phone. For a truly efficient reading and usability experience, I'd personally want both blind-centric software and hardware with physical buttons. That's not at all realistic, though. Welcome to being blind in a world made for sighted people.
@TheQuinbox @modulux And that’s on touchscreens with a screen reader available. Things are different when you’ve got a rubbish ‘Guide Voice’ feature that doesn’t even qualify as a screen reader, as is the case with some Yamaha Arrangers, for example. Or when you’re sitting in the passenger seat of a car and you can’t even adjust the air conditioning, or – in very modern cars – you can’t even adjust your seat. (1/2)
-
@TheQuinbox @modulux And that’s on touchscreens with a screen reader available. Things are different when you’ve got a rubbish ‘Guide Voice’ feature that doesn’t even qualify as a screen reader, as is the case with some Yamaha Arrangers, for example. Or when you’re sitting in the passenger seat of a car and you can’t even adjust the air conditioning, or – in very modern cars – you can’t even adjust your seat. (1/2)
Yes, the touchscreen has come about to cut costs for the manufacturer, to charge the buyer more, and to make life a nightmare for the blindversion) (2/2)
@TheQuinbox @modulux -
I absolutely hate touch screens! I love my current phone, a Pixel 9A. It has good battery, good speakers, a flat back, etc. But I am so fucking inefficient on a touch screen, no matter if its iOS or android. Want me to google something? Okay, let me look around for the web browser, double tap on it, explore by touch until I find the address bar which might or might not have been moved or altered in a recent app update, double tap there, type way slower than on a physical keyboard, hit search, switch my rotor/reading control to headings, and very slowly start reading through results. Touch screens are remarklably efficient for people with functioning eyeballs, and I've seen people who can text on a phone almost as fast as I can type on a computer. But for me, a metal slab with a glass screen and way more computing power than I would've ever thought possible, no matter how fucking cool it is that we can drop that in our pockets like its nothing, will never ever be as efficient as win+r, browsername, enter, start typing, enter, press h, boom first result. This is not helped by the mainstream screen readers on both mobile operating systems having agrivating bugs. On Android scrolling locks up your screen reader while it refreshes the screen, because we're apparently still living in 2005, and VO has just started getting worse and worse with every iteration. I see the downsides to this approach, but I'm really starting to think the best solution for mobile devices for blind people is custom hardware/software. There are plenty of examples of getting this wrong, but I think that's mostly due to people not eating their own dog food as opposed to it being an impossible task. Paperback for Android has shown me that you can make as polished of Android software as you want, but there are still no physical buttons on the front of your phone. For a truly efficient reading and usability experience, I'd personally want both blind-centric software and hardware with physical buttons. That's not at all realistic, though. Welcome to being blind in a world made for sighted people.
@TheQuinbox I use a BT keyboard to type on my phone for this exact reason. I'm much better with actual buttons and keys than I *ever* will be on a touch screen. Also did someone say 2005?
-
@TheQuinbox I'm sighted but I've been working on making a portable audio based desktop environment for these exact same reasons. I use a one handed keyboard and bluetooth headphones with a single board computer hooked to a portable battery bank. Sadly I found linux screen readers have been too slow to use so I'm designing my own. IMO screen reader first setups could be better than dedicated linux phones if you focus on keyboard access and ignore the rendering entirely.
@mauve @TheQuinbox yo, that's awesome! do you have a git repo or something I can look at?
About the screenreader, sure you can build your own, and depending on what you want to do maybe you should, but me and some other people are working on a screenreader for linux, to replace orca because of multiple grievances we have with it. Work on it is really slow especially now because we're at the heuristics stage, but you know, it's a thing which may give you inspiration and stuff if you don't want to make it from scratch. -
@TheQuinbox And people just genuinely don't understand why I only ever use my phone with resistance. Even other blind people. I literally never web search on the phone because even with dictate solving the typing problem, ever noticed that one VO quirk where the further you get down the page the slower it gets? Plus web minus adblocker is no web at all.
@x0 @TheQuinbox I hate searching for anything on my phone. I'll use it for anything else but web searching. Nope.
-
I absolutely hate touch screens! I love my current phone, a Pixel 9A. It has good battery, good speakers, a flat back, etc. But I am so fucking inefficient on a touch screen, no matter if its iOS or android. Want me to google something? Okay, let me look around for the web browser, double tap on it, explore by touch until I find the address bar which might or might not have been moved or altered in a recent app update, double tap there, type way slower than on a physical keyboard, hit search, switch my rotor/reading control to headings, and very slowly start reading through results. Touch screens are remarklably efficient for people with functioning eyeballs, and I've seen people who can text on a phone almost as fast as I can type on a computer. But for me, a metal slab with a glass screen and way more computing power than I would've ever thought possible, no matter how fucking cool it is that we can drop that in our pockets like its nothing, will never ever be as efficient as win+r, browsername, enter, start typing, enter, press h, boom first result. This is not helped by the mainstream screen readers on both mobile operating systems having agrivating bugs. On Android scrolling locks up your screen reader while it refreshes the screen, because we're apparently still living in 2005, and VO has just started getting worse and worse with every iteration. I see the downsides to this approach, but I'm really starting to think the best solution for mobile devices for blind people is custom hardware/software. There are plenty of examples of getting this wrong, but I think that's mostly due to people not eating their own dog food as opposed to it being an impossible task. Paperback for Android has shown me that you can make as polished of Android software as you want, but there are still no physical buttons on the front of your phone. For a truly efficient reading and usability experience, I'd personally want both blind-centric software and hardware with physical buttons. That's not at all realistic, though. Welcome to being blind in a world made for sighted people.
@TheQuinbox I don't like touchscreens very much myself. I have a Hable, and it gets the job done, when I remember to use it that is. I'm so used to using BSI and touch-typing that I don't really think to use something like my Hable. I like using bluetooth keyboards, but again, it just seems like one extra thing to carry around. I've started using this thing called Whisper Flow, which is a voice dictation keyboard that you can literally whisper to, and it does a hell of a lot better job than iOS stock dictation. I really don't know the right answer, but I know one thing for sure. If Flicktype hadn't gone away, I would still be using that and typing more efficiently than I am right now. I don't even know if blaming Apple for that is the most accurate thing with this particular situation, but yeah.
-
I absolutely hate touch screens! I love my current phone, a Pixel 9A. It has good battery, good speakers, a flat back, etc. But I am so fucking inefficient on a touch screen, no matter if its iOS or android. Want me to google something? Okay, let me look around for the web browser, double tap on it, explore by touch until I find the address bar which might or might not have been moved or altered in a recent app update, double tap there, type way slower than on a physical keyboard, hit search, switch my rotor/reading control to headings, and very slowly start reading through results. Touch screens are remarklably efficient for people with functioning eyeballs, and I've seen people who can text on a phone almost as fast as I can type on a computer. But for me, a metal slab with a glass screen and way more computing power than I would've ever thought possible, no matter how fucking cool it is that we can drop that in our pockets like its nothing, will never ever be as efficient as win+r, browsername, enter, start typing, enter, press h, boom first result. This is not helped by the mainstream screen readers on both mobile operating systems having agrivating bugs. On Android scrolling locks up your screen reader while it refreshes the screen, because we're apparently still living in 2005, and VO has just started getting worse and worse with every iteration. I see the downsides to this approach, but I'm really starting to think the best solution for mobile devices for blind people is custom hardware/software. There are plenty of examples of getting this wrong, but I think that's mostly due to people not eating their own dog food as opposed to it being an impossible task. Paperback for Android has shown me that you can make as polished of Android software as you want, but there are still no physical buttons on the front of your phone. For a truly efficient reading and usability experience, I'd personally want both blind-centric software and hardware with physical buttons. That's not at all realistic, though. Welcome to being blind in a world made for sighted people.
@mustikkasoppa @TheQuinbox yup. I have partially solved this by cramming my Pixel into a Clicks keyboard case, which at least makes text entry less painful. And I will say that once muscle memory sets in, and it actually works (read; doesn't get fucked with by an update), it can be very smooth to grab phone, unlock, tap banner notification for bank confirmation, tap fingerprint sensor, put away phone. But for longer interactions you inevitably slow down.
I honestly don't really know how we would fix it OS-wide. Touchscreens being organic and using spatiality to its advantage is its strength and its weakness and screenreaders don't have an effective interaction layer for them et -
@mustikkasoppa @TheQuinbox yup. I have partially solved this by cramming my Pixel into a Clicks keyboard case, which at least makes text entry less painful. And I will say that once muscle memory sets in, and it actually works (read; doesn't get fucked with by an update), it can be very smooth to grab phone, unlock, tap banner notification for bank confirmation, tap fingerprint sensor, put away phone. But for longer interactions you inevitably slow down.
I honestly don't really know how we would fix it OS-wide. Touchscreens being organic and using spatiality to its advantage is its strength and its weakness and screenreaders don't have an effective interaction layer for them et@zersiax @mustikkasoppa @TheQuinbox That's why touch screens really only work for me on phones. I also have an iPad, but hardly use it, or if I use, only with a keyboard attached or paired. And I never used Windows with a touch screen, even when the Surface laptop I once owned, had one. It is just too cumbersome and too unnatural for me.
