Testing
Unit testing
System testing
Regression testing
Accessibility testing
Norwegian law requires that our clients follow the international Web Content Accessibility Guidelines WCAG 2.0 AA.
These guidelines were developed to ensure that web content is available to as many people as possible. Some points require special attention to users with special needs, but most guidelines are simply a formalization of good usability advice and best practice that any well designed solution should follow regardless of what the law requires. A common misconception is that WCAG limits innovative thinking and leads to dull designs. This is not true. WCAG should be viewed as a guide on the road to happier users, but you also need to think for yourself. WCAG is no substitute for design methodology and user research.
Unfortunately, WCAG is written in a complicated and "legal" manner that makes it seem more difficult than it actually is. Making Waves has created guidelines in an attempt to simplify, adapt and explain WCAG in a way that is useful and suitable to the different roles in your project team. You'll find the entire list of guidelines at Making Waves Confluence space (authentication required) Universal design, Web Accessibility and WCAG Home
Accessibility testing checklist
Teams should aim at verifying code as it is developed, continually testing accessibility.
Validate code front end code during development using Tenon (Håkon has API key)
Validate Color contrast using Wave or Check my Colors
Wave toolbar for Firefox check that there is no holes in the heading structure, and make sure that it is according to practice described in this article HTML Heading structure - Yoast
Using Wave or Wave toolbar for Firefox check for any errors and warnings, and report if any
Navigate page / template using keyboard, and make sure all navigation elements are reachable using keyboard.
Links to accessibility testing tools
Performance testing
Front End performance testing
Making Waves Performance Best Practices is based on Google Performance Best Practices
Google Performance Best Practices
Front end performance testing should be conducted during development of new front end units and on a systems level after development of Front End code before a system / solution is put in to production. Front end performance testing should also be conducted when new units are introduced to already existing systems / solutions.
Tools Making Waves use for testing Front End Performance: