UX Check-up

Follow the simple steps to complete your UX Audit Check-up.

1
/ 16

Is the main objective of the interface shared with the users, including clear benefits?

Is the primary purpose of the interface clearly understood?

See Example
2
/ 16

Is the design consistent throughout the interface? Do the colors, buttons, fonts, inputs, layouts have a pattern?

Is the navigation consistent? Are fonts, colors, buttons and x consistent in the interface? Are the flow and visibility consistent? Is there consistency in the interaction elements?

See Example
3
/ 16

Do similar actions and flows have similar structures?

The same elements need to be consistent in different streams.

See Example
4
/ 16

Is the interface free from unnecessary content, features and elements?

The design should be free from unnecessary content.

See Example
5
/ 16

Are design elements like colors, fonts, buttons consistent in order to prevent complexity?

The information given should be presented in meaningful groupings. The information presented with few items in the main menu, provides more information on the detail pages, keeping us away from the information confusion.

See Example
6
/ 16

Are the main actions clearly defined and easily recognizable?

Are the main action buttons easily recognizable to ensure that tasks are done in a short time?

See Example
7
/ 16

Does the interface perform as the users would expect? Are the icons, words, phrases familiar to the user?

Is a user familiar language used? Do the icons and sentences used provide familiar meanings to the user? Are descriptive texts provided without the user having to search in the browser?

See Example
8
/ 16

Are the contents well grouped and prioritised in order to direct users to the necessary information and actions?

Can users easily find the information they want to reach under the headings? Are the titles sufficient and informative for this?

See Example
9
/ 16

Does the interface keep its users informed about where they are and what is going on?

Does the user understand where he is in the site structure? If in a flow, is there information indicating which step is in the flow, how many steps are left, and the purpose of the steps? Are there breadcrumbs on the site indicating where it is?

See Example
10
/ 16

Are there necessary information and warnings in order to prevent possible errors?

There should be informed to prevent possible errors of users. For example, "Your password should be 8 digits" and "Capital and lowercase letters" are used in account creation steps. When the search page cannot be reached, the user should be directed to the home page or the page that is closely related.

See Example
11
/ 16

Is it clear how to and what to do in specific interaction elements?

Are the elements that the user will interact with intelligible about what to do and how?

See Example
12
/ 16

Is the interface compatible with different screen sizes, especially the mobile phones?

When we change platforms, does the site structure adapt? Is the design mobile friendly? When users switch platforms, do they encounter the familiar interface?

See Example
13
/ 16

Does the interface load and act fast?

The page shouldn't take too long to load to reach the user goal. The difficulty of reaching the goal can distract the user from the action and the page user is on. Actions and interactive elements in the interface should not give the user the feeling of "not working".

See Example
14
/ 16

Are the edge cases like empty states, failures, over filled states handled in the interface in all channels?

Have the possible situations in the page structure such as leaving the input fields blank in all channels of the interface, misspellings and out-of-line entries overcome?

See Example
15
/ 16

Are errors clear, consistent and have clear recover steps in the interface?

It is necessary to tell the error to the user. The user should understand the page's error and have directions where the user can take the actions required to improve the page.

See Example
16
/ 16

Do the users have full control like undo, cancel, leave the flows, make changes throughout the interface?

Has the structure of the site considered what needs to be done in possible faulty scenarios? Does it give the user full control over possible faulty scenarios?

See Example
Final!

Register your project!

We'll send you a link to your e-mail.
Check the results from your e-mail address. Thanks for using!

Thanks for Subscribing!

We've recieved your submission and will be in touch shortly.
Oops! Something went wrong while submitting the form