Search
Items tagged with: xkcd
Seems like this technique could be easily bruteforced by a dictionary attack, despite being a longer number of characters.
Personally (I'm no expert) I use a password manager. Most of my passwords are 128 characters (longer than four average words) that also use special characters, numbers, upper and lower case characters. Using a physical key such as a #Yubikey seems a better way, too.
I love #XKCD, but the advice in this strip seems kinda out of date.
So apparently, even as #MathML support is improving at the browser level, in order to get #NVDA to _read_ math, you need to install #MathPlayer -- which is fine in and of itself, but it really bothers me that the MathPlayer webpage (https://info.wiris.com/mathplayer-info) says both "Accessibility for web environments using MathPlayer is limited to obsolete browsers such as Internet Explorer 8" and (in bold) "We are not actively developing MathPlayer."
It seems really odd for such a necessary tool to have such prominent warnings (but then, of course, there's an #XKCD for everything: https://xkcd.com/2347/). And nearly every instructional page I found while looking for information on MathPlayer references using it in Internet Explorer, which is now officially dead (and is actually being remotely disabled on people's machines, which seems rather draconian).
On the bright side, once MathPlayer is installed, NVDA seems to be able to read (properly MathML coded) math just fine, even in Chrome, which the MathJax documentation says doesn't work; probably due to recent MathML support improvements in Chrome.
Accessibility in general I'm really enjoying learning more about. STEM accessibility is giving me headaches.
