Skip to content
Chris Wells edited this page May 6, 2017 · 1 revision

Browser testing

Test every view and function on:

  • Windows (IE, Edge, Chrome, Firefox)
  • Mac (Safari, Chrome, Firefox)
  • Android (Firefox, Chrome)
  • iOS iPad and iPhone (Safari & Chrome)

Accessibility testing

ARIA Landmarks

See http://a11yproject.com/checklist.html

  • ARIA Landmarks set up correctly for banner, navigation, main, article, aside ("complementary"), footer ("contentinfo"), meta info, copyright, company info, etc, form role="search", Language Attribute, etc
  • Language attribute declared on HTML element
  • Specify a language with the lang attribute on the element.
  • Document Outline
  • Use semantic headings and structure
  • Links have :focus state
  • Links are recognizable (underlined)
  • Images have appropriate alt text (see: http://a11yproject.com/posts/alt-text)
  • Javascript is unobtrusive (no inline scripting)
  • Alternatives provided for users without Javascript enabled
  • Tab order of forms follows logical pattern
  • Associated label for all form controls (e.g. input, select etc.)
  • Placeholder attributes are NOT being used in place of label tags
  • Form elements grouped with fieldsets
  • Fieldsets described with legend (esp. for Radio buttons and Checkbox groups)
  • Transcriptions of video and audio media assets
  • Site tested using a screen reader only
  • Site tested using keyboard only

Flight-check tests

  • Test that all file download links do not carry the test/dev server URLs
  • [ ]

Remote testing

  • Prepare Live- site before inviting user testing group into test site:
  • Check is site name and email correct?
  • Is email configuration setup?
  • Are typical performance and caching options enabled?
  • Draft then send test email out to user group
  • [ ]