QA List

# Site launch checklist
This checklist aims to standardize how we build and ship new sites/pages outside of Dotcom and feature-flag driven development in Dotcom; some steps won’t be applicable to every project.

To use, copy this master document into a new markdown file within an individual project repo and name it `launch-checklist.md`. If there are particular items that you know don’t apply to your project (ex: the page doesn’t have any forms on it), feel free to leave those off. As items are completed throughout development, check them off the list. The launch checklist should be complete before the page(s) are shared to a wider audience of stakeholders for general QA review.

## 🧪 Before testing
- [ ] Create list of pages to test
- [ ] Confirm copy and layout is accurate and up to date
- [ ] Confirm logged in / out differences, if any

## 🤖 CI and errors
- [ ] Confirm CI builds pass
- [ ] Confirm no console errors or warnings

## 🤝 Integrations
- [ ] Google Analytics and set up [click tracking](https://githubber.com/article/technology/dotcom/google-analytics#how-to-add-ga-tracking) (Request access to GA in [`github/it`](https://github.com/github/it/issues/new?title=Access+to+Google+Analytics&body=%3Awave%3A+Hi+there%21+Can+you+please+add+me+to+the+Google+Analytics+account?+Thanks%21+%3Agrinning%3A%0A%0A%2Fcc+%40github%2Fsecurity-ops))
- [ ] Other necessary data/service integrations like Eloqua, Mailchimp, SendGrid, etc.

## 📂 Assets
- [ ] Add favicon
- [ ] Create and add [social card](https://github.com/github/site-design/blob/master/strategy/docs/social-cards.md)
- [ ] Optimize/minify images ([ImageOptim](https://imageoptim.com/mac) for `.jpg` or `.png`, [ImageAlpha](https://pngmini.com/) for transparent `.png`, [SVGO](https://github.com/svg/svgo) for `.svg`)
- [ ] Confirm images are in the appropriate directories
- [ ] Confirm we have the appropriate license for a new webfont

## 💞 Accessibility (via [WCAG 2.0 AA](https://www.w3.org/TR/WCAG20))
- [ ] Test for [color contrast](https://www.w3.org/WAI/WCAG21/quickref/?versions=2.0#qr-visual-audio-contrast-contrast) with a ratio goal of 4.5:1
- [ ] Include appropriate `alt` tags on images
- [ ] Include appropriate [`aria-label`](https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/ARIA_Techniques/Using_the_aria-label_attribute) on necessary components
- [ ] Confirm [`form` inputs have explicit labels](https://accessibility.18f.gov/forms/)
- [ ] Confirm [headings are nested logically](https://accessibility.18f.gov/headings/)
- [ ] Confirm usable [keyboard access](https://accessibility.18f.gov/keyboard/)

## 🗣 Social optimization
- [ ] Page title, meta description, and social card image [output correctly for social sharing](https://metatags.io/)

## 💻 Cross-browser testing
Check for visual bugs in browsers (Request access to [Browserstack](https://browserstack.com) in [`github/design`](https://github.com/github/design/issues/new?title=Access+to+BrowserStack&body=%3Awave%3A+Hi%20there%21+Can+you+please+add+me+to+the+GitHub+BrowserStack+account?+Thanks%21+%3Agrinning%3A]))

- [ ] Mac
  - [ ] Latest Safari
  - [ ] Latest Chrome
  - [ ] Latest Firefox
- [ ] Windows
  - [ ] Latest Edge
  
## 📱 Mobile device testing 
Review the responsive layout and check for visual bugs on different mobile devices. Try to use physical devices for testing whenever possible; if none are available, then use [Browserstack](https://browserstack.com) instead.
- [ ] iPhone
- [ ] iPad
- [ ] Android

## ✅ Forms
If pages being developed contain forms (input/submit), test their functionality and user feedback for success/error states.
- [ ] Confirm that forms submit info as expected
- [ ] Success messaging when form is submitted correctly
- [ ] Error messaging when form is not submitted

## 🛠 Workflows and functionality
- [ ] Add new Dotcom marketing pages to the Privacy Policy
- [ ] Confirm the right people have push access in the repo settings
- [ ] [Feature flag](https://githubber.com/article/technology/dotcom/feature-flags#step-by-step-through-the-life-of-a-new-feature) toggles relevant views and changes
- [ ] GitHub Pages and custom (sub)domain are configured properly
- [ ] Redirects are properly in place