Accessibility

This accessibility statement applies to ​Chronicle CampusPress site​. ​CampusPress​ is a third-party application.  

​​The Chronicle CampusPress​ is provided by ​CampusPress​ to King’s College London to ​provide fully managed, accessible & hassle-free WordPress hosting for the whole university, to allow for enhanced teaching, learning and collaboration experience​. 

Chronicle CampusPress allows for embedded links or artefacts to several complementary applications as listed below which support different aspects of learning and teaching e.g. Kaltura.   

    • Kaltura – Video on demand service  
    • YouTube   
    • Google Maps  
    • Microsoft applications 
    • Embedded PDF documents or images 

​​[Application version]​ ​[Publication date 26/08/2025]​ 

Using the application 

We want as many people as possible to be able to use, read and understand the content of ​the Chronicle CampusPress​ site. 

This means that you should be able to:  

    • Zoom in up to 300% without the text spilling off the screen.  
    • Set the font size and preference within your browser (except for section headings).  
    • Navigate most of the website using just a keyboard.  
    • Skip to main content using keyboard navigation.  
    • Navigate most of the website using speech recognition software. 
    • Use screen readers such as JAWS and VoiceOver. 
    • Collapse the course menu to reduce the clutter on the page and help you focus on the task at hand. 
    • Use a range of devices to access Chronicle CampusPress WordPress pages e.g. mobile phone, tablet or laptop.   

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

How accessible this application is 

Chronicle CampusPress is used in Teaching & Learning activities from 2025, we are aware that some parts of Chronicle CampusPress may not be fully accessible. The volume of content added to blogs and web pages may present difficulties in identifying and amending all the accessibility issues, including content without captions or transcripts, user generated documents and media content that does not meet current King’s standards. 

CampusPress takes the following measures to ensure accessibility of all their WordPress hosting & services provided to their customers: 

    • Includes accessibility throughout their internal policies. For example, all new or updated plugins or themes that CampusPress creates must conform with the WCAG 2.2 guidelines at level AA. 
    • CampusPress integrates accessibility into their procurement practices. When evaluating WordPress plugins and themes, support services, and other 3rd party tools that they use, accessibility is included in the research and considered in decision making. CampusPress will not contract with new services that have significant accessibility shortcomings.
    • CampusPress also provide continual accessibility training for their staff through conferences, internal training, and support for their design, development, and support teams.
    • CampusPress employ formal accessibility quality assurance methods. They use a combination of manual and automated tools in accessibility auditing.  

We know some parts of ​Chronicle CampusPress​ are not fully accessible:  

    • ​​User generated content is something that is very difficult to ensure is accessible. ​ 

For more information the accessibility of CampusPress and WordPress:  

Feedback and contact information  

If you find any problems not listed in this statement or think we’re not meeting accessibility requirements, email diversity@kcl.ac.uk.  

If you need information on this application in a different format like accessible PDF, large print, easy read, audio recording or braille, email diversity@kcl.ac.uk. 

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

If you need to escalate your issue further, please contact the Director of Culture and Talent via diversity@kcl.ac.uk. You can expect an acknowledgement of your issue within 7 days and a full reply within 14 days. If your complaint raises complex issues that cannot be answered within 14 days, we will keep you informed of progress until we can fully respond. 

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 application’s accessibility

King’s College London is committed to making this application accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018. 

Compliance status  

This application is partially compliant with the Web Content Accessibility Guidelines version 2.2 AA standard, due to ​‘the non-compliances’ ​listed below. 

Non-accessible content 

​​Chronicle CampusPress​ is provided by a third-party supplier which means that some aspects of accessibility are outside our immediate control.  

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

User generated content: The main function of the Chronicle CampusPress service is to host user-generated content. This also includes WordPress themes and plugins created by other developers, so CampusPress cannot ensure the quality of contributions, code, and content from others.  

CampusPress works with contributors, content authors, and customers to help with training and awareness of accessibility best practices. They will forward any known issues they encounter or that are reported to them and provide guidance whenever possible. 

Non-compliance with the accessibility regulations 

    • ​​1.1.1 Non-text Content: Some elements need text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language. 
    • ​1.3.1 Info and relationships: Several elements require correct coding to reinforce relationships and information conveyed through the presentation. 
    • ​1.4.1 Use of Color: It appears that color is the only distinguishing feature about links in blocks of text. 
    • ​1.4.3 Contrast (Minimum): The color of the text and the color of the background are not in sufficient contrast to each other. 
    • ​1.4.5 Images of text: In all visual presentations, text is used to convey information rather than images of text. 
    • ​​1.4.6 Contrast (enhanced): Visual presentation of text and images of text has a contrast ratio of at least 7:1. 
    • ​​2.2.1 Timing Adjustable: Ensure that users are provided enough time to complete tasks. 
    • ​2.4.3 Focus order: Ensure that elements receive focus in an order that allows for a logical tabbing sequence? 
    • ​​2.4.4 Link purpose (in context): Provide descriptive names or context for all links. 
    • ​2.4.7 Focus Visible, with keyboard navigation it is important that the focused component can be visually identified. 
    • ​2.4.9 Link Purpose (Link Only): The same link text is used for links going to different destinations. Users might not know the difference if they are not somehow explained. 
    • ​2.4.10 Section Headings: The headings on the page must be hierarchically organized. 
    • ​3.3.1 Error Identification: The page contains an error container made with the WAI-ARIA role=”alert” or aria-live=”assertive” attributes, but it does not contain a WAI-ARIA attribute that will make sure all assistive technologies can read the error message after more than one invalid submission. 
    • ​3.3.2 Labels or Instructions: All labels or instructions should be provided for digital content that requires user input. 
    • ​4.1.1 Parsing: The ID used for an element on the page is also used for another element on the page. 
    • ​4.1.2 Name, Role, Value: For all user interface components (e.g. forms, links, scripts, controls, etc.), the name and role of those components should be coded in.​ 

Disproportionate burden 

​​At this time, we have not made any disproportionate burden claims. ​

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 ​PDFs, images or other documents that have been attached or embedded in user blogs.​ 

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

Live video 

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

What we are doing to improve accessibility

King’s College London are working with ​CampusPress​ to fix or provide alternatives for all issues that are we are made aware of or are identified by our internal testing and auditing processes.  

​​Platform-specific action plans to ensure accessibility will be developed by specialist action groups within King’s, include: 

​Using WordPress accessibility ready themes across the Chronicle CampusPress site:  

​These themes will be automatically updated and maintained centrally in King’s in collaboration with CampusPress.  

​Enabling the cross-platform Accessibility Plugin (https://docs.campuspress.com/en/articles/550-accessibility-plugin) on all the accessibility ready themes in Chronicle CampusPress. The accessibility plugin helps with a variety of common accessibility problems in WordPress themes.  It adds several helpful accessibility features that can be enabled or disabled based on your theme’s needs.

Preparation of this accessibility statement

This statement was prepared on ​18th February 2025​. It was last reviewed on ​5th June 2025​. 

This application was last tested on ​4th June 2025​.  

The test was carried out by ​Education Applications team in the Information Technology department manually using the Site Improve Accessibility Checker​​.  

We tested: