tvararu

+1, or with cognitive impairments like ADHD, learning disorders...

Accessible design helps everyone.

> Receive salary > pay bills, buy food etc. > all the rest, transfer to a investment account

One thing that has worked for me is to “pay myself first.” [0]

If £4000 comes in and your monthly outgoings are around £2000, invest the remaining £2000 immediately. The main benefit this gets me is that it forces me to budget better and come up with other streams of income (usually eBaying stuff) in case I come up short.

[0] https://www.investopedia.com/terms/p/payyourselffirst.asp

Yes you can. One side quest with a companion expires in 24 hours upon receiving. If you don’t complete it, you can’t access that ending.

As a counter-point, my UK ISP uses Cloudflare 1.1.1.1 last I checked.

I’d argue pirating is a justified measure in this situation.

“Effective delegation requires giving up some control of exactly how the work is to be executed.”

One of the many reasons why I prefer working as a contractor where I have to provide my own gear. Everything I run is by my own choice.

Seriously considering trading my maxed out 2018 13" for this, but in the end probably not going to do it.

The VW E-Golf (since 2017) is exactly that, but doesn't have the best range.

I have both. If the AirPods Pro didn't make my inner ear sore after wearing for 3+ hours, I would sell my Sony's immediately. I might sell them anyway. They are inferior in everything apart from comfort.

> because even with a $200 per day flight, I would still retire a decade earlier than taking a local job

You'd get so many air miles too!

I refer often to this poster from the Microsoft Inclusive Design Toolkit:

https://camo.githubusercontent.com/b25f31e420c078114a2abee62...

More here: https://github.com/alphagov/accessibility-community-notes-an...

"No Stress Booking - Chrome Web Store

Hides all the red alerts and stressful messages from your favourite booking site"

https://www.chrome.google.com/webstore/detail/no-stress-book...

> Although gyms are different, likely because if you are healthy enough to hit the gym you are healthy enough to go home.

St. Thomas' in London (UK) has a gym for patients that need to do phisyotherapy exercises. I don't recall treadmills or squat racks, but they had medicine balls, free weights, instructors, music, and so on.

45 if you remove the trailing }.

This is principle 10 in the UK Government design principles. https://www.gov.uk/guidance/government-design-principles#mak...

I was surprised to learn that many commercial HDR 4K TVs have a 50Hz real refresh rate. Sub 60Hz screens are bountiful and common.

It is not.

Though, it’s interesting to note that once when I took a date picker component and attempted to morph it into a full-blown MacOS calendar, with calendar appointments that slot into different time slots and don’t overlap, I found that that is an NP-Hard bin packing problem.

Currently saving up a retirement nest egg to work on video games full time. Your advice matches with my own research.

My thinking is that commonly activity on master halts for months/years because a v.NEXT is being worked on, so it's worth checking if that's the case and whether it's worth waiting for the new version or adopting the alpha/beta.

The list seems to be overly reliant on GitHub stars as the main metric for measuring if a library is worth considering or not.

I wrote a checklist with some questions that can help you find potential issues with third party packages:

- [ ] Is the package licensed in a way you can use?

- [ ] Is the package's latest published version free of known security vulnerabilities? (can check with https://snyk.io/vuln/npm:moment)

- [ ] Is the package tested? (there need to be at least some unit tests)

- [ ] Is the package lightweight? (can check with https://bundlephobia.com/, this should be considered alongside the size of the problem being solved)

- [ ] Is the package dependant on no other packages? (0 dependencies = less to worry about)

- [ ] Is the package maintained? (activity in the last year, don't forget to check branches other than master)

- [ ] Is the package popular and widely used? (depended on by lots of other projects, number of stars on GitHub)

- [ ] Is the package well structured and easy to understand? (could you contribute and make changes to it quickly? you may have to!)

Once you do decide to adopt something, it's a good pattern to only import it in one place (like an internal `helper` library) and to reference that in every part of the codebase where it's needed. This is in case you decide to replace it in the future, so you only have to change one place.

That would be a lot easier. I've assumed that NVDA would be the easiest to plug into for obvious reasons but have not looked into it specifically.

I used JAWS and Windows IE11 as a specific example because that's a popular combination with screen reader users. If something works well in NVDA and FireFox on Linux it does not follow that it will work in other combinations, at least in my own testing with things I've worked on in the past. Though targeting the low hanging fruit to begin with is how I'd also start if I was building something for this in earnest, ideally I'd want to automate testing with all the popular combinations that I expect users to have.

The only way I'm aware of today is to learn to use assistive technologies and use them on the right combinations of browser/OS/version. These are recommendations for common combinations. [0]

I've given the CI deal a good amount of thought. You'd have to go through the trouble of:

- Provisioning a Windows VM with specific versions of browsers (e.g. IE11) and AT (e.g. JAWS 17, the versions differ quite significantly)

- Writing an automation suite that is capable of controlling the browser and AT (Selenium probably does fine), but crucially interpreting the feedback from the assistive tool to check for correctness. This is tremendously hard. Either using some debugging APIs if any exist in the various assistive tools, or reading memory / reverse engineering using IDA, or capturing the audio output to the sound card and running it through speech recognition to figure out if what was said by the screen reader is what you'd expect. With something like Dragon Dictate you'd have to figure out how to trigger voice commands.

- Expose the VM using an API that you can call from your test suite

- `expect(jawsOutput).toBe("Type in two or more characters for results.")`

That's a potentially tremendously profitable SaaS offering (to the right companies), if someone can build it.

[0]: https://accessibility.blog.gov.uk/2016/11/01/results-of-the-...

Not sure about Apple, but on a hackintosh you can install Nvidia Geforce drivers that allow you to turn on GSync.

These kind of high-level overviews of prototype implementations are very useful, thank you for sharing.

Airport routers are not vulnerable to this exploit.

macOS and iOS computers have been issued patches to mitigate the issue on vulnerable networks.

Source: https://m.imore.com/krack-wpa2-wi-fi-exploit-already-fixed-i...

Tacking on accessibility at the end is very difficult (most of the time it's quicker to rewrite). By not considering it from the beginning it means these components will never be usable by people with access needs.

Also it is possible to call out a critical oversight in the design of a product while not shaming them for releasing it.

Interesting, when I used to play League of Legends I was sure that the crit chance wasn't random at all. In my experience, at 25% crit precisely every 4th strike would crit, at 50% precisely half, and at 75% every 4th strike I'd do wouldn't be a crit. It seemed fully deterministic which I thought was an interesting way to make the mechanic more skillful as you could count in your head when you'll get a damage spike; you could fire some useless shots on minions then dive in for a trade on your enemy laner knowing that you'd win because of your guaranteed crit.

John Romero learned this in his early days at ID Software: it's crucial that you can still boot the game even when things are missing, but make them very apparent.

Source: somewhere in this video https://www.youtube.com/watch?v=E2MIpi8pIvY

You might be interested in the results of the 2016 GOV.UK assistive technology survey. [0]

iOS VoiceOver ranked as one of the 3 most popular screen readers, second to JAWS for Windows [1] (closed source, paid) and above NVDA for Windows [2] (closed source, free, donations encouraged).

ChromeVox [3] is AFAICT the only free and open source screen reader that came up in the survey, at 1%.

- [0] https://accessibility.blog.gov.uk/2016/11/01/results-of-the-...

- [1] https://www.nvaccess.org

- [2] http://www.freedomscientific.com/Products/Blindness/JAWS

- [3] http://www.chromevox.com