Nueva Handbook

# Preliminary Work

  • Consistent Naming (Specs, Tickets, (Design), Frontend, Backend)
  • Design Review with Designer and PM
    • Deconstruct into components
    • Clarify UI Behaviour
    • Resolve inconsistency
    • Define basic user stories for testing the final site
  • Clarify Requirements (A11y, i18n, Browsersupport, SEO, Tracking, Forms)
  • Complete Styleguide (Fonts, Colors, Components/Variants)
  • Define media(image/video) size and aspect ration per component
  • Does the website need to be usable without JS?
  • Is the design confirmed by the client?

# Acceptance Criteria

# Components

  • Are all required variants implemented and available?
  • Does the component stay consistent with too much or too little content?
  • How does the component handle different media aspect ratios?
  • Are conditions in place to catch edge cases like missing content (props)?
  • Is all content editable(no hardcoded content)? (i18n file or CMS)
  • Does the component work as expected on all required browsers?
  • Is the responsive behavoir correct?

# Markup

  • Is the markup valid(W3 Validator)?
  • Is the heading hierarchy respected on all pages?
  • Are the components correctly nested? Used as they are meant to be?

# Styles

  • Does the implementation match the design?
  • Are the required Browsers supported (IE11 and max. 3 latest major versions)
  • How does the website look on screens with lower resolution?
  • Do media element have a large enough resolution for Retina screens?
  • How does the website look when printed? (optional, only if required)
  • Is the implementation reviewed by the designer?

# Function

  • Is all required functionality implemented and working?
  • Are polyfills in place where needed? (only for req. browsers)
  • How does the site/components behave on error? (Error Handling)
  • Is the site/component useable for touch device and keyboard-only users?
  • Are all console logs removed? (no console logs in production)
  • Are there any tests for the function?

# Accessibility

  • Are components usable with the help of a screenreader?
  • Is all content readable, even with High Contrast Mode?
  • Are components useable for keyboard-only users?
  • Are screenreader status hints and focus handling in place? (aria, SR texts)
  • Does the site provide navigation, orientation and usability features for screenreaders?

# Other

  • Are there any dead links?
  • Are there any orthography errors?
  • Do the monitoring/tracking scripts respect the cookie consent?
  • How is the performance performance, pagespeed (Lighthouse, Low-Mid-Range Devices, 3G)
  • Redirect Handling
  • 404 Page
  • Favicon
  • Does social media sharing work?
  • JS/CSS minified
  • No large assets in repo?
  • Are SEO elements in place?