I'm totally blind and have a second hand iphone 10. Face ID works well enough but isn't as nice as touch id. I'm trying to convince my self that I really do need an iPhone SE especially if were wearing masks when I'm back in the office.
Assuming there was an open source version of Windows 7 Microsoft would have to make Windows 10 much worse before I'd consider switching to it. WSL has bought me a lot of good will toward Microsoft. It probably helps that I'm blind so can't see any adds or crap ware installed on the start menu.
The fact that I can't tab to the cURL, Python, etc options when using Jaws doesn't fill me with confidence. I realize this may be because of the SaaS platform you chose but it still doesn't reflect particularly well on the developers of this.
I'm not sure if accessibility is something you focused on or if you just got lucky but according to this thread I need to give insomnia a try since Postman is not concerned with making there software even marginally usable if your blind.
https://github.com/postmanlabs/postman-app-support/issues/31...
I've found Mybatis[1] to be a better alternative to Hibernate. At least with the version I was using you had to do complex mapping in XML instead of annotations which isn't great but I'll make the trade-off to avoid the ORM. Not sure if this is improved in 3.5.
[1]
https://github.com/mybatis/mybatis-3
Often blindness is one of many disabilities a child may have. If a child is severely impaired basic skills such as the ability to dress and feed them selves are a lot more important then the ability to read braille. I’d like to see these statistics broken down in a way that considers individuals with multiple disabilities.
Were you born blind or did you lose your vision later in life? I was born totally blind and grew up as computers became accessible. While I don’t use braille much now, I don’t understand how someone born blind can have basic literacy using only speech. Growing up reading books allowed me to understand basic sentence structure, spelling, etc. These are all important as a programmer considering a large part of the job is communicating your decisions and opinions. I also found braille to be very useful in math. I think that braille is critical for early education if you are blind. It’s less important if you lose your vision later in life and already are literate do to reading print growing up.
I have the latest Windows insiders build on a spare machine. I've found all the aws tooling including SAM works pretty well under WSL 2 now that WSL uses a true Linux kernel.
I am blind and depend on the sound of cars a lot. When crossing busy streets I listen for traffic patterns to let me know what light is green and red. On less busy streets I listen for individual cars. There are not a lot of electric cars around me so I don't have any first hand experience on if tire noise is enough.
What are the odds that this will support 1080p streaming with Plex? I've tried Plex on a Pi 3 using a Roku as a player with 1080p and it's a complete failure. Plex tries to encode everything even if native playback to the Roku is possible using the Roku media player.
I'm a totally blind developer and I find the easiest way to do code reviews is to use git format-patch on the branch containing the code. I read the patch files in a text editor. Perhaps comments in the pull request referencing a commit and line would allow the developer to get the required context from the patch files?
As a blind user I don't want an easy way for websites or add tracking code to know if I'm using a screen reader. If this feature has to exist then it should be a site by site option that is disabled by default. I can then make the choice to determine if I want a site to know I'm using a screen reader based on the reasoning the site is asking. A blog does not need to know if I'm using a screen reader while a single page app may. I would argue that if a site has screen reader specific code they are doing things wrong but at least having to manually enable the option on a specific site would allow me to decide if the downsides of the site knowing I am blind are worth the reasoning they ask me to enable it.
Maybe Apple should take accessibility more seriously then? I'm a Voiceover user on iOS and accessibility has been regressing recently. Two examples I can think of include the fact that in the last several releases of iOS Voiceover can no longer read an entire article in the news app with out losing focus as well as the fact that all reviews in the app store have "developer response" announced even when none are available. Apple also appears to make no effort to engage with the accessibility community in the same way Microsoft or Google do. While Apple may have been a pioneer in accessibility I'm starting to look at cheep Android One phones to determine if I can switch from iOS.
If your electrical wiring is not super old and you are OK with transfer speeds between 100MBPS and 1GBPS consider powerline ethernet adaptors instead of running Ethernet cable depending on the difficulty of your runs. I have 100 MBPS internet service and I can saturate it using a powerline adaptor. I've also been able to cover my entire house with a single Unifi wifi access point plugged into a powerline adaptor by locating the access point in the center of my house on the first floor.
https://thewirecutter.com/reviews/best-powerline-networking-...
Just gave this another look and the sliders do work with my screen reading software which is an improvement. As far as I can tell the page up and down keys don't move in larger increments. Home and end don't move to the top or bottom either. Because of this when looking for servers priced between $0 and $5 I had to repeatedly hit left arrow a bunch of times. Ideally I could have gone to the maximum price slider, hit home to set it to 0, then hit right arrow several times to find my maximum price. I assume this is behavior of the noUiSlider framework and not code you have written.
Are the sliders keyboard accessible? I use Jaws for Windows as my screen reading software and am unable to adjust the price slider in either Firefox or Chrome.
I use Windows 10 machines and make heavy use of WSL. I use Eclipse as my IDE when doing Java work. I use Jaws for Windows as my primary screen reading software and NVDA occasionally for things it handles better then Jaws. I used to own a Mac but booted it into Windows most of the time once WSL became a thing. In my limited experience the Mac is OK for general computing from an accessibility perspective but does not offer the screen reader customizability and efficiency that Windows does.
https://www.freedomscientific.com/Products/Blindness/JAWShttps://www.nvaccess.org/
So just because this specific person has an issue that doesn't allow them to use a Chromebook they should make a blanket statement that they are inaccessible? I'm totally blind and have had a Chromebook for several years. I got it as a gift because I was interested in its accessibility. I've seen Google make large strides in accessibility in the couple years I've owned it. It went from barely usable to something I am comfortable using as my only computer if I don't need to do any programming. Just because something may not be fully accessible to someone does not mean we should ignore all the work companies have done to move accessibility from nonexistent to decent.
I got the Macbook air 6 years ago because it was the best windows ultrabook you could get at the time. Once WSL came out I rarely used OSX. WSL has drasticaly increased my productivity and basically made Windows 10 a completely new OS.
I'm curious if there are any blind programmers who prefer OSX to Windows when it comes to screen reading software. I used to own a Mac and found Voiceover easy to get started with, but not very efficient compared to Jaws for Windows. I'm not sure if this is because I didn't use it enough or if Jaws and possibly NVDA are better for experienced screen reader users who want all the easily accessible shortcuts.
ON windows I always manually set the volume of itunes much lower then the system volume. I assume you can do this on OSX. I find this a lot better then using audio ducking. It's jarring to have the music volume increase when I am thinking through a problem instead of doing something on the computer that causes my screen reader to speak.
Facebook automatically creates alt tags for images and describes them with text such as "three people outdoors with a tree." As someone who's blind I found it interesting for five minutes and have not visited Facebook again. I have been totally blind since birth, and I don't think any amount of textual description will make me interested in scrolling through a photo stream. I could see this being different if you lost your sight later in life.
OCR in it's current state is a bad idea as a primary way to get information when using a computer. My screen reader allows me to use OCR to find out what's on the screen. It works OK for specific situations such as an inaccessible installer with a couple controls. It falls down if I were to try and use OCR to read Java code.
I'm a blind developer and my job is all back-end database and REST api development. I have done UI development on internal applications where function mattered more then looks. It's pretty easy to create basic UI's using HTML since everything is in code. Specifically I used Grails to generate UI scaffolding as a starting point that I was then able to modify. Once I got everything working another developer spent a day adding some CSS and fixing a few rough edges.
I'm a totally blind developer and have never gotten Linux to work very well. What distro do you use? I'm also curious if you run Linux in VM's with speach? I think part of my problem may be bad audio support in Virtualbox and I may have better luck with VMware.
I use Windows 10 every day with Jaws and Windows subsystem for Linux. WSL has noticeably increased my productivity compared to Cygwin do to the larger volume of software that runs in it and no longer having the need to spend time compiling tools from source.
I find NVDA to be a pretty good screen reader and you could probably use it full time. I've used Jaws for over 20 years though so it's worth paying the $100 a year to keep up to date rather then spending the time getting used to a new screen reader. It's also nice to have a company you can call for support and talk to someone instantly when your entire ability to do your job depends on screen reading software.