We committed to making sure its services are accessible to everyone. This includes our website. We have therefore included the following functionality to meet the The W3C Web Accessibility Initiative Web Content Accessibility Guidelines (WCAG) Version 2.0 guidelines:
Provide text alternatives for non-text content.
- Content plugins have the ability to add ‘alt’ text and ‘title’ content. These are enabled by default and will require the content editor to ensure fields are completed e.g. when uploading or adding images.
- Multimedia, charts and images have title and caption fields to improve understanding and comprehension.
- Built in form controls such as search icon buttons have screen reader and additional information such as aria-label=’search’ for screen reader and image free understanding.
- Navigation bars and page elements are defined as necessary with ‘sr-only’ tags for appropriate screen reader content. Defined ‘roles’ assist with determining an elements function.
Provide captions and other alternatives for multimedia.
- Images and multimedia have caption fields to assist users in understanding the context and content of images, videos, audio and other multimedia files.
- Where possible we will provide one or more of the following with audio or multimedia content:
- Text transcripts and captions for audio content, such as recordings of a radio interview;
- Audio descriptions, which are narrations to describe important visual details in a video;
- Sign language interpretation of audio content, including relevant auditory experiences.
- Create content that can be presented in different ways, including by assistive technologies, without losing meaning.
- Using simple and clean mark-up, the templates and plugins provide headings, lists, tables and other structures can be viewed and understood outside of the normal stylesheets or presentation layer.
- Sequences of information are governed by structure and independent of the stylesheet designs. This is a design paradigm ensuring that content and presentation are managed separately.
- By using a generic and robust structure browsers and assistive technologies can customize the presentation of content.
- Where a document is provided in a screen reader, it will also be available to download in another recognised format such as Word or PDF.
Make it easier for users to see and hear content.
- Although colour and icons are used to simplify the interface, they are not the primary form of conveying information or content to users. For example, icons and menu items can be styled to improve differentiation, but the content is still clear.
- The main site content is based on a light background and high contrast foreground elements, with other combinations such as the navigation bar providing sufficient contrast against dark backgrounds.
- As the site is dynamically responsive, text can be resized up to 200% without losing information, using a standard browser.
- Images of text are avoided where possible, for instance the proposed Allerdale logo uses a scalable SVG file format.
- Functionality for embedding audio is available and can be paused, stopped, and the volume adjusted within the embedded player.
- Subsites and embedded external applications via iframes will provide their own level of accessibility.
Make all functionality available from a keyboard.
- All functionality, such as buttons, forms, and links are available by keyboard as well as mouse and touch-screen.
- Keyboard focus can be changed throughout the site using the usual ‘tab’ command, with the order of elements starting from the top of the navigation bar.
Give users enough time to read and use content.
- Currently all external or login required content is managed and provided via external providers.
- Any content requiring login access will be preserved within the timeout period of the user’s session.
Do not use content that causes seizures.
- Limited dynamic content will be used on the site, however there is the option to include dynamic slide galleries with customisable settings.
- All dynamic content on the site is set to scroll or rotate with a pause of at least three seconds to avoid causing seizures (10 seconds on built-in navigation templates).
Help users navigate and find content.
- We have devised a simple and clear organisational hierarchy for managing and structuring pages using a plain naming convention.
- Each page has a clear hierarchy of menus showing to help with navigation.
- Each page has clear titles and can be organised under meaningful section headings as managed by the council’s content managers.
- A multifaceted approach to finding pages means that there is more than one way to find relevant pages, using: search, menus, categories, and tags.
- A simple breadcrumb system at the top of each page informs users about their current location within the site.
- The keyboard tab and focus order follow a meaningful sequence, starting at the top navigation bar.
- Links that are added via the link plugin can be customised to indicate clearly where users are being directed to, including if the link opens in a new tab or window.
Make text readable and understandable.
- Our CMS is a multilingual compatible system, with the current site clearly written in English using the ‘../en/..’ url syntax.
- Metadata included on the pages also indicates the language and type of content.
- The council content editors follow the plain English language and style guide when creating content.
Make content appear and operate in predictable ways.
- Using the proposed clear and simple design, the header and footer of the site are accessible from all pages. These include navigation and links that are consistent across the site.
- Typically the site will provide consistent static information for users, with dynamic content (e.g. payment, planning sites) being managed by external suppliers.
Help users avoid and correct mistakes.
- Users can use any of the methods of contact available on our 'contact us' page.
Maximize compatibility with current and future user tools.
- HTML mark-up is kept as simple as possible to ensure that it is easy to manage, validate and potentially be accessed or migrated to any other system.
- Any non-standard user interface components can have attributes added to them as required, however these are not common on the site. For example role=”navigation” for the main navigation bar.
Further information and contact
For further information on this, contact the Council's website editing team at firstname.lastname@example.org , use our general enquiry contact form or give us a ring. Details are available on our "contact us" page.
Documents on the website will be provided in Word, Excel or PDF format. We have provided links to document readers which you can download.