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 difficult-to-read 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 websiteAbilityNet 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 Charts in the Analytics Dashboard can’t be customised in colour, background or font 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 Images are missing alt text There is text as an image Not all links have meaningful hypertext There is a cognitive test with no forgotten password option There are areas missing error messages where this would be helpful Feedback and contact information If you need information on this website in a different format, including accessible PDF, large print, audio recording or braille: Email: dasusers@ed.ac.uk Telephone: +44 (0)131 650 2240 British Sign Language (BSL) users can contact us via Contact Scotland BSL, the on-line BSL interpreting service. 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: Email: dasusers@ed.ac.uk Telephone: +44 (0)131 650 2240 British Sign Language (BSL) users can contact us via Contact Scotland BSL, the on-line BSL interpreting service. We’ll consider your request and get back to you in 5 working days. Enforcement procedureThe 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 1.1.1 Non Text Content 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 1.3.1 Info and Relationships Colour is used solely as a way of communicating information 1.4.1 Use of Colour Not all colour contrasts meet the required contrast ratios 1.4.3 Contrast Minimum There is text displayed as an image 1.4.5 Images of Text No all pages reflow to 400% 1.4.10 Reflow Tooltips are not available by keyboard or with assistive software but only with mouse over 1.4.13 Content on Hover or Focus Not all content is keyboard accessible 2.1.1. Keyboard There is not a skip to main content option 2.4.1 Bypass Blocks Links do not always have meaningful hypertext 2.4.4. Link Purpose in Context Not all headings are coded as heading and heading levels are skipped 2.4.6 Headings and Labels It is not always clear where you have tabbed to when using keyboard navigation 2.4.7 Focus Visible There are places where the user needs to drag content and there is not a keyboard alternative 2.5.7 Dragging Movements Pages do not have a valid language attribute 3.1.1 Language of Page New browser tabs and pop ups occur without the user being alerted this will happen 3.2.2 On Input Error suggestions are not always given where they would be beneficial 3.3.3 Error Suggestion There is a password requirement and there is no forgotten password option 3.3.8 Accessible Authentication Minimum The system is not coded correctly for compatibility with assistive software ARIA commands do not always have an accessible name Elements do not only use supported ARIA attributes ARIA hidden elements are focusable or contain focusable elements Elements do not only use permitted ARIA attributes ARIA roles do not always conform to valid values Interactive controls must not be nested Some buttons do not have discernible text Frames do not always have an accessible name 4.1.3 Status Messages 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 2026. 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 we will work to resolve these by May 2026. 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 14th May 2025. The website was last tested on 20th March 2025. 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 20th March 2025 Testing found these improvements: We could not longer identify any keyboard traps in the system where a user must use a mouse to exit content 2.1.2 No Keyboard Trap When tabbing through content this does not appear to follow a more logical order on the page 2.4.3 Focus Order This article was published on 2025-06-04