CMS Test & Certify
Overview
Would you like your software platform or Content Management System tested and certified for WCAG 2.2 accessibility?
me2 can certify and endorse your software as producing accessible web content and functionality.
Who we help?
- CMS vendors
- Software development houses
- Technology companies
We offer
A flexible approach, as making software and CMS accessible can be difficult. We can certify individual modules of the software or the whole app to be:- WCAG 2.2 Single A
- WCAG 2.2 Double AA
- WCAG 2.2 Part Compliant
What we test
We test the frontend of the software or CMS. Get in touch if you require the backend included.
We test a sample standard installation ‘white labelled’ version of the website or a set of templates created using the CMS.
Once all the issues are resolved, you can claim that your CMS can produce WCAG compliant websites.
How We Test
Our consultants are technical accessibility experts with years of experience and have undertaken hundreds of audits.
Expert Human Analysis
Our team manually review each page against the WCAG 2.2.
Testing Software
We use a combination of accessibility software (WAVE, etc).
Assistive Technology
We test each page using screen readers (JAWS, NVDA) & magnifiers.
Mobile: Responsive Websites
We test on mobile devices with VoiceOver on iOS & Zoom on Android.
User Testing
We test the site with a blind screen reader user.
Keyboard Only
We ensure all functionality works with a keyboard.
Our Audit Report
Our reports are easy to read and understand, while offering technical recommendations and bespoke code solutions.
Issue Description
We cite the relevant WCAG Success Criterion, and provide a detailed outline of the issue.
Impact of the Issue
A description of the impact the issue has on real end users.
Bespoke Recommendations
Tailor-made recommendations including code snippets and screen grabs to illustrate each issue.
Related Success Techniques
A list of associated WCAG Success Techniques.
Severity
All issues are not equal. We rate each issue from Minor (minor issue that is a matter of technical compliance and has little impact) through Problematic, Serious and Catastrophic.
We Include More Examples
A common failure of traditional technical accessibility audits is a small number of examples.
Developers often only fix the issues in the audit without realising that other examples are present across the app.
We overcome this problem by citing multiple examples of the issue - allowing for all instances of the issue to be easily identified and fixed.
Test Method
How developers can replicate this test themselves and check if the problem has been fixed.
Users Feedback
Feedback from a blind screen reader user.
Audit Handover & Support
Presentation of Findings
Handover of the audit report, and a presentation of the audit findings and phone workshop.
Support
Each audit comes with an extended four hours' email and phone support over 60 days.
We also provide support on an ad-hoc basis at an hourly rate if required, learn more.
Flexible Recommendations
One size doesn’t always fit all, especially with web applications and complex websites. If a recommendation can't be implemented, we are happy to work with your team to identify an alternative.

