The Representative Sample Approach to Testing with AMP

  • Updated


What Exactly Should I Be Testing?

Due to the popularity of templates and predetermined designs for pages and elements in digital properties, Level Access recommends testing a representative set of pages. The thoughtful selection of representative pages leads to a clearer, more manageable view of compliance, types of problems, and how to prioritize remediation.This allows you to minimize needless duplications and get a more efficient, streamlined workflow. While the optimal representative sample would be different for every site or system, Level Access generally recommends between 15 to 30 modules (web pages, major components, etc.) as a good starting point.


As for which modules to select, below are some ideas to consider for module selection:

  • Individual page templates
  • Unique and high profile pages
  • Pages in a Pattern Library or Design System that include and use JavaScript or ARIA, or otherwise appear to pose the greatest accessibility challenges
  • Forms critical to the typical ‘user path’ (like login and registration forms)
  • Site navigation components/pages – this could include site maps or a ‘hamburger’ menu on a mobile site
  • Settings, preferences or support pages
  • Multimedia-focused pages: HTML5 players, and/or representative videos for multimedia alternatives
  • Content source
  • User types or roles
  • Third-party components
  • Primary components in single-page web apps (e.g., modals, panels)
  • Any pages or parts of the user experience that have specifically been called out in any complaint or previous audit


Was this article helpful?

0 out of 2 found this helpful