CWDO Inclusive Testing Project – General Planning

note: This is a plain paste from the google docs planning document from the event:

Random Hacks of Kindness

CWDO Hackathon:

Involving PWD in Online Development

Inclusive Testing

Inclusive by design, accessible by default

For more information, see:

Jeffrey Stark

[email protected]

Inclusive Design Research Centre

idrc.ocadu.ca

-----

CWDO Hackathon: Involving PWD in Online Development

MAIN TASKS / WORKING GROUPS

Process / project management [Jeffrey, Daphne, Angelo, Martyna]

  1. For now collect our information in Google docs, maybe later in Github

  2. Develop lists of what needs to be done

  3. Develop draft processes for company/organizations, users, accessibility users

  4. Develop projected phases

Developing project content [Jeffrey, Daphne, Angelo, Martyna]

A. Developing content for forms: (initially google doc, maybe github later)

  1. Collect info from organizations that require accessibility user testing

  2. Collect info from users that can do testing

  3. Collect info from accessibility ‘experts’ that organizations can hire to help make their content meet accessibility standards

  4. Test/validate users’ ability to do certain kinds of ability testing

B. Developing other content for the site

  1. About

  2. Introductory or instructional text for each section of site

  3. Contact us

C.   Developing marketing content

  1. Press release

  2. Marketing introduction to project/service (text, possibly also video)

    1. Post/send for organizations serving people with disabilities

    2. Post/send for organizations seeking user accessibility testing

    3. We Need Your Expertise and Help to break down barriers and help build virtual wheelchair ramps into the sites, services and systems of the future so everyone regardless of ability can get in through the door.

Platform and Module Set-up and testing [Michael, Larry, Ying, Eric, Dragan]

  1. Research and develop accessible Drupal theme and modules that can achieve this kind of profiling

    1. Dragan suggested a module

  2. Get server running. Brett gets instance running?

  3. How to interface UI with Drupal

  4. How to test users’ abilities to do accessibility testing?

    1. How does

Project members 2017-03-25

  1. Angelo DeMarsico

  2. Eric Mulligan

  3. Larry Burge

  4. Martyna Marjanska

  5. Jeffery Stark

  6. Cheng Giaoying

  7. Michael Milette

  8. Daphne Uras

  9. Dragan Nevjestic

Projected Phases

  1. PHASE ONE: 

    1. GOALS: Build English proof of concept for testing with computers, demonstrate demand, get basic workflow in place so can apply for funds for further development

    2. Build prototype (using processes A and B) that allows

      1. Testers to register

      2. Companies to find testers   

      3. Testers to upload videos of their tests (records both the audio of the speaker and the video of the screen).

      4. Provide some resources for building accessible web or mobile products

  2. PHASE TWO: 

    1. GOALS: Using external funding (?), build larger scale and more automated version

    2. Build version that can handle more testers, more company requests

    3. Outsource payment system?

    4. Make site bilingual

    5. Expand resources for building accessible web or mobile and other products

    6. Provide ability for WCAG experts to register in directory, so companies can find help (phase 2 or 3)

  3. PHASE THREE

    1. GOALS: Sustainable model that incorporates lessons learned from phase two, and expands testing environments

    2. Build in extra features, eg coordinating companies with testers who are willing/able to work onsite

    3. Permit testers to upload videos of their tests of mobile environments as well as computer environments: videos will also capture taps, swipes, and gestures

    4. Further expand resources for building accessible web or mobile products if necessary

    5. Provide ability for WCAG experts to register in directory, so companies can find help (phase 2 or 3)

       

  4. PHASE FOUR (dream options)

    1.  

 

User Process Maps 

Process A: Tester Signup experience process map

Process A: Tester Signup experience process map

  1. PHASE ONE

    1. Register their testing abilities on site

      1. Create account, email verification

      2. Review technical requirements

      3. Sign confidentiality agreement

      4. Fill in profile (type of disability, technology, adaptive technology)

      5. Do a sample test or multiple tests (tests are vetted by CWDO)

Process B: Company/organization experience process map

Process B: Company/organization experience process map

 

  1. PHASE ONE

    1. Company/organization registers

    2. Company/organization posts a project and their requirements

    3. For security reasons, project gets sent to CWDO administrator/group for approval/search

    4. CWDO administrator/group finds appropriate testers

    5. CWDO sends project description to potential testers

    6. Testers can review material and indicate interest/availability to CWDO

    7. CWDO sends user info to company

    8. Company sends users content for testing

    9. Testers upload their results (and notifies CWDO)

    10. CWDO pays tester

       

  2. PHASE TWO (after demonstrated success, something that can apply for funding)

    1. System gets more automated to not require so much human handling and to let payment happen through site

Process C: WCAG Expert Signup experience process map

Process C: WCAG Expert Signup experience process map

 

Proposed Website Structure 

This is currently based on Usertesting.com’s structure, and should be reviewed and revised as necessary.

  1. Home:

    • Inclusive Testing can help your company improve the usability, accessibility, and searchability of your web products. We match companies with people with disabilities, who will record 10-15 minute videos detailing their usability test of your website. For a low cost you can ensure that people with a variety of disabilities as well as search engines can find, navigate and use your content.

  2. Log in: Allows registered company to enter the system

  3. Company sign up: Allows a company to register (see Proposed Form Fields)

  4. Get paid to test: Sign up form to become a tester. Two types of testers. People with disability and WCAG testers. (see Proposed Form Fields)

  5. How it works:

    • Companies submit projects that CWDO disseminates to testers, who record their tests using screen recording software (length of the videos range between 10 and 15 minutes, depending on how many tasks the user is asked to do. Pro plans offers videos as long as an hour.)

    • Who uses us: Overview, Designers, Product Managers, marketers, Agencies, mobile Game Developers

    • Videos (sample, explanations)

    • FAQ

  6. Resources: Overview, case studies, webinars, ebooks, white papers, tips and checklist, industry reports, our blog

  7. About us: Overview, Executive team, in the news, contact us

  8. Pricing: Request pricing details (call or email)

  9. Help: Contact us form, FAQ

Proposed Devices Requirements:

These requirements are subject to revision; they will depend on the video testing tool.

Either a PC or Mac that meets these requirements:

For mobile tests, your device will need to meet these requirements:

  1. Microphone, example

  2. Screen recorder, administrator’s access is required to install the software on the computer. Some free choices are listed here: http://download.cnet.com/s/video-record-capture/windows/?tag=bc. Maybe this one which is free could be used for the purpose of this exercise: http://download.cnet.com/Apowersoft-Free-Screen-Recorder/3000-13633_4-75959899.html. It may only work for windows OS: Windows XP/2003/Vista/7/8/10

  3. PayPal account, to get paid.

Proposed Form Fields

Company Sign Up Form

Choose type of organization:

  1. Individual

  2. Non-profit/charitable

  3. Enterprise

Registration form:

Registration form for disability user tester

Registration form for WCAG tester

 

Accessibility Resources for site

 

Random Hacks of Kindness

CWDO Hackathon:

Inclusive Testing

Inclusive by design, accessible by default

Jeffrey Stark

Inclusive Design Research Centre

idrc.ocadu.ca

Questions?

Thank you to our RHoK team this weekend

Posted 366 weeks ago
#jeffreystark  #tech  
Share