ABCDEFG
1
IDUser journeyDescription, test objectiveAssessmentObservation commentsQuotes, recordingsBlockers
2
1J1Login, dashboard, guided tour, find navigationCompleted independently- Login: Quick and easy to input and sign in
- Dashboard and navigation: Explored quickly and efficently all options on toolbar, main navigation and dashboard until the person had a good feel for the contents. Similar to other CMSes. The person uses headings to move from "Home dashboard" and found headings on main menu, seemed to be helped to get an overview of these contents with these headings.
- Tour: Organically did not use the guided tour, we did not direct them there. 		Login "Felt good"None
3
2J2Create new article, add category, insert mediaBlocked or failed- Create new article, navigation: Did not use main menu, used Create new article button directly on startpage.
- Create new article, page: Started with navigating on headings with H - found just main headng, then moved on to combing through form fields with F on screen reader. Quickly found the main form fields such as title.
- Insert media: Unclear how to upload image, both on form and button leading to diaglog, and in the dialogue. No feedback on image is selected and did not find the select button for the chosen image, screenshot from test where user got confused and thought image was selected. This was a blocking issue.
When getting support to choose image, the read on the object getting back from dialoge was long and not easy to understand. Also the label "No description" for the checkbox, was a bit confusing label when first listening to it.
- Add category: When being on other tabs, such as images and links, it seemed not intuitive to find category on the tab "Content", thought about going to "Options". Later discusses that the placement under content is fine, just needed to look for it a bit. Select category, element worked well for this user.
"I braced myself on finding thousands of buttons and headings, so I used strategies for that (shortcuts H anf F), but it wasnt that much! These main elements was quite high up. Better than wordpress!"

Clip showing issues on selecting image, and user describes. 		Image selector form field, image selector dialogue
4
3J3Filter articles, select multiple elements, action change statusCompleted with friction- Aricle list: The user found information in the table easy, and also understood that it is a table with contents. The cell contents seemed understandable, such as the name on actions under feature or status. The user thought "Public" ment that it was published (before finding the status column)
- Filter options: The user did not at all understand that the filters expanded, got no feedback on that, and tid not find the contents that was expanded. I needed to guide the user to them in order for them to find these. When found the comboboxes seemed to work well.
- Select multiple, change status: Found checkboxed and could check them. Quite a lot of redundant info on these before getting to the "checked" part of the announcement. Issue: Did not find the actions, button to do an action on these checked rows. Looked before the table, and below. When I guided them to the placement above to the "Actions" button, the name seemed good but the placement obviously did not match the expected. It was to high up.

Note: This user did not react initally, but we discussed that the visual feedback "Article saved" from creating the article in J2 was not announced. 		Moving around in the table on headings and contents: "Moving with arrows is how you navigate in these tables".

Question: Did you get feedback that your article was saved?
"No, I didnt, no more than it moved to a new page".

"Im not aware of if something happens when i press Filter options"

When trying to do actions on multiple checkboxes "There is no obvious place".
Filter options button (and order/focus to find contents), Actions button for multiple elements.
5
4J4Create menu item, type modalCompleted independently- Navigation to Menus: Did not get information about the expanded sub-menu. Figured it out anyway, but commented on it.
- Create menu item: Moved to the menu part we defined they add one in, bottom menu, directly in the sub-menu. In that menus: itemm (bottom menu) page, orient quickly to one of the existing items in the table "Login", and seem to crasp the concept.
Thinks about how to create new, look for actions.
- Type modal: Knowing that they should select a type of menu item, they were a bit confused on the input field before the "Select button". Later found the button select and moved into the dialogue to choose a pre-existing menu item type. The modal/dialoge worked well, and the user found the type in the accordions in it.

Note: Commented that after selection on modal the focus went to the start of the page again. (So a thought could be that the user would want to keep focus closer to the selection place.)		"It (Menus in navigation) didn't say anything about expanding something"

"Here (in the Menus: Items, bottom menu) we have the same concept as in the Artcles page".

"Now I need to figure out how to create a new one, is it in an action menu maybe?"..."Here I found an action menu, I only find rebuild when I open that" (later find "new" next to them).		None
6
5J6Find and change global config.settingsNot tested---
7
6J5Frontend login, edit buttons, find login fields and test Completed independently- Frontend login: The user came to the start page and quickly went looking for the credentals we sent them. While doing that they expressed that they had already found the login before. We observed that they jumped straight to the user name field on the start page. (analysis, they probably used the F command to find this).

- Edit buttons: Found edit buttons and they were understandable for the user. 		"Under Main menu (heading on typography page) we have an Edit button"None