| A | B | C | D | E | F | G | |
|---|---|---|---|---|---|---|---|
1 | ID | User journey | Description, test objective | Assessment | Observation comments | Quotes, recordings | Blockers |
2 | 1 | J1 | Login, dashboard, guided tour, find navigation | Completed independently | - Login: went well, - Navigation: quickly find main menu, and navigate via headings on dashboard. Usually skip directly to main navigation and main content, ignores the links and toolbar at the top. - Dashboard: React to ending "J" then "X" keyboard shortcuts. Not keen on taking a guided tour, want to explore by themself. | Highligts connected to user journey. | |
3 | 2 | J2 | Create new article, add category, insert media | Completed with friction | - Navigation: Uses the main menu for the new article button. - Rich text editor: Reacts negatively to that there is a lot of elements to choose from directly after the editor, and also does not like the widget of rich area. I would rather do adjustments to a plain text field with markdown. Could not use the rich text widget with NVDA, could not reach the controls. Only the text field. - Toggle editor: Found that they could get a normal plain text field, was happy about that. - Image select: Managed to upload image, comments on that it is unclear that it is selected or not (on the pre uploaded images). Adds alt-text and other texts. - Save and close: Not clear if the page will be published or not, even if the person had added the article as published and in the category blog. | "Ah so there is a sort of widget here, rich text, I hate that! I want clean fields with less clutter". "I get that people want to click on features to adjust content, such as heading levels, but I want generally a plain text area that I can put markdown in". Toggle edifor, presses. "Yes this is what I was looking for! Then I dont need to use that terrible rich text area widget". Soundclip of user describing the issues regarding editor and toggle editor. | Editor (rich text widget), Image selector dialogue. |
4 | 3 | J3 | Filter articles, select multiple elements, action change status | Completed with friction | - Table: works well, the user feels confident when moving around in the table and exploring al the rows with articles. - Filter: It didnt say that filter opens but the person is used to that and found them anyway, used to that type of inaccessibility. - Comboboxes in filter: When arrowing down change occur directly and page reloads, need to go all the way back. Enoying. Says that the event onchange is an issue. - Select multiple articles: Checks two articles. Seems difficult to find action button, wanders throuh lots of elements such as filters and seach. Expresses that they cant find it. Its to high up and lack a heading. | "I can't find the button for actions, its so many items before it and a lot of clutter, I want it to come a bit closer" Soundclip of user describing the issue to find actions. | Action button. |
5 | 4 | J4 | Create menu item, type modal | Completed with friction | - Create menu item: Have difficulties finding the menu item type. Seem to find the text field, thinks its strange that its read only text field. After a while finds select button and tries it. - Dialogue: In the dialoge selects item easily when finding dialogue. Even if this person managed to solve it, the person got frustrated and thinks its way to complex, could be two comboboxes instead of this solution. | "Its an empty read only text-field", "Its so unnecessarily complex, use a plain combobox!". | Text field and select button to choose menu item type. |
6 | 5 | J6 | Find and change global config.settings | Completed independently | - Finding global configuration: Goes to settings on dashboard and fint it.This was easy to find. Did not hear that global configurations was selected, but the user noted that it said "visited" on the link for that menu option in the settings list, so they figured that it was the current page. - Fiding tabs, check permissions: Found the tab and roles for permissons, as an example of settings. Understood the different options for, but found the list of option for each role a bit strange, contentwise. | - | - |
7 | 6 | J5 | Frontend login, edit buttons, find login fields and test | Completed independently | - Login: went well. No issues. - Edit: Find edits. Goes to article and edit mode for that. Thinks it works good. Especially that you also there can toggle editor type. | - | - |