Testing a web page

  1. W3C HTML validator. Should pass without critical errors.
  2. W3C CSS validator. Should pass without errors that cause problems in practice. For example vendor prefixes may report errors but they may sometimes be necessary to use.
  3. Using the webpage with a keyboard only. Check if the page is usable without a mouse. While navigating with a keyboard (usually tab key), is it visible which element is currently in focus?
  4. Does it work properly with a touchscreen?
  5. Without image files. Test the page in a situation where image files are not loaded. The page must remain user-friendly and content must be accessible. For example in Firefox loading images can be disabled:
    1. Go to about:config in Firefox
    2. Search for permissions.default.image
    3. Change the value to 2 (default is 1)
  6. JavaScript. Test the page without JavaScript. In Firefox JavaScript can be disabled:
    1. Go to about:config in Firefox
    2. Search for javascript.enabled
    3. Change the value to false (default is true)
  7. CSS. Test the page without CSS:
    1. Is the content structure logical and user-friendly? In many browsers CSS can be disabled: View>Style>No Style
    2. Does the page work if text is chenged or added? Does it work if the user increases the text size in the browser up to 200%? (In Firefox View>Zoom>Zoom text only)
  8. Different devices and media types.
    1. RWD (Responsive Web Design). Test for various screen sizes. Desktop browser's Responsive Design View may be used.
    2. Print. Test print preview, does the page make sense when printed on paper?
      Print view should be controlled via CSS, usually there's no need for a separate print version of the page.
  9. Different browsers. The page shoud be user-friendly with the newest versions of the following browsers: