Admin Details

Maggie Deng, Founder of Yellow Fellows

Testing Document

Our testing document asks a series of questions in 3 sections. The first section is general information: name, age, device, and browser. The second section walks the tester through two scenarios. The first asks the tester to locate a staff member. The second asks the tester to find some fashion tips and features. This section also asks for feedback on accomplishing these particular tasks. The third and last section asks for general feedback on the site as a whole.

Tester Audience

We shared the testing form via our facebook accounts since the intended audience is quite wide. There was a description posted with the post that explained the intent of the website as a platform for APIA, Asian Pacific Islander American, content and discussion of issues pertaining to the community. 94.4% of participants were from ages of 15-19. The last 5.6% came from the 20-29 category. Because of scheduling conflicts with potential live testers, we were not able to get live testing results.

Testing Platforms

Our testers used Apple laptops/desktops, Windows laptops/desktops, mobile phones, or other platforms (besides tablets, which none of our testers used.) The majority of testers used laptops/desktops, taking up 77.8% of the testers, 38.9% using Apple laptops/desktops and anoter 38.9% using Windows laptops/ desktops. 16.7% of testers used mobile devices. 5.6% used another device.
As for browsers, a majority of our testers,83.3%, used Google Chrome, however our whole participant pool used Chrome, Firefox, or Safari. Firefox testers made up 11.1% of the testers and Safari testers made up 5.6%.

Feedback Summary

Design: We had a few notes about improving general design of the site. One of the main concern was the white on yellow was a bit hard to read for the dates and other design elements.

Navigation: Not many testers mentioned any issues here, one person said: It was a bit confusing distinguishing the feature articles from the regular category ones, but only for a second. Pretty straightforward afterwards. which we will definitely keep in mind. Someone else mentioned that when they clicked on each tab that was offered and looked through the whole website. I imagine that itll be a little different in the future when there are more posts but I think it was really well organized, which is something else Havannah will consider when she works on the website more over summer.

Content: The content of the site was provided to us, so we don't personally find this feedback entirely constructive towards us. Most people simply wanted to see more content; one piece of feedback from our presentation mentioned that they personally did not like the name of the site, but again that is a piece of feedback for Maggie more than us as the web developers.

Usability: This is probably the most commented on topic. Many people had issues with the image sizes on smaller screens, probably because these images had fixed dimensions. Additionally, a few people mentioned that the staff and about pages should be on separate drop down tabs. The homepage's purpose was commented on the most, with the most direct comment saying I don't know what's going on on the home page. We will probably talk to Maggie about what would be a better use of the homepage to display the content.

Response

The response to feedback will be organized in the same way as the the feedback itself. The titled sections will refer to their respective feedback counterparts in the previous section.

Design: We definitely agree that our design could be more appealing. This simply means having more time to make more mock ups and seeing which ones we like the most. The white on yellow is an easy fix, we just need to replace the yellow with black.

Navigation: We can make some sort of design distinction between features and regular articles using perhaps a different colored title or something more distinguishing.

Content: We will probably mention to Maggie that her idea was good and her and her team should put out more content. Havannah will mention the issue people found with the name as well.

Usability: Instead of using fixed dimensions for the thumbnails, we could use percentages, like we did for the divs and other non-image elements. Adding in a separate page for the staff and about pages would be a good idea, and adding in two separate tabs to the about drop down menu. Like mentioned before, as for the homepage, we have to talk to Maggie about what she would like to do about that.

Self Reflection

This project felt like a wild ride. Neither of us have really worked in web development before and to understand how difficult it was to make these kinds of interfaces that we deal with every day was definitely an interesting experience (for lack of a better word.) Havannah personally wishes she had more time to work on this project before she presented (though she will be working on Yellow Fellows in the summer, so she still has an opportunity to improve on things she and the web development team want to work on.)
Obviously, both of us learned a lot about CSS/HTML/Javascript, but we also learned a lot about web accessibillity and how web development is more than making a pretty website. The platform has to work on multiple devices and be accessible to all people (regardless of ability.)
Furthermore, this project helped us realize the capabilities of CSS/HTML/Javascript. In class, we learned the languages but to apply to our project allowed us to really understand how powerful and creative coding can be.