Testing mobile sites and native apps for accessibility
With mobile and tablet use continually increasing, it is important to make sure your content is accessible from portable devices.
We can test your website’s accessibility using W3C standards-based testing, or test your mobile applications with assistive technology features.
We offer different testing options that are designed to suit your business needs and budget.
Option 1 – W3C standards-based testing of websites
AccessibilityOz has developed a methodology for evaluating the accessibility of mobile websites; we test your website against the W3C recommended guidelines/standards for making accessible content and best practices for making mobile-friendly content.
- Web Content Accessibility Guidelines (WCAG) is a guide for making websites accessible to people with disabilities.
- Mobile Web Best Practices (MWBP) is a guide for making websites usable from a mobile device.
- Mobile Web Application Best Practices (MWABP) is a guide for developing and delivering web applications on mobile devices.
Our expert accessibility consultants test your website systematically using manual inspection and our unique automated testing tool, OzART (AccessibilityOz Reporting Tool).
We can test all your website pages or a selection, such as the most popular pages.
Option 2 – Assistive feature testing of mobile applications
We test your mobile application (app) on smartphones and tablets using the built-in (native) assistive features of the three most used operating systems and their default browsers.
The operating systems and browsers are:
- Apple iOS / Safari browser
- Android / Android Browser
- Windows / Internet Explorer
Each operating system has different assistive features for the following disability groups:
- Vision – for people who are blind or have trouble viewing the screen.
- Hearing – for people who are deaf or have trouble hearing.
- Cognitive and learning – for people with cognitive and learning disabilities.
- Physical and motor skills – for people with physical disabilities.
Testing is done on a selection of your mobile app screens—such as the most popular screens—or by following common tasks performed on your mobile app.
Option 3 – User testing with people with disabilities
At AccessibilityOz, we have a policy to use people with disabilities as much as possible – more than twenty percent of our staff have a disability of some sort.
User testing with people with disabilities is strongly recommended as it can bring an alternative view of the accessibility of a website. Often user testing can be a way of determining how important certain errors are, and what needs to be fixed first.
Assistive feature testing can be conducted by people with disabilities. For more information on the operating systems and assistive features tested please refer to Option 2 – Assistive feature testing.
A variety of other user testing can be conducted on request.
The accessibility report includes the findings of the audit; it is comprised of the following information:
- Success Criterion that the error applies to
- Level (A or AA)
- Occurrence: whether the error was found in the template or content
- Impact: the actual impact on people with disabilities
- Error description
- Example, including URL, screenshot of the error and relevant code
- Solution to the error.
Presentation of audit findings
At the conclusion of the audit a walkthrough will be held for the Web Manager, developers and content authors. This session will walk through the audit report, providing an opportunity for people to ask questions arising from their audit.