The statement applies to content published on blogs.kcl.ac.uk (KCL blogs) run by King\u2019s 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.<\/p>\n\n\n\n
The WordPress application is an open source tool that we have no control over. They have an accessibility statement on the tool.<\/a><\/p>\n\n\n\n We want as many people as possible to be able to use these websites. For example, that means you should be able to: King\u2019s 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.<\/p>\n\n\n\n This website is partially compliant with the\u202fWeb Content Accessibility Guidelines version 2.1\u202fAA standard, due to the non-compliance areas listed below.<\/p>\n\n\n\n We know some parts of KCL Blogs aren\u2019t 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.<\/p>\n\n\n\n \u2022 WordPress uses themes which users can\u2019t customise so not all aspects are compliant. Many of our older PDFs and Word documents don\u2019t meet accessibility standards \u2013 for example, they may not be structured so they\u2019re accessible to a screen reader. This doesn\u2019t meet WCAG 2.1 success criterion 4.1.2 (name, role value).<\/p>\n\n\n\n If you need information on WordPress multisite in a different format like accessible PDF, large print, easy read, audio recording or braille email diversity@kcl.ac.uk<\/a>.<\/p>\n\n\n\n We\u2019ll consider your request and get back to you in 7 days.<\/p>\n\n\n\n We\u2019re always looking to improve the accessibility of WordPress multisite. If you find any problems that aren\u2019t listed on this page or think we\u2019re not meeting accessibility requirements email diversity@kcl.ac.uk<\/a>.<\/p>\n\n\n\nUsing WordPress<\/h3>\n\n\n\n
\u2022 change colours, contrast levels and fonts
\u2022 zoom in up to 300% without the text spilling off the screen
\u2022 navigate most of the website using just a keyboard
\u2022 navigate most of the website using speech recognition software
\u2022 listen to most of the website using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver).
We\u2019ve also made the website text as simple as possible to understand<\/p>\n\n\n\nTechnical information about WordPress multisite accessibility<\/h3>\n\n\n\n
\u2022 Some images don\u2019t have a text alternative, so the information in them isn\u2019t available to people using a screen reader. This doesn\u2019t meet WCAG 2.1 success criterion 1.1.1 (non-text content).
\u2022 Many of our PDFs and Word documents don\u2019t meet accessibility standards \u2013 for example, they may not be structured so they\u2019re accessible to a screen reader. This doesn\u2019t meet WCAG 2.1 success criterion 4.1.2 (name, role value).
\u2022 Our site includes 3rd party content and functionality. Depending on our relationship with the 3rd party, we cannot always guarantee its accessibility.
\u2022 Themes and plugins are developed by third-parties and added by individual site owners and not all are compliant.
\u2022 Some headings may have empty tags.
\u2022 Some links are only identifiable by colour.
\u2022 HTML has been used for structural purposes within the site (for example tables for layout).
\u2022 ID elements may not be unique.
\u2022 Same link text is used to go to multiple destinations.
\u2022 Some form elements are not grouped, making keyboard navigation harder.
\u2022 Colour contrast might not be sufficient in certain circumstances.
\u2022 Some input fields may be missing a description, have issues with focus or have missing labels.
\u2022 Some tables may not be fully accessible to screen reader software.<\/p>\n\n\n\nPDFs and other documents<\/h3>\n\n\n\n
What to do if you can\u2019t access parts of WordPress multisite<\/h3>\n\n\n\n
Reporting accessibility problems with WordPress multisite<\/h4>\n\n\n\n
Escalation procedure<\/h4>\n\n\n\n