Back to: Create a Static Student Website
Pre-launch QA Diligence
Prior to the launch of web sites both big and small, there are several techniques and best practices to help ensure the delivery of a quality product that is performant and bug free. Often times addressed toward the end of a project, one of the most commonly used terms to describe this step of the process is quality assurance, or QA.
Quality assurance (QA) is a way of preventing mistakes and defects in manufactured products and avoiding problems when delivering solutions or services to customers
– Wikipedia
Bug Tracking
Validate, Fix Errors, and Test, Test, Test…
- Validate your code
- Validate HTML
- Validate CSS
- Validate Accessibility (Section 508 compliance)
- Provide “equivalent” experience to all users. For example, make sure all img alt tags are appropriate.
- Check out online resources, such as: The W3C Web Accessibility Initiative (WAI) and their list of resources, the A11Y Project, ARIA, etc.
- Test in multiple Platforms, Browsers, Screen Sizes, and Devices
- Example of online Tools: Browserling, Netrenderer, Sauce Labs, Browserstack, Browsershots, Chrome’s Device Mode
Checklist
- Is your HTML & CSS validating with no errors?
- Is your site Section 508 Compliant?
- Have you tested on Multiple Platforms, Browsers, Devices, and Screen Sizes?
- Mac and PC
- Chrome, Firefox, Safari, IE, Edge
- Large Monitor, Laptop Display, Tablet, Mobile (including portrait & landscape views)
- iOS and Android