Getting Accessibility Advice

Planning Phase

Type of advice: Requirements

• Provide accessibility requirements for Requirements Document (1 day)
• Create/modify user stories to cater for disability (½ day)
• Why now? Because IT developers will charge more if you introduce changes down the track.

Design Phase

Type of advice: Design review

• Review wireframes: navigation consistency check (1 day)
• Review design concepts (Figma / Photoshop): contrast check (1 day)
• Why now? Because, it is much easier to change designs when they exist as concepts. If changes are required, the original designer can do them, without compromising the design.
• Sample report - desktop (staff access only)
• Sample report - mobile (staff access only)

Build Phase

Type of advice: Code review

• Accessibility audit (5 days)
• Why now? Because you want to make sure that everybody can access your service
• Sample report (staff access only)

Testing Phase

Type of advice: User testing

• User testing - test plan (1 day)
• User testing - recruit participants x 10 (2 days)
• User testing - run interviews (5 days)
• User testing - compile results (5 days)
• Why now? Because if there are still problems, you want to hear about them before you receive a complaint
• Sample user testing video (staff access only)

Release

Because of the previous planning, the site should be accessible to all.