slideshare quotation-marks triangle book file-text2 file-picture file-music file-play file-video location calendar search wrench cogs stats-dots hammer2 menu download2 question cross enter google-plus facebook instagram twitter medium linkedin drupal GitHub quotes-close

Accessibility statement for Code Enigma


This website is run by Code Enigma. We want as many people as possible to be able to use this website. That means you should be able to:


  • Change colours, contrast levels and fonts
  • Zoom in up to 300% without text spilling off the screen
  • Navigate most of the website using just a keyboard
  • Listen to most of the website using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver)


We’ve also made the website text as simple as possible to understand.




AbilityNet has advice on making your device easier to use if you have a disability.



How accessible this website is


We’re aware that some parts of this website aren’t fully accessible, yet.


  • Alternative text on photographs don’t always provide accurate context
  • We need to improve our contrast ratios on things like cta buttons and images
  • We could utilise headers better to suit the content



What to do if you can’t access parts of this website


If you need information on this website in a different format, we don’t currently have any options like accessible PDF, large print, easy read, audio recording or braille, but we will happily talk to you over the phone or via email. 



Alternatively, you can install Chrome extensions for screen reading. Also, you can edit your font preferences in the Chrome settings so all websites appear how you need them to.


Call: +44 (0)20 3588 1550


Reporting accessibility problems with this website



We’re always looking to improve the accessibility of this website. If you find any problems that aren’t listed on this page, or think we’re not meeting accessibility requirements, contact our development team at or call us on: +44 (0)20 3588 1550



Enforcement procedure


The Equality and Human Rights Commission (EHRC) is responsible for enforcing the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 (the ‘accessibility regulations’). If you’re not happy with how we respond to your complaint, contact the Equality Advisory and Support Service (EASS).



Contacting us by phone or visiting us in person


Our telephone service is managed by TTNC who will take a message and we will get back to you. Please do tell TTNC how you’d like us to contact you, we prefer email, but are happy to call you back. 


We’re a distributed company, so if we need to meet, we’d like to come to you, where you’re most comfortable. If this isn’t possible we do have a serviced office in Farringdon, London. There are 4 steps at the front of the building, we can talk to the office and ask for a ramp if required. 



Technical information about this website’s accessibility



Code Enigma is committed to making its website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.


This website is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to the non-compliances listed below.



Non-accessible content


The content listed below is non-accessible for the following reasons. 


Current issues on our site that to do not comply with WCAG accessibility regulations 





Elements must only use allowed ARIA attributes


Using an invalid role-attribute combination will, at best, result in no effect on the accessibility of the application and, at worst, trigger behaviour that disables accessibility for entire portions of an application. This doesn’t meet WCAG 4.1.2. The solution is to check (and where necessary, correct) each element with an ARIA role uses only ARIA attributes allowed for that role.


We plan to address the issue and make these changes live by December 2021.


Links must have discernible text

Users who rely exclusively on a keyboard (and no mouse) to navigate a webpage can only click on links that can receive programmatic focus. A link that cannot receive programmatic focus is inaccessible to these users. This doesn’t meet WCAG: 2.4.4, 4.1.2. The solution is to ensure all links can receive programmatic focus and are visible to screen readers. 

We plan to address the issue and make these changes live by December 2021.


Elements must have sufficient color contrast

Some people with low vision experience low contrast, meaning that there aren't very many bright or dark areas. Everything tends to appear about the same brightness, which makes it hard to distinguish outlines, borders, edges, and details. Text that is too close in luminance (brightness) to the background can be hard to read. Insufficient contrast doesn’t meet WCAG 1.4.3. The solution is to ensure color contrast of at least 4.5:1 for small text or 3:1 for large text, even if text is part of an image. Large text has been defined in the requirements as 18pt or 14pt bold.

We plan to address the issue and make these changes live by December 2021.


How we tested this website


This website was last tested on August 18th 2021. The test was carried out by Code Enigma as part of internal auditing.

We used the following approach to decide on a sample of pages to test: 

One of each content type, every list (Drupal View) generated in Drupal, Drupal specific pages, such as user, log in and error pages. Including any content pages which has notably different HTML structures, when this content is created by our editors, the URL gets added to the audit list and will become part of our regression testing. 

We tested:

Homepage -
Team member page -
Case Study -
Blog  -
Standard Page - 


You can read the full accessibility test report by following this link.


What we’re doing to improve accessibility


This statement was prepared on July 19th 2021 and updated on August 18th 2021.