ABCDEFG
1
IDUser journeyDescription, test objectiveAssessmentObservation commentsQuotes, recordingsBlockers
2
1J1Login, dashboard, guided tour, find navigationCompleted independently- Login: Went well. Like the passkey option.

- Explore startpage: Thinks its a bit strange that you hear that it is keyboard commands, wven when not a keyboard plugged in on a touch screen.

- Navigation: In bottom navigation, dont like the static name of "Toggle menu", want the name to be named "Menu" and the actual state seperate as "collapsed" only.

(Observation note: Difference in iOS and on desktop, on desktop the menu items was not announced as expandable, but they are here on iOS)		Dot menu in bottom: "More elements, i dont know what it does". -
3
2J2Create new article, add category, insert mediaBlocked or failed- Create new article, navigation: Goes to main menu, to content page, to article page and there "New".

- Create new article page: Finds the toolbar. Moves on to title, adds that. Go to content, reacts to not hearing the tabs. Category input a bit easier to understand than in desktop. But still picked up remove button and such as label.

- Image selection, in editor: Finds image selector, under content area. Tries that and does not understand the "Source" field.

- Images and links: Found that Content button can be collapsed, collapsed and found images and links. In that section the field before select, but after found select button and open dialogue. The dialogue is highly inaccessible for the user, static texts such as headers, banners, sampledata without any context. The selector for a png image and manage buttons are not at all read for the users, or the announcements are very cryptic.
"I have not found the tabs here yet (after Content), but Im sure they are here somewhere".

Image in content "I dont know how to choose image".

On the static text in dialogue for image selector "This text cassiopeia seem to be a relevant image". 		Image selector in editor, image selector in tab images and links, dialogues for image selection.
4
3J3Filter articles, select multiple elements, action change statusCompleted with friction- Filter: Finds button to filter but no feedback on if they open. Does not themself find the expanded elements, that come after sort elements and such.
Comments on combobox in filters: when you try to type the suggested items, number in list found or such would be good feedback. Bigger issue is that this user cant get focus, cant access the suggested items in the list but stepping down in the list, can only find it by touch.

- Multiple select: Checks off two items in table rows, finds the action button in the toolbar - since things gathered high up seem to be in the toolbar.
--
5
4J4Create menu item, type modalCompleted with friction- Create menu: Goes to the page with menu items for bottom menu. Looks in toolbar, and find "New".

- New menu item page: Thinks the menu item type field is strange, its a text field, but not its protected so not writable. No feedback on what happnes if you try to press ir type. Later finds buttom select. Like the text under "Ordering", about that it will be available after saving, good feedback.
Did not at all understand the field "Finish publishing" after the field for start publishing.

- Dialogue: Choosing in dialoge went ok (beside reacting to that they are links). Did not get any feedback on the made selection when focus went back to the "Select" button. Continued down and tried to find the selected type.

- Saving: Did expect to find saving options in the end at the page, but later found it in the toolbar. Thinks that maybe you learn this after a while but would expect to find it in the end.
"Its a benefit if you have tested this on other pages, since the pattern of toolbar and new" for example, reoccurs"

"Aha! This button (Select) should be named Select item type."

"Finish publishing, what does that mean?"
6
5J6Find and change global config.settingsBlocked or failed- Toggle menu/Tabs: Very confused by the toggle menu vs expandable sections below. Do not seem to understand the connections between the global config menu item and the "tabs" connected to them, nor that the expandable elements change depending on selected element in toggle menu.
In later discussion we found that the selected item in the toggle menu such as "global configuration" does not get announced as selected or current, so this seem to be a part for the confusion. It also made the user click on that link in the beginning of this test, in the task of comming to the global configurations.

The divisions under each expandable element, such as permissions was not easy to understand the role of, but after a while the user understands them as different roles for permissions.
"It would be good it these (expandable elements, and the nested elements under these) also was coded as headings"Toggle menu, selected item. Structure.
7
6J5Frontend login, edit buttons, find login fields and test Completed with friction- Navigation: Goes from dashboard to a specific article where the user remember the frontend link. Does not find the link in the header, where expected from also trying this on desktop. Thinks if preview in toolbar is right. Explores other menus and finds the cryptic "More elements" button.

- Login: Some struggles for the user to get focus on page and to start navigate on page, need to navigate by touch first to then be able to step. (Need to be re-tested with this setup to verify). Finds login in menu, logs in without issues.

- Edit: Find edit button for menu, above menu. Assumes you can edit the menu with pressing that, hear that page reloads when clicking it but nothing else changes in the users mind. Edit fields shows up last, I show the user, but the user would not have noticed it. 		- "Very strange to have both toolbar and more elements, more elements is very unspecific".

- Focus handling/concept to find editable fields after edit button.