Accessibility

Find out how to navigate the University of Sussex website and see our accessibility statement.

Contact

If you are having trouble accessing content on this site please contact us: web-accessibility@sussex.ac.uk

  • Finding your way around

    There are a variety of techniques you can use to navigate our site.

    You can use the top-level drop-down navigation and the site search, both of which give you access across our website and resources contained within. On most sections of the site you can use the page navigation (which appears to the left of this content) and the breadcrumb trail (which appears just above this content).

  • Text resizing and page zooming

    Most modern browsers support some form of built-in text resizing or page zooming. Changing the text size or zoom varies depending on the browser you are using.

    Resizing a page depends on the browser you are using:

    • PC / Internet Explorer 11

      From the 'Tools' cog icon in the top right corner, select 'Zoom' and then choose your setting

    • PC / other browsers

      Hold down the CTRL key and press + to increase the text/zoom
      Hold down the CTRL key and press - to decrease the text/zoom

    • Mac / all browsers

      Hold down the Command key and press + to increase the text/zoom
      Hold down the Command key and press - to decrease the text/zoom

  • Known browser support for the site

    Our site supports:

    • Internet Explorer 11 and above
    • Firefox – latest version
    • Safari – latest version
    • Chrome – latest version
  • Get advice

    Refer to the following websites to get information relating to accessibility matters such as how to adjust your browser, computer, keyboard and mouse settings to suit your individual needs

  • Accessibility statement

    This website is run by the University of Sussex. We want as many people as possible to be able to use this website.

    That means everyone should be able to:

    • access most of the information found on the site.
    • zoom most pages 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, and navigate, most of the website using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver).
    • access all video content, either visually, or through accessible technology.

    We’ve also made the website text as simple as possible to understand. Within our content management system (CMS), we have a built in readability score tool. This generates a score which tells us if our content is readable.

  • How accessible is this website?

    The website has been developed following guidelines which are aimed at achieving a good level of accessibility – we endeavour to meet with WCAG 2.1 AA standards.

    We have taken the following accessibility and usability guidelines into consideration when developing the site:

    • providing simple, consistent operable site navigation.
    • providing easy to percieve and understand content.
    • using style sheets for visual layout, the content can still be read with style sheets turned off or with a different style applied by your own browser set-up.
    • using an easy-to-read font type.
    • endeavouring to provide suitable foreground and background colour contrast.
    • providing text equivalents for images, where appropriate.
    • using semantic HTML to improve readability by screen readers.
    • ensuring javascript degrades gracefully, so content is accessible without javascript wherever possible.
    • using accessible alternatives where necessary to ensure the website is robust - such as with the modified html version of the virtual campus tour.
  • Staff training

    We have produced and are preparing to deliver our web accessibility roadshow. This will be a series of talks, presented to our web editors, highlighting the requirements for our website and the importance of accessibility. This will focus on how editors can make our website perceivable, operable, understandable and robust.

    We have developed our accessible web components library and are in the process of training all web editors to use these.

    We have develped a series of "How to" pages for creating accessible documents and are currently preparing to deliver a series of training sessions for all staff who produce online documents.

    We are in the process of developing a series of training sessons around converting current video to an accessible format. This will include adding closed captions, transcripts and audio descriptions where required.

  • Some known areas where we need to improve

    Some areas of the website which were developed before September 2018 may not meet the AA accessibility standard, such as:

    • some images do not have alt tags
    • some pdfs and other files may not be optimised for screen readers
    • some video embeds may not have captions
    • some video embeds have captions that are on a 70% transparent colour block
    • some video embeds do not have transcripts
    • some video embeds do not have an audio described option
    • the campus map is a pdf file and is not screen reader friendly - we do have an alternative with AccessAble and a page on how to travel to the University.

    There may be other areas we have yet to pick up on as we continue to audit the site. The University is in the process of improving it's core web templates to meet AA standards. It has set up an accessibility working group and will be running workshops with devolved editors to promote the importance of accessibility and to make sure standards are adhered to.

  • Technical information about this website’s accessibility

    The University of Sussex is committed to making its 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 listed below.

  • How we tested this website

    This website is continually tested and we have recently carried out tests on sample pages within our components library. We also crawl the site regularly to find issues such as where images without alt tags are located. Tests are carried out with users and via automated software.

    We have tested the website using the following methods so far:

    The pages the components library cover and the ones we have tested are:

    How we tested PDFs:

  • What else are we doing to improve accessibility

    We have set up an accessibility working group which will oversee digital accessibility improvements. The group will form part of wider accessibility group within the University. 

    An action plan will be published shortly with details of timings and the actions of the group.

    Members of our development team have taken training courses provided by W3 and WebAIM to enable them to provide a more accessible experience for our visitors.

    This statement was prepared on 20 September 2019. It was last updated on 10 March 2020 and will be updated regularly as we move forward with our actions and research.

  • What to do if you cannot access parts of this website

    We endeavour to make the content on the website accessible to all. If you are having trouble accessing content on the website let us know and we will do our best to provide the information in another format:

    Email: web-accessibility@sussex.ac.uk

    We’ll consider your request and get back to you in seven days.

  • 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).

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

    PDFs and other documents

    • Many of our older PDFs and Word documents do not meet accessibility standards - for example, they may not be structured so they’re accessible to a screen reader. This does not meet WCAG 2.1 success criterion 4.1.2 (name, role value).

      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 old pdfs which are in our archive.

      Any new PDFs or Word documents we publish will meet accessibility standards.

    Live video