CAMLORN

7 ms·

1.
by CAMLORN 7y ago
Strict or no, Google actually fails at accessibility a lot. The basically broken unergonomic keybindings in docs for starters and the entire fiasco that is Android come to mind immediately. For a really "fun" fail that's rec
2.
by CAMLORN 7y ago
Sadly the screen readers do actually do a not-so-good job of this, but I think that may in practice be more a function of poor UI for switching indicators on and off. You get 80 cells at most, and even the most conservatively unambiguous a
3.
by CAMLORN 7y ago
I own a braille display and use the 93-volume trigonometry textbook from high school and the logic around it with respect to making sure the right chapter was in the classroom with me as an analogy when explaining CPU caches to people. In
4.
by CAMLORN 7y ago
Sadly no. Making charts accessible is an unsolved problem. There have been some efforts for accessible graphing calculators that work more or less, but it's not trivial to make a generic one-size-fits-all solution. For Sheets, the un
5.
by CAMLORN 7y ago
From my perspective there is very little difference. The interface I get out of Firefox is exposed as if it were a text-based browser for lack of a better analogy (it's not quite the same, but the differences are subtle and not obviou
6.
by CAMLORN 7y ago
Firefox and Chrome both have mature accessibility API implementations at this point. Edge is also at least okay. Internet Explorer has worked forever. You then couple those with a screen reader--most commonly Jaws or NVDA--and you get so
7.
by CAMLORN 7y ago
I appreciate your assistance but I can check spelling; a simple "Did you know that it's Lynx" would have sufficed. Good to know there's two text-based browsers. I didn't, but I and everyone else I know will go on
8.
by CAMLORN 7y ago
Google themselves are your example. Leaving aside some horrible accessibility keybindings in Docs, both Docs and Sheets are basically fully accessible. in fact Sheets is the best spreadsheet program I've used. It's not as power
9.
by CAMLORN 7y ago
I see this like supporting DOS in 2019 or somesuch. There might be an esoteric reason to do so but when 99% of the userbase has left and the old thing can't support new technologies, saying that we need to support the old thing forever
10.
by CAMLORN 7y ago
I am blind. I know or have known at least 20 other blind people sufficiently to know what their browsers are. None of them used Links. One of them used Edbrowse. The rest (including myself) are Firefox, Chrome, or Safari. I have at least
11.
by CAMLORN 7y ago
In the insert case call the function InsertWithAllocqation, and also provide an Insert variant that doesn't allocate but can fail. In the reversing case, call the function ReverseInPlace, then require the user to make a copy either be
12.
by CAMLORN 7y ago
Screen readers have a lot of commands for reading different sized chunks of content. In general there's probably around 50 keystrokes I use on a daily basis. It's not as straightforward as reading from top to bottom, though it c
13.
by CAMLORN 7y ago
They're harsh. But you get used to it in about a week. Espeak is an atypically bad example, which is why NVDA experimented with a fork (and maybe one day the NVDA work will make it upstream). part of what allows them to stay intellig
14.
by CAMLORN 7y ago
I haven't specifically tried different types of audiobooks to see if there's some preferred category. With movies I don't bother with them unless they have descriptive audio, at which point you've got music, sound effect
15.
by CAMLORN 7y ago
But when the in-group is defined as "is blind"?? I'm not just talking about programmers in this context, or any other cross-section wherein there's some sort of shared vocabulary and context other than the disability it
16.
by CAMLORN 7y ago
You can pass Espeak recordings around legally. It's just GPL. The license applies to the software, not the content produced via it. I will attempt to remember and find the time to take my demo recording of this on Rust compiler sourc
17.
by CAMLORN 7y ago
Other people in realtime aren't...I guess the best way I have to put it is informationally sparse. There's a lot going on beside what's being said in conversation. Synths don't imply things for example; in a context wi
18.
by CAMLORN 7y ago
And as a followup to that--because really this is the weird part--some circles of blind people (including mine) talk faster between ourselves. That's not common, but it happens. I still sometimes have to remember that other people ca
19.
by CAMLORN 7y ago
I'm the blind dev who refactored a huge chunk of the Rust compiler [0]. I'm at roughly 800 words a minute with a synth, with the proven ability to top out at 1219. 800 or so is the norm among programmers. In order to get it we
20.
by CAMLORN 7y ago
Location: Seattle Remote: Strongly preferred Willing to relocate: Not right now Programming languages: Python, Rust, C++, some JavaScript and Go Technologies: Most of Google Cloud platform, Kubernetes, SQL (Postgres, BigQuery), RabbitMQ, Pg
21.
by CAMLORN 7y ago
Location: Seattle Remote: Strongly preferred Willing to relocate: Not right now Programming languages: Python, Rust, C++, some JavaScript and Go Technologies: Most of Google Cloud platform, Kubernetes, SQL (Postgres, BigQuery), RabbitMQ, Pg
22.
by CAMLORN 9y ago
I'd agree with you here, but Rust is powerful enough to abstract serialization behind a macro. You'd probably be using something like Serde instead of writing your own decoder. The macro just adds repr(C) for you and does it, if
23.
by CAMLORN 9y ago
I haven't looked at libstd, so I can't comment to that specifically. But we don't reorder two-field structs. Rustc special cases them in a lot of places to do things that I will not even pretend to understand, and not reorde
24.
by CAMLORN 9y ago
This is admittedly a bit ranty, but it hits some important points that a lot of sighted people miss, so I'm posting it anyway. People have started going down the blind programming language road; look up Quorum. What's not obvious
25.
by CAMLORN 9y ago
Depends on the standard. there are parts of pep8 that are nearly impossible for me to follow, namely the bits about indenting complex expressions that span multiple lines. I mostly don't care about it, save for indenting by fixed amo
26.
by CAMLORN 9y ago
In fairness, the compiler is actually simpler now. Perhaps not as simple as if fields were always in order, but we only determine what type layouts should be in one place instead of two now, and 99% of what you have to do in the rest of it
27.
by CAMLORN 9y ago
The first time I think I saw the idea was [0], but I don't know if this is the post that got linked in the discussion threads. Rust didn't have fuel at all until after my changes, and I don't think it's necessary to use
28.
by CAMLORN 9y ago
There are two specific cases here where the layout is not obvious. The first is the null-pointer optimization (I think this is the official name but I swear I question myself every time I mention it), in which we use knowledge that an inner
29.
by CAMLORN 9y ago
Didn't know about this. I'll have to see if I can stay involved with some sort of project--the problem is that, currently, the one I was doing is...well...done. I don't want to leave the Rust ecosystem, and I'd kill to
30.
by CAMLORN 9y ago
Yes, it will do exactly that.

More ›