This site is powered by EPrints 3, free software developed by the University of Southampton.
This accessibility statement applies to the Repository of Art Design and Architecture Research (RADAR) (http://radar.gsa.ac.uk/) run by The Glasgow School of Art. RADAR is a Glasgow School of Art application based on the open source EPrints platform. We are working to make sure that the content on RADAR is designed for everyone to find, read, and understand.
We want as many people as possible to be able to use this website. For example, that means you should be able to:
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.
We know some parts of RADAR are not fully accessible, for example:
If users require anything on the repository in a different format or an accessible version of an older research output, please email radar@gsa.ac.uk Please provide details of the output you would like to access and the format you would prefer. We’ll consider your request and get back to you in 10 days.
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, email: radar@gsa.ac.uk
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).
The Glasgow School of Art is committed to making its website and associate subdomains 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 version 2.1 AA standard, due to the non-compliances listed below.
The content listed below is non-accessible for the following reasons.
This section covers issues that we need to fix and are working to do so. The issues listed in this section refer to both the platform (RADAR) and the content hosted on RADAR. Where issues are part of the EPrints platform we may not be able to fix these in house.
Some of the images on our repository don’t have any, or appropriate, alternative text. This will cause difficulty for those who use screen readers or assistive technology and require this information to understand the image and its purpose. This does not meet WCAG 2.1 success criterion 1.1.1 (non-text content).
Some of the headings on RADAR pages are not logically structured. The h2 element appears to be the primary document heading on each page and should be an h1 element. This may affect disabled users who require a meaningful heading hierarchy to help navigate long web pages with assistive technologies. This does not meet WCAG 2.1 success criterion 1.3.1 (info and relationships).
Some of the pages have no page regions defined or ARIA landmarks. Landmarks help assistive technology users orient themselves to a page and help them navigate easily to various sections of a page. This does not meet WCAG 2.1 success criterion 1.3.1 (info and relationships).
Some of the form elements are missing form field labels. This may cause the function or purpose of that form control not to be presented to screen reader users. Form labels also provide visible descriptions and larger clickable targets for form controls. This does not meet WCAG 2.1 success criterion 1.3.1 (info and relationships).
Pages on RADAR do not retain their content or functionality without the need to scroll horizontally when zoomed to 300%. The text on pages does not reflow when zoomed to 400%. This will affect users who need to enlarge web content in order to read it and may not be able to scroll horizontally. This does not meet WCAG 2.1 success criterion 1.4.4 (resize text).
Some buttons on the repository have insufficient contrast between the text and its background. This can cause the text to be difficult to read, especially for those with low vision, poor eyesight or colour blindness. This does not meet WCAG 2.1 success criterion 1.4.6 (contrast enhanced).
Some of the elements of the RADAR homepage and search functionality can’t by accessed using a keyboard alone and requires users to use a mouse. This does not meet WCAG 2.1 success criterion 2.1.1 (keyboard).
RADAR does not have skip links which allow users to bypass repeated content (such as the navigation menu) with their keyboard. Users will have to tab through the menu on every page before they can access the main content. This does not meet WCAG 2.1 success criterion 2.4.1 (bypass blocks).
The purpose of the link text in some of our pages is ambiguous and cannot be determined from the link text alone when read out of context by screen readers. There are also adjacent links that link to the same content which will result in additional navigation and repetition for keyboard and screen reader users. This does not meet WCAG 2.1 success criterion 2.4.4 (link purpose).
Focus indication is not visible on the radio keys within the advanced search function, this will make navigating this form with a keyboard alone difficult. This does not meet WCAG 2.1 success criterion 2.4.7 (focus visible).
RADAR does not have a language specified. Assistive technologies can render text more accurately when the language of the page is identified. This does not meet WCAG 2.1 success criterion 3.1.1 (language of page).
Some documents (word and PDF) contain images that don’t have a description, or alternative text. This will cause difficulty for those who use screen readers or assistive technology who require this information to understand the image and its purpose. This does not meet WCAG 2.1 success criterion 1.1.1 (non-text content).
Some documents (word and PDF) contain tables without a header, this will affect users of screen readers and assistive technology from determining the header from the table content. This does not meet WCAG 2.1 success criterion 1.3.1 (info and relationships).
Some document headings are not logically structured, this will affect disabled users who require a clear and consistent structure to help navigate long documents with assistive technologies. This does not meet WCAG 2.1 success criterion 1.3.1 (info and relationships).
Some PDF documents are ‘untagged’ – tags are hidden elements that indicate the reading sequence of the document. This will affect keyboard and assistive technology users who rely on the tags to reflect the logical order of the document. This does not meet WCAG 2.1 success criterion 1.3.2 (meaningful sequence).
The purpose of the link text in some of our documents is ambiguous and cannot be determined from the link text alone when read out of context by screen readers. This does not meet WCAG 2.1 success criterion 2.4.4 (link purpose).
Some documents do not have a language specified. Assistive technologies can render text more accurately when the language of the document page is identified. This does not meet WCAG 2.1 success criterion 3.1.1 (language of page).
We have not identified any issues that we believe to be a disproportionate burden.
PDFs and other documents
The accessibility regulations do not require us to fix PDFs or other documents published before 23 September 2018 if they’re not essential to providing our services.
Any new PDFs or Word documents we publish will meet accessibility standards.
Heritage Collections
The accessibility regulations do not require us to fix reproductions of items in heritage collections and therefore we will not be making our ‘Mackintosh Dissertations’ accessible due to the unavailability of automated and cost-efficient solutions that would easily extract the text of these manuscripts and transform it into content compatible with the accessibility requirement.
This statement was prepared on 21 September 2020. It was last reviewed on 21 September 2020.
This website was last tested on 18 September 2020. The test was carried out by The Glasgow School of Art.
How we tested RADAR
Testing was carried out by
