Close
landing page banner image

Accessibility statement for the London School of Economics

This accessibility statement applies to the sections of the following URLs that use the Contensis CMS platform:

  • https://www.lse.ac.uk
  • https://info.lse.ac.uk.

This website is run by the London School of Economics. 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).

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 are not fully accessible:

  • images and buttons contain inappropriate accessible text

  • pre-recorded video is present without synchronised captions, descriptive text transcript or audio description track

  • audio-only content does not have a text transcript

  • page regions are not always identified by an ARIA landmark

  • related link elements aren’t grouped appropriately

  • headings are not appropriately structured across the site

  • the tabbing order of the website may not always be logical

  • a focus indicator is not always visible

  • visual names of user interface elements do not always match the accessible label

  • HTML validation errors are present.

Feedback and contact information

If you find any problems not listed on this page or think we’re not meeting accessibility requirements on these platforms, please email LSE’s Digital Communications team. We aim to get back to you in 2 working days.

If you cannot view the map on our Campus Map page, please email LSE’s Digital Communications team.

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

Technical information about this website’s accessibility

The London School of Economics 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 not compliant with the Web Content Accessibility Guidelines version 2.2 AA standard. The non-compliances are listed below.

Non-accessible content

The content listed below is non-accessible for the following reasons.

Non-compliance with the accessibility regulations

Perceivable

  • Some images do not have a text alternative, so people using a screen reader cannot access the information. This fails WCAG 2.2 success criterion 1.1.1 (Non-text Content)

  • Decorative images have informative alternative attributes, which presents unnecessary information to screen reader users. This fails WCAG 2.2 success criterion 1.1.1 (Non-text Content)

  • Adjacent image and text links are not combined, which may result in screen readers announcing these elements multiple times. This fails WCAG 2.2 success criterion 1.1.1 (Non-Text Content)

  • Buttons do not have appropriate labels. Buttons without labels do not provide information about the functionality of the button to screen reader users. This fails WCAG 2.2 success criterion 1.1.1 (Non-text Content)

  • Audio-only content is present which does not have a text transcript, preventing some users from accessing the audio. This fails WCAG 2.2 success criterion 1.2.1 (Pre-Recorded Audio-Only and Video-Only)

  • Pre-recorded videos do not have synchronised captions, which may impact users with hearing impairments. This fails WCAG 2.2 success criterion 1.2.2 (Captions (Pre-Recorded))

  • Pre-recorded videos do not have a text transcript or audio description track. This fails WCAG 2.2 success criterion 1.2.3 (Audio Description or Media Alternative)

  • ARIA Landmarks aren’t used to identify all page content. This may cause content to be missed by screen reader users. This fails WCAG 2.2 success criterion 1.3.1 (Info and Relationships)

  • Some navigational links on the page are not contained within a navigation element or are contained within an incorrect navigation element. This stops users who navigate using landmarks from being able to directly access the navigational links. This fails WCAG 2.2 success criterion 1.3.1 (Info and Relationships)

  • Text does not meet sufficient contrast requirements against the page background. This fails WCAG 2.2 success criterion 1.4.3 (Contrast (Minimum))

  • Rendering issues are present with text when zooming text only to 200% using browser zoom controls. This fails WCAG 2.2 success criterion 1.4.4 (Resize Text)

  • CAPTCHAs and content accessible by arrow buttons are not available when viewing the site at 400% zoom with a browser width of 1280px. This fails WCAG 2.2 success criterion 1.4.10 (Reflow)

  • Custom styling cannot be applied to text within student cards This fails WCAG 2.2 success criterion 1.4.12 (Text Spacing)

  • Content that appears on hover or focus is unable to be dismissed without moving the pointer cursor. This fails WCAG 2.2 success criterion 1.4.13 (Content on Hover or Focus).

Operable

  • A correctly formed heading structure is not present to facilitate navigation across the site, with skipped or no heading levels present. This fails WCAG 2.2 success criterion 2.4.1 (Bypass Blocks)

  • Frame elements are not appropriately titled which may result in unexpected announcements by screen readers. This fails WCAG 2.2 success criterion 2.4.1 (Bypass Blocks)

  • The focus order of the page is not logical. Users who rely on a keyboard access for operating a page benefit from a logical, usable focus order. This fails WCAG 2.2 success criterion 2.4.3 (Focus Order)

  • The focus indicator is not visible for some user interface elements. This can make it difficult for keyboard only users to keep track of the elements currently in focus. This fails WCAG 2.2 success criterion 2.4.7 (Focus Visible)

  • The displayed name of a user interface component does not always match the accessible label. This may result in navigation issues for speech recognition users. This fails WCAG 2.2 success criterion 2.5.3 (Label in Name).

Understandable

  • The header and footer are inconsistently displayed between pages which could cause confusion when navigating. This fails WCAG 2.2 success criterion 3.2.3 (Consistent Navigation).

Robust

  • Gallery images have multiple labels and may be announced incorrectly by screen readers. This fails WCAG 2.2 success criterion 4.1.2 (Name, Role, Value)

  • Decorative separator elements are announced by screen readers. This fails WCAG 2.2 success criterion 4.1.2 (Name, Role, Value)

  • Interactive controls are nested and may be inaccessible to assistive technology. This fails WCAG 2.2 success criterion 4.1.2 (Name, Role, Value)

  • Changes to dropdown menus such as whether they are expanded or collapsed are not announced by  screen readers. This fails WCAG 2.2 success criterion 4.1.2 (Name, Role, Value)

  • Some uses of ARIA are not appropriate and may result in some content being announced incorrectly by screen readers. This fails WCAG 2.2 success criterion 4.1.2 (Name, Role, Value)

  • Status messages are announced incorrectly or not announced by screen readers. This may result in users being unable to correct input errors. This fails WCAG 2.2 success criterion 4.1.3 (Status Messages)

  • Some images do not have a text alternative, so people using a screen reader cannot access the information. This fails WCAG 2.2 success criterion 1.1.1 (Non-text Content)

  • Decorative images have informative alternative attributes, which presents unnecessary information to screen reader users. This fails WCAG 2.2 success criterion 1.1.1 (Non-text Content)

  • Adjacent image and text links are not combined, which may result in screen readers announcing these elements multiple times. This fails WCAG 2.2 success criterion 1.1.1 (Non-Text Content)

  • Buttons do not have appropriate labels. Buttons without labels do not provide information about the functionality of the button to screen reader users. This fails WCAG 2.2 success criterion 1.1.1 (Non-text Content)

  • Audio-only content is present which does not have a text transcript, preventing some users from accessing the audio. This fails WCAG 2.2 success criterion 1.2.1 (Pre-Recorded Audio-Only and Video-Only)

  • Pre-recorded videos do not have synchronised captions, which may impact users with hearing impairments. This fails WCAG 2.2 success criterion 1.2.2 (Captions (Pre-Recorded))

  • Pre-recorded videos do not have a text transcript or audio description track. This fails WCAG 2.2 success criterion 1.2.3 (Audio Description or Media Alternative)

  • ARIA Landmarks aren’t used to identify all page content. This may cause content to be missed by screen reader users. This fails WCAG 2.2 success criterion 1.3.1 (Info and Relationships)

  • Some navigational links on the page are not contained within a navigation element or are contained within an incorrect navigation element. This stops users who navigate using landmarks from being able to directly access the navigational links. This fails WCAG 2.2 success criterion 1.3.1 (Info and Relationships)

  • Text does not meet sufficient contrast requirements against the page background. This fails WCAG 2.2 success criterion 1.4.3 (Contrast (Minimum))

  • Rendering issues are present with text when zooming text only to 200% using browser zoom controls. This fails WCAG 2.2 success criterion 1.4.4 (Resize Text)

  • CAPTCHAs and content accessible by arrow buttons are not available when viewing the site at 400% zoom with a browser width of 1280px. This fails WCAG 2.2 success criterion 1.4.10 (Reflow)

  • Custom styling cannot be applied to text within student cards This fails WCAG 2.2 success criterion 1.4.12 (Text Spacing)

  • Content that appears on hover or focus is unable to be dismissed without moving the pointer cursor. This fails WCAG 2.2 success criterion 1.4.13 (Content on Hover or Focus)

  • A correctly formed heading structure is not present to facilitate navigation across the site, with skipped or no heading levels present. This fails WCAG 2.2 success criterion 2.4.1 (Bypass Blocks)

  • Frame elements are not appropriately titled which may result in unexpected announcements by screen readers. This fails WCAG 2.2 success criterion 2.4.1 (Bypass Blocks)

  • The focus order of the page is not logical. Users who rely on a keyboard access for operating a page benefit from a logical, usable focus order. This fails WCAG 2.2 success criterion 2.4.3 (Focus Order)

  • The focus indicator is not visible for some user interface elements. This can make it difficult for keyboard only users to keep track of the elements currently in focus. This fails WCAG 2.2 success criterion 2.4.7 (Focus Visible)

  • The displayed name of a user interface component does not always match the accessible label. This may result in navigation issues for speech recognition users. This fails WCAG 2.2 success criterion 2.5.3 (Label in Name)

  • The header and footer are inconsistently displayed between pages which could cause confusion when navigating. This fails WCAG 2.2 success criterion 3.2.3 (Consistent Navigation)

  • Gallery images have multiple labels and may be announced incorrectly by screen readers. This fails WCAG 2.2 success criterion 4.1.2 (Name, Role, Value)

  • Decorative separator elements are announced by screen readers. This fails WCAG 2.2 success criterion 4.1.2 (Name, Role, Value)

  • Interactive controls are nested and may be inaccessible to assistive technology. This fails WCAG 2.2 success criterion 4.1.2 (Name, Role, Value)

  • Changes to dropdown menus such as whether they are expanded or collapsed are not announced by screen readers. This fails WCAG 2.2 success criterion 4.1.2 (Name, Role, Value)

  • Some uses of ARIA are not appropriate and may result in some content announcing incorrectly by screen readers. This fails WCAG 2.2 success criterion 4.1.2 (Name, Role, Value)

  • Status messages are announced incorrectly or not announced by screen readers. This may result in users being unable to correct input errors. This fails WCAG 2.2 success criterion 4.1.3 (Status Messages).

We are working with our developers to fix the issues listed above. We aim to launch these changes across the platform between September 2026 and September 2027.

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

PDFs and other documents

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 this PDF of a programme for a conference in 2016.

Live video

We do not plan to add captions to live video streams because live video is exempt from meeting the accessibility regulations.

Third party systems

Some content on our website is provided by third-party suppliers. While we seek to ensure accessibility wherever possible, we may not have full control over the accessibility of third-party systems. We work with suppliers to promote compliance with accessibility requirements. 

What we’re doing to improve accessibility

      • We are working with our developers to fix the issues listed above. We aim to launch these changes across the platform between September 2026 and September 2027.

      • We have published an Accessibility Hub for editors with wide ranging guidance on meeting accessibility criteria

      • We have ran several training sessions with lead editors to improve their working knowledge of best accessibility practices

      • We are continuing to conduct accessibility audits across the platform to test and retest different pages and templates.

Preparation of this accessibility statement

This statement was prepared on 08/10/2026. It was last reviewed on 08/10/2026.

This website was last tested on 23/02/2026. The test was carried out by Zoonou.

Zoonou used WCAG-EM to define the pages tested and test approach. Their WCAG audit is based on a scripted approach and uses a representative sample as described in the WCAG Evaluation Methodology.

The audit’s primary focus is to identify non-conformances to the WCAG success criteria. They supplement this with testing of best practices and user journeys using assistive technology to ensure no assistive technology specific usability issues are present.

Share