I can think of only one tool that will test, score and identify accessibility issues, as well as track progression/regression over time. A testing tool provided by User1st. uTester
That said, automated testing can test anywhere from 30-40% of WCAG, leaving the rest to be found by a manual review. If you are not familiar with JAWS, NVDA, VoiceOver or TalkBack then a large portion of WCAG on your site(s) will go un-tested.
I know that this was originally posted as a write-up by the New York Times, but I figured it would be nice to have a look at the actual paper. This goes in-depth on the various approaches taken, which may be of more interest to some people here.
My understanding is that with PICO-8 you can export to HTML5. If this is the case, (I haven't used this myself.. Yet.) why would you need direct support for mobile and Pi's? Couldn't you just change the dimensions of the app to fit mobile devices, and take advantage of the HTML5 support while on a Pi?
Hmm.. seems interesting. Could this potentially be a more easily understood and adoptable method of encryption? Although, I am not sure how secure it would be to use accounts from twitter or facebook, as they contain personally identifiable information.