Accessibility statement for University of Edinburgh Event Booking System

• zoom in up to 200% 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 Job Access with Speech (JAWS), NonVisual Desktop Access (NVDA) and VoiceOver)
• use the system and it will not time you out

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

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 to make it easier to read and navigate.

Additional information on how to customise our website appearance

If you are a member of the University staff or a student you can use the free Sensus Access accessible document conversion service.

SenusAccess Information

How accessible this website is

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

• some parts may not be fully compatible with screen readers i.e. due to labeling of headings
• It is not possible to access all content by using the keyboard alone or always clear where a user has tabbed too.
• Not all non-text content has text alternatives
• some text may not reflow in a single column when you change the size of the browser window and at certain levels of magnification
• Not all colour contrasts meet the recommended WCAG 2.1 AA standards

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 Service.management@ed.ac.uk
• telephone +44 (0)131 650 9299
• British Sign Language (BSL) users can contact us via contactSCOTLAND-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’re 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 let us know.

• email Service.management@ed.ac.uk
• telephone +44 (0)131 650 9299
• British Sign Language (BSL) users can contact us via contactSCOTLAND-BSL, the on-line BSL interpreting service.

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

contactSCOTLAND-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 24 hours a day, 7 days a week.

contactSCOTLAND-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.

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

The full guidelines are available at:

Web Content Accessibility Guidelines (WCAG) 2.1 AA standard

Non accessible content

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

Noncompliance with the accessibility regulations

The following items to not comply with the WCAG 2.1 AA success criteria:

Page structure

• There are some missing table headings for tables on the site.    

  • Criterion 1.3.1: Info and Relationships
• There are no page landmark regions in use across both The University of Edinburgh Events Booking page and The University of Edinburgh Events Booking Attendance recorder
  • Criterion 2.4.1: Bypass blocks

Keyboard access

• Not all parts of the admin site are accessible using the keyboard including the pop-up calendar, some drop downs and toggles within the attendance recorder.   

  • Criterion 2.1.2 No Keyboard Trap
  • Criterion 2.1.4: Character Key Shortcuts
  • Criterion 2.4.3: Focus Order

• The focus highlighting may be difficult to see on the page.

  • Criterion 2.4.7: Focus Visible

Forms

• Labels are being used as titles for displaying content that cannot be edited in a number of places across the site and are not associated with form controls.

  • Criterion 3.3.2 Labels or Instructions
  • Criterion 4.1.1: Parsing
• The “required” attribute is not being used on required fields across The University of Edinburgh Events Booking page.
  • Criterion 1.3.1: Info and Relationships
• On the buttons, the title attribute is being used instead of link text which is not supported on all screen readers.  Keyboard shortcuts are being defined but do not work.  Tables are being used for layout.
  • Criterion 1.3.1: Info and Relationships
  • Criterion 2.1.4 Character Key Shortcuts
  • Criterion 2.4.4: Link Purpose (In Context)
• Invalid form submission on the Events Admin site does not properly identify the individual field validation errors.
  • Criterion 3.3.1 Error Identification
• On The University of Edinburgh Events Booking page and The University of Edinburgh Events Booking Administrator page, the spellcheck attribute is not applied to any text inputs.
  • Criterion 3.3.3 Error Suggestion

Legibility

• There may not be sufficient colour contrast between font and background colours especially where the text size is very small.

  • Criterion 1.4.3: Contrast (Minimum)

Images and icons

• The alt text on the Attendance recorder image is “The University of Edinburgh home” which is not appropriate since the image is not a link to the University’s website. Title text is being used for some graphic’s alternative text.

  • Criterion 2.4.4: Link Purpose (In Context)

Content

• Pages on The University of Edinburgh Events Booking page, The University of Edinburgh Events Booking Administrator page and the Attendance Recorder’s registration page at are not defining the human language in use on the page. 

  • Criterion 3.1.1: Language of Page

Links

• There is no “skip to content” link available in the The University of Edinburgh Events Booking and The University of Edinburgh Events Booking Administrator sites.

  • Criterion 2.4.1: Bypass blocks
• On the “create event” form, there are multiple buttons (styled as links) all with just the text “definition”.
  • Criterion 2.4.4: Link Purpose (In Context)

JavaScript

• The date lookup widget and rich text editor used on the Admin site are not accessible.

  • Criterion 2.1.1: Keyboard
  • Criterion 4.1.2: Name, Role, Value
  • Criterion 1.4.13 Content on Hover or Focus

Customisation

• There is no text fallback for the rich text editor buttons when not loading CSS so the buttons are indistinguishable. 

  • Criterion 1.1.1: Non-text Content

Scaling

• Horizontal scrolling is required on The University of Edinburgh Events Booking Page and The University of Edinburgh Events Booking Administrator Page for viewing the site on narrow viewports (320px width).

  • Criterion 1.3.4: Orientation
  • Criterion 1.4.10 Reflow

NVDA compatibility

• Landmark navigation is not possible across any of the sites.

  • Criterion 1.3.1: Info and Relationships
  • Criterion 2.4.1: Bypass blocks
• In the Attendance Recorder, when the screen content changes nothing is announced to the user so the user is unaware of any action taking place.
  • Criterion 4.1.2: Name, Role, Value
  • Criterion 4.1.3 Status Messages
• In the Attendance Recorder, NVDA announces the event title as a “clickable list” however it is not focusable and so is not clickable using keyboard navigation.  None of the content in collapsible divisions is available to NVDA.
  • Criterion 2.1.1: Keyboard
  • Criterion 2.4.3 Focus Order
• It is not possible to navigate to the attended toggles nor change attendees’ status in NVDA using the keyboard.
  • Criterion 2.1.1: Keyboard
  • Criterion 2.4.3 Focus Order
• NVDA is unable to properly read out the link titles in the header where block capitals are used.   
  • Criterion 2.4.4: Link Purpose (In Context)
• None of the labels for fields are read out so the user does not know what the current input field is for. 
  • Criterion 3.3.2 Labels or Instructions
• Required form fields are not announced as such.
  • Criterion 1.3.1: Info and Relationships
• The validation error message for a form field is not announced.
  • Criterion 3.3.1 Error Identification
• Using keyboard shortcuts to change text styling (eg turning Bold on/off) in the rich text area is not announced to the user and the content area is a focus trap.
  • Criterion 2.1.4: Character Key Shortcuts
  • Criterion 2.1.2: No Keyboard Trap
• In Event Listing tables in the Admin site, the event for the row you are on is not announced because it is just an ordinary cell in the table row for the first schedule but empty if for second and subsequent schedules.  
  • Criterion 1.3.1: Info and Relationships

JAWS compatibility

• Landmark navigation is not possible across any of the sites.

  • Criterion 1.3.1: Info and Relationships
  • Success Criterion 2.4.1: Bypass blocks
• In the Attendance Recorder, when the screen content changes nothing is announced to the user.   
  • Criterion 4.1.2: Name, Role, Value
  • Criterion 4.1.3 Status Messages
• In the Attendance Recorder, none of the content in collapsible divs is available to JAWS.
  • Criterion 2.1.1: Keyboard
  • Criterion 2.4.3 Focus Order
• It is not possible to navigate to the attended toggles nor change attendees’ status in JAWS using the keyboard.
  • Criterion 2.1.1: Keyboard
  • Criterion 2.4.3 Focus Order
• JAWS is unable to properly read out the link titles in the header where block capitals are used. 
  • Criterion 2.4.4: Link Purpose (In Context)
• None of the labels for fields are read out so the user does not know what the current input field is for.
  • Criterion 3.3.2 Labels or Instructions
• Required form fields are not announced as such.
  • Criterion 1.3.1: Info and Relationships
• The validation error message for a form field is not announced when it gains focus.
  • Criterion 3.3.1 Error Identification
• Using keyboard shortcuts to change text styling (eg turning Bold on/off) in the rich text area is not announced to the user and the content area is a focus trap.
  • Criterion 2.1.4: Character Key Shortcuts
  • Criterion 2.1.2: No Keyboard Trap
• In Event Listing tables in the Admin site, the event for the row you are on is not announced because it is just an ordinary cell in the table row for the first schedule but empty if for second and subsequent schedules. 
  • Criterion 1.3.1: Info and Relationships  

Unless specified otherwise, a complete solution, or significant improvement, will be in place for those items within our control by March 2021.

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 do not believe that any content is outside the scope of the accessibility regulations.

What we’re doing to improve accessibility

We will continue to address the accessibility issues highlighted, alongside working to deliver a solution or suitable workaround. Unless specified otherwise, a complete solution or significant improvement will be in place for those items within our control by March 2021.

While we are in the process of resolving these accessibility issues, or where we are unable, 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 31/07/2020. It was last reviewed on 21/08/2020.

The Events sites were last tested by the Information Services Group Applications Development Team in July 2020, primarily using Chrome. Chrome was chosen as it has been identified as the most popular browser when using a screen reader. The site was also tested using Internet Explorer as it is still used by around 15% of screen reader users, even though Internet Explorer cannot support many modern features.

The two most popular screen-readers were used to test the site: NVDA (with Chrome) and JAWS (with Internet Explorer) as well as ZoomText (with Chrome) and TextHelp Read&Write (with Internet Explorer).

World-wide usage levels for different screen readers and browers can be found in the WebAIM annual surveys

We tested:

• Spellcheck functionality
• Data validation
• Scaling using different resolutions
• Options to customise the interface (magnification, font and background colour changing etc)
• Keyboard navigation
• Warning of links opening in a new tab or window
• Information conveyed in colour or sound only
• Flashing or scrolling text
• Operability if Javascript is disabled
• Use with screenreading software (JAWS)
• TextHelp Read and Write (assistive software)
• Zoomtext (assistive software)
• Time limits