Accessibility statement

This accessibility statement applies to https://swansea.ac.uk

This website has been developed by Swansea University. We want as many people as possible to be able to use the website, feel welcome and find the experience rewarding. For example, that means you should be able to

  • Zoom in up to 200% without the text spilling off the screen.
  • Adjust text spacing without affecting layout or usability.
  • Navigate the website using just a keyboard.
  • Use ReciteMe Application to provide an array of accessibility tools.

AbilityNet has advice on making your device easier to use if you have a disability.

 

How accessible swansea.ac.uk is?

The website has been evaluated by our internal specialist and they certify that swansea.ac.uk is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard.

We know some parts of swansea.ac.uk aren't as accessible as they should be:

  • Some pages misuse headings or have headings missing.
  • Some of the ARIA Design Patterns for site menu and tab components we have added need more work to function as expected.
  • Virtual Tours does not work fully with keyboard navigation and has no Image descriptions.
  • Screen readers do not get announcements for all errors or statuses and require focus on search results and on some forms.
  • Some pages do not parse and have valid HTML and ARIA markup has been incorrectly added.

 

Feedback and contact information

If you need information on swansea.ac.uk in a different format like accessible PDF, large print, easy read, audio recording or braille you can contact our Transcription Centre:

Email: braille@swansea.ac.uk
Twitter: @SUTranscription

Swansea University Transcription Centre Amy Dillwyn Building, Swansea University, Singleton Park, Swansea SA2 8PP, United Kingdom

How to find the transcription center: SUTC-Accessible-Guide

We'll consider your request and get back to you in 7 days.

 

Reporting accessibility problems with swansea.ac.uk

We're always looking to improve the accessibility of the website. If you find any problems not listed on this page or think we're not meeting accessibility requirements:

Email: accessibility@swansea.ac.uk
Call us: +44 (0)1792 295500

 

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)

 

Contacting us by phone or visiting us in person

The university aims to provide professional information and guidance services for disabled students, students with specific needs and/or medical conditions. We can provide support if you would like to visit us or phone us.
Please contact the disability office:

Telephone: +44 (0)1792 60 6617
Email: disability@swansea.ac.uk

 

Technical information about the website’s accessibility

Swansea University is committed to making all its websites accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

Compliance status

swansea.ac.uk is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA/A standard, due to the non-compliances listed below.

 

Non accessible content

Swansea University is committed to sustain the Level AA accessibility. The following information explains any areas of the website that to our knowledge are not conformant and what we're doing to make that happen.
The content listed below is non-accessible for the following reasons.

 

WCAG 2.1 success criterion: 1.1.1 Non-text Content

Pages with poor image descriptions provided by content editors

Some pages of the website have poor descriptions of images.

Pages with Unique Graphical Content and Third-Party Embeds have poor alternative text

Some pages on the site such as “How far is Swansea” and “Virtual Open Day” use SVG graphics which limited image descriptions. The site also has an externally developed "Virtual Tour" which has no image descriptions.

 

WCAG 2.1 success criterion: 1.3.1 Info and Relationships

Some ARIA roles do not function correctly or have required child or parent elements

Our development team are trying to implement Accessible Design Patterns. But the MenuBar and Tablist Patterns are not implemented to specifications and do not function as expected. This affects the Site Menu and Sidebar Menu.

Landmarks are duplicated and unlabelled

Numerous Landmark issues exist on our site which we are addressing. They include:

  • Course Pages using Third-Party embeds which add multiple banner and main roles to the page.
  • The externally developed site "Virtual Tours" does not use any landmarks.
Modules Tables on course pages

Modules tables on our course pages are not designed for screen readers. So do not announce the context of column names.

 

WCAG 2.1 success criterion: 1.4.1 Sensory

Some Links use only color to convey meaning

On pages with older forms (prospectus form) or unique content (virtual open days) links have been added without a text underline and can only be identified as a link by colour.

 

WCAG 2.1 success criterion: 1.4.3 Contrast Minimum

Legacy Forms with poor contrast

Some older forms (prospectus forms) have been embedded on the site, which do not meet contrast guidelines with text links.

 

WCAG 2.1 success criterion: 2.1.1: Keyboard

Virtual Tour Navigation

Keyboard users cannot use the map view fully as popup information boxes can only be triggered by hovers and some menus cannot be tabbed into.

Menubar, Tablist Navigation

Due to design patterns and markup not being implemented for "Menubar" and "Tablist" keyboard interaction (arrow navigation) is not supported to WS3 specification on features such as Mega Menu, Course A-Z tabs and Key Features Course Tabs.

 

WCAG 2.1 success criterion: 2.4.1 Bypass Blocks

Bypass blocks broken styles on Virtual Open Day Page

The bypass block is functional but has no instructional text when tabbed into.

No Bypass blocks broken styles on Virtual Tours Site

No bypass block is available on the Virtual Tours Site.

 

WCAG 2.1 success criterion: 2.4.2 Page Titled

Virtual Tours Page titles are not unique

Each page is titled Virtual Tours, regardless of which campus or building you are currently viewing.

 

WCAG 2.1 success criterion: 2.4.3 Focus Order

Focus order is broken on Virtual Tours

Due to some elements being unavailable by keyboard navigation, the focus order is incorrect on the virtual tour site.

Modal dialogs can only be triggered by mouseover and mouse out on Virtual Tours

The small modal popups do not allow explicit dismissing and require hover to be maintained to view information.

Course A-Z Focus is not moved to content

When selecting a tab with hidden content, keyboard focus is not moved to tab content. Users must tab through other items to reach the content they selected.

Course Page Focus does not preserve meaning

The course pages visual user-flow would be Key Features, Course Overview and Course Information Expanders with secondary content available. A tabbed users flow is not the same they are forced through all secondary content before reaching Information Expanders.

 

WCAG 2.1 success criterion: 2.4.4 Link Purpose (In Context)

Links on How far is Swansea Map unavailable for Screen readers

A third-party embed showing maps to support travel to Swansea does not state a discernable link purpose or any text other than “Clickable”. 

Virtual Tours Links unavailable for Screen readers

A third-party developed site showing students virtually around campus does not state a discernable link purpose or any text other than “Void”. 

Search result numbered page links

The search returns paginated search results. The page links (1,2,3,4,5) are only described as numbers with no heading to set context. So, these links are not described by link text alone.

 

WCAG 2.1 success criterion: 2.4.6 Headings and Labels

Misuse of Headings

Some page's headings have been used for large areas of text and visual styling, not for structure. In some cases H2 is overused and this impacts pages breaking page hierachy and structure.

Job Description Missing Headings

A H3 (current vacancies) and H2 (job description) tag are missing on jobs pages.

Heading Level

Embedded videos from Vimeo inject a H1 tag into a page that already features a H1 tag and breaks page structure.

On a limited number of pages headings are missing (e.g. H1, H2, H5) such as prospectus form, virtual open day and Search pages.

 

WCAG 2.1 success criterion: 2.4.7 Visible Focus

Virtual Tours has inconsistent Focus Rings

Only some of the site displays visible focus, but important controls such as these dropdowns do not.

 

WCAG 2.1 success criterion: 3.3.1 Error Identification

Legacy Forms do not give detailed error messages

The Prospectus request form only informs users of missing subjects, not any other required fields that are missing.

DotDigital Forms do not give detailed error messages

The Prospectus request form only informs users of missing subjects, not any other required fields that are missing.

 

WCAG 2.1 success criterion: 4.1.1 Parsing

Google Tag Manger (GTM) and third-party content generates issues with validation

Due to the site being large and a content management system with third-party embeds, some HTML does not validate correctly.

 

WCAG 2.1 success criterion: 4.1.2 Name, Role, Value

Search controls do not have discernable text or labels

The submit and clear elements do not have labels or aria-label on the search results page.

Custom Widget

Roles such as MenuBar (Mega Menu) and Tablist (Key Features and Course A-Z) have been added to site components, but have not been implemented correctly to WS3 specifications.

 

WCAG 2.1 success criterion: 4.1.3 Status Messages

Current Vacancies Status Message Needs Focus

When performing a filtered job search, the status is not within an ARIA role alert. This means the status must be focused to be announced.

Search results and filter Announcements

The results of a search are not announced when available. A user must move and focus through the page. This also applies when filter parameters are added and removed, no announcements are made. All content must receive focus to be heard.

Legacy Forms and Dot Digital Forms do not give adequate error messages

The prospectus request form and a Keep in touch Form do not give detailed error messages if submitted incorrectly. An error message is announced but its ambiguous, does not support unsighted users by moving them to the error and is primarily visual error support.

 

How we will address non-compliance

The above criterion failures will be addressed through the following:

  • A process of accessibility awareness-raising with Content Editors.
  • Contact third-party vendors, request fixes to the accessibility issues we found.
  • Assigning designated time for the Web Development Team to address these issues.
  • Investigate ways to automate accessibility testing within our development process.

 

Disproportionate Burden

An assessment has been made taking into account the size and resources available to the organization, any content that is judged a disproportionate burden are stated in this section.

Navigation and accessing information

No issues or not applicable.

Interactive tools and transactions

No issues or not applicable.

Interactive tools

No issues or not applicable.

 

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

An assessment has been made taking into account the size and resources available to the organization, any content that is judged out of scope of the regulations are stated in this section.

PDFs and other documents

A sample selection of PDF's have been accessibility tested and some minor errors were reported. We will work with content editors to ensure they have the training and resources to address any errors found.

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. Any new PDFs or Word documents we publish will meet accessibility standards.

 

What we’re doing to improve accessibility

Our Accessibility Roadmap shows how and when we plan to improve accessibility on swansea.ac.uk.

 

Preparation of this accessibility statement

This statement was prepared on 15/08/2021 It was last updated on 20/08/2021.

The website swansea.ac.uk was last tested on 15/08/2021. The test was carried out by our internal usability and accessibility specialist.

We used a consistent process and approach to deciding on a sample of pages to test. This is available in How we tested the website

The full accessibility report is available on request.