The statement applies to content published on blogs.kcl.ac.uk (KCL blogs) run by King’s College London. This domain contains around 100 individual WordPress sites such as blogs.kcl.ac.uk/observatoryusa. These sites use different themes and plugins to control their appearance and management of content. This statement applies on to blogs that are using the supported theme WordPress Twenty Nineteen with no customisation undertaken locally by the blog owner.
The WordPress application is an open source tool that we have no control over. They have an accessibility statement on the tool.
We want as many people as possible to be able to use these websites. 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
Technical information about WordPress multisite accessibility
King’s College London is committed to making KCL Blogs, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018. We work to achieve and maintain WCAG 2.1 AA standards, but it is not always possible for all our content to be accessible.
This website is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to the non-compliance areas listed below.
We know some parts of KCL Blogs aren’t fully accessible, and the complexity and volume of content available presents difficulties in identifying all accessibility issues. Users may experience issues depending on the blog they are accessing. The content listed below is not accessible for the following reasons.
• WordPress uses themes which users can’t customise so not all aspects are compliant.
• Some images don’t have a text alternative, so the information in them isn’t available to people using a screen reader. This doesn’t meet WCAG 2.1 success criterion 1.1.1 (non-text content).
• Many of our PDFs and Word documents don’t meet accessibility standards – for example, they may not be structured so they’re accessible to a screen reader. This doesn’t meet WCAG 2.1 success criterion 4.1.2 (name, role value).
• Our site includes 3rd party content and functionality. Depending on our relationship with the 3rd party, we cannot always guarantee its accessibility.
• Themes and plugins are developed by third-parties and added by individual site owners and not all are compliant.
• Some headings may have empty tags.
• Some links are only identifiable by colour.
• HTML has been used for structural purposes within the site (for example tables for layout).
• ID elements may not be unique.
• Same link text is used to go to multiple destinations.
• Some form elements are not grouped, making keyboard navigation harder.
• Colour contrast might not be sufficient in certain circumstances.
• Some input fields may be missing a description, have issues with focus or have missing labels.
• Some tables may not be fully accessible to screen reader software.
PDFs and other documents
Many of our older PDFs and Word documents don’t meet accessibility standards – for example, they may not be structured so they’re accessible to a screen reader. This doesn’t meet WCAG 2.1 success criterion 4.1.2 (name, role value).
What to do if you can’t access parts of WordPress multisite
If you need information on WordPress multisite in a different format like accessible PDF, large print, easy read, audio recording or braille email email@example.com.
We’ll consider your request and get back to you in 7 days.
Reporting accessibility problems with WordPress multisite
We’re always looking to improve the accessibility of WordPress multisite. If you find any problems that aren’t listed on this page or think we’re not meeting accessibility requirements email firstname.lastname@example.org.
If you need to escalate your issue further, contact Sarah Guerra, Director of Diversity & Inclusion via email@example.com. 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.
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).
How we tested this website
This website was last tested on 17 September 2019. The test was carried out manually by the IT Services team in King’s College London. We tested the supported theme with automatic tools and human tests. The site is scanned weekly by an industry leading tool to report any failings.
We only tested blogs that are using the supported theme WordPress Twenty Nineteen with no customisation undertaken locally by the blog owner. No other template or plugin combinations have been tested.
What we’re doing to improve accessibility
King’s College London has convened a college-wide action group to address the accessibility of its digital information and actions are currently being undertaken around:
• Assessing, prioritising and improving the accessibility of the 100+ digital platforms in use at King’s and highest priority is being given to those holding student teaching materials;
• Improving the accessibility of online teaching materials;
• ensuring all future purchases or development of digital platforms are accessible;
• ensuring that all future teaching materials being developed and uploaded are accessible.
Activities to improve the accessibility of WordPress are as follows:
• We are currently advising site owner switch to our existing WordPress sites to accessible themes. New WordPress sites will be given an accessible theme by default.
• WordPress plugins will be reviewed to ensure they meet accessibility standards.
• We have also built a “feature” template inside the main King’s website and recommending that user move to the main site and decommission their blog.
This statement was prepared on 17 September 2019. It was last updated on 22 October 2020.