[Accessibility-testing] 2018 goals review

[Jason McIntosh]

Hullo team,

I'd like to begin the year by reviewing and confirming this project's goals. After that, I'd like to lay out an overall schedule, and then start defining and assigning our next tasks. (I realize that we're due to carry some tasks over from last year, and do plan to review those with y'all when we get to it.)

To start, I'd ask for y'all's confirmation on some assertions about this project I feel comfortable making. These mix my reading of the committee charter, my review of this mailing list's 2016-2017 content, and my own understanding:

• The project's mission remains as stated in its committee's charter (http://iftechfoundation.org/documents/access-committee.pdf).

    • We will organize a "Testathon" event, which is understood to mean crowd-sourced testing of given software for accessibility compliance.
    
    • Testers can be anyone with user-level access to the software being tested. They needn't be assistive technology users, or even people with disabilities -- though of course we'll welcome and encourage participation from AT users & PwDs.
    
    • Generally speaking, we'll generate a big matrix that splits up every piece of software being tested into small-as-possible discrete actions that anyone with access to the software can attempt, each with pass/fail results.
    
    • We will publish documentation about the methods we used to organize said Testathon, as well as the results of the crowd-sourced tests and the subsquent conclusions of the accessibility and platform experts on the team.
    
    • This project will conclude with the release of all the above.

• This project can and should deliver its mission-declared publications by the end of calendar year 2018.

Is all the above correct?