Assumptions
I believe products owners, product manager or any recruiter looking for UX/UI design role with Front-end skill could check it out going through a website built myself. If at some point this is not clear I would go for User Scenario, User testing, user experience map until I find what ever problem-solving.
Code Quality
A code quality testing and solved was performed in order o prevent bugs and display errors on the different current browsers. Ensure a code quality with linters in all the pages and avoid misspellings, ambivalente syntax in addition to easy readable code and having consistent code.
Cross browsers
The cross-browser test was proceed throughout the main two operating systems on the marked. Whether online service exits, the chosen procedure was by manual testing because it is a personal project. Despite I have found some issues on Internet Explorer browser, I decided not to take care of it since it is used by a very little amount of users nowadays. Due to the lack of time and resources on the process of the project I decided not to test on tablet and other different devices.
Following Accessibility Guidelines WCAG 2.0
Accessibility is a priority in this process. It can be an arduous task as It would mean to exclude some ideas regarding on the initial design. To make sure the site pass the minimum accessibility, the website has been designed and checked under the minimum requerements of WCAG 2.0.
Goal & Success criteria
User criteria & Participants
Scenarios & Open questions
The scenarios have been created to cover goals and make sure success criteria would be evaluated correctly.
The next open questions were where the a great list of interactions for improvements were found.
- How was the orientation within the website for you?
- Was there something you really liked or really disliked?
- Do you feel like there’s something missing?
- Suggestions
Analysing
The three factors; frequency, impact and persistence has been used to measure the severity from 0 to 4 rating scale according to Nielsen Norman group. From goals and success criteria it is safe to say the usability test didn´t bring that much requirements for iterations. Although that doesn´t mean there wasn´t room for improvements, actually there was. From open questions there was found a lot of work for iteractions, some of them were implemented, others were filed for near future.
