Accessibility statement for Edinburgh College Application System

This accessibility statement applies to This website is run by Edinburgh College. We want as many people as possible to be able to use this website. For example, that means you should be able to:

  • change colours, contrast levels and fonts
  • zoom in up to 300% without the text spilling off the screen
  • navigate most of the website using just a keyboard
  • navigate most of the website using speech recognition software
  • 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.

Edinburgh College is due to launch a redesigned application system at the beginning of 2021 which will be fully compliant with WCAG 2.1 guidelines.

How accessible this website is

  • Some images are missing an alternative text description, or an alt attribute, which means the image’s content is unavailable for screen reader users.
  • Some form fields do not have a corresponding text label associated with it. These labels are used by screen readers to understand the function or purpose of a given form field.
  • In some areas, the contrast between the text colour and the background colour is too low, which can make the text difficult to read.

Feedback and reporting accessibility problems with this website

If you cannot access any part of this site or want to report an accessibility problem, please tell us by emailing

Enforcement procedure

The Equality and Human Rights Commission enforces the accessibility regulations (the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018).

If you're not happy with how we respond to your feedback, contact the Equality Advisory and Support Service. They are an independent advice service. They will advise you on what to do next.

Compliance status

Edinburgh College 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 not compliant with the Web Content Accessibility Guidelines version 2.1 AA standard. The non-compliances and exemptions are listed below.

Non-compliance with the accessibility regulations

1.1.1 Non-text Content:

  • Images, form image buttons, and image map hot spots do not have appropriate, equivalent alternative text.
  • Images that do not convey content, are decorative, or contain content that is already conveyed in text are given null alt text (alt="") or implemented as CSS backgrounds. All linked images do not have descriptive alternative text.
  • Equivalent alternatives to complex images are not provided in context or on a separate linked page.
  • Form buttons do not have a descriptive value.
  • Form inputs do not have associated text labels.

1.3.1 Info and Relationships:

  • Semantic markup is not used to designate headings (<h1>), regions/landmarks, lists (<ul>, <ol>, and <dl>), emphasized or special text (<strong>, <code>, <abbr>, <blockquote>.
  • Tables are not used for tabular data and data cells are associated with their headers.
  • Text labels are not associated with form input elements. Related form elements are not grouped with fieldset/legend.

1.3.2 Meaningful Sequence:

  • The reading and navigation order (determined by code order) is in places not logical and intuitive.

1.3.3 Sensory Characteristics:

  • Instructions rely upon shape, size, or visual location.

1.3.5 Identify Input Purpose:

  • Input fields that collect certain types of user information do not have an appropriate autocomplete attribute defined.

1.4.1 Use of Colour:

  • Colour is may be used as the sole method of conveying content or distinguishing visual elements.
  • Colour alone may be used to distinguish links from surrounding text.

1.4.3 Contrast (Minimum):

  • Text and images of text do not have a contrast ratio of at least 4.5:1.
  • Large text - at least 18 point (typically 24px) or 14 point (typically 18.66px) and bold does not have a contrast ratio of at least 3:1.

1.4.10 Reflow:

  • A loss of content or functionality occurs and horizontal scrolling is occurs when content is presented at a width of 320 pixels.

1.4.11 Non-text Contrast:

  • A contrast ratio of at least 3:1 is not present for differentiating graphical objects.
  • At least 3:1 contrast is not provided in the various states (focus, hover, active, etc.) of author-customized interactive components.

1.4.13 Content on Hover or Focus:

  • The newly revealed content cannot be dismissed (generally via the Esc key) without moving the pointer or keyboard focus.

2.1.1 Keyboard:

  • Some page functionality is unavailable using the keyboard.

2.1.2 No Keyboard Trap:

  • Keyboard focus may be locked or trapped at one particular page element.

2.2.1 Timing Adjustable:

  • The application has a time limit, the user is not given options to turn off, adjust, or extend that time limit.

2.4.1 Bypass Blocks:

  • No link is provided to skip navigation and other page elements that are repeated across web pages.
  • No heading structure and/or identification of page regions/landmarks or ‘skip’ link provided.

2.4.2 Page Titled:

  • Page titles are not descriptive or informative.

2.4.3 Focus Order:

  • The navigation order of links, form elements is not logical and intuitive.

2.4.4 Link Purpose (In Context)

  • Some links cannot be determined from the link text alone, or from the link text and its context.
  • Links (or form image buttons) with the same text that go to different locations are not readily distinguishable.

2.4.7 Focus Visible:

  • It is not visually apparent which page element has the current keyboard focus.

2.5.2 Pointer Cancellation:

  • Non-essential down-event (e.g., onmousedown) activation when clicking, tapping, or long pressing the screen does occur.

2.5.3 Label in Name:

  • If an interface component (link, button, etc.) presents text (or images of text), the accessible name (label, alternative text, aria-label, etc.) for that component does not include the visible text.

2.4.5 Multiple Ways:

  • Multiple ways are not available to find other web pages on the site.

3.2.1 On Focus:

  • When a page element receives focus, it can result in a substantial change to the page.

3.2.2 On Input:

  • When a user inputs information or interacts with a control, it does can result in a substantial change to the page.

3.3.1 Error Identification:

  • Required form elements or form elements that require a specific format, value, or length provide this information is not within the element's label.
  • Form validation errors are not efficient, intuitive, and accessible.

3.3.2 Labels or Instructions:

  • Sufficient labels, cues, and instructions for required interactive elements are not provided via instructions.

4.1.1 Parsing:

  • HTML/XHTML validation/parsing errors are not present.

4.1.2 Name, Role, Value:

  • Markup is not used in a way that facilitates accessibility.
  • ARIA is used not used.

4.1.3 Status Messages:

  • If an important status message is presented and focus is not set to that message, the message will not announced to screen reader users.

What we’re doing to improve accessibility

Edinburgh College is due to launch a redesigned application system at the beginning of 2021 which will be fully compliant with WCAG 2.1 guidelines.

Preparation of this accessibility statement

This statement was prepared on 22/09/2020. It was last reviewed on 22/09/2020.