What fresh hell is THIS now? - Patrick Lauke
[karlgroves] > Looking for a good domain name is like going on a spiritual journey
“Back in the day” domain names were so easy to find.
Tenon.io actually got its name after a month-long automated search.
Here’s what I did:
Get a plain text list of all words in the English dictionary
Purge all words > 7 characters long, because we wanted something easy to type in CLI.
Write shell script to go through the dictionary list one word at a time, append ‘.io’ to it (because all the kewl kids have .io names) and then do a WHOIS on that domain name
If the domain name is available, append it to a file of available names.
Go through the available names one by one and get rid of all gibberish like ‘abtfrw.io’ (ok that’s not a real word, but you know what I mean)
Go through all the remaining names and find one you like. This was about 7000 names.
eventually we narrowed it down to about 200 words that were at least actual, sensible, non-offensive words.
Funny thing is that although I do woodworking, Asa was the one who said “Oooooh Tenon! I like that!” and thus we had our product name and domain name.
FWIW, at least two years ago you pretty much had your pick of almost any offensive word + ‘.io’. We had a good time chuckling like junior high kids at all the offensive name possibilities.
[karlgroves] Oooooh. This looks easy to play with
https://www.npmjs.com/package/node-whois
If I get time, I’ll try to find that dictionary dump.
Basically in Node you’d use FS to read the file, then run the whois, then write the file.
The reason why it took a month, BTW, is because I didn’t want to have more than one whois request per minute, otherwise I’d get blocked for abuse
[karlgroves] So what you’d have to do to determine whether the name is available is do a string search for
"Domain [your requested domain] is available for purchase"
title
isn't read consistently across AT
title
https://www.paciellogroup.com/blog/2012/01/html5-accessibility-chops-title-attribute-use-and-abuse/ h/t @stevef
[karlgroves] FWIW the single most important important product feature is whether the product is capable of testing the rendered DOM of the page. That basically means it either exists in a browser or uses a headless browser.
http://www.karlgroves.com/2013/09/06/web-accessibility-testing-tools-who-tests-the-dom/
For the most part that limits you to Tenon, WAVE, Google Dev Tools, aXe, SortSite, Opquast, and Worldspace. (I have no data on AMP or Compliance Sheriff)
@pkra note that JAWS does not officially support chrome, but mostly works OK, in order to know where issue lies, need test file/example where it happens also JAWS/chrome version