Accessibility statement for Access Charity CRM

Website accessibility statement in line with Public Sector Body (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018

This accessibility statement applies to: 

https://go.accessacloud.com  

This website is run by the Development and Alumni Department, University of Edinburgh. The system uses a third party application, ‘Access Charity CRM’. We want as many people as possible to be able to use this application. For example, that means you should be able to:  

  • Change colours, contrast levels and fonts 
  • Zoom in up to 200% without the text spilling off the screen 
  • Use the site without moving or scrolling text 
  • Use the site without time limits  

We’ve also made the website text as simple as possible to understand. However, some of our content is technical, and we use technical terms where there is no easier wording we could use without changing what the text means.  

Customising the website

AbilityNet has advice on making your device easier to use if you have a disability. This is an external site with suggestions to make your computer more accessible:  

AbilityNet - My Computer My Way  

With a few simple steps you can customise the appearance of our website using your browser settings to make it easier to read and navigate:  

Additional information on how to customise our website appearance  

If you are a member of University staff or a student, you can use the free SensusAccess accessible document conversion service:  

Information on SensusAccess  

How accessible this website is  

We know some parts of this website are not fully accessible:  

  • Not all colour contrasts meet the levels required
  • Colour is used to convey information without an alterative
  • Not all content can be reached by keyboard e.g. data charts
  • It can be difficult to tell where you have navigated to by keyboard only
  • There is no skip to main content option
  • There are sliders that require the user to drag with the mouse
  • Reflow is not enabled to 400%
  • The system is not fully compatible with screen readers such as JAWS
  • The system is not fully compatible with voice recognition software e.g Dragon
  • Tooltips are not accessible by keyboard or by assistive software
  • There is a cognitive test with no forgotten password option
  • There are areas missing error messages where this would be helpful
  • Some heading levels are missing or used incorrectly
  • Some non-text content does not have appropriate alternative text
  • Some pop ups appear without the user being alerted
  • Error suggestions and advice are not always given
  • Some error messages obscure other content 

Feedback and contact information  

If you need information on this website in a different format, including accessible PDF, large print, audio recording or braille:

We’ll consider your request and get back to you in 5 working days.

Reporting accessibility problems with this website

We are always looking to improve the accessibility of this website. If you find any problems not listed on this page, or think we’re not meeting accessibility requirements, please contact:

We’ll consider your request and get back to you in 5 working days.

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 please contact the Equality Advisory and Support Service (EASS) directly:

Contact details for the Equality Advisory and Support Service (EASS)

The government has produced information on how to report accessibility issues:

Reporting an accessibility problem on a public sector website

Contacting us by phone using British Sign Language 

British Sign Language service 

Contact Scotland BSL runs a service for British Sign Language users and all of Scotland’s public bodies using video relay. This enables sign language users to contact public bodies and vice versa. The service operates from 8.00am to 12.00am, 7 days a week. 

Contact Scotland BSL service details.  

Technical information about this website’s accessibility 

The University of Edinburgh is committed to making its websites and applications accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.  

Compliance Status 

This website is partially compliant with the Web Content Accessibility Guidelines (WCAG) 2.2 AA standard, due to the non-compliances listed below.  

The full guidelines are available at:  

Web Content Accessibility Guidelines (WCAG) 2.2 AA standard  

Non accessible content  

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

Noncompliance with the accessibility regulations

The following items do not comply with the WCAG 2.2 AA success criteria:

Not all content has a text alternative

Information, structure, and relationships conveyed through presentation cannot always be programmatically determined e.g certain ARIA roles do not contain particular children, <ul> and <ol> do not only directly contain <li>, <script> or <template> elements, <li> elements must be contained in a <ul> or <ol>

Colour is used solely as a way of communicating information

Not all colour contrasts meet the required contrast ratios

No all pages reflow to 400%

Tooltips are not available by keyboard or with assistive software but only with mouse over

Not all content is keyboard accessible

There is not a skip to main content option

Links do not always have meaningful hypertext

Not all headings are coded as heading and heading levels are skipped

It is not always clear where you have tabbed to when using keyboard navigation

There are places where the user needs to drag content and there is not a keyboard alternative

New browser tabs and pop ups occur without the user being alerted this will happen

Error suggestions are not always given where they would be beneficial

The system is not coded correctly for compatibility with assistive software

  • ARIA commands do not always have an accessible name
  • ARIA hidden elements are focusable or contain focusable elements
  • ARIA roles do not always conform to valid values
  • Elements must only use supported ARIA attributes
  • Interactive controls must not be nested
  • Some buttons do not have discernible text
  • Frames do not always have an accessible name
  • 4.1.2 Name, Role, Value

We aim to improve our websites accessibility on a regular and continuous basis. See the section below ('What we're doing to improve accessibility') on how we are improving our site accessibility.

Most of the issues are outwith our control and sit with the third party supplier. At this time we do not believe any issues are within our control but if we identify any we will work to resolve these by May 2027. The site is run for us by a third party and we will be working with them to resolve these issues.

Disproportionate burden 

We are not currently claiming that any accessibility problems would be a disproportionate burden to fix.

Content that’s not within the scope of the accessibility regulations

At this time we believe no content is outwith the scope of the accessibility regulations.  

What we’re doing to improve accessibility  

We will continue to address and make adequate improvements to the accessibility issues highlighted. At this time we do not believe any issues are within our control but instead sit with the third party supplier Access. If we identify any issues within our control, we will work to resolve these by May 2027.The majority of errors are outside our control and sit with the supplier, Access. We will continue to work with them to resolve the issues above.

While we are in the process of resolving these accessibility issues we will ensure reasonable adjustments are in place to make sure no user is disadvantaged. As changes are made, we will continue to review accessibility and retest the accessibility of this website.

Preparation of this accessibility statement  

This statement was prepared on 5th October 2022. It was last reviewed on 18th May 2026.

The website was last tested on 8th May 2026. The testing was carried out by Development and Alumni Department at the University of Edinburgh using both automated and manual methods. The site was tested on a PC, primarily using Microsoft Edge alongside Mozilla Firefox and Google Chrome.

Recent world-wide usage levels survey for different screen readers and browsers shows that Chrome, Mozilla Firefox and Microsoft Edge are increasing in popularity and Google Chrome is now the favoured browser for screen readers:

WebAIM: Screen Reader User Survey  

The aforementioned three browsers have been used in certain questions for reasons of breadth and variety.

We ran automated testing using AXE and then manual testing that included:

  • Spell check functionality;
  • Scaling using different resolutions and reflow;
  • Options to customise the interface (magnification, font, background colour, etc);
  • Keyboard navigation and keyboard traps;
  • Data validation;
  • Warning of links opening in new tab or window;
  • Information conveyed in the colour or sound only;
  • Flashing, moving or scrolling text;
  • Use with screen reading software (for example JAWS);
  • Assistive software (TextHelp Read and Write, Windows Magnifier, ZoomText, Dragon Naturally Speaking);
  • Tooltips and text alternatives for any non-text content;
  • Time limits;
  • Any drag functionality and alternatives
  • Consistent help function
  • No need to re enter data already submitted
  • Any cognitive tests

Change Log  

8th May 2026

Testing found these improvements:  

All pages have a valid language attribute

All images that were previously found to lack alt-text have been updated however there are still several icons without it.

The system is not coded correctly for compatibility with assistive software:

  • ARIA commands do not always have an accessible name
    • This has been fixed in Workspaces, Calling App and the Analytics Dashboard
  • Elements do not only use supported ARIA attributes
    • This has been fixed in the Analytics Dashboard
  • Elements do not only use permitted ARIA attributes
    • This has been fixed

20th March 2025

Testing found these improvements:

We could no longer identify any keyboard traps in the system where a user must use a mouse to exit content

When tabbing through content this appears to follow a more logical order on the page

This article was published on