Accessibility statement for eGo, Online applications and Online payments
This accessibility statement applies to eGo, Online applications and Online payments webpages on the domain https://resources.gsmd.ac.uk
This website is run by Guildhall School of Music & Drama under license agreement with the application provider Tribal Education Ltd. 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)
- navigate through links and understand their purposes from the link text
- use pages when stylesheets are disabled
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 aren’t fully accessible:
- some forms (short course bookings) may not be easily readable by a screen reader
- some of our online forms (short course bookings) are difficult to navigate using just a keyboard
- most older PDF documents aren’t fully accessible to screen reader software
- some PDF documents created from html files aren’t fully accessible to screen reader software
- two BMus Elective videos hosted on YouTube are not captioned and do not have transcripts
Please see technical detail below
What to do if you can’t access parts of this website
If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille:
- email email@example.com
- call 02073827181
- make an appointment to visit in person at the Registry Office, Level 5, Milton Court, 1 Milton Street, London, EC2Y 9BH
Reporting accessibility problems with this website
We’re always looking to improve the accessibility of this website. If you find any problems that aren’t listed in this statement or think we’re not meeting accessibility requirements, please contact the Registry Office with details including screenshots if relevant: firstname.lastname@example.org
If you are not happy with the initial response within the Guildhall School you can contact email@example.com to escalate your request.
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 requests, you can contact the Equality Advisory and Support Service (EASS).
Contacting us by phone or visiting us in person
Throughout Milton Court we have an Infra-Red system for those who are hearing impaired. All floors and venues in Milton Court are fully accessible, except for the cloakroom on Level -1 – staff will arrange your cloakroom items to be taken down for you upon request at the entrance. In our Silk Street building, hearing loops are provided in the Music Hall and Theatre, with all venues suitable for wheelchair users.
Download our Milton Court Access Guides from the Visiting Us webpage to find out more about accessibility in Milton Court.
Technical information about this website’s accessibility
Guildhall School of Music & Drama is committed to making this website 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 and exemptions listed below.
Non accessible content
The content listed below is non-accessible for the following reasons.
- With the release of v10.0, the web content of this software used by the Guildhall School is fully compliant with the WCAG 2.1 AA standard, however this version will not be implemented until November 2020. The majority of the software already meets and exceeds WCAG 2.0 AA standard. The three biggest gaps in WCAG 2.0 are related to:
- mobile technology
- low vision
- cognitive disabilities.
- known technical issues logged with the software supplier (see details below)
- In particular, the Short Course bookings template provided by the supplier will not be fully compliant until version 10.0. The Guildhall School is currently testing the new template and can provide an alternative if needed.
- Content that is configured internally by the Guildhall School or through consultancy that has not been updated or changed recently is expected to meet the standards but will not be tested until next updated
- most PDF documents for earlier academic cycles aren’t fully accessible to screen reader software but are not expected to be accessed
- PDF documents containing personal data created via html from the student records system aren’t fully accessible to screen reader software
- two BMus elective choice videos hosted on YouTube are auto captioned and do not have transcripts
- Student Experience Festival Recordings hosted on eStream are not captioned and do not have transcripts
- Embedded cookie message popup may not be fully accessible
Non compliance with the accessibility regulations
The accessibility problems and plans to fix them are listed in the ‘Navigation and accessing information’, ‘Images and video content’, ‘Interactive tools and transactions’ and ‘PDFs and other documents’ sections.
Web content on this site consists of a mixture of template content from the software supplier and internally configured content from the Guildhall School. The software supplier will not release fully accessible content until Version 10.0 (May 2020) which the Guildhall School will implement in November 2020. The Guildhall School has assessed the cost, time and resources required for doing a detailed WCAG 2.1 evaluation prior to then. We believe that doing so now would be a disproportionate burden within the scope and meaning of the accessibility regulations. Please see the results of our Second Basic Accessibility Check in the next sections, and the ‘What we’re doing to improve accessibility’ for our plans for future audit.
PDF documents (see ‘PDFs and other documents’) for academic years prior to 2020/21 are not expected to be accessed and therefore it would be a disproportionate burden to update them. See ‘What to do if you can’t access parts of this website’ for details of how to request content in alternative formats.
The process to generate PDF files containing personal student data from the student records system has been investigated during 19/20 and the free software currently being used does not enable us to meet accessibility standards. We’ve assessed the cost of replacing the software during 2019/20 however we believed that doing so during Summer Term 2019/20 was a disproportionate burden within the meaning of the accessibility regulations. We will investigate alternatives and make another assessment before the end of 2020/21.
Recordings of videos containing guidance information were added during the Covid-19 pandemic. The information was also available via other resources and on request. The Guildhall School has assessed the cost, time and resources required for adding closed captions and transcripts and believe that doing so at the time would be a disproportionate burden within the scope and meaning of the accessibility regulations. See ‘What to do if you can’t access parts of this website’ for details of how to request content in alternative formats.
Navigation and accessing information
- Navigation bar on every eGo page hasn’t got an accessible name: [WCAG2 1.1.1/1.3.1/3.3.2/4.1.2 (A)] User interface controls without a label should have an accessible name. Logged with Tribal PPL 729828
- Form control labels on search box on every evision page are not unique: [WCAG2 2.4.6 (AA)] Form control labels must be unique. ACTION: Logged with Tribal PPL 729828 and will optimise search contents
- In some old content, table and header cells are not all explicitly associated in complex data tables [WCAG2 1.3.1 (A)]. ACTION: We will review content as it is updated during 2020/21
- Errors with embedded script for cookie message popup: WCAG2 2.1.1 (A)] a tags or area tags without an 'href' cannot receive keyboard focus, [WCAG2 1.4.3 (AA)] Text within this element has a low contrast ratio Detected ratio: 4. ACTION: Added to development requirements for 2020/21
- Short Course bookings form may not be navigable using keyboard. ACTION: Should be fixed by release of 10.0 in November 2020
- eGo ‘Vista’ and datatables (lists of records for staff) pagination has missing/unnecessary aria tags, needs accessible description and has some areas of low contrast: [WCAG2 1.3.1 (A)] Distinguish between navigation groups using an ARIA label, You should not use ARIA roles, that are the default for the element, [WCAG2 1.4.3 (AA)] Text within this element has a low contrast ratio Detected ratio: 4.48, [WCAG21 1.3.1 (A)] Provide an accessible description for complex data tables. ACTION: Logged with Tribal PPL 729828, Colour contrast across system to be reviewed during 20/21
- Google Tag Manager adds two empty script tags with blank IDs at the bottom of each page. ACTION: Logged with marketing manager
- Repeated table on application form causing unique reference errors: The value of the attribute must match an id in the same document, [WCAG21 1.3.1 (A)] Provide an accessible description for complex data tables, [WCAG21 1.3.1/2.4.6 (A/AA)] Unique accessible name required. ACTION: Logged with Tribal PPL 728871
Images and video content
- Prerecorded video does not have captions or a transcript [WCAG2 1.2]. ACTION: Pre-recorded audio and video published before 23 September 2020 are exempt however these will be replaced in the next year or two as part of normal business.
Interactive tools and transactions
- Form on all Static html pages e.g. paypal.html doesn't have visual error identifiers (does have text) (or vice versa): [WCAG2 3.3.1] Error Identification. ACTION: Added to development requirements Summer 2021
- Some error messages do not provide suggestions for correcting input errors [WCAG2 3.3.3]. ACTION: Added to development requirements Summer 2021
- Short Course bookings form may not be understandable with a screen reader and completion via a keyboard may not be possible. ACTION: Should be fixed by release of 10.0 in November 2020
- Forms using the ‘Chosen’ widget supplied by Tribal have issues with title, contrast and tags for presentation: [WCAG2 2.4.4/2.4.9 (A/AAA)] Is the 'title' text deliberately empty?, [WCAG2 1.4.3 (AA)] Text within this element has a low contrast ratio. Detected ratio: 3.62, [WCAG2 1.3.1 (A)] Use CSS for presentation effect. ACTION:Tribal confirmed no impact to title and presentation tags however check if still exists after 10.0 update. ACTION: Colour contrast across system to be reviewed during 20/21
- Activating a component that reveals hidden content does not move input focus into the revealed content [WCAG2 2.4.3]. ACTION: Added to development requirements Summer 2021
- Some of our interactive forms do not allow the user to check and review their answers before submitting them. We intended to implement a new enrolment form however this was delayed until at least September 2021. ACTION: The replacement enrolment form will incorporate a check process, and as application forms are replaced in the future these will also follow the same structure.
- Form (‘Task’) with a final step of certain format has no submit button: [WCAG2 3.2.2 (A)] A submit button is missing. ACTION: Review each form when next updated & check options with Tribal.
- Aria tags added into Tribal’s template forms (‘Tasks’) do not appear in the page. ACTION:Review areas where used during 2020/21 and check otherwise usuable
- Uploading documents (using ‘Plupload’ widget provided by supplier) has a link containing invalid script: The 'href' attribute does not have a valid value: It is an invalid URI, most likely containing invalid characters such as spaces (see rfc3986). ACTION: Logged with Tribal PPL 729828
Content that’s not within the scope of the accessibility regulations
The regulations apply to publicly facing webpages. Pages for staff do not need to demonstrate compliance but through a wider commitment to accessibility Tribal and the Guildhall School are also amending staff screens where possible.
The accessibility regulations don’t require us to fix intranet content behind a login (including eGo and our application forms) published before September 2019 until they are reviewed however we have agreed a plan for review in order of priority.
PDFs and other documents
Many of our older PDFs and Word documents don’t meet accessibility standards - for example, they may not be structured so they’re accessible to a screen reader. This doesn’t meet WCAG 2.1 success criterion 4.1.2 (name, role value).
The accessibility regulations don’t require us to fix PDFs or other documents published before 23 September 2018 if they’re not essential to providing our services. For example, we do not plan to fix documents previously generated by the student records system as an audit trail, or files we no longer expect to be accessed. See ‘What to do if you can’t access parts of this website’ for details of how to request content in alternative formats.
Some of our PDFs and Word documents are essential to providing our services. For example, we have PDFs with information on how users can access our services, and forms published as Word documents. For the 2020/21 academic year onwards we have either fixed these or replace them with accessible HTML pages.
Any new PDFs or Word documents we publish will meet accessibility standards.
How we tested this website.
This website was last tested by the Guildhall School between 01/07/2020 and 21/09/2020. The basic accessibility test was carried out by the Assistant Registrar – Student Database Support at the Guildhall School using TotalValidator, NVDA and inspection.
We used this approach to deciding on a sample of pages to test:
- All completely customised content (Course Link Pages and Paypal forms)
- An example of dynamic content including a mixture of supplier provided and customised content for a wide range of users)
- An example of dynamic content including a mixture of supplier provided and customised content for external applicants)
- New content created or significantly updated for enquirers, applicants and students during this time
- our application course links
- our login page
- our student enrolment task on our student records portal (eGo) content (behind a login)
- our mailing list form
- Our Higher Education online applications content (behind a login), an example at 21/09/2020
- our Higher Education eGo Applicant page (behind a login)
- our accessibility page
- our Terms and Conditions page
Additional areas of non-compliance have been logged from tests with other new content during 2019/20.
What we’re doing to improve accessibility
We plan to:
- upgrade the software to v10.0 in November 2020 and apply hotfixes after then to ensure that template content is fully compliant to WCAG 2.1 AA standard
- complete an audit on existing content if not already tested during the 2020/21 academic year
- monitor known issues (see details in non-compliance section) including those reported to our supplier
- report new issues with the software supplied template to the supplier
- consult with technical support to ensure we can generate accessible PDF documents within the database
- undertake development in specific areas (see details in non-compliance section)
- document common problems to avoid recurrence in future
- optimise search options
- test all new content for accessibility as it is published
- review this accessibility statement annually.
If you would like to find out more about our accessibility plans and roadmap for this site please contact us on firstname.lastname@example.org
This statement was prepared on 21 September 2019. It was last updated on 30 September 2020.