Digital Prototype: Off-class tests by Rena

Here are some records for the Digital Prototype test session I ran in my friend's house last Sunday. Both of the tester are bachelor students major in IT related fields with some fundamental HTML and CSS knowledge.

Number of users: 2

Task 1: Login stress test and workflow test

• Didn't realise he had to sign up first as the sign up button is not clear enough
• In the [member area], found that there is not [back to home] link after login
• Would prefer a automatic drop down list of [About]

Task 2: Working panel and accessing help

Did you read the instructions on the home page?

• yes, and it looks interesting
• yes 

Would you expect further instructions at this point?

• No, it's quite clear x 2

Do you know what to do on this page?

• No, because I don't know I should sign up first
• Yes, to choose category after sign in 

What would make the errors easier to read?

• It's pretty obvious
• maybe present the Errors messages in red colour

If you didn't understand an error, where would you look for help?

• 1.Help Button -> Google -> w3school
• Google is our good friend:)

For each web page, there are multiple modules (e.g. Cricket Australia has 8 modules) that all pertain to the one page.  When you add CSS to the CSS editor and save, would you expect to see your saved CSS when you progress to the next module (i.e. Module 1 to Module 2)?

• Yes
• Yes, that would look more organised

Task 3: Use the working panel

• When click [save], would be better if there is a message saying "processing", otherwise I will click the button several times, and feels like its not working
• As it requires some time to process the validate function, it would be better to show up a "please wait" message after clicking [validate]

Feedback response: update

Here is the amalgamated feedback we have received to date (Part A presentation, paper prototype, Part B presentation, Digital prototype) and how we have or will incorporate it into our design.

Done! Will do (but haven't yet) Might do (if there's time) update

Feedback	When	Responses
Levels/Gamification
Add gamification including level up, easy/hard mode, or points for completion. Hard mode could include editing without validating first (see if you can find the errors yourself).	Part A /Digital prototype	Easy/hard mode has been added.   Easy/hard has been changed to modules.  Easy levels have smaller modules, code is broken up into chunks
Content
Add in option for users to find out more about their content.  Could be through linking back to trove to search topic.	Part A	Will add if there's time. Tangential learning is a sub-goal of our product. Users will already be learning through the content provided within the websites.
Have multi-user option (like google drive) or set up a study group to work on problem together to solve collaboratively.	Part A	Context of use is for classrooms or extension work.  The style of problem is more suited to individual learning.  We will add a commenting feature for other user’s projects if there is time. Likely we will not have time to implement this feature.
Help
How do users get help?  Could add chat panel or discussion board. Make help more obvious on editor page	Part A /Digital prototype	Help section has been added.   Help similar to codeacademy where they link to relevant stack overflow discussions. Will include glossary page with information from W3C on tags and tag changes across versions. Will move help button to errors panel.   Will make help a pop-out if time.
Audience
Concerns that initial audience of grade 7 & 8 students is too young.	Part A	Did further research that is discussed in previous blog post. Audience has been modified Web historians is for people: who are familiar with HTML and CSS but still beginners might know what validation is but don't necessarily understand it's importance or how/when it can be used would suit grade 10 at school but other beginners in the general public and university would suit classroom use or as extension work for school students
Features
Add in extra level of complexity with option of re-designing pages, not just cleaning up old tags and layout.  HTML5 validators don’t check for aesthetics.	Part A	Will add redesign feature if there is time but is not part of our core concept of correcting archived content to current web standards. Likely we will not have time to implement this feature.
Add in a gallery of finished projects with a voting system	Part A	Gallery of finished projects added (for all users to see). Will add in voting if we have time to implement redesigning feature as well otherwise voting doesn't’ serve much purpose. Likely we will not have time to implement working gallery feature.
Separate profile setting and instruction page.	Paper prototype	Done.
Logo position and style not consistent across all page.	Paper prototype	Done, logo and header now consistent.
Landing/Home Page
Reduce the amount of text to explain concept	Paper prototype	Added an infographic/flowchart to explain concept and how you use site.
It should be more obvious whether you are singing up or login (make buttons more distinct from each other).	Paper prototype	Done with colours/CSS styling
Add explanation for difference between easy and hard mode.	Paper prototype	Done on infographic.
Add in extra explanations/instructions for use.	Paper prototype	Will add more instructions on 'getting started page.
Make categories more obvious and easier to read.	Paper prototype	Done with CSS Styling. Have increased font size and made categories more obvious through use of colour.
Add in more categories	Paper prototype	If there is time. Likely we will not have time to implement this feature.
Editing page
Make it obvious what and how users are doing on this page. Make errors easier to read	Paper prototype /Digital prototype	Will display number of errors left to solve. Have changed layout of page to reflect order of work (e.g. errors 1st, editor 2nd, "Save" and "Publish" 3rd) Add small tutorial/instructions on how panels work/what you do on this page. Will group errors together, add space between each error, numbering if possible.
Make sure "Publish" button saves as well	Paper prototype	Will be removing Publish button based on other feedback.  Users will get a 'winning' screen when all errors are solved that will allow them to publish.
Make navigation consistent across all pages (currently different on this page)	Paper prototype	Navigation/header has been updated on all pages to be the same.
Make layout of editor customisable.	Paper prototype	Will do if there's time.  This is high on the list of to-do features. Suggested toggle box to make windows larger or smaller and continue to work in them or a pop-out system.
(relates to previous feedback) Make code editing window larger. (breaking up the errors into segments would also help with smaller code blocks).	Part B	We will need to look into the current capabilities for adjusting the editors size as well as users ability to resize windows. (Changes to overall page width will need to be represented across the site). ather than make panels movable, put content in tabs, either errors thin at top, 2 tabs: html editor and css side by side; viewer, OR separate html/css/viewer separate tabs and errors visible all the time
Add user name to work	Paper prototype	Has been implemented on gallery page
Let users know when they have solved errors.	Paper prototype/ Part B	Will add a 'congratulations' screen. Remove publish button and allow users to publish privately or public gallery via win screen/pop-up. Option to share success to social media if there is time.Likely we will not have time to implement this feature.
Add in a seperate box for CSS	Paper prototype/ Digital prototype	Have done (but not currently fully functional). Will make CSS save between modules.
Large amount of errors which load into the working panel. Hard to read/understand/manage (looks hard on easy level). Suggestions: order the errors by importance (must be fixed vs best practice) break  rebuild into sections; could be a good way to tie in gamification components would be a good way to work, encouraging users to encapsulate their code for each segment of a page.	Part B/ Digital prototype	Done See: Easy/hard has been changed to modules.
HTML editor text is small for some users.  Many found side scroll annoying.	Digital prototype	Let users use in-browser magnification to increase or decrease text size as needed. Have changed scroll to text wrap in editors.
Users would like ability to upload own images to working panel	Digital prototype	Will not have time to implement this feature
My Restorations
Make format similar to Gallery/Categories (i.e. tiles in a column/grid)	Paper prototype	Done
Change % progress bar to actual number of errors to make it more meaningful	Paper prototype	Done
Login
Would like log in to autofill after sign-up align font awesome icons	Paper prototype	Will do if there is time.

Digital Protoype: In class session results

Here are the result of the Digital Protoype test session we ran in our contact session this week.  We aim to conduct the same test with real users in the next week.

Number of users: 5

Task 1: Login stress test and workflow test

• Would like log in to autofill after sign-up
• align font awesome icons

Task 2: Working panel and accessing help

Did you read the instructions on the home page?

• no but prior knowledge of product x2
• yes x2

Would you expect further instructions at this point?

• as a dev, would rather play first
• small tutorial maybe?
• no
• instructions didn’t cover working panel windows, this is what each bit is, need to understand layout

Do you know what to do on this page?

• yes
• where can i type?  looks a bit scary?

What would make the errors easier to read?

• grouped together, space between each error, numbering would be good, bullet points, checkmarks
• they are fine to read
• multi-line erros, where does one error end and another start, gaps between each error, alternting line colours, wrap in container

If you didn't understand an error, where would you look for help?

• google problem, not go to internal help
• help should not be at the bottom
• help should be modal or pop-out
• difficult to see help button, add '?' help to error panel
• put help with errors
• google, stack overflow is industry standard on how to look for help

For each web page, there are multiple modules (e.g. Cricket Australia has 8 modules) that all pertain to the one page.  When you add CSS to the CSS editor and save, would you expect to see your saved CSS when you progress to the next module (i.e. Module 1 to Module 2)?

• blank, prefer to start fresh each module
• carry over if part of same website
• frustrating to start over
• would copy and paste if not automatic
• yes, definetly

Task 3: Use the working panel

• would like ability to upload own images 
• html editor text small x 2
• html editor wrap text rather than scroll x2
• rather than make panels movable, put content in tabs, either
• errors thin at top, 2 tabs: html editor and css side by side; viewer, OR
• separate html/css/viewer separate tabs and errors visible all the time

Digital Protoyping Usability session

This is the procedure we used in the digital protoyping session in class and will repeat with real users in the next week.  Sessions are run a one-on-one, in-situ interviews and usability tests.  Encourage users to talk aloud as they participate.  Remember - it is the system being tested, not the user.

Pitch the concept:

Explain concept but don't give any specific instructions on how to use site.

Web standards are important to ensure that web pages display correctly in all browsers. Learning current web standards and how to comply with them are an essential part of learning how to write HTML and CSS. As web standards change over time, they depreciate old tags and introduce new tags and new features. One of the problems with archiving old websites (e.g. Trove, Pandora, Wayback Machine) is that even as web standards change, the archived websites still use the old, out-dated HTML tags.
Web Historians provides HTML/CSS beginners with a practical, interactive web application to familiarise them with correct syntax and layout, the concept of web standards, the process of validating code against the latest standard, in context use of HTML and CSS, and basic editing.

Task 1: Login stress test and workflow test

Ask users to familiarise themselves with the home page (index.php) and when they are ready, sign up, log in, and log out.
(tests the login system, workflow of log in/out and set-ups for the next task to see if the instructions/information on the home page are read)

Task 2: Working panel and accessing help

Ask users to log in with test account (tester/tester) and navigate to the test module for Cricket Australia. (tests navigation to working panel)

Questions:

• Did you read the instructions on the home page?
• Would you expect further instructions at this point?
• Do you know what to do on this page?
• What would make the errors easier to read?
• If you didn't understand an error, where would you look for help?
• For each web page, there are multiple modules (e.g. Cricket Australia has 8 modules) that all pertain to the one page.  When you add CSS to the CSS editor and save, would you expect to see your saved CSS when you progress to the next module (i.e. Module 1 to Module 2)?

Task 3: Use the working panel

Ask users to have a play with the working panel, they can edit HTML, add CSS, and re-validate.  Ask if they have any comments or feedback.