Accessibility statement for Barnsley.ac.uk
This accessibility statement applies to the barnsley.ac.uk domain
This website is run by Barnsley College.
We are aware that disabled people may have difficulty using our website or accessing some of its content. For this we apologise and will to do everything we can to help whilst we are working to resolve them.
How accessible this website is
We know some parts of this website are not fully accessible:
- The website currently offers the ReciteMe overlay, with allows visitors to change aspects of the website to improve accessibility. Unfortunately, overlays of this nature actually make the website less accessible for some disabled people and we are looking to fully replace this as soon as possible. In order to assist some disabled people who may experience issues with ReciteMe, this website also offers a range of additional accessibility tools on the left-hand side that assist in changing elements of the site such as the Text Size or the Colour Contrast. This website also offers a text only option.
- Some pages on this website do not print correctly.
- Some of the images have Alt Tags that are either missing or incorrectly labelled.
- The website does not currently display correctly with the latest version of every browser.
- The Cookie Control facility does not function correctly with screen readers.
- It is difficult to see when a link is active.
- There is a use of Flip Books to present some information. They are not accessible with assistive technology.
- Headers have not been used consistently.
- Accordions are used on this website to hide some information to reduce the size of the pages. They do not function correctly with screen readers.
Some of the PDFs on this website are inaccessible. We aim to replace these
The following issues may occur with screen readers:
- Link text replaced by aria-label attribute doesn’t work in some screen readers.
- iframe with title attribute doesn’t work in some screen readers.
- input type=text with aria-label attribute doesn’t work in some screen readers.
- input type=text with title attribute doesn’t work in some screen readers.
- An element placeholder link with no event handler or href attribute doesn’t work in some screen readers.
By September 2023 we plan to either fix these or replace them with accessible HTML pages.
Any new PDFs or Word documents we publish will meet accessibility standards.
Feedback and contact information
If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille, please contact us using any of the following methods:
Follow this link to send us an email: accessibility@barnsley.ac.uk
Fill in our Accessibility enquiry form (opens in a new window).
We aim to return all priority enquiries within 30 minutes during working hours. If you would prefer to call us, our contact number is 01226 216 216.
We’ll consider your request and get back to you within 1 working day.
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)
Reporting problems with this website
If you find that you are unable to access any information on this website, please do get in touch using any of the following methods:
Follow this link to send us an email: accessibility@barnsley.ac.uk
Fill in our Accessibility enquiry form (opens in a new window).
We aim to return all priority enquiries within 30 minutes during working hours. If you would prefer to call us, our contact number is 01226 216 216.
Technical information about this website’s accessibility
Barnsley College 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 (WCAG) version 2.1 A standard, AA standard and AAA standard.
Non-accessible content
A detailed audit of this website has been carried out and each page has been tested for the following areas. Each of these either directly or indirectly affects the accessibility of the website.
- Website Accessibility Errors Priority A
- Website Accessibility Errors Priority AA
- Website Accessibility Errors Priority AAA
- Website Accessibility Errors for Screen Readers
- Website Coding Errors that affect Search Engines
- Website Coding Errors (W3C Standards)
- Usability and Navigation Issues
In addition, a thorough manual evaluation of different aspects of this website has been undertaken. If you would like a copy of the full accessibility report, please contact us.
The content listed below is non-accessible on one or more website pages for the following reasons.
Non-compliance with the accessibility regulations (WCAG 2.1)
Priority A
| Don’t use CSS animations or transitions in interactions without giving the user a way to turn them off. (Fails under WCAG 2.1 2.3.3 ) |
| Word document contains a graphic without Alt Text. (Fails under WCAG 2.1 A 1.1.1 Section 508 (2017) A 1.1.1 ) |
| The aria-labelled by attribute must point to IDs of elements in the same document. (Fails under WCAG 2.1 A 1.3.1 Section 508 (2017) A 1.3.1 ARIA 1.1 ) |
| PDFs must be tagged to be accessible by screen readers. (Fails under WCAG 2.1 A 1.3.1 Section 508 (2017) A 1.3.1 Matterhorn 1.02 01-005 ) |
| Word document contains a non-inline graphic or object. (Fails under WCAG 2.1 A 1.3.2 Section 508 (2017) A 1.3.2 ) |
| Web pages must not contain large images that flash more than three times in any one second period. (Fails under WCAG 2.1 A 2.3.1 Section 508 (2017) A 2.3.1 ) |
| iframe and frame elements must have a title attribute. (Fails under WCAG 2.1 A 2.4.1 Section 508 (2017) A 2.4.1 ) |
| Use the lang attribute to identify the language of the page. (Fails under WCAG 2.1 A 3.1.1 Section 508 (2017) A 3.1.1 Matterhorn 1.02 11-001 ) |
| Duplicate id – the same ID is used on more than one element. (Fails under WCAG 2.1 A 4.1.1 Section 508 (2017) A 4.1.1 ) |
| The label element is blank. (Fails under WCAG 2.1 A 4.1.2 Section 508 (2017) A 4.1.2 ) |
| Document title must not be blank. (Fails under WCAG 2.1 A F25 Section 508 (2017) A F25 Matterhorn 1.02 06-004 ) |
| Alt text should not contain placeholders like ‘picture’ or ‘spacer’. (Fails under WCAG 2.1 A F30 Section 508 (2017) A F30 ) |
| Alt text should not be an image file name. (Fails under WCAG 2.1 A F30 Section 508 (2017) A F30 Matterhorn 1.02 13-004 ) |
| Several links on a page share the same link text and surrounding context, but go to different destinations. (Fails under WCAG 2.1 A F63 Section 508 (2017) A F63 ) |
| Area elements must have an accessible name. (Fails under WCAG 2.1 A F65 Section 508 (2017) A F65 ) |
| Figures and images in PDF documents should have non blank ALT text, except for decorative images which should be marked as artifacts. (Fails under WCAG 2.1 A F65 Section 508 (2017) A F65 Matterhorn 1.02 13-004 ) |
| HTML form control has no accessible name. (Fails under WCAG 2.1 A F68 Section 508 (2017) A F68 ) |
| Each a element must contain text or an img with an alt attribute. (Fails under WCAG 2.1 A F89 Section 508 (2017) A F89 ) |
| Identify row and column headers in data tables using the elements, and mark layout tables with role=presentation. (Fails under WCAG 2.1 A F91 Section 508 (2017) A F91 ) |
All of these issues we aim to have resolved by 26 May 2023
Priority AA
| Equations rendered as images should be marked up with MathML. When an appropriate markup language exists, use markup rather than images to convey information. (Fails under WCAG 2.1 AA 1.4.5 Section 508 (2017) AA 1.4.5 ) |
| Control labels should be unique on a page, or be close to text providing context. (Fails under WCAG 2.1 AA 2.4.6 Section 508 (2017) AA 2.4.6 ) |
| The CSS outline or border style on this element makes it difficult or impossible to see the dotted link focus outline. (Fails under WCAG 2.1 AA F78 Section 508 (2017) AA F78 ) |
| Headings should not be empty. (Fails under WCAG 2.1 AA G130 Section 508 (2017) AA G130 ) |
All of these issues we aim to have resolved by 26 May 2023
Disproportionate burden
Not applicable.
Content that’s not within the scope of the accessibility regulations
General Website Content
PDFs
The PDF documents on this website may not be accessible. For example, they may be missing clear and simple document structure and missing text alternatives.
By September 2023 we plan to either fix these or replace them with accessible HTML pages.
Any new PDFs or Word documents we publish will meet accessibility standards.
AAA Standard
Some pages have the following issues that fail the ‘AAA’ standard of the WCAG Guidelines. This is not currently a requirement but we include as it would be good practice to eliminate these in the future:
| Ensure that text and background colours have a 7:1 contrast ratio. (Fails under WCAG 2.1 AAA 1.4.6 ) |
| Several links on a page share the same link text, but go to different destinations. (Fails under WCAG 2.1 AAA 2.4.9 ) |
| This page is hard to read for users with learning disabilities or reading disorders like dyslexia. (Fails under WCAG 2.1 AAA 3.1.5 ) |
| Avoid specifying a new window as the target of a link with target=_blank. (Fails under WCAG 2.1 AAA F22 ) |
| Link uses general text like ‘Click Here’ which doesn’t explain link purpose. (Fails under WCAG 2.1 AAA F84 ) |
How this website was tested
This website was tested for compliance with the Web Content Accessibility Guidelines V2.1 level A, level AA and AAA using a variety of software, and extensive manual checking and testing.
This includes the following tools and software:
- Wave
- Axe
- SortSite
- JAWS
- Dragon Dictation
What we’re doing to improve accessibility
We plan to identify and fix issues, which fail the Web Content Accessibility Guidelines version 2.1 A and AA standard, by 1 December 2023.
We will update the accessibility statement when issues are fixed or when we expect them to be fixed.
Preparation of this accessibility statement
This statement was originally prepared on 24 March 2023 and updated on 16 October 202.
The website was lasted tested on 24 March 2023. It will be audited again on the 5th of March 2024.
The test was carried out by Clive Loseby, with some additional support from two members of Access by Design’s Team of Disabled Testers. Access by Design
The full Audit, along with this Accessibility Statement, was prepared and produced by Clive Loseby, Access by Design. If you wish to receive a copy of the audit please contact us on marketing@barnsley.ac.uk
updated 16 October 2024
Date of next review 28 February 2024
Last updated: 16th October 2024