Accessibility

Last updated: 4 July 2026

Approach

This site is intended to be usable by as many people as possible, including people using assistive technologies, keyboard navigation, screen readers, magnification software or mobile devices.

The site aims to be clear, simple and accessible by:

• using plain language where possible
• using meaningful headings and page structure
• providing descriptive link text
• ensuring images have appropriate alternative text
• keeping navigation consistent across the site
• checking colour contrast
• making sure the site can be used with a keyboard
• testing pages on different screen sizes
• testing both static pages and interactive features

Accessibility standard

The aim is to follow the Web Content Accessibility Guidelines, known as WCAG, at level AA where practical for this type of community site.

This site is built as a simple static site using 11ty and Web Awesome components. Web Awesome is designed with accessibility in mind, but accessible components still need to be used carefully and tested as part of the finished page.

How accessible this site is

The core pages of this site are intended to be accessible and usable.

Visitors should be able to:

• navigate the site using a keyboard
• skip directly to the main content
• zoom in without the layout becoming unusable
• read pages on mobile, tablet and desktop screens
• understand the page structure from headings and landmarks
• use links and buttons with clear, visible focus styles
• use the community groups search field
• open and use the mobile navigation
• view logo gallery entries and follow gallery links

Testing

The site is tested using a combination of automated and manual checks.

Automated tests are run against the built site. These currently include checks for:

• automatically detectable accessibility issues using axe
• page language, titles and meta descriptions
• skip links and main content landmarks
• heading structure
• image alternative text
• labelled navigation landmarks
• labelled form controls
• meaningful link and button text
• internal links pointing to valid built pages
• mobile navigation behaviour
• the groups search feature
• logo gallery links
• Web Awesome components loading correctly in the browser

Two types of automated testing are currently used:

• Jest-based tests against the built HTML, to check page structure and common accessibility issues quickly
• Playwright browser tests using axe, to check pages in a real browser, including mobile views and interactive behaviour

The Playwright tests currently run against desktop Chromium and a mobile Chrome-style viewport.

Automated accessibility testing is useful, but it cannot prove that a site is fully accessible. Some issues can only be found through manual testing, user feedback, or testing with specific assistive technologies.

Manual checks may include:

• navigating each page using only the keyboard
• checking that focus is visible
• checking that headings appear in a sensible order
• checking that links and buttons have meaningful text
• checking that images have suitable alternative text
• viewing pages at increased zoom levels
• testing pages on smaller screens
• checking colour contrast where possible
• checking that interactive features remain usable without a mouse

Known issues

There are no currently known significant accessibility issues on the core pages of this site.

This site has not been audited by an external accessibility specialist. Some issues may only become clear as the site grows or as people use it with different devices, browsers and assistive technologies.

This page will be updated if known accessibility problems are identified.

Third-party components and content

This site uses Web Awesome components for some layout and interface elements. The finished pages are tested rather than assuming that any component is accessible simply because it comes from an accessible component library.

The site is intended to remain simple and lightweight.

If third-party content is added in the future, such as maps, videos, booking forms or social media embeds, efforts should be made to ensure that it is accessible. However, some third-party content may not be fully under local control.

Reporting accessibility problems

If something on this site is difficult to use, please report it by email:

hello@sustainable-witchford.co.uk

It would be helpful to include:

• the page or feature being used
• what went wrong
• what device, browser or assistive technology was being used, if relevant

Reported issues will be reviewed and used to improve the site where possible.

Future improvements

As the site develops, accessibility should remain part of the process when adding new pages, images, documents, components or interactive features.

The automated test suite should also be kept up to date so that new pages and features continue to be checked as the site grows.