The Attain Virtual Learning Environment and the Mahara e-portfolio are run by South and City College Birmingham. Attain is based on the Moodle platform and as such is compliant to WCAG 2.0 but only partially compliant to WCAG 2.1 AA, however, 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 these websites are not fully accessible:
most older PDF, Word, PowerPoint and Excel documents held on Attain are not fully accessible to screen reader software some of our online forms are difficult to navigate using just a keyboard.
If you need information on these websites in a different format like accessible PDF, large print, easy read, audio recording or braille:
email: studentservices@sccb.ac.uk
call: 0121 694 5000
We’ll consider your request and get back to you in ten days.
We are always looking to improve the accessibility of Attain and Mahara. If you find any problems not listed on this page or think we’re not meeting accessibility requirements, contact: [provide both details of how to report these issues to your organisation, and contact details for the unit or person responsible for dealing with these reports].
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).
If you contact us before your visit we can arrange a British Sign Language (BSL) interpreter.
Find out how to contact us [add link to contact details page].
South and City College Birmingham is committed to making its websites accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
These websites are 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.
Some images do not have a text alternative, so people using a screen reader cannot access the information. This fails WCAG 2.1 success criterion 1.1.1 (non-text content).
We plan to add text alternatives for all images by September 2020. When we publish new content we’ll make sure our use of images meets accessibility standards.
Given the vast number of legacy content contained in Attain we feel that it would be a disproportionate burden to retrospectively fix all accessibility issues with all of the content Attain holds by September 2020. We are however embarking on a long term course upgrade programme that will also deal with the accessibility issues of the content.
It is not always possible to navigate content using only a keyboard.
It’s not always possible to change the device orientation from horizontal to vertical without making it more difficult to view the content.
Some of our interactive forms are difficult to navigate using a keyboard. For example, because some form controls are missing a ‘label’ tag.
Some of our interactive content is difficult to navigate using a keyboard
We’ve assessed the cost of fixing the issues with navigation and accessing information, and with interactive tools and transactions. We believe that doing so now would be a disproportionate burden within the meaning of the accessibility regulations. We will make another assessment when the supplier contract is up for renewal, likely to be in [rough timing].
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. By September 2020, we plan to either fix these or replace them with accessible HTML pages.
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. For example, we do not plan to fix [example of non-essential document].
Any new PDFs or Word documents we publish will meet accessibility standards.
Captions can be added to live video streams through the use of captions in Microsoft Teams
Our accessibility roadmap [add link to roadmap] shows how and when we plan to improve accessibility on this website.
This statement was prepared on [22/09/2020]. It was last reviewed on [22/09/2020].