{"id":1094,"date":"2024-08-06T07:00:00","date_gmt":"2024-08-06T05:00:00","guid":{"rendered":"https:\/\/o-matic.ch\/blog\/non-categorise\/bastien-and-scapins-criteria\/"},"modified":"2026-02-10T12:37:17","modified_gmt":"2026-02-10T11:37:17","slug":"bastien-and-scapins-criteria","status":"publish","type":"post","link":"https:\/\/o-matic.ch\/en\/blog\/ux-ui\/bastien-and-scapins-criteria\/","title":{"rendered":"Bastien and Scapin’s criteria"},"content":{"rendered":"\n

J. M. Christian Bastien and Dominique Scapin are two researchers in ergonomic psychology and cognitive ergonomics who have conducted research on user interfaces. In 1993, they published their heuristics<\/a>, also known as the \u2018Bastien and Scapin criteria\u2019<\/em>, which enable the usability of a website, software or application to be measured using specific criteria. <\/p>\n\n

These criteria enable us to measure the quality of interaction between the user and the interface through 17 criteria divided into 8 categories, which we will present here.<\/p>\n\n

This article is quite long, but it lists all the categories and criteria. We will come back to this later to create a summary sheet! <\/em> <\/p>\n\n

\n

Table of contents<\/h2>\n\n\n\n

1. Guidance<\/a><\/h3>\n\n\n\n

2. Workload<\/a><\/h3>\n\n\n\n

3. Explicit control<\/a><\/h3>\n\n\n\n

4. Adaptability<\/a><\/h3>\n\n\n\n

5. Error handling<\/a><\/h3>\n\n\n\n

6. Consistency and coherence<\/a><\/h3>\n\n\n\n

7. Meaning of codes and names<\/a><\/h3>\n\n\n\n

8. Compatibility<\/a><\/h3>\n<\/div><\/div>\n\n

1. Guidance<\/h2>\n\n

Guidance is the first of the eight categories of criteria. It helps the user interact with the interface. <\/p>\n\n

It comprises four criteria: <\/p>\n\n

Incentive<\/h3>\n\n

The first criterion, incentive, as its name suggests, encourages the user to perform specific actions and presents different alternatives.<\/p>\n\n

We can list:<\/p>\n\n

    \n
  • l’indication du format ad\u00e9quat \u00e0 saisir dans un champ de texte (ex : jj\/mm\/aaaa<\/em>)<\/li>\n\n\n\n
  • add labels to fill-in fields<\/li>\n\n\n\n
  • announcing the expected length in a field<\/li>\n<\/ul>\n\n

    Grouping and distinguishing items<\/h3>\n\n

    This is simply the visual organization of interface elements. <\/p>\n\n

    \"\"
    Source : Google images<\/em><\/figcaption><\/figure>\n\n

    Based, among other things, on Gestalt principles,<\/em> this criterion can be used to differentiate and\/or bring together several visual elements:<\/p>\n\n

      \n
    • by location: when close together, they seem connected; when apart, they are indifferent to each other<\/li>\n\n\n\n
    • by format: with the same size, the same color… elements come together<\/li>\n<\/ul>\n\n

      Good organization of elements on an interface provides a more pleasant experience for the user, enabling him to find his way around and memorize elements.<\/p>\n\n

      Immediate feedback<\/h3>\n\n

      This is one of the most important criteria: showing that an action is carried out as quickly as possible:<\/p>\n\n

        \n
      • Showing real-time field input allows the user to see where they are in the process.<\/li>\n\n\n\n
      • indicate a bug, a delay to inform the user of the processing of his request<\/li>\n<\/ul>\n\n

        Legibility<\/h3>\n\n

        Ce crit\u00e8re se rapproche de pr\u00e8s de l’accessibilit\u00e9. Offrir \u00e0 l’utilisateur une interface r\u00e9fl\u00e9chie, non pas uniquement pour \u00eatre jolie, mais aussi et surtout pour \u00eatre lisible, est l’une des meilleures mani\u00e8res de ne pas le frustrer et faciliter sa lecture. <\/p>\n\n

        Readability includes all lexical characteristics:<\/p>\n\n

          \n
        • text line length<\/li>\n\n\n\n
        • title and text case<\/li>\n\n\n\n
        • text alignment and justification<\/li>\n\n\n\n
        • hyphenation avoidance<\/li>\n\n\n\n
        • \u2026<\/li>\n<\/ul>\n\n

          Reading on a screen is not as easy as reading on paper: the typography is different, the distance changes… Making it easier for a user to read by respecting defined criteria therefore creates the best conditions.<\/p>\n\n

          2. Workload<\/h2>\n\n

          The second category of Bastien and Scapin’s criteria! The greater the workload, the greater the number of errors. <\/p>\n\n

          By reducing the load a user perceives, by reducing actions and their duration, we also reduce the risk of abandonment.<\/p>\n\n

          There are 2 criteria in this category: <\/p>\n\n

          Brevity<\/h3>\n\n

          The faster the activity, the fewer the errors.<\/p>\n\n

          In fact, by being concise and reducing the number of actions, the user’s experience is enhanced, as his or her reading and typing work is reduced.<\/p>\n\n

          Information density<\/h3>\n\n

          Information density refers to a user’s perception of a set of elements. <\/p>\n\n

          When too many elements are perceived, or when it is asked to remember previous actions or data, users perceive this negatively. It demands too much attention and effort, when the action could be avoided or appear otherwise. <\/p>\n\n

          3. Explicit control<\/h2>\n\n

          It’s all about user control over the interface. The system must react correctly to the user’s actions. This category includes 2 key criteria: <\/p>\n\n

          Explicit actions<\/h3>\n\n

          When a user acts on an interface, his or her action must be carried out when requested, and without a hitch. <\/p>\n\n

          User control<\/h3>\n\n

          Users must be able to control their own actions. <\/p>\n\n

          We must therefore give him the opportunity : <\/p>\n\n

            \n
          • interrupt an ongoing procedure<\/li>\n\n\n\n
          • cancel an action or allow it to resume a previously cancelled action<\/li>\n\n\n\n
          • to make it easy for him to go back<\/li>\n\n\n\n
          • allow the user to control the pace of input rather than depend on the system’s pace<\/li>\n<\/ul>\n\n

            4. Adaptability<\/h2>\n\n

            Adaptability concerns the system’s ability to react to the user’s actions and preferences. A task can be performed differently depending on the user’s profile and situation. <\/p>\n\n

            2 criteria apply:<\/p>\n\n

            Flexibility<\/h3>\n\n

            Flexibility can be translated (with a pinch of salt) as accessibility: the system can offer interface customization and accessibility options to users.<\/p>\n\n

            Taking user experience into account<\/h3>\n\n

            The interface must adapt to the user’s level and not exclude certain types: <\/p>\n\n

              \n
            • Experienced users can skip certain steps, notably by using keyboard shortcuts.<\/li>\n\n\n\n
            • Novice users need more support, and shouldn’t be held back by a lack of understanding.<\/li>\n<\/ul>\n\n

              5. Error handling<\/h2>\n\n

              How do you get around mistakes? That’s the question this category answers through 3 criteria. <\/p>\n\n

              Error protection<\/h3>\n\n

              The interface must prevent and detect errors. By implementing an analysis during data entry rather than at validation, users are informed at the right moment. <\/p>\n\n

              In this way, you can : <\/p>\n\n

                \n
              • tell users when their session has ended and offer them the option of continuing their session.<\/li>\n\n\n\n
              • include the words “mandatory” or an asterisk * in labels to indicate when a field is required<\/li>\n\n\n\n
              • \u2026<\/li>\n<\/ul>\n\n

                Quality of error messages<\/h3>\n\n

                Error messages are very important. Apart from the traditional 404 error indicating that a page cannot be found, few people know the meaning of error codes. That is why messages must be short, in the right place, accurate and easy to understand. <\/p>\n\n

                Error correction<\/h3>\n\n

                The system must allow interface users to correct their errors, both during and after input: <\/p>\n\n

                  \n
                • Indicate live progress in a maximum number of characters, allowing the user to see where he stands<\/li>\n\n\n\n
                • Showing the expected data format enables (see Guidance > Incentives) correct data completion.<\/li>\n<\/ul>\n\n

                  6. Consistency and coherence<\/h2>\n\n

                  A basic Bastien and Scapin criterion, the aim here is to respect the same style, the same codes and the same locations throughout the interface, in order to preserve consistency and coherence. <\/p>\n\n

                  Today, we also talk about design systems that enable us to establish the components to be used across the screens of an interface (colours, fonts, buttons, text fields, etc.).<\/p>\n\n

                  7. Meaning of codes and names<\/h2>\n\n

                  Every action has a code. Copy and paste is done with Ctrl-C\/Ctrl-V. If this shortcut were to change, many users would be at a loss. <\/p>\n\n

                  On an interface, it’s the same thing: <\/p>\n\n

                    \n
                  • icons have a code that most people know: \n
                      \n
                    • <\/i> gears or tools for adjustments<\/li>\n\n\n\n
                    • <\/i> a stylized character for the customer area<\/li>\n\n\n\n
                    • <\/i> an arrow coming out of a rectangle to disconnect<\/li>\n<\/ul>\n<\/li>\n\n\n\n
                    • colors have a code:\n
                        \n
                      • red for an error<\/li>\n\n\n\n
                      • green for information, correct entry<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n

                        8. Compatibility<\/h2>\n\n

                        The last of Bastien and Scapin’s criteria refers to the relationship between several elements:<\/p>\n\n

                          \n
                        • user characteristics (age, perception, expectations, skills, etc.), constraints (situation, disabilities, etc.) and tasks performed. <\/li>\n\n\n\n
                        • compatibility between user actions and system results.<\/li>\n\n\n\n
                        • consistency between the different stages of a process.<\/li>\n<\/ul>\n\n

                          In a nutshell<\/h2>\n\n

                          Bastien and Scapin’s heuristics or Crit\u00e8res de Bastien et Scapin (Bastien and Scapin’s Criteria) have become benchmarks in ergonomics, as they enable us to evaluate an interface without necessarily calling for user testing. From an initial analysis, they can highlight usability problems and correct them as quickly as possible, right from the design stage, to create interfaces that are pleasant, interesting and easy to use. <\/p>\n","protected":false},"excerpt":{"rendered":"

                          J. M. Christian Bastien and Dominique Scapin are two researchers in ergonomic psychology and cognitive ergonomics who have conducted research on user interfaces. In 1993, they published their heuristics, also known as the \u2018Bastien and Scapin criteria\u2019, which enable the usability of a website, software or application to be measured using specific criteria. These criteria […]<\/p>\n","protected":false},"author":2,"featured_media":1095,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[48],"tags":[],"class_list":["post-1094","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-ux-ui"],"_links":{"self":[{"href":"https:\/\/o-matic.ch\/en\/wp-json\/wp\/v2\/posts\/1094","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/o-matic.ch\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/o-matic.ch\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/o-matic.ch\/en\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/o-matic.ch\/en\/wp-json\/wp\/v2\/comments?post=1094"}],"version-history":[{"count":2,"href":"https:\/\/o-matic.ch\/en\/wp-json\/wp\/v2\/posts\/1094\/revisions"}],"predecessor-version":[{"id":2011,"href":"https:\/\/o-matic.ch\/en\/wp-json\/wp\/v2\/posts\/1094\/revisions\/2011"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/o-matic.ch\/en\/wp-json\/wp\/v2\/media\/1095"}],"wp:attachment":[{"href":"https:\/\/o-matic.ch\/en\/wp-json\/wp\/v2\/media?parent=1094"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/o-matic.ch\/en\/wp-json\/wp\/v2\/categories?post=1094"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/o-matic.ch\/en\/wp-json\/wp\/v2\/tags?post=1094"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}