This website is run by Glasgow Life (Culture and Sport Glasgow (Trading) CIC).  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.

 

 

How accessible this website is:

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

  • Some search buttons do not have discernable and accessible text. This fails WCAG 2.1 success criterion 1.2 (Name, Role, Value)

  • Element has insufficient colour contrast of 2.57 (foreground colour: #afa07d, background colour: #ffffff, font size: 42.0pt (56px), font weight:              bold). Expected contrast ratio of 3:1, Elements have insufficient colour contrast of 3.94 (foreground colour: #808080, background colour: #ffffff,          font size: 9.0pt (12px), font weight: normal). Expected contrast ratio of 4.5:1. This fails WCAG 2.1 success criterion 4.3 (Contrast (Minimum))

  • The site and some documents have active elements with the same id attribute: js-menu-gm. This fails WCAG 2.1 success criterion 1.1 (Parsing)

  • Page titles should be more descriptive so that they help the user navigate the site easily. This fails WCAG 2.1 success criterion 4.2 (Page Titled)

 

  • Visual focus indicator is not sufficient on the search button on the search overlay and is not consistent throughout the site. This fails WCAG 2.1            success criterion 4.7 (Focus Visible)

 

  • Some skip to links do not become visible on focus. This fails WCAG 2.1 success criterion 4.1 (Bypass blocks)

 

  • An aria role has been used that requires children roles but these child roles are not present. This fails WCAG 2.1 success criterion 3.1 (Info and            relationships)

 

  • Element has insufficient colour contrast of 2.57 (foreground colour: #afa07d, background colour: #ffffff, font size: 18.0pt (24px), font weight:          bold). Expected contrast ratio of 3:1. Element has insufficient colour contrast of 2.57 (foreground colour: #ffffff, background colour: #afa07d,              font size: 21.6pt (28.8px), font weight: bold). Expected contrast ratio of 3:1. Element has insufficient colour contrast of 4 (foreground colour:              #7f7f7f, background colour: #ffffff, font size: 9.0pt (12px), font weight: bold). Expected contrast ratio of 4.5:1. Element has insufficient colour            contrast of 3.04 (foreground colour: #90949c, background colour: #ffffff, font size: 8.3pt (11px), font weight: normal). Expected contrast ratio            of 4.5:1. This fails WCAG 2.1 success criterion 4.3 (Contrast (Minimum))

 

  •  Decorative images are missing a null alt tag. This fails WCAG 2.1 success criterion 1.1 (Non-text Content)

 

  • Images containing text have been used. This fails WCAG 2.1 success criterion 4.5 (Images of Text)

 

  • Links are missing accessible text on several pages. There are a lot of links contained within the Facebook widget that do not provide additional context. This fails WCAG 2.1 success criterion 1.2 (Name, Role, Value) and 2.4.4 (Link Purpose (In context))

 

  • There are skipped headings. This fails WCAG 2.1 success criterion 3.1 (Info and relationships), 2.4.1 (Bypass Blocks) and 2.4.6 (Headings and Labels)

 

  • Focus goes to the main navigation before the linked logo. This fails WCAG 2.1 success criterion 4.3 (Focus Order)

 

  • Cookie policy link received focus after the main navigation items and before the Kelvin Hall logo. This fails WCAG 2.1 success criterion 4.3 (Focus Order)

 

  • Visual focus indicator is not sufficient on the search button on the search overlay. This fails WCAG 2.1 success criterion 4.7 (Focus Visible)

 

  • Close button on the search overlay does not receive keyboard focus. This fails WCAG 2.1 success criterion 1.1 (Keyboard)

 

  • Indicate that there is a secondary navigation present on the page to a screen reader. This fails WCAG 2.1 success criterion 3.1 (Info and relationships)

 

  • Page titles should be more descriptive and provide organisation. This fails WCAG 2.1 success criterion 4.2 (Page Titled)

 

  • Breadcrumbs are not marked up adequately for screen reader users. This fails WCAG 2.1 success criterion 1.2 (Name, Role, Value)

 

  • Tables have been used but they are not marked up adequately for the information they contain. This fails WCAG 2.1 success criterion 3.1 (Info and Relationships) and 1.3.2 (Meaningful Sequence)

 

  • Accordions have not been applied correctly - focus goes to the login to book link contained within the panel before moving to the next accordion. This fails WCAG 2.1 success criterion 4.3 (Focus Order)

 

  • Entire accordion area for the class timetable is not accessible to screen reader users. Accordions do not expand via keyboard and therefore it is not possible to Login to Book a class via the screen reader. This fails WCAG 2.1 success criterion 1.1 (Keyboard)

 

  • Ambiguous links are present and need to be more descriptive. This fails WCAG 2.1 success criterion 4.4 (Link Purpose (In Context))

 

  • There are colour contrast issues present throughout the site. This fails WCAG 2.1 success criterion 4.3 (Contrast (Minimum))

 

  • Form inputs are not adequately labelled - need specific labels. This fails WCAG 2.1 success criterion 1.1 (Non text Content), 1.3.1 (Info and Relationships), 2.4.6 (Headings and Labels), and 3.3.2 (Labels or Instructions)

 

  • Images are missing alternative tags. This fails WCAG 2.1 success criterion 1.1 (Non-text Content)

 

  • Date picker interaction is not accessible for keyboard users. Tabbing to the "To" date picker results in the page refreshing and focus returning to the top of the page. This seems to be a bug and prevents a keyboard user from adequately searching this page for an event. This fails WCAG 2.1 success criterion 1.1 (Keyboard) and 3.2.1 (On focus)

 

  • Buttons do not has discernable and accessible text. This fails WCAG 2.1 success criterion 1.2 (Name, Role, Value)

 

  • Links are not marked up adequately for screen readers -visually displaying that the link will open in another window or go to another site but this is not conveyed to the screen reader. This fails WCAG 2.1 success criterion 4.4 (Link Purpose (In context))

 

  • Linked images are present on the search results. These appear as redundant and therefore should be removed from the code. This fails WCAG 2.1 success criterion 1.1 (Parsing) and 4.1.2 (Name, Role, Value)

 

  • Number of search results text should be assigned a h2. This fails WCAG 2.1 success criterion 3.1 (Info and relationships)

 

  • Elements do not receive focus when the video is expanded. This fails WCAG 2.1 success criterion 1.1 (Keyboard)

 

  • Images are present which need a null alt tag or have role = presentation applied. This fails WCAG 2.1 success criterion 1.1 (Non-text Content)

 

  • The videos presented do not contain audio and are image and text based with music. This fails WCAG 2.1 success criterion 2.1 (Audio-only and Video-only (Pre-recorded))

 

  • Logo overlaps text at specific breakpoints

 

 

Feedback and contact information

If you need information on this website in a different format:

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

 

 

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, contact:

 

 

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)(opens in a new tab).

 

 

Technical information about this website’s accessibility

 

Glasgow Life is committed to making its website 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 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.

 

Non-compliance with the accessibility regulations:

 

  • Some search buttons do not have discernable and accessible text. This fails WCAG 2.1 success criterion 1.2 (Name, Role, Value)

 

  • Element has insufficient colour contrast of 2.57 (foreground colour: #afa07d, background colour: #ffffff, font size: 42.0pt (56px), font weight: bold). Expected contrast ratio of 3:1, Elements have insufficient colour contrast of 3.94 (foreground colour: #808080, background colour: #ffffff, font size: 9.0pt (12px), font weight: normal). Expected contrast ratio of 4.5:1. This fails WCAG 2.1 success criterion 4.3 (Contrast (Minimum))

 

  • The site and some documents have active elements with the same id attribute: js-menu-gm. This fails WCAG 2.1 success criterion 1.1 (Parsing)

 

  • Page titles should be more descriptive so that they help the user navigate the site easily. This fails WCAG 2.1 success criterion 4.2 (Page Titled)

 

  • Visual focus indicator is not sufficient on the search button on the search overlay and is not consistent throughout the site. This fails WCAG 2.1 success criterion 4.7 (Focus Visible)

 

  • Some skip to links do not become visible on focus. This fails WCAG 2.1 success criterion 4.1 (Bypass blocks)

 

  • An aria role has been used that requires children roles but these child roles are not present. This fails WCAG 2.1 success criterion 3.1 (Info and relationships)

 

  • Element has insufficient colour contrast of 2.57 (foreground colour: #afa07d, background colour: #ffffff, font size: 18.0pt (24px), font weight: bold). Expected contrast ratio of 3:1. Element has insufficient colour contrast of 2.57 (foreground colour: #ffffff, background colour: #afa07d, font size: 21.6pt (28.8px), font weight: bold). Expected contrast ratio of 3:1. Element has insufficient colour contrast of 4 (foreground colour: #7f7f7f, background colour: #ffffff, font size: 9.0pt (12px), font weight: bold). Expected contrast ratio of 4.5:1. Element has insufficient colour contrast of 3.04 (foreground colour: #90949c, background colour: #ffffff, font size: 8.3pt (11px), font weight: normal). Expected contrast ratio of 4.5:1. This fails WCAG 2.1 success criterion 4.3 (Contrast (Minimum))

 

  • Decorative images are missing a null alt tag. This fails WCAG 2.1 success criterion 1.1 (Non-text Content)

 

  • Images containing text have been used. This fails WCAG 2.1 success criterion 4.5 (Images of Text)

 

  • Links are missing accessible text on several pages. There are a lot of links contained within the Facebook widget that do not provide additional context. This fails WCAG 2.1 success criterion 1.2 (Name, Role, Value) and 2.4.4 (Link Purpose (In context))

 

  • There are skipped headings. This fails WCAG 2.1 success criterion 3.1 (Info and relationships), 2.4.1 (Bypass Blocks) and 2.4.6 (Headings and Labels)

 

  • Focus goes to the main navigation before the linked logo. This fails WCAG 2.1 success criterion 4.3 (Focus Order)

 

  • Cookie policy link received focus after the main navigation items and before the Kelvin Hall logo. This fails WCAG 2.1 success criterion 4.3 (Focus Order)

 

  • Visual focus indicator is not sufficient on the search button on the search overlay. This fails WCAG 2.1 success criterion 4.7 (Focus Visible)

 

  • Close button on the search overlay does not receive keyboard focus. This fails WCAG 2.1 success criterion 1.1 (Keyboard)

 

  • Indicate that there is a secondary navigation present on the page to a screen reader. This fails WCAG 2.1 success criterion 3.1 (Info and relationships)

 

  • Page titles should be more descriptive and provide organisation. This fails WCAG 2.1 success criterion 4.2 (Page Titled)

 

  • Breadcrumbs are not marked up adequately for screen reader users. This fails WCAG 2.1 success criterion 1.2 (Name, Role, Value)

 

  • Tables have been used but they are not marked up adequately for the information they contain. This fails WCAG 2.1 success criterion 3.1 (Info and Relationships) and 1.3.2 (Meaningful Sequence)

 

  • Accordions have not been applied correctly - focus goes to the login to book link contained within the panel before moving to the next accordion. This fails WCAG 2.1 success criterion 4.3 (Focus Order)

 

  • Entire accordion area for the class timetable is not accessible to screen reader users. Accordions do not expand via keyboard and therefore it is not possible to Login to Book a class via the screen reader. This fails WCAG 2.1 success criterion 1.1 (Keyboard)

 

  • Ambiguous links are present and need to be more descriptive. This fails WCAG 2.1 success criterion 4.4 (Link Purpose (In Context))

 

  • There are colour contrast issues present throughout the site. This fails WCAG 2.1 success criterion 4.3 (Contrast (Minimum))

 

  • Form inputs are not adequately labelled - need specific labels. This fails WCAG 2.1 success criterion 1.1 (Non text Content), 1.3.1 (Info and Relationships), 2.4.6 (Headings and Labels), and 3.3.2 (Labels or Instructions)

 

  • Images are missing alternative tags. This fails WCAG 2.1 success criterion 1.1 (Non-text Content)

 

  • Date picker interaction is not accessible for keyboard users. Tabbing to the "To" date picker results in the page refreshing and focus returning to the top of the page. This seems to be a bug and prevents a keyboard user from adequately searching this page for an event. This fails WCAG 2.1 success criterion 1.1 (Keyboard) and 3.2.1 (On focus)

 

  • Buttons do not has discernable and accessible text. This fails WCAG 2.1 success criterion 1.2 (Name, Role, Value)

 

  • Links are not marked up adequately for screen readers -visually displaying that the link will open in another window or go to another site but this is not conveyed to the screen reader. This fails WCAG 2.1 success criterion 4.4 (Link Purpose (In context))

 

  • Linked images are present on the search results. These appear as redundant and therefore should be removed from the code. This fails WCAG 2.1 success criterion 1.1 (Parsing) and 4.1.2 (Name, Role, Value)

 

  • Number of search results text should be assigned a h2. This fails WCAG 2.1 success criterion 3.1 (Info and relationships)

 

  • Elements do not receive focus when the video is expanded. This fails WCAG 2.1 success criterion 1.1 (Keyboard)

 

  • Images are present which need a null alt tag or have role = presentation applied. This fails WCAG 2.1 success criterion 1.1 (Non-text Content)

 

  • The videos presented do not contain audio and are image and text based with music. This fails WCAG 2.1 success criterion 2.1 (Audio-only and Video-only (Pre-recorded))

 

  • Logo overlaps text at specific breakpoints

 

 

 

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

   

 

Pre-recorded videos

Some pre-recorded videos don’t have an audio captioning or description, so the information in them isn’t available to people who cannot see or the hear the video content. This doesn’t meet WCAG 2.1 success criterion 1.2.2, 1.2.3, 1.2.5.

The accessibility regulations do not require us to fix pre-recorded videos published before 23 September 2018 if they’re not essential to providing our services.

When we publish new content, we’ll make sure our use of images meets accessibility standards.

 

 

What we’re doing to improve accessibility

We are always open to suggestions, additions or the reporting of accessibility problems. Users can use the contact details supplied above.

  • We plan to address all above non-compliant criteria by December 2020.

 

 

 

Preparation of this accessibility statement

 

The audit included a full evaluation the site against the WCAG level AA accessibility guidelines version 2.1, producing a report highlighting all issues and recommendations to rectify any issues.

 

Website evaluation included review of the following sections (some of these pages are no longer available):

 

  1. Homepage: https://kelvinhall.org.uk/

  2. About page: https://kelvinhall.org.uk/about/

  3. Classes page: http://kelvinhall.org.uk/glasgow-club/classes/

  4. Class page: http://kelvinhall.org.uk/glasgow-club/classes/body-attack-level-3-5/

  5. Contact page: https://kelvinhall.org.uk/visit/

  6. Error page: https://kelvinhall.org.uk/page-not-found

  7. Events: https://kelvinhall.org.uk/whats-on/Events/?eventId=f68bf7dd-cd28-4302-a102-ab4401389ac0

  8. Link directory page: https://kelvinhall.org.uk/about/collections-at-kelvin-hall/

  9. News page: https://kelvinhall.org.uk/about/blog/

  10. News article: https://kelvinhall.org.uk/glasgow-club/latest-news/kelvin-hall-staff-get-back-on-their-bikes-and-take-millport-by-storm/

  11. Partner landing page: https://kelvinhall.org.uk/university-of-glasgow/

  12. Partner article page: https://kelvinhall.org.uk/national-library-of-scotland/about-us/

  13. Search page: https://kelvinhall.org.uk/search-results/?s=glasgow

  14. Video page: https://kelvinhall.org.uk/about/kelvin-hall-on-film/

  15. What’s on: https://kelvinhall.org.uk/whats-on/


We tested: our main website platform, available at kelvinhall.org.uk.

 

This statement was prepared on 23rd September 2020. It was last updated on 28th September 2020.

 

 

  • 1445 Argyle Street Glasgow G3 8AW Scotland
How to get here