Opquast Web Quality Checklist

(en / fr)
Go to the filters

Filtered results: 296 best practices.

1. Each decorative image has an appropriate text alternative.

Objectif:

To prevent users in environments where images are not seen (text browsers, screen readers or browsers with the images disabled) from being bothered by information about images that are unimportant to them.

To provide only pertinent information to web crawlers.

Checklist
  • Best practices
Project phase
  • Integration
  • Content
Tag
  • Accessibility
  • SEO
  • Opquast label

2. Each decorative image link has an appropriate text alternative.

Objectif:

To allow users in environments where images are not seen (text browsers, screen readers or browsers with the images disabled) to understand the meaning of the links attached to images that they cannot see.

To enable bots to exploit the information carried by the image links (to reference, index and perform machine translation on the image text alternatives).

To enable the display of relevant text while images are loading.

Checklist
  • Best practices
Project phase
  • Integration
  • Content
Tag
  • Accessibility
  • SEO
  • Opquast label

3. Each information-carrying image has an appropriate text alternative.

Objectif:

To allow users in environments where images are not seen (text browsers, screen readers or browsers with the images disabled) to understand the meaning of the images that they cannot see.

To enable bots to exploit the information carried by the images (to reference, index and perform machine translation on the image text alternatives).

To enable the display of relevant text while images are loading.

Checklist
  • Best practices
Project phase
  • Integration
  • Content
Tag
  • Accessibility
  • SEO
  • Opquast label

4. Included objects have an appropriate text alternative.

Objectif:

To provide access to the information to users whose browsers or platforms don’t support the inclusion of objects or the technologies used by the included objects.

To facilitate the exploitation of that content by bots (especially web crawlers)

To simplify the presentation and/or reuse of the included content

Checklist
  • Best practices
Project phase
  • Integration
  • Content
Tag
  • Accessibility
  • SEO
  • Opquast label

5. Content managed by styles has an appropriate alternative.

Objectif:

To ensure access to the content, regardless of whether or not the CSS formatting layer is handled.

To allow content to be reused on media and platforms that do not handle formatting for on-screen display.

To give users in environments where styles are not reproduced (text browsers, screen readers or browsers with the images disabled) access to information that takes the form of CSS-generated content(particularly background images).

To enable bots to exploit the information carried by CSS styles (to reference, index and perform machine translation on the alternatives).

Checklist
  • Best practices
Project phase
  • Integration
Tag
  • Accessibility
  • SEO
  • Opquast label

6. Typographic symbols have an appropriate alternative.

Objectif:

To enable users in environments where the CSS fonts used to display symbols are not reproduced (text browsers, screen readers or browsers with the images disabled) to understand the meanings of those symbols.

To enable bots to exploit the information carried by those symbols (to reference, index and perform machine translation on the alternatives).

Checklist
  • Best practices
Project phase
  • Integration
Tag
  • Accessibility
  • SEO

7. All audio and video content is accompanied by a text transcription.

Objectif:

To give users unable to perceive the proposed sound or image to access a text transcription as an alternative.

To give users unable to hear the sound to access the information contained in the video.

To enable bots to exploit the information, in order to improve its indexing and referencing, or to translate it using online language tools.

Checklist
  • Best practices
Project phase
  • Content
Tag
  • Accessibility
  • SEO

8. Information is not conveyed by color alone.

Objectif:

To give users whose browser, platform, technical aid or disability (likecolor-blindness) prevents them from viewing or differentiating between colors access to the information.

To make the information accessible by web crawlers

Checklist
  • Best practices
Project phase
  • Design
  • Content
Tag
  • Accessibility
  • Opquast label

9. Audio captchas can be replayed at will.

Objectif:

To facilitate access to content and services that are protected by captchas, for users that cannot see the graphic captchas.

To facilitate the use of audio captchas

Checklist
  • Best practices
Project phase
  • Design
  • Development
Tag
  • Accessibility

10. Captchas are accompanied by an alternative access solution.

Objectif:

To give users with difficulty taking captcha tests, especially graphic ones, access to the protected content or services by alternative means.

Checklist
  • Best practices
Project phase
  • Design
  • Development
Tag
  • Accessibility
  • Security

11. Each page’s source code begins with a document type declaration (doctype or DTD), whose syntax is one of those recommended by W3C.

Objectif:

To simplify source-code validation

To foster a rendering that is predictable on all browsers (browser versions still in circulation may rely on the precise syntax of the DTD to adopt a CSS rendering mode).

Checklist
  • Best practices
Project phase
  • Integration
Tag
  • Accessibility

12. Each HTML ID is only used once per page.

Objectif:

To prevent content reproduction errors and interaction errors via scripts

To limit the risk of random interpretation of the Document Object Model (DOM) by different user agents.

Checklist
  • Best practices
Project phase
  • Integration
Tag
  • Accessibility
  • Robustness

13. Each page’s content is organized according to a hierarchical structure of headings and sub-headings.

Objectif:

To allow interested users to view and navigate through the structure of the page’s content.

To enable machines and indexing tools to extract each page’s map

To improve SEO by simplifying the content’s interpretation by web crawlers.

Checklist
  • Best practices
Project phase
  • Integration
  • Content
Tag
  • Accessibility
  • SEO
  • Opquast label

14. The site does not force any redirects or auto-refreshes on the client side.

Objectif:

To allow users to maintain control over their work environments.

To prevent cut-offs or losses of information while reading, particularly for users with screen readers whose functions would be interrupted by a timed refresh or redirect.

To not penalize mobile users trying to access content when their network signal is variable over short periods of time.

To prevent unwanted increases in the cost to users of using mobile data.

Checklist
  • Best practices
Project phase
  • Development
Tag
  • Usability
  • Accessibility
  • Opquast label

15. Dates are presented in an explicit format.

Objectif:

To prevent users from misinterpreting the meaning of a date

To simplify the comprehension and reuse of the relevant content

Checklist
  • Best practices
Project phase
  • Content
Tag
  • Usability
  • Internationalization

16. Navigation blocks are located in the same place in every page’s source code.

Objectif:

To facilitate memorization of the pages’ organization and navigation for users with screen readers and users who navigate by keyboard.

Checklist
  • Best practices
Project phase
  • Integration
Tag
  • Usability
  • Accessibility

17. The character encoding is UTF-8.

Objectif:

To use an international character set

To prevent display faults

To simplify content manipulation by users and developers

Checklist
  • Best practices
Project phase
  • Integration
Tag
  • Usability

18. Each page’s source code contains metadata that define the character set used.

Objectif:

To display pages offline correctly, by telling the browser which character set was used.

Toprevent the risk of character display problems associated with the sometimes unsure functioning of browsers’ catch-up mechanisms when they don’t receive the necessary information from the HTTP content-type header.

Checklist
  • Best practices
Project phase
  • Integration
Tag
  • Accessibility
  • SEO

19. Content that should be reproduced by screen readers is not hidden from them.

Objectif:

To ensure the correct reproduction of masked content to be read by screen readers.

Checklist
  • Best practices
Project phase
  • Integration
Tag
  • Accessibility

20. The content and meaning of each page are not altered when styles are disabled.

Objectif:

To allow users whose browsers don’t apply the website’s style sheets or whose method of access is not visible to understand the site’s content.

To meticulously separate the content from its presentation, to foster interoperability

Checklist
  • Best practices
Project phase
  • Integration
Tag
  • Usability
  • Accessibility

21. Elements that are visually displayed as lists are tagged in an appropriate way in the source code.

Objectif:

To enable browsers and technical aids to identify lists and then reproduce them accurately, in order to facilitate their understanding by users.

To improve the semantics of page content and its reusability

Checklist
  • Best practices
Project phase
  • Integration
  • Content
Tag
  • Accessibility

22. Text that can be formatted using styles is not replaced by images.

Objectif:

To facilitate the rendering’s adaptation to the medium (mobile or other) or to the user’s needs (increasing the characters’ size, changing the colors, the font,the bolding, the alignment, etc.).

Checklist
  • Best practices
Project phase
  • Integration
  • Content
Tag
  • Accessibility
  • SEO

23. The first occurrence of an abbreviation or an acronym in the body of any page provides an explanation of its meaning.

Objectif:

To allow users to quickly understand the meaning of an acronym

To enable bots to exploit the content (inorder to establish an index of abbreviations).

To foster referencing of the content

Checklist
  • Best practices
Project phase
  • Design
  • Integration
  • Development
  • Content
Tag
  • Usability
  • Accessibility

24. Each page’s source code contains no elements that were misused for presentational purposes.

Objectif:

To enable the correct exploitation of the course code by user agents (browsers,search engine web crawlers, Braille terminals, etc.).

To simplify the source code, by remoting the formatting to CSS

Checklist
  • Best practices
Project phase
  • Integration
Tag
  • Accessibility

25. Each page's source code does not contain any presentational tag or attribute

Objectif:

To foster the adaptation of content formatting by user agents, depending on the user’s needs.

To simplify the pages’ source code, by encouraging the pooling and outsourcing of formatting information by means of CSS.

To simplify the unconstrained reuse of content associated with its initial formatting

Checklist
  • Best practices
Project phase
  • Integration
Tag
  • Accessibility
  • Ecodesign

26. The site provides at least one means of contact.

Objectif:

To facilitate feedback from users

To encourage trust by guaranteeing, from the outset, that users have an option in the case of any problems.

Checklist
  • Best practices
Project phase
  • Prototype
Tag
  • Usability
  • Trust

27. The site provides at least two means of contact.

Objectif:

To optimize options for users to provide feedback

To avoid putting a user in a difficult position, if one of the means of contact is unavailable or causing problems to the user.

Checklist
  • Best practices
Project phase
  • Prototype
Tag
  • Usability

28. Mail and phone information for companies’ and organizations’ local branches or headquarters are provided.

Objectif:

To identify the entity responsible for the content and the services.

To provide an alternative means of contact.

Checklist
  • Best practices
Project phase
  • Prototype
  • Content
Tag
  • Usability
  • Opquast label

29. Every information request submitted produces an acknowledgment of receipt.

Objectif:

To inform users that their requests have been received

To give users a confirmation of receipt of their request for information, which they can save.

Checklist
  • Best practices
Project phase
  • Development
Tag
  • Usability
  • Opquast label

30. Response times are provided for information requests.

Objectif:

To give users a quantified timeframe for a response

To limit the risk of follow-up by users

To reassure users about the site managers’ ability to respond to requests

Checklist
  • Best practices
Project phase
  • Prototype
  • Content
Tag
  • Usability

31. The data in the site’s WHOIS information allow users to connect it with its owner.

Objectif:

To simplify identification of the person or entity responsible for the content or the services.

To allow users to confirm that they are on the right website and not on a phishing site, for example.

Checklist
  • Best practices
Project phase
  • Development
Tag
  • Personal data

32. Each page provides a title that enables one to identify the site

Objectif:

To allow users to immediately identify the website in tabs, favorites, windows, browser histories, and screen readers.

To improve the site’s SEO and its presentation in search engine results

Checklist
  • Best practices
Project phase
  • Development
  • Content
Tag
  • Accessibility
  • SEO
  • Opquast label

33. Each page provides a title that enables one to identify its content

Objectif:

To allow users to immediately identify the nature of each page’s content in tabs, favorites, windows, browser histories, and screen readers.

To improve the pages’SEO and their presentation in search engine results

>
Checklist
  • Best practices
Project phase
  • Content
Tag
  • Accessibility
  • SEO
  • Opquast label

34. Advertisements and sponsored content are identified as such.

Objectif:

To enable the immediate identification of advertisements and sponsored content

To avoid confusion between editorial and advertising content

To prevent the risks associated with conflicts of interest

Checklist
  • Best practices
Project phase
  • Design
  • Content
Tag
  • Usability

35. Information about copyrights and reuse rights can be accessed from every page.

Objectif:

To inform the users of the conditions under which the content is published

To inform the users of the conditions for copying and reusing the content

Checklist
  • Best practices
Project phase
  • Prototype
  • Content
Tag
  • Usability

36. The site provides a way for users to find out about new content and services.

Objectif:

To enable users to immediately identify new online content and services.

Checklist
  • Best practices
Project phase
  • Prototype
  • Content
Tag
  • SEO

37. If the site provides a personal space (or a subscriber space), personal content can be backed up in a standard format.

Objectif:

To enable user-generated content to be archived

To avoid the user having to re-enter data, in the event of their reuse of content

Checklist
  • Best practices
Project phase
  • Development
Tag
  • Security
  • Personal data

38. A lexicon or a glossary adapted to the target audience explains the industry-specific or technical vocabulary used.

Objectif:

To allow users to understand industry-specific and technical content

To simplify use of a service

To improve SEO on keywords or technical expressions

Checklist
  • Best practices
Project phase
  • Content
Tag
  • Accessibility
  • SEO

39. A product or service can be purchased without creating an account.

Objectif:

To allow buyers top lace an order immediately

To remove the barrier of account creation

To increase the conversion rate

Checklist
  • Best practices
Project phase
  • Development
Tag
  • Personal data

40. No additional products or services are added to the shopping cart without a customer action.

Objectif:

To give users control over their orders

To not compromise your trusted relationship with your users

To avoid any form of forced sales

Checklist
  • Best practices
Project phase
  • Prototype
Tag
  • Trust

41. Product availability is shown before final order placement.

Objectif:

To anticipate any possible difficulties and delivery delays

Checklist
  • Best practices
Project phase
  • Prototype
  • Content
Tag
  • Opquast label

42. The estimated delivery date is shown before final order placement.

Objectif:

To allow users to plan ahead for the conditions and means of accessing the service or the virtual item.

To avoid disappointments and complaints.

Checklist
  • Best practices
Project phase
  • Prototype
  • Content
Tag
  • Opquast label

43. The method for retrieving a virtual item is explained before order placement.

Objectif:

To allow users to plan ahead for the conditions and means of accessing the service or the virtual item.

To avoid disappointments and complaints

Checklist
  • Best practices
Project phase
  • Prototype
  • Content
Tag

    44. Users can still modify each item’s quantity, and add or delete one or more items, as long as the order has not definitively been placed.

    Objectif:

    To allow users to easily edit their orders

    Checklist
    • Best practices
    Project phase
    • Prototype
    • Development
    Tag
    • Usability
    • Opquast label

    45. The nature and quantifiable characteristics of products and services are provided.

    Objectif:

    To allow users to identify the exact nature and specifications of the products

    Checklist
    • Best practices
    Project phase
    • Prototype
    • Content
    Tag
    • SEO
    • Opquast label

    46. The period of validity and conditions of special offers and promotions are indicated.

    Objectif:

    To allow users to identify the period during which they can enjoy special offers.

    Checklist
    • Best practices
    Project phase
    • Content
    Tag

      47. The company’s or organization’s legal registration number, issued in its home country, is provided.

      Objectif:

      To give users a verifiable indication of the official existence of the structure offering the content or services.

      Checklist
      • Best practices
      Project phase
      • Content
      Tag

        48. The detailed sub-total is indicated before final order placement.

        Objectif:

        To provide users withdetails of the prices of their orders

        To remove an obstacle to order placement

        Checklist
        • Best practices
        Project phase
        • Prototype
        • Development
        Tag

          49. Financing conditions are indicated.

          Objectif:

          To allow users to identify the total amount they will have to pay and how that amount breaks down.

          Checklist
          • Best practices
          Project phase
          • Content
          Tag

            50. Customer support service conditions are provided.

            Objectif:

            To inform users about the conditions for obtaining assistance and support, if they need it

            Checklist
            • Best practices
            Project phase
            • Content
            Tag
            • Opquast label

            51. Debit and charge conditions are explained before final order placement.

            Objectif:

            To enable users to identify the detailed payment charge conditions

            Checklist
            • Best practices
            Project phase
            • Content
            Tag

              52. Warranty conditions are specified.

              Objectif:

              To enable users to identify the specific nature of the associated services and their costs.

              Checklist
              • Best practices
              Project phase
              • Content
              Tag
              • Opquast label

              53. The terms of sale and use can be accessed from every page.

              Objectif:

              To provide continuous, easy access to all of the terms and conditions of fulfillment of the service

              Checklist
              • Best practices
              Project phase
              • Prototype
              • Content
              Tag
              • Opquast label

              54. Information is provided about the products or services delivery zones.

              Objectif:

              To avoid pointless browsing and orders, or even a waste of time for your users and for the organization that is offering the goods or services.

              Checklist
              • Best practices
              Project phase
              • Content
              Tag
              • Opquast label

              55. The accepted payment methods and their associated procedures are indicated.

              Objectif:

              To give users advance notice of the payment methods and conditions, so they will know whether or not they are able to place an order.

              Checklist
              • Best practices
              Project phase
              • Prototype
              • Content
              Tag
              • Opquast label

              56. The hours and prices for the services offered to customers are listed.

              Objectif:

              To inform users of the services that are available to them and how they work.

              Checklist
              • Best practices
              Project phase
              • Prototype
              • Content
              Tag
              • Opquast label

              57. Dispute procedures are explained in the general terms of sale or use.

              Objectif:

              To reassure users before they make a purchase

              To give buyers all of the relevant information related to their purchases, whether or not everything goes well.

              Checklist
              • Best practices
              Project phase
              • Content
              Tag

                58. The address and the terms and conditions for returns (on-site, at the workshop, etc.) are provided.

                Objectif:

                To allow users to plan ahead in case of any problems with the use and/or operation of the good or service.

                To reduce the strain on customer service

                Checklist
                • Best practices
                Project phase
                • Content
                Tag
                • Opquast label

                59. The procedure for submitting a complaint and for how it will be handled is explained.

                Objectif:

                To allow users to understand or anticipate any problems they may encounter on the website or during a transaction.

                Checklist
                • Best practices
                Project phase
                • Content
                Tag

                  60. The conditions for getting a refund are explained.

                  Objectif:

                  To allow users to identify the exact documents required, if they need to return a product.

                  To anticipate potential problems, in the case of a refund request submitted afterthe statutory cooling-off period.

                  To reduce the number of needless procedures and the number of customer service requests

                  To increase an e-commerce site’s conversion rate

                  Checklist
                  • Best practices
                  Project phase
                  • Content
                  Tag
                  • Opquast label

                  61. The hardware and software required for the service to run are provided before final order placement.

                  Objectif:

                  To allow users to anticipate the conditions and means of use of the service

                  To reduce complaints

                  Checklist
                  • Best practices
                  Project phase
                  • Content
                  Tag

                    62. The displayed prices show the applied taxes and any additional charges, as well as tax-exclusive prices.

                    Objectif:

                    To allow users to identify the precise total amount they will have to pay, before placing an order.

                    To enable users to accurately identify any deductible amounts and the different itemizations.

                    Checklist
                    • Best practices
                    Project phase
                    • Content
                    Tag

                      63. Different shipping and billing addresses can be specified.

                      Objectif:

                      To allow users to have their purchases delivered to the location of their choice

                      Checklist
                      • Best practices
                      Project phase
                      • Prototype
                      • Development
                      Tag
                      • Opquast label

                      64. The website accepts at least two payment methods.

                      Objectif:

                      To allow users to choose their preferred payment method in their specific situation.

                      To offer at least one alternative to users temporarily or permanently unable to use a particular payment method.

                      Checklist
                      • Best practices
                      Project phase
                      • Prototype
                      • Development
                      Tag
                      • Opquast label

                      65. The transaction’s reference number is displayed to the customer, once the order has been placed.

                      Objectif:

                      To allow users to see and, potentially, printout a trace of their orders.

                      To give users written proof of the transaction

                      To improve the traceability of transactions

                      Checklist
                      • Best practices
                      Project phase
                      • Prototype
                      • Development
                      Tag

                        66. Any mention of an affiliation with a professional association, or endorsement by a label or an award, features a link to the source.

                        Objectif:

                        To give users immediate access, so they can understand what those mentions mean.

                        To enable users to check the information themselves

                        To increase the level of trust or credibility

                        Checklist
                        • Best practices
                        Project phase
                        • Content
                        Tag
                        • Trust

                        67. Unavailable products are differentiated by visual and textual means.

                        Objectif:

                        To allow users to immediately identify products that are unavailable, with no possibility of confusion.

                        To avoid disappointment of when a user starts a purchase, only to discover later on that the product they want is not available.

                        Checklist
                        • Best practices
                        Project phase
                        • Design
                        • Content
                        Tag
                        • Opquast label

                        68. An email providing the transaction’s reference number and the order details is sent after order placement.

                        Objectif:

                        To give users confirmation of their order information

                        To allow users to keep a history of their transactions, elsewhere than on the website.

                        Checklist
                        • Best practices
                        Project phase
                        • Development
                        Tag

                          69. Every complaint submitted produces an acknowledgment of receipt.

                          Objectif:

                          To give users confirmation of their requests, outside the context of the website.

                          To avoid customer service receiving multiple requests for the same complaint

                          Checklist
                          • Best practices
                          Project phase
                          • Development
                          Tag

                            70. The site provides at least one means of contacting the person in charge of complaints.

                            Objectif:

                            To allow users to reach out to or send their complaints directly to the right person.

                            To reassure users that they can easily interact with the complaint department, in the event of a problem.

                            Checklist
                            • Best practices
                            Project phase
                            • Prototype
                            • Content
                            Tag

                              71. The site provides at least one means of contacting the moderator of public spaces.

                              Objectif:

                              To allow users to contact the moderator, so they can request corrections, ask questions or report abuse.

                              Checklist
                              • Best practices
                              Project phase
                              • Prototype
                              Tag
                              • Trust
                              • Public spaces
                              • Personal data

                              72. Public spaces offer at least one way to report abuse.

                              Objectif:

                              To simplify reporting of illegal or inappropriate content

                              To speed up the detection of such content

                              To limit the risk of accessing illegal or inappropriate content

                              Checklist
                              • Best practices
                              Project phase
                              • Prototype
                              Tag
                              • Trust
                              • Public spaces

                              73. The conditions for moderation of public spaces are explained.

                              Objectif:

                              To explain to the users why and how their posts may be moderated.

                              To reduce the number of complaints from users who don’t see their posts online.

                              Checklist
                              • Best practices
                              Project phase
                              • Content
                              Tag
                              • Trust
                              • Public spaces

                              74. Content and files intended for public spaces can be checked before upload.

                              Objectif:

                              To allow users to check their input in context and, if necessary, to correct it before submitting it.

                              To reduce the number of correction and removal requests

                              Checklist
                              • Best practices
                              Project phase
                              • Development
                              Tag
                              • Usability
                              • Public spaces

                              75. Information intended for public spaces can be previewed in their final form.

                              Objectif:

                              To allow users to check and, if necessary, correct their input, account taken of the final layout of the content.

                              To reduce the number of correction and removal requests

                              Checklist
                              • Best practices
                              Project phase
                              • Development
                              Tag
                              • Usability
                              • Public spaces

                              76. The length of video and audio content is displayed.

                              Objectif:

                              To inform users, so they can decide whether ornot to play or download the content, with full knowledge of the facts.

                              Checklist
                              • Best practices
                              Project phase
                              • Prototype
                              • Development
                              • Content
                              Tag
                              • Usability

                              77. The format of downloadable files is displayed.

                              Objectif:

                              To let users know, in a timely manner, whether their tools will allow them to view the downloadable files.

                              To reduce server load by avoiding needless downloads

                              Checklist
                              • Best practices
                              Project phase
                              • Development
                              • Content
                              Tag
                              • Usability
                              • Accessibility
                              • Opquast label

                              78. The size of downloadable files is displayed.

                              Objectif:

                              To provide advancenotice to the users on the quantity of data that will be downloaded, as a preventive measure

                              To allow users to wait to download the file over a low-speed or mobile connection

                              Checklist
                              • Best practices
                              Project phase
                              • Development
                              • Content
                              Tag
                              • Usability
                              • Accessibility

                              79. The language of downloadable files is mentioned, if not the same as on the original page.

                              Objectif:

                              To avoid pointless downloads for users

                              To inform users about the files they’re going to download

                              Checklist
                              • Best practices
                              Project phase
                              • Content
                              Tag
                              • Usability
                              • Accessibility
                              • Internationalization

                              80. Animations, sounds and blinking can be paused.

                              Objectif:

                              To give the user control over animation when viewing content

                              To not distract the user’s attention by forcing elements on them that might annoy them

                              To allow sequential animations and sound content to be accessed step by step

                              Checklist
                              • Best practices
                              Project phase
                              • Design
                              • Integration
                              Tag
                              • Usability
                              • Accessibility
                              • Opquast label

                              81. Running animation does not block access to navigation or content.

                              Objectif:

                              To give users direct, immediate access to the content, even when the webmaster has decided

                              To include animation or an ad beforehand.

                              Checklist
                              • Best practices
                              Project phase
                              • Prototype
                              • Integration
                              Tag
                              • Usability
                              • Opquast label

                              82. Sound and video are launched by the user.

                              Objectif:

                              To give the user control over the visual and auditory interface when visiting a website.

                              To not surprise the user by unexpectedly playing audio content

                              To not impose the playback of animated content on the user

                              Checklist
                              • Best practices
                              Project phase
                              • Prototype
                              • Integration
                              Tag
                              • Usability
                              • Accessibility
                              • Opquast label

                              83. The text of internal PDF documents can be selected.

                              Objectif:

                              To enable the referencing of the contents of PDF documents

                              To simplify the handling and reuse of the contents of PDF documents

                              To ensure the readability of the contents of PDF documents

                              Checklist
                              • Best practices
                              Project phase
                              • Content
                              Tag
                              • Usability
                              • Accessibility
                              • SEO

                              84. Internal PDF documents are given a structure based on headings.

                              Objectif:

                              To give users direct access to the different sections of a PDF file

                              To provide a structure of headings to users who need that

                              To allow PDFs to be read using a technical aid

                              Checklist
                              • Best practices
                              Project phase
                              • Content
                              Tag
                              • Usability
                              • Accessibility
                              • SEO

                              85. In the source code, each field in the form is associated with a label that is specific to it.

                              Objectif:

                              To facilitate the understanding of the data expected in forms

                              To allow technical accessibility aids torender the fields in forms by systematically attaching a label to them, indicating their role and the nature of the expected input.

                              To simplify input by allowing users to select the field by clicking on either its label or the field itself (especially in the case of a checkbox or a radio button).

                              Checklist
                              • Best practices
                              Project phase
                              • Integration
                              Tag
                              • Accessibility
                              • Opquast label

                              86. Information supplementing a field’s label is associated with that field in the source code.

                              Objectif:

                              To optimize the rendering on screen readers, by making it possible to spell out the form’s field labels.

                              Checklist
                              • Best practices
                              Project phase
                              • Integration
                              Tag
                              • Accessibility

                              87. Each form field’s label indicates whether or not it is a required field.

                              Objectif:

                              To tell users in advance whether or not a field is required

                              To prevent mistakes before they are made

                              Checklist
                              • Best practices
                              Project phase
                              • Prototype
                              • Integration
                              Tag
                              • Usability
                              • Accessibility
                              • Opquast label
                              • Personal data

                              88. Each form field’s label indicates the required data format, if any.

                              Objectif:

                              To reduce the risk of input errors

                              To reduce the risks associated with sending incorrect or unusable data

                              To prevent the user from giving up, for lack of information about the expected input

                              Checklist
                              • Best practices
                              Project phase
                              • Prototype
                              Tag
                              • Usability
                              • Accessibility
                              • Opquast label

                              89. The user is warned whenever a field is case-sensitive.

                              Objectif:

                              To prevent the risk of mistakes and, as a result, prevent the user from having to fill out the same field several times.

                              To prevent confusion in users who think they correctly completed the field, but see it marked as an error.

                              Checklist
                              • Best practices
                              Project phase
                              • Prototype
                              • Integration
                              Tag
                              • Usability
                              • Accessibility

                              90. There is an input error prevention mechanism for user password creation.

                              Objectif:

                              To prevent users from entering passwords that don’t match the ones that they wanted or that they memorized.

                              Checklist
                              • Best practices
                              Project phase
                              • Prototype
                              • Development
                              Tag
                              • Usability

                              91. The characters entered in a password field can be displayed in clear text.

                              Objectif:

                              To simplify password entry, especially on mobile devices’ virtual keyboards.

                              To prevent mistakes

                              Checklist
                              • Best practices
                              Project phase
                              • Prototype
                              • Integration
                              Tag
                              • Usability

                              92. Every form label is visually attached to the field that it describes.

                              Objectif:

                              To allow users to unambiguously identify the form’s fields and the type of information they are expected to input.

                              To prevent input errors

                              To simplify and speed up use of the form, especially on a mobile device or for users of screen magnifiers and, more generally, for any user employing the zoom function.

                              Checklist
                              • Best practices
                              Project phase
                              • Prototype
                              • Design
                              Tag
                              • Usability
                              • Accessibility
                              • Opquast label

                              93. If any data entered in the form are rejected, the fields containing the rejected data are highlighted for the user.

                              Objectif:

                              To provide feedback to users on the actions they just performed

                              To guide users directly to the items with which they must interact

                              Checklist
                              • Best practices
                              Project phase
                              • Prototype
                              • Integration
                              Tag
                              • Usability
                              • Accessibility
                              • Opquast label

                              94. If any data entered in the form are rejected, the reason(s) why are explained to the user.

                              Objectif:

                              To help users understand what is expected and, by doing so, facilitate their progression to the next step.

                              To prevent user frustration in the face of mistakes for which they don’t have an immediate solution.

                              Checklist
                              • Best practices
                              Project phase
                              • Prototype
                              • Integration
                              Tag
                              • Usability
                              • Accessibility
                              • Opquast label

                              95. If any data entered in the form are rejected, the user can change any of the input data.

                              Objectif:

                              To give users control over all of the information that they provide

                              To simplify the correction of mistakes made by users

                              To allow users to edit the information they want to change

                              To prevent the user from leaving the form before it is submitted

                              Checklist
                              • Best practices
                              Project phase
                              • Development
                              Tag
                              • Usability
                              • Opquast label

                              96. For forms divided over several pages, an overall summary is displayed before the final version is submitted.

                              Objectif:

                              To give users an overview of what they entered on the previous pages

                              To allow users to reviews all of the information for a complex procedure, before submitting it.

                              Checklist
                              • Best practices
                              Project phase
                              • Prototype
                              • Development
                              Tag
                              • Usability
                              • Opquast label

                              97. The page displayed after the form’s submission allows the user to return to their navigation directly.

                              Objectif:

                              To avoid putting your users off by taking them to a dead-end page, including by means of the browser’s“ Previous page” function.

                              To limit the risk of duplicate form submissions

                              Checklist
                              • Best practices
                              Project phase
                              • Development
                              Tag
                              • Usability

                              98. Form submission is followed by a message indicating whether or not the action was successful.

                              Objectif:

                              To give the user immediate, explicit feedback on the action they just performed

                              To prevent user frustration when they think the process was a success, but there was, in fact, a problem.

                              Checklist
                              • Best practices
                              Project phase
                              • Prototype
                              • Development
                              Tag
                              • Usability
                              • Opquast label

                              99. Complex processes are accompanied by a list of their steps.

                              Objectif:

                              To give users visibility of the actions they are going to be performing (time, order of steps, information required toc omplete them, etc.).

                              To prevent users from feeling trapped in a process that takes longer than expected.

                              Checklist
                              • Best practices
                              Project phase
                              • Prototype
                              Tag
                              • Usability
                              • Opquast label

                              100. The current step in a complex process is indicated.

                              Objectif:

                              To allow users to determine their progress in a process

                              To reassure users when engaged in a complex process

                              Checklist
                              • Best practices
                              Project phase
                              • Prototype
                              • Design
                              Tag
                              • Usability
                              • Opquast label

                              101. Each step in a complex process allows the user to go back to the previous step.

                              Objectif:

                              To simplify the use of forms divided over several pages in a row

                              To reduce the risk of input errors

                              To limit the risk of abandoning the process

                              Checklist
                              • Best practices
                              Project phase
                              • Prototype
                              • Development
                              Tag
                              • Usability

                              102. The user is warned that they will lose information if they go back using their browser’s history during a complex process.

                              Objectif:

                              To simplify the use of forms divided over several pages in a row

                              To limit the risk of abandoning the process

                              Checklist
                              • Best practices
                              Project phase
                              • Prototype
                              • Development
                              Tag
                              • Usability

                              103. Navigating through a complex process does not cause any previously-submitted data to be lost.

                              Objectif:

                              To simplify input and corrections in forms divided into multiple steps

                              To limit the risk of abandoning the procedure

                              Checklist
                              • Best practices
                              Project phase
                              • Development
                              Tag
                              • Usability

                              104. Copy-and-paste is possible in the form’s fields.

                              Objectif:

                              To simplify form completion

                              Checklist
                              • Best practices
                              Project phase
                              • Integration
                              Tag
                              • Usability
                              • Opquast label

                              105. The items in a drop-down list are grouped together appropriately, where applicable.

                              Objectif:

                              To allow technical aids to return a list to the user whose organization is clear to see, and that simplifies moving from one item on the list to another.

                              To foster the accurate rendering of complex drop-down lists in every browser

                              Checklist
                              • Best practices
                              Project phase
                              • Integration
                              Tag
                              • Usability
                              • Accessibility

                              106. The lists of form options are presented in an identifiable order.

                              Objectif:

                              To give users fast access to the item they want in a list

                              Checklist
                              • Best practices
                              Project phase
                              • Integration
                              Tag
                              • Usability
                              • Accessibility

                              107. Each link has a proper label in the source code.

                              Objectif:

                              To prevent users from only having a hard-to-understand URL as a label

                              To avoid links that become invisible when CSS styles or background images are not handled.

                              Checklist
                              • Best practices
                              Project phase
                              • Integration
                              Tag
                              • Usability
                              • Accessibility
                              • Opquast label

                              108. Underlining cannot be used for elements other than hyperlinks.

                              Objectif:

                              To prevent pointless clicking on underlined content perceived as hyperlinks

                              To simplify the identification of links

                              Checklist
                              • Best practices
                              Project phase
                              • Design
                              • Content
                              Tag
                              • Usability
                              • Opquast label

                              109. Hyperlinks are visually differentiated from the rest of the content.

                              Objectif:

                              To allow users to easily identify links in the text, as well as navigation blocks.

                              To improve the visibility and affordance of links in different browsing environments

                              Checklist
                              • Best practices
                              Project phase
                              • Design
                              Tag
                              • Usability
                              • Accessibility
                              • Opquast label

                              110. The site applies a different style to visited and unvisited links.

                              Objectif:

                              To facilitate the identification of content that has already been visited

                              To facilitate the identification of content that has yet to be explored

                              To encourage users to navigate to new pages

                              Checklist
                              • Best practices
                              Project phase
                              • Design
                              • Integration
                              Tag
                              • Usability

                              111. The site does not prohibit or restrict incoming links.

                              Objectif:

                              To facilitate referencing through backlinks

                              To increase the site’s visibility to users

                              Checklist
                              • Best practices
                              Project phase
                              • Content
                              Tag
                              • SEO
                              • Opquast label

                              112. Hovering over, or activating, hyperlinks does not alter the page layout.

                              Objectif:

                              To limit problems clicking on a link when it takes up more space when hovered over or activated.

                              To reduce the flickering or shifting of content when hovering over a link or using keyboard focus on it.

                              Checklist
                              • Best practices
                              Project phase
                              • Integration
                              Tag
                              • Usability

                              113. Hyperlinks of the same nature have identical colors, shapes and behaviors on all pages.

                              Objectif:

                              To accelerate user learning about how the interface works

                              To improve users’ identification of links and their respective functions

                              Checklist
                              • Best practices
                              Project phase
                              • Prototype
                              • Design
                              Tag
                              • Usability

                              114. All hyperlinks internal to the site are valid.

                              Objectif:

                              To avoid 404 errors while browsing

                              To facilitate fast access to all of the content

                              Checklist
                              • Best practices
                              Project phase
                              • Development
                              Tag
                              • Usability
                              • SEO

                              115. Each hyperlink’s label describes either its function or the nature of its target.

                              Objectif:

                              To allow users to accurately identify the nature of the link and prevent incorrect actions.

                              To enable indexing tools to associate a label with a resource

                              To allow screen readers to explicitly indicate the target and, as a result, to prevent user disorientation.

                              Checklist
                              • Best practices
                              Project phase
                              • Content
                              Tag
                              • Accessibility
                              • SEO
                              • Opquast label

                              116. Consecutive hyperlinks are separated visually.

                              Objectif:

                              To avoid confusion between two consecutive links

                              To improve the readability of links and content

                              Checklist
                              • Best practices
                              Project phase
                              • Design
                              • Content
                              Tag
                              • Usability

                              117. Internal and external hyperlinks are differentiated.

                              Objectif:

                              To clearly inform users that they are about to leave the online service that they were visiting.

                              To facilitate the identification of external links

                              Checklist
                              • Best practices
                              Project phase
                              • Design
                              Tag
                              • Usability
                              • Internationalization

                              118. The identity of the author, the company or the organization is provided.

                              Objectif:

                              To reassure users, by allowing them to directly identify the author (in the broadest sense of the term)

                              To limit the risk of mistrust

                              Checklist
                              • Best practices
                              Project phase
                              • Content
                              Tag
                              • SEO

                              119. The identity of the person or the service responsible for the content is provided.

                              Objectif:

                              To allow users to unambiguously identify a physical person capable of answering any questions about the available content or of assuming responsibility for that content.

                              Checklist
                              • Best practices
                              Project phase
                              • Content
                              Tag
                              • Usability

                              120. The homepage explains the nature of the content and services on offer.

                              Objectif:

                              To give users an immediate view of the nature of the website and the content it offers.

                              To avoid needless searching

                              Checklist
                              • Best practices
                              Project phase
                              • Prototype
                              • Content
                              Tag
                              • SEO

                              121. The name of the website and/or its author is displayed on every page.

                              Objectif:

                              To allow users to immediately and continuously identify the author, the entity administrating the website or the site itself, as the case may be.

                              Checklist
                              • Best practices
                              Project phase
                              • Prototype
                              • Content
                              Tag
                              • SEO

                              122. If the site is reserved or intended for a specific audience, that audience is mentioned, at least on the homepage.

                              Objectif:

                              To avoid pointless visits

                              To give users a warning

                              Checklist
                              • Best practices
                              Project phase
                              • Prototype
                              • Content
                              Tag
                              • Usability

                              123. The complete address and phone number of companies and organizations can be reached from all of the site’s pages.

                              Objectif:

                              To give interested users the possibility of easily accessing the entity’s telephone and mailing contact information.

                              Checklist
                              • Best practices
                              Project phase
                              • Prototype
                              • Content
                              Tag
                              • SEO

                              124. The site’s root contains instructions for web crawlers.

                              Objectif:

                              To enable targeted referencing

                              To improve guidance for search tools

                              Checklist
                              • Best practices
                              Project phase
                              • Development
                              Tag
                              • Ecodesign
                              • SEO
                              • Opquast label

                              125. Each page’s source code contains metadata that describe the content.

                              Objectif:

                              To enable search and indexing tools to extract information about the pages’ content and, as a result, to improve the search results returned to users.

                              Checklist
                              • Best practices
                              Project phase
                              • Integration
                              • Content
                              Tag
                              • SEO
                              • Opquast label

                              126. The source code of the pages contains a valid call to a favourite icon (“favicon”)

                              Objectif:

                              To improve the visual identification of the site and its pages

                              To facilitate identification in the browser and the favorites or bookmarks

                              To enable all browsers to display, call and, potentially, memorize the favicon.

                              Checklist
                              • Best practices
                              Project phase
                              • Integration
                              Tag
                              • Usability
                              • Opquast label

                              127. The extension used is consistent with the entity’s identity, activities, geographical area or domain name.

                              Objectif:

                              To contribute to the immediate understanding of the site’s identity, activities or geographic area.

                              To improve users’ ability to memorize the website’s address and find it again, if they forget it.

                              Checklist
                              • Best practices
                              Project phase
                              • Development
                              Tag
                              • Usability
                              • SEO

                              128. The website provides a sitemap file listing the content to be crawled.

                              Objectif:

                              To provide summary information about all of the available content that is machine-readable.

                              The sitemap file indicates all of the content for major search engines to index. This is primarily useful for websites with great depth, like online catalogs of thousands of products, and sites whose content is hard to read in a linear fashion, like encyclopedias.

                              It is of little to no use for sites with just a few pages, although the file’s presence will not be harmful to them.

                              Checklist
                              • Best practices
                              Project phase
                              • Development
                              Tag
                              • Ecodesign
                              • SEO
                              • Opquast label

                              129. If the site claims to adhere to one or more standards or guidelines, a link is provided to each of them.

                              Objectif:

                              To simplify users’ understanding of the quality, accessibility and other rules applied to the website.

                              To increase confidence in the information provided on the website

                              Checklist
                              • Best practices
                              Project phase
                              • Content
                              Tag
                              • Trust
                              • Personal data

                              130. The country code is provided for all phone numbers

                              Objectif:

                              To enable the immediate use of telephone contacts, regardless of the user’s environment.

                              Checklist
                              • Best practices
                              Project phase
                              • Content
                              Tag
                              • Internationalization

                              131. The country is mentioned for all mailing addresses.

                              Objectif:

                              To allow users to immediately identify the country associated with the mailing address, unambiguously and without having to make use of other information (city/town, region, zip code or phone number) to determine it.

                              Checklist
                              • Best practices
                              Project phase
                              • Content
                              Tag
                              • Internationalization

                              132. Each page’s source code specifies the content’s main language.

                              Objectif:

                              To cultivate content indexing by language

                              To facilitate machine translation

                              To enable correct reading of the content by a synthesized speech tool

                              Checklist
                              • Best practices
                              Project phase
                              • Integration
                              Tag
                              • Accessibility
                              • Internationalization
                              • SEO
                              • Opquast label

                              133. The main language of a link’s target page is provided, if different from the original page.

                              Objectif:

                              To allow users and navigation tools to anticipate the change in language mid-navigation.

                              To prevent users from being taken to pages whose language they don’t understand

                              Checklist
                              • Best practices
                              Project phase
                              • Content
                              Tag
                              • Usability
                              • Internationalization

                              134. Each language change is indicated.

                              Objectif:

                              To enable technical aids to correctly interpret content expressed in another language.

                              To simplify the work of machine translation tools

                              To enable web crawlers to extract strings of characters in a given language

                              Checklist
                              • Best practices
                              Project phase
                              • Content
                              Tag
                              • Accessibility
                              • Internationalization

                              135. Links to translated versions point directly to the current page’s translation.

                              Objectif:

                              To provide direct, immediate access to translations of the current page

                              Checklist
                              • Best practices
                              Project phase
                              • Content
                              Tag
                              • Usability
                              • Internationalization

                              136. Links to equivalent versions of a page or site are written in the target language.

                              Objectif:

                              To allow users to immediately identify the relevant link

                              To make links that were specially created for a specific audience understandable

                              Checklist
                              • Best practices
                              Project phase
                              • Content
                              Tag
                              • Usability
                              • Internationalization

                              137. The server does not force redirects from the desktop version to the mobile version.

                              Objectif:

                              To leave the choice of version to the users and their own personal preferences

                              Checklist
                              • Best practices
                              Project phase
                              • Development
                              Tag
                              • Usability
                              • Mobile

                              138. Users can switch between the website’s mobile and desktop versions from each page.

                              Objectif:

                              To allow users to choose the rendering mode that is the best suited to their preferences and their environments.

                              Checklist
                              • Best practices
                              Project phase
                              • Prototype
                              Tag
                              • Usability
                              • Mobile

                              139. The website does not block the browser’s zoom functionalities.

                              Objectif:

                              To allow users to adapt the rendering to their needs or preferences, by means of the graphic zoom.

                              Checklist
                              • Best practices
                              Project phase
                              • Integration
                              Tag
                              • Accessibility
                              • Mobile
                              • Opquast label

                              140. JavaScript alerts and modal pop-up windows inviting the user to install a mobile app only appear once each session.

                              Objectif:

                              To prevent the repetitive imposition of advertising

                              To simplify navigation on the website

                              To prevent any penalties from search engines

                              Checklist
                              • Best practices
                              Project phase
                              • Integration
                              • Development
                              Tag
                              • Usability
                              • Mobile

                              141. The promotion of a mobile app does not use either JavaScript alerts or modal pop-up windows.

                              Objectif:

                              To prevent the repetitive imposition of advertising

                              To simplify navigation on the website

                              To prevent any penalties from search engines

                              Checklist
                              • Best practices
                              Project phase
                              • Prototype
                              Tag
                              • Usability
                              • Opquast label

                              142. The website offers one or more mechanisms for adapting to mobile devices.

                              Objectif:

                              To facilitate access on mobile devices

                              To improve your positioning in web crawlers that take this criterion into account.

                              Checklist
                              • Best practices
                              Project phase
                              • Design
                              • Integration
                              Tag
                              • Usability
                              • Mobile
                              • Opquast label

                              143. Email, URL, telephone, number, search, password, and date and time input fields are assigned an appropriate type.

                              Objectif:

                              To allow the use of virtual keyboards adapted to the different input modes on mobile devices.

                              To facilitate submission of the input data

                              Checklist
                              • Best practices
                              Project phase
                              • Integration
                              • Development
                              Tag
                              • Usability
                              • Mobile
                              • Opquast label

                              144. Phone numbers can be enabled using the appropriate protocol.

                              Objectif:

                              To simplify the use of telephone numbers, particularly on mobile devices

                              Checklist
                              • Best practices
                              Project phase
                              • Integration
                              • Development
                              Tag
                              • Usability
                              • Mobile

                              145. Each iframe has its own description.

                              Objectif:

                              To allow for alternative renderings of iframes in the form of a correctly-labeled link to the included content.

                              Checklist
                              • Best practices
                              Project phase
                              • Integration
                              Tag
                              • Accessibility

                              146. The site does not use framesets.

                              Objectif:

                              To improve access and navigation for people with disabilities

                              To avoid problems with printing or favoriting

                              To improve referencing by avoiding indexing orphan pages

                              Checklist
                              • Best practices
                              Project phase
                              • Integration
                              Tag
                              • Usability

                              147. It is possible to go back to the homepage from any page.

                              Objectif:

                              To let users return to the homepage if they get disoriented

                              To identify the main link for accessing the site

                              Checklist
                              • Best practices
                              Project phase
                              • Prototype
                              Tag
                              • Usability

                              148. The user is warned before new windows are opened.

                              Objectif:

                              To allow users to anticipate what will happen when a link is activated

                              To prevent users of technical aids from becoming disoriented when a new window opens, which is not always perceptible and which disrupts the use of the browsing history, in particular.

                              Checklist
                              • Best practices
                              Project phase
                              • Integration
                              Tag
                              • Accessibility

                              149. Navigating the website does not open any pop-up windows.

                              Objectif:

                              To allow users to navigate the website without having to perform any particular actions during their navigation.

                              To prevent users of technical aids from becoming disoriented when a new window opens, which will not always be perceptible and which disrupts the use of the browsing history, in particular, or hides the main window on a screen reader.

                              Checklist
                              • Best practices
                              Project phase
                              • Prototype
                              Tag
                              • Usability
                              • Accessibility
                              • Opquast label

                              150. Mechanisms for closing windows are visually attached to their content.

                              Objectif:

                              To reduce the time it takes to learn to use the interface

                              To speed up access to the content

                              To simplify navigation

                              Checklist
                              • Best practices
                              Project phase
                              • Design
                              Tag
                              • Usability

                              151. Mechanisms for closing windows are immediately available.

                              Objectif:

                              To reduce the time it takes to learn to use the interface

                              To speed up access to the content

                              To reduce the bounce rate

                              Checklist
                              • Best practices
                              Project phase
                              • Prototype
                              Tag
                              • Usability

                              152. New windows that are specially sized and modal windows are all equipped with explicit close buttons.

                              Objectif:

                              To give users explicit information

                              To speed up access to the content

                              Checklist
                              • Best practices
                              Project phase
                              • Prototype
                              • Integration
                              Tag
                              • Usability

                              153. Mechanisms for closing windows are shown in the same location on every page.

                              Objectif:

                              To reduce the time it takes to learn to use the interface

                              To speed up access to the content

                              To simplify navigation

                              Checklist
                              • Best practices
                              Project phase
                              • Prototype
                              Tag
                              • Usability

                              154. The site does not resize the browser window.

                              Objectif:

                              To let users control their browsers and their viewing interfaces

                              To not disorient or surprise them with an unexpected change to those

                              Checklist
                              • Best practices
                              Project phase
                              • Prototype
                              Tag
                              • Usability

                              155. Keyboard focus has not been removed or masked.

                              Objectif:

                              To allow navigation using the keyboard or input devices or other mechanisms that are not reliant on the mouse.

                              Checklist
                              • Best practices
                              Project phase
                              • Integration
                              Tag
                              • Accessibility

                              156. The site can be navigated in its entirety using only a keyboard.

                              Objectif:

                              To allow keyboard navigation for users with a preference for that practice.

                              To allow content to be accessed and services to be used, regardless of the input device, so as to make them accessible by users of technical aids (screenreaders, for example) who only utilize the keyboard or a more specific device based on the same mechanisms as a keyboard (like a push button)

                              Checklist
                              • Best practices
                              Project phase
                              • Integration
                              Tag
                              • Accessibility
                              • Opquast label

                              157. Keyboard navigation is set up in a predictable order.

                              Objectif:

                              To enable keyboard navigation

                              To not put off the user

                              Checklist
                              • Best practices
                              Project phase
                              • Integration
                              Tag
                              • Accessibility

                              158. The site does not contain any links to pages under construction.

                              Objectif:

                              To prevent users from useless clicking

                              To reduce the needless consumption of bandwidth

                              To offer value-added content

                              Checklist
                              • Best practices
                              Project phase
                              • Content
                              Tag
                              • Usability
                              • SEO

                              159. Each page displays information as to where it is located in the site’s tree structure.

                              Objectif:

                              To let users identify their location on the website

                              To simplify scanning by search engines

                              To facilitate navigation of the content tree

                              Checklist
                              • Best practices
                              Project phase
                              • Prototype
                              Tag
                              • Usability
                              • Opquast label

                              160. The site offers an internal search engine.

                              Objectif:

                              To provide users with an alternative navigation solution and fast access to the content associated with the keywords.

                              Checklist
                              • Best practices
                              Project phase
                              • Prototype
                              Tag
                              • Accessibility
                              • Ecodesign
                              • Opquast label

                              161. The search result page indicates the number of results, the number of pages of results, and the number of results per page.

                              Objectif:

                              To give users access to all of the essential information related to the search that they ran.

                              Checklist
                              • Best practices
                              Project phase
                              • Prototype
                              • Development
                              Tag
                              • Usability

                              162. Each search result page can be reached by means of a web address.

                              Objectif:

                              To allow users to share search results or share them as a bookmark.

                              Checklist
                              • Best practices
                              Project phase
                              • Development
                              Tag
                              • Usability
                              • Ecodesign

                              163. The site map can be reached from every page.

                              Objectif:

                              To provide users with a solution, in case they become disoriented, for navigating and getting their bearings within the site and for viewing all of the contents and the size of the site.

                              To encourage content managers to provide graphic representations and streamline their content.

                              Checklist
                              • Best practices
                              Project phase
                              • Prototype
                              Tag
                              • Accessibility
                              • SEO
                              • Opquast label

                              164. Navigation blocks of the same nature are in the same place on every page.

                              Objectif:

                              To facilitate users’ learning of how to navigate the interface

                              To simplify the identification of information

                              Checklist
                              • Best practices
                              Project phase
                              • Prototype
                              • Design
                              Tag
                              • Usability
                              • Accessibility

                              165. Navigation icons are provided with explicit legends.

                              Objectif:

                              To reduce the time it takes to learn to use the interface

                              To facilitate your users’ understanding of the icons

                              To reduce the risk of error

                              Checklist
                              • Best practices
                              Project phase
                              • Design
                              • Integration
                              Tag
                              • Usability

                              166. Links to external software have an explicit label.

                              Objectif:

                              To avoid the unexpected launch of software other than the web browser on the client workstation

                              Checklist
                              • Best practices
                              Project phase
                              • Content
                              Tag
                              • Usability
                              • Accessibility

                              167. If the site is not restricted to a specific public, its content can be accessed directly.

                              Objectif:

                              To allow users to immediately start navigating on the resource they requested.

                              Checklist
                              • Best practices
                              Project phase
                              • Prototype
                              Tag
                              • Usability
                              • SEO

                              168. Each page provides skip links at the beginning of its source code.

                              Objectif:

                              To allow users visiting the pages in a linear fashion (in voice mode) or a semi-linear way (on a small screen) to not have to scroll through all of each page’s elements in order to access the content.

                              To provide shortcuts that accelerate keyboard navigation and that avoid the repetition of keyboard actions in order to browse through the page and get to the zone they want.

                              Checklist
                              • Best practices
                              Project phase
                              • Design
                              • Integration
                              Tag
                              • Accessibility

                              169. An unsubscribe link is provided in each newsletter.

                              Objectif:

                              To allow subscribers to stop receiving a newsletter

                              Checklist
                              • Best practices
                              Project phase
                              • Prototype
                              • Development
                              Tag
                              • Usability
                              • Newsletter
                              • Personal data

                              170. Unsubscribing from within the newsletter does not require email confirmation.

                              Objectif:

                              To not force an extra step on the users when not necessarily in that context

                              Checklist
                              • Best practices
                              Project phase
                              • Development
                              Tag
                              • Usability
                              • Ecodesign
                              • Newsletter
                              • Personal data

                              171. Subscribing to newsletters is subject to a confirmation process.

                              Objectif:

                              To prevent third parties from subscribing someone else to a newsletter

                              To check that the email address was input correctly

                              Checklist
                              • Best practices
                              Project phase
                              • Development
                              Tag
                              • Usability
                              • Newsletter
                              • Personal data

                              172. It is possible to unsubscribe from newsletters from the website.

                              Objectif:

                              To allow users to unsubscribe, without necessarily having to send out an email

                              Checklist
                              • Best practices
                              Project phase
                              • Development
                              Tag
                              • Usability
                              • Newsletter
                              • Personal data

                              173. The latest edition of the newsletter is available online.

                              Objectif:

                              To give users an idea of the newsletter that is sent out to subscribers

                              To allow users to access the newsletter outside the constraints of email

                              To boost your content’s referencing

                              Checklist
                              • Best practices
                              Project phase
                              • Prototype
                              Tag
                              • Usability
                              • Newsletter

                              174. Newsletter archives are available online.

                              Objectif:

                              To simplify the consultation of your archived newsletters

                              To give users an idea of the newsletter that is sent out to subscribers

                              To boost your content’s referencing

                              Checklist
                              • Best practices
                              Project phase
                              • Prototype
                              Tag
                              • SEO
                              • Newsletter

                              175. The newsletters’ frequency can be found before subscribing.

                              Objectif:

                              To tell users, before they sign up, how often they can expect to receive the newsletter

                              Checklist
                              • Best practices
                              Project phase
                              • Prototype
                              • Content
                              Tag
                              • Usability
                              • Newsletter
                              • Personal data

                              176. The design is consistent throughout the site.

                              Objectif:

                              To ensure consistency and continuity while visiting and navigating

                              To provide continuous identification of the visited online service

                              Checklist
                              • Best practices
                              Project phase
                              • Design
                              Tag
                              • Usability

                              177. The display font size is expressed in variable units, not fixed units.

                              Objectif:

                              To allow users with browsers that don’t support the enlargement of fixed-size fonts to enlarge those fonts with ease.

                              Checklist
                              • Best practices
                              Project phase
                              • Integration
                              Tag
                              • Accessibility

                              178. The site provides at least one style sheet for printing.

                              Objectif:

                              To allow content to be printed in a form that is appropriate to the medium

                              Checklist
                              • Best practices
                              Project phase
                              • Integration
                              Tag
                              • Usability

                              179. The content of each page can be printed without navigation blocks.

                              Objectif:

                              To improve the readability and the relevance of the printed content

                              To streamline the space used by the printed content and save paper

                              Checklist
                              • Best practices
                              Project phase
                              • Integration
                              Tag
                              • Usability
                              • Ecodesign

                              180. A generic font family is listed as the last alternative in font family lists.

                              Objectif:

                              To enable your content to display correctly, even when the planned fonts don’t exist on a user’s system.

                              Checklist
                              • Best practices
                              Project phase
                              • Integration
                              Tag
                              • Robustness

                              181. Content is presented with sufficient contrast to its background.

                              Objectif:

                              To provide good readability of your content

                              To limit the mental load while reading

                              Checklist
                              • Best practices
                              Project phase
                              • Design
                              Tag
                              • Accessibility
                              • Opquast label

                              182. Words are capitalized for decorative purposes by means of styles.

                              Objectif:

                              To enable cutting-and-pasting of content, regardless of any all-caps formatting.

                              To simplify the adaptation of formatting to users with trouble reading texts inall caps.

                              Checklist
                              • Best practices
                              Project phase
                              • Integration
                              • Content
                              Tag
                              • Usability

                              183. Styles do not justify the text.

                              Objectif:

                              To simplify reading onthe screen, especially for people with dyslexia

                              Checklist
                              • Best practices
                              Project phase
                              • Design
                              Tag
                              • Accessibility

                              184. Content is only designated by its shape or its position on the screen.

                              Objectif:

                              To allow users to understand the information without having access to the visual medium or when its rendering has been altered.

                              Checklist
                              • Best practices
                              Project phase
                              • Content
                              Tag
                              • Accessibility

                              185. The identity of third-parties involved in transactions is provided

                              Objectif:

                              To give users information about the third-party providers involved in their transactions.

                              Checklist
                              • Best practices
                              Project phase
                              • Content
                              Tag
                              • Security
                              • Personal data

                              186. The privacy policy can be reached from any page

                              Objectif:

                              To give users access to the conditions under which their personal data are conserved

                              Checklist
                              • Best practices
                              Project phase
                              • Content
                              Tag
                              • Security
                              • Personal data

                              187. The site provides a way to reinitialise a password if it's lost, stolen or forgotten

                              Objectif:

                              To allow users to access their accounts, even if they have lost their passwords.

                              To simplify user account management.

                              To boost security, by preventing the storage of passwords that are unencrypted so they can be re-sent to their users.

                              Checklist
                              • Best practices
                              Project phase
                              • Development
                              Tag
                              • Security
                              • Opquast label

                              188. Passwords can be chosen and changed by the user

                              Objectif:

                              To allow users to choose personalized passwords.

                              To avoid users struggling to remember their passwords every time they log in.

                              Checklist
                              • Best practices
                              Project phase
                              • Development
                              Tag
                              • Usability
                              • Security
                              • Opquast label

                              189. User passwords allow graphic characters from the ASCII table.

                              Objectif:

                              To foster high password security.

                              Checklist
                              • Best practices
                              Project phase
                              • Development
                              Tag
                              • Security

                              190. There is a mechanism that informs users of their chosen password’s level of security.

                              Objectif:

                              To inform users of the level of security of their selected passwords and, therefore, the risk of being hacked.

                              Checklist
                              • Best practices
                              Project phase
                              • Development
                              Tag
                              • Security

                              191. Security certificates are signed and valid.

                              Objectif:

                              To allow users to check the certificate’s validity and to contribute to transactional security.

                              Checklist
                              • Best practices
                              Project phase
                              • Development
                              Tag
                              • Security
                              • Opquast label

                              192. Sensitive data are not transmitted in clear text in URLs.

                              Objectif:

                              To prevent sensitive data from being made public or stored unencrypted at any stage in accessing a page (ISP, proxy, web server, browser history, third-party services, etc.).

                              To allow users to enter sensitive data, safe in the knowledge that they will be protected and kept confidential.

                              Checklist
                              • Best practices
                              Project phase
                              • Development
                              Tag
                              • Security

                              193. Sensitive data are transmitted securely and are identified as such.

                              Objectif:

                              To reassure users.

                              To allow users to enter sensitive data, safe in the knowledge that they will be protected.

                              To minimize the risk of fraudulent use of user data.

                              Checklist
                              • Best practices
                              Project phase
                              • Development
                              Tag
                              • Trust
                              • Security
                              • Opquast label

                              194. The headers sent by the server disable automatic detection of each resource’s MIME type.

                              Objectif:

                              To reduce the risk of downloading dangerous hidden content.

                              Checklist
                              • Best practices
                              Project phase
                              • Development
                              Tag
                              • Security

                              195. The server indicates each resource’s MIME type.

                              Objectif:

                               To reduce the risk of downloading dangerous hidden content.

                              Checklist
                              • Best practices
                              Project phase
                              • Development
                              Tag
                              • Security

                              196. Information is provided on transaction security.

                              Objectif:

                              To inform users about the security of exchanges of sensitive data.

                              Checklist
                              • Best practices
                              Project phase
                              • Content
                              Tag
                              • Security
                              • Opquast label

                              197. The purpose of cookies, and the consequences of refusing them, are explained to users.

                              Objectif:

                              To inform users about the use of cookies.

                              To explain their role and their purpose.

                              Checklist
                              • Best practices
                              Project phase
                              • Content
                              Tag
                              • Security
                              • Opquast label
                              • Personal data

                              198. The process for accessing and modifying personal data is explained.

                              Objectif:

                              To inform users of how their personal data will be used.

                              To boost confidence in the site or service.

                              To simplify the management of requests related to personal data.

                              Checklist
                              • Best practices
                              Project phase
                              • Content
                              Tag
                              • Trust
                              • Personal data

                              199. Account creation is subject to a confirmation process.

                              Objectif:

                              To reduce the risk of users being registered without their knowledge.

                              Checklist
                              • Best practices
                              Project phase
                              • Development
                              Tag
                              • Security
                              • Personal data

                              200. Accounts can be created without the need to use a third-party identification system.

                              Objectif:

                              To let users choose whether or not they want to use a third-party service.

                              To provide an alternate means of access to the service.

                              To provide a means of access under the control of the service’s administrators.

                              To limit your dependence on a third party, whose policies and technical and sales strategy will undoubtedly change over time.

                              Checklist
                              • Best practices
                              Project phase
                              • Development
                              Tag
                              • Usability
                              • Security
                              • Personal data

                              201. Accounts and subscriptions opened online can also be closed online.

                              Objectif:

                              To spare the user complicated procedures in order to leave the service.

                              To let the user know, right off the bat, that they won’t be trapped into the service.

                              To cut the cost of user account management.

                              To boost confidence in the site or service.

                              To improve your reputation and reduce the risk of bad press.

                              Checklist
                              • Best practices
                              Project phase
                              • Development
                              Tag
                              • Trust
                              • Personal data

                              202. The server does not send lists of files in directories that don’t have index pages.

                              Objectif:

                              To prevent the display of lists of files contained in a directory.

                              To improve the server’s security.

                              To reduce the risk of intrusion

                              Checklist
                              • Best practices
                              Project phase
                              • Development
                              Tag
                              • Security

                              203. The server sends activation information for protection against cross-site scripting.

                              Objectif:

                              To reduce the risk of downloading dangerous hidden content.

                              Checklist
                              • Best practices
                              Project phase
                              • Development
                              Tag
                              • Security

                              204. The server sends information that indicates which domains are allowed to embed its pages in frames.

                              Objectif:

                              To reduce the risk of your content being used in misleading ways.

                              Checklist
                              • Best practices
                              Project phase
                              • Development
                              Tag
                              • Security

                              205. The website offers a security mechanism that limits the sources of its content.

                              Objectif:

                              To reduce the risk of executing or serving content that is undesirable or that comes from an unauthorized source.

                              Checklist
                              • Best practices
                              Project phase
                              • Integration
                              • Development
                              Tag
                              • Security

                              206. The server sends information to enable content caching.

                              Objectif:

                              To speed up the display of content and enable a smoother navigation experience.

                              To reduce bandwidth costs.

                              Checklist
                              • Best practices
                              Project phase
                              • Development
                              Tag
                              • Performance
                              • Opquast label

                              207. The server sends a 404 HTTP error code for resources not found.

                              Objectif:

                              To enable the automated detection of incorrect URLs.

                              To send reliable information to the browser.

                              Checklist
                              • Best practices
                              Project phase
                              • Development
                              Tag
                              • Ecodesign
                              • SEO

                              208. The server sends a personalized 404 error page.

                              Objectif:

                              To inform users of the error encountered, of the server’s continuing operation, and to verify any problems with their connectivity.

                              Checklist
                              • Best practices
                              Project phase
                              • Design
                              • Development
                              Tag
                              • Usability
                              • Opquast label

                              209. The server sends a personalized 403 “Forbidden” error page.

                              Objectif:

                              To reassure users that they are still on the same website.

                              To allow the webmaster to provide guidance to your users.

                              To inform users of the error encountered, of the server’s continuing operation, and to confirm the problem is not with their connectivity.

                              Checklist
                              • Best practices
                              Project phase
                              • Design
                              • Development
                              Tag
                              • Usability

                              210. The main navigation menu is displayed on personalized error pages.

                              Objectif:

                              To save users from any interruption in their navigation, landing on dead-end pages, or being forced to use their browser’s Back button.

                              Checklist
                              • Best practices
                              Project phase
                              • Prototype
                              • Development
                              Tag
                              • Usability
                              • Opquast label

                              211. The server compresses content, if the client accepts compressed content.

                              Objectif:

                              To improve the speed of the page’s rendering.

                              To reduce bandwidth costs.

                              Checklist
                              • Best practices
                              Project phase
                              • Development
                              Tag
                              • Ecodesign
                              • Performance
                              • Opquast label

                              212. Headers sent by the server contain information about the character set employed.

                              Objectif:

                              To allow the browser to choose the right character encoding to display the page.

                              Checklist
                              • Best practices
                              Project phase
                              • Integration
                              • Development
                              Tag
                              • SEO

                              213. The server respects the preferred language order specified in the user agents.

                              Objectif:

                              To serve pages in the desired language.

                              Checklist
                              • Best practices
                              Project phase
                              • Development
                              Tag
                              • Usability
                              • Internationalization

                              214. Style sheets are minified.

                              Objectif:

                              To minimize the quantity of data for users to download.

                              To improve performance.

                              Checklist
                              • Best practices
                              Project phase
                              • Integration
                              Tag
                              • Ecodesign
                              • Performance

                              215. Scripts are minified.

                              Objectif:

                              To speed up the display of your pages.

                              To improve performance.

                              To reduce the quantity of data to download.

                              Checklist
                              • Best practices
                              Project phase
                              • Integration
                              Tag
                              • Ecodesign
                              • Performance

                              216. Script functions are placed in external files.

                              Objectif:

                              To minimize the quantity of data for users to download.

                              To improve performance.

                              Checklist
                              • Best practices
                              Project phase
                              • Integration
                              Tag
                              • Ecodesign
                              • Performance
                              • Opquast label

                              217. The addresses of the site and its subdomains work with and without the “www” prefix.

                              Objectif:

                              To allow users to reach the site’s homepage, even if they forget to enter the “www” prefix.

                              Checklist
                              • Best practices
                              Project phase
                              • Development
                              Tag
                              • Usability
                              • Ecodesign

                              218. The source codes of syndication feeds indicate their update intervals.

                              Objectif:

                              To allow users to configure the frequency at which their tools check the syndication feed.

                              To reduce server load.

                              Checklist
                              • Best practices
                              Project phase
                              • Development
                              Tag
                              • Ecodesign
                              • Performance
                              • SEO
                              • Syndication

                              219. Syndication feeds can be detected by user agents.

                              Objectif:

                              To allow browsers to indicate, in their interfaces, the presence of a syndication feed associated with the current page

                              Checklist
                              • Best practices
                              Project phase
                              • Integration
                              Tag
                              • Usability
                              • Syndication

                              220. Hyperlinks in syndication feeds are absolute.

                              Objectif:

                              To ensure the reliability of links when content is reused.

                              Checklist
                              • Best practices
                              Project phase
                              • Development
                              Tag
                              • Usability
                              • SEO
                              • Syndication

                              221. The site provides at least one link to each syndication feed.

                              Objectif:

                              To allow users to easily subscribe to syndication feeds.

                              Checklist
                              • Best practices
                              Project phase
                              • Integration
                              Tag
                              • Usability
                              • Syndication

                              222. Cells in data tables are linked to their headers.

                              Objectif:

                              To allow technical aids to return the information contained in data tables in a comprehensible way, by informing users of the logical relationships between the table’s content and headers

                              Checklist
                              • Best practices
                              Project phase
                              • Integration
                              Tag
                              • Accessibility
                              • Opquast label

                              223. Titles are provided for any data tables.

                              Objectif:

                              To allow users of technical aids (like screen readers) to easily identify the nature of the information provided in a table.

                              Checklist
                              • Best practices
                              Project phase
                              • Integration
                              • Content
                              Tag
                              • Accessibility

                              224. Linearizing layout tables does not impede the understanding of the content.

                              Objectif:

                              To supply content that is understandable to users whose user agents or technical aids (screen readers) cannot reconstruct the formatting that was initially defined by a table.

                              Checklist
                              • Best practices
                              Project phase
                              • Integration
                              Tag
                              • Accessibility

                              225. Data tables are not replaced by images.

                              Objectif:

                              To give users access to tables that are exploitable by their user agents and that can be reproduced in a way that will always be understandable.

                              Checklist
                              • Best practices
                              Project phase
                              • Integration
                              • Content
                              Tag
                              • Usability
                              • Accessibility
                              • SEO

                              226. Data tables are not simulated using styled text.

                              Objectif:

                              To give users access to tables that are exploitable by their user agents and that can be reproduced in a way that will always be understandable.

                              Checklist
                              • Best practices
                              Project phase
                              • Integration
                              • Content
                              Tag
                              • Accessibility
                              • SEO

                              R1. If content is not accessible, an accessible version is provided.

                              Objectif:
                              Checklist
                              • Recommendations
                              Project phase
                              • Prototype
                              • Integration
                              • Development
                              • Content
                              Tag
                              • Accessibility

                              R2. A long description, correctly associated, complements the alternative of complex images.

                              Objectif:
                              Checklist
                              • Recommendations
                              Project phase
                              • Prototype
                              • Integration
                              • Content
                              Tag
                              • Accessibility

                              R3. Audio captchas can be paused.

                              Objectif:
                              Checklist
                              • Recommendations
                              Project phase
                              • Development
                              Tag
                              • Usability

                              R4. The page's source code includes no error in either the tree of the document or the syntax of tags and attributes.

                              Objectif:
                              Checklist
                              • Recommendations
                              Project phase
                              • Integration
                              • Development
                              Tag
                              • Accessibility
                              • Robustness

                              R5. The page's source code is valid according to the chosen grammar.

                              Objectif:
                              Checklist
                              • Recommendations
                              Project phase
                              • Integration
                              • Development
                              Tag
                              • Robustness

                              R6. Native semantic elements are favoured.

                              Objectif:
                              Checklist
                              • Recommendations
                              Project phase
                              • Integration
                              • Development
                              Tag
                              • Robustness

                              R7. Main regions of the page are identified in the source code.

                              Objectif:
                              Checklist
                              • Recommendations
                              Project phase
                              • Integration
                              • Development
                              Tag
                              • Accessibility

                              R8. Quotes are tagged in an appropriate way in the source code.

                              Objectif:
                              Checklist
                              • Recommendations
                              Project phase
                              • Integration
                              Tag
                              • Accessibility

                              R9. Real dimensions of images are indicated in the source code.

                              Objectif:
                              Checklist
                              • Recommendations
                              Project phase
                              • Integration
                              • Development
                              Tag
                              • Performance

                              R10. Contents and services remain available when scripts are disabled.

                              Objectif:
                              Checklist
                              • Recommendations
                              Project phase
                              • Integration
                              • Development
                              Tag
                              • Robustness

                              R11. The site does not use any technique to block or hinder the display or the reading of the source code.

                              Objectif:
                              Checklist
                              • Recommendations
                              Project phase
                              • Integration
                              • Development
                              Tag
                              • Trust

                              R12. The site does not use any technique to block the use of native functions of the user agents.

                              Objectif:
                              Checklist
                              • Recommendations
                              Project phase
                              • Integration
                              • Development
                              Tag
                              • Usability

                              R13. Each article author is identifiable.

                              Objectif:
                              Checklist
                              • Recommendations
                              Project phase
                              • Prototype
                              • Integration
                              Tag
                              • Trust

                              R14. Sources legitimize the informations or their authors.

                              Objectif:
                              Checklist
                              • Recommendations
                              Project phase
                              • Content
                              Tag
                              • Trust

                              R15. The identity of the translator is provided.

                              Objectif:
                              Checklist
                              • Recommendations
                              Project phase
                              • Content
                              Tag
                              • Internationalization

                              R16. Editorial content is associated with a publication date or period, if required.

                              Objectif:
                              Checklist
                              • Recommendations
                              Project phase
                              • Prototype
                              • Integration
                              Tag
                              • Usability
                              • Trust

                              R17. The date of updating of the contractual contents is provided.

                              Objectif:
                              Checklist
                              • Recommendations
                              Project phase
                              • Content
                              Tag
                              • Trust
                              • Personal data

                              R18. The voting systems, notes and polls indicate the number of voters, the period and the mode of measurement.

                              Objectif:
                              Checklist
                              • Recommendations
                              Project phase
                              • Content
                              Tag
                              • Trust

                              R19. The ortho-typographical rules of the text language are respected.

                              Objectif:
                              Checklist
                              • Recommendations
                              Project phase
                              • Content
                              Tag
                              • Trust

                              R20. The content of the pages do not contain any hidden keywords.

                              Objectif:
                              Checklist
                              • Recommendations
                              Project phase
                              • Content
                              Tag
                              • SEO

                              R21. The display of advertising or sponsored content does not automatically change the layout.

                              Objectif:
                              Checklist
                              • Recommendations
                              Project phase
                              • Integration
                              • Development
                              Tag
                              • Usability

                              R22. is indicated

                              Objectif:
                              Checklist
                              • Recommendations
                              Project phase
                              • Development
                              Tag
                              • SEO

                              R23. Data tables are structured into internal PDF documents.

                              Objectif:
                              Checklist
                              • Recommendations
                              Project phase
                              • Development
                              • Content
                              Tag
                              • Accessibility

                              R24. Ordered and unordered lists are structured into internal PDF documents.

                              Objectif:
                              Checklist
                              • Recommendations
                              Project phase
                              • Development
                              • Content
                              Tag
                              • Accessibility

                              R25. Images have text alternative into internal PDF documents.

                              Objectif:
                              Checklist
                              • Recommendations
                              Project phase
                              • Development
                              • Content
                              Tag
                              • Accessibility

                              R26. PDF documents can be linearized.

                              Objectif:
                              Checklist
                              • Recommendations
                              Project phase
                              • Development
                              • Content
                              Tag
                              • Accessibility

                              R27. A short text alternative describes the purpose of synchronized sound, visual, animated and synchronized media.

                              Objectif:
                              Checklist
                              • Recommendations
                              Project phase
                              • Integration
                              • Content
                              Tag
                              • Accessibility

                              R28. Multimedia content is subtitled.

                              Objectif:
                              Checklist
                              • Recommendations
                              Project phase
                              • Content
                              Tag
                              • Accessibility

                              R29. Each video content has an audio description.

                              Objectif:
                              Checklist
                              • Recommendations
                              Project phase
                              • Content
                              Tag
                              • Accessibility

                              R30. The user is notified if his keyboard is in caps lock mode when entering a case-sensitive field.

                              Objectif:
                              Checklist
                              • Recommendations
                              Project phase
                              • Prototype
                              • Integration
                              Tag
                              • Usability

                              R31. The position of the labels and fields is uniform in each form.

                              Objectif:
                              Checklist
                              • Recommendations
                              Project phase
                              • Design
                              Tag
                              • Accessibility

                              R32. Form validation on the client side is also done on the server side.

                              Objectif:
                              Checklist
                              • Recommendations
                              Project phase
                              • Development
                              Tag
                              • Robustness

                              R33. The ability to submit a form pressing the enter key on the keyboard is not altered.

                              Objectif:
                              Checklist
                              • Recommendations
                              Project phase
                              • Integration
                              • Development
                              Tag
                              • Accessibility

                              R34. The activation link of the contextual help to a form field is visually attached to the label of that field.

                              Objectif:
                              Checklist
                              • Recommendations
                              Project phase
                              • Design
                              Tag
                              • Usability

                              R35. The information concerning site trafic and audience are accompanied by the period covered and the method of measurement.

                              Objectif:
                              Checklist
                              • Recommendations
                              Project phase
                              • Content
                              Tag
                              • Trust

                              R36. The syntax of the URLs is consistent throughout the site.

                              Objectif:
                              Checklist
                              • Recommendations
                              Project phase
                              • Development
                              Tag
                              • Usability

                              R37. Only one set of identifiers is required to access all the services offered.

                              Objectif:
                              Checklist
                              • Recommendations
                              Project phase
                              • Development
                              Tag
                              • Usability

                              R38. Titles, labels and alternative content are translated into the language of the page.

                              Objectif:
                              Checklist
                              • Recommendations
                              Project phase
                              • Development
                              • Content
                              Tag
                              • Internationalization

                              R39. The forms and associated messages are written in a single language.

                              Objectif:
                              Checklist
                              • Recommendations
                              Project phase
                              • Integration
                              • Development
                              Tag
                              • Internationalization

                              R40. The original version of the translated contents is indicated.

                              Objectif:
                              Checklist
                              • Recommendations
                              Project phase
                              • Development
                              • Content
                              Tag
                              • Internationalization

                              R41. Pages whose content is derived from an automatic translation are reported as such.

                              Objectif:
                              Checklist
                              • Recommendations
                              Project phase
                              • Content
                              Tag
                              • Internationalization

                              R42. The content's text direction is indicated when it differs from default.

                              Objectif:
                              Checklist
                              • Recommendations
                              Project phase
                              • Integration
                              • Content
                              Tag
                              • Accessibility

                              R43. The pages contain cross-links (alternatives to menu navigation)

                              Objectif:
                              Checklist
                              • Recommendations
                              Project phase
                              • Prototype
                              Tag
                              • Usability

                              R44. Each page's source code contains relative links to the author, the reproduction rights, the home page and the site map.

                              Objectif:
                              Checklist
                              • Recommendations
                              Project phase
                              • Development
                              Tag
                              • SEO

                              R45. The content blocks displayed individually at the request of the user can be opened at one time.

                              Objectif:
                              Checklist
                              • Recommendations
                              Project phase
                              • Integration
                              Tag
                              • Usability

                              R46. Content scrolling does not cause interstitial content to automatically display.

                              Objectif:
                              Checklist
                              • Recommendations
                              Project phase
                              • Prototype
                              Tag
                              • Usability

                              R47. Each search result is accompanied by an excerpt of the content.

                              Objectif:
                              Checklist
                              • Recommendations
                              Project phase
                              • Prototype
                              • Development
                              Tag
                              • Usability

                              R48. The user can choose the number of search results displayed per page.

                              Objectif:
                              Checklist
                              • Recommendations
                              Project phase
                              • Prototype
                              • Development
                              Tag
                              • Usability

                              R49. Text alternatives, labels, and link labels with identical functions are consistent throughout the site.

                              Objectif:
                              Checklist
                              • Recommendations
                              Project phase
                              • Integration
                              • Development
                              Tag
                              • Accessibility

                              R50. Access to each timed-based content can be paused or extended.

                              Objectif:
                              Checklist
                              • Recommendations
                              Project phase
                              • Integration
                              Tag
                              • Accessibility

                              R51. The recipient field of the newsletter includes only the recipient's e-mail.

                              Objectif:
                              Checklist
                              • Recommendations
                              Project phase
                              • Development
                              Tag
                              • Newsletter

                              R52. Letter spacing is done only with CSS styles.

                              Objectif:
                              Checklist
                              • Recommendations
                              Project phase
                              • Integration
                              Tag
                              • Usability

                              R53. The character size change devices proposed by the site act on the entire page.

                              Objectif:
                              Checklist
                              • Recommendations
                              Project phase
                              • Integration
                              Tag
                              • Usability

                              R54. Inline styles are only used if they can not be externalized.

                              Objectif:
                              Checklist
                              • Recommendations
                              Project phase
                              • Integration
                              • Development
                              Tag
                              • Performance

                              R55. Text content can still be read when text is increased twice in the browser.

                              Objectif:
                              Checklist
                              • Recommendations
                              Project phase
                              • Integration
                              Tag
                              • Accessibility

                              R56. Thumbnails are not bigger images that were resized on the client side.

                              Objectif:
                              Checklist
                              • Recommendations
                              Project phase
                              • Integration
                              Tag
                              • Performance

                              R57. The site does not impose flashing contents.

                              Objectif:
                              Checklist
                              • Recommendations
                              Project phase
                              • Design
                              Tag
                              • Accessibility

                              R58. The order or the creation of account does not cause automatic inscription to a newsletter.

                              Objectif:
                              Checklist
                              • Recommendations
                              Project phase
                              • Development
                              Tag
                              • Trust
                              • E-Commerce
                              • Newsletter
                              • Personal data

                              R59. The contents of submitted forms are filtered to avoid injections.

                              Objectif:
                              Checklist
                              • Recommendations
                              Project phase
                              • Development
                              Tag
                              • Security

                              R60. The user can change his choices regarding cookies at any time.

                              Objectif:
                              Checklist
                              • Recommendations
                              Project phase
                              • Development
                              Tag
                              • Trust

                              R61. Any collection of personal information is explained or justified.

                              Objectif:
                              Checklist
                              • Recommendations
                              Project phase
                              • Content
                              Tag
                              • Trust
                              • Personal data

                              R62. The server is configured not to return information about the versions of the software and languages used.

                              Objectif:
                              Checklist
                              • Recommendations
                              Project phase
                              • Development
                              Tag
                              • Security

                              R63. The server sends a 301 HTTP code for the permanently changed address.

                              Objectif:
                              Checklist
                              • Recommendations
                              Project phase
                              • Development
                              Tag
                              • SEO

                              R64. The site does not use user-agent detection.

                              Objectif:
                              Checklist
                              • Recommendations
                              Project phase
                              • Development
                              Tag
                              • Robustness

                              R65. Scripts are not duplicated.

                              Objectif:
                              Checklist
                              • Recommendations
                              Project phase
                              • Development
                              Tag
                              • Performance

                              R66. The date and time of the server are correct.

                              Objectif:
                              Checklist
                              • Recommendations
                              Project phase
                              • Development
                              Tag
                              • Robustness

                              R67. Scripts are called after the content.

                              Objectif:
                              Checklist
                              • Recommendations
                              Project phase
                              • Integration
                              Tag
                              • Performance

                              R68. The server sends personalised error pages.

                              Objectif:
                              Checklist
                              • Recommendations
                              Project phase
                              • Development
                              Tag
                              • Usability

                              R69. The number of HTTP requests is optimized.

                              Objectif:
                              Checklist
                              • Recommendations
                              Project phase
                              • Development
                              Tag
                              • Performance

                              R70. The site does not have complex data tables.

                              Objectif:
                              Checklist
                              • Recommendations
                              Project phase
                              • Content
                              Tag
                              • Accessibility