Accessibility

We want everyone to be able to read and use this website, whatever device or assistive technology they use. This page explains what we have done, what we know is not yet right, and how to tell us if something gets in your way.

How this site is built to be used

You should be able to do all of the following.

• Move through every page using only a keyboard, and see where you are as you go.
• Skip straight past the navigation to the main content, using the link that appears when you first press Tab.
• Navigate by headings and landmarks with a screen reader. Every page has one main heading and a consistent structure.
• Resize text up to 200 per cent, or zoom the page, without losing content or having to scroll sideways.
• Read the site in your own colour or contrast settings.
• Turn off movement. Where the site animates anything, it respects the reduced-motion setting on your device.

Every image in our media library carries a text description, so pictures are described rather than skipped. The site declares its language, so screen readers pronounce it correctly, and the fonts are served from this site rather than from a third party.

How we tested it

The site was checked during its build, in September 2026, using automated testing across eight page types: the home page, a network page, the Exchange, News, Events, Publications, Contact and About. Those checks found no failures against the WCAG 2.1 AA success criteria they cover. Automated testing catches roughly a third of accessibility problems, so this was combined with manual checks of keyboard operation, heading structure and colour contrast.

The automated tools could not calculate a contrast ratio for a handful of elements, because of the way those elements layer over one another. We measured those by hand instead, and they pass.

We should be straightforward about the limits of that. The site has not had an independent accessibility audit, and it has not been tested with disabled people using their own assistive technology. Both would tell us more than our own testing can.

What we know is not yet right

We are aware of the following, and none of it is a reason to stay quiet about the rest.

• Audio recordings do not have transcripts. Our archive includes recorded talks and conversations, and most are published as audio only. If you need a transcript of a particular recording, please ask and we will produce one.
• Captions on embedded video depend on the source. Some of the video on this site is hosted elsewhere, and we cannot guarantee captions on material we did not produce.
• Older PDFs are not tagged for screen readers. That includes the back issues of Landscape Research Extra and some historic reports. If you need the content of one of these in another format, please ask.
• Some non-English phrases are not marked up as such. On a few pages, words in other languages sit inside English text without being identified, so a screen reader may pronounce them as English.

Tell us if something does not work

If you find something on this site you cannot use, or you need a page, document or recording in a different format, please get in touch. It helps if you can tell us the address of the page, what you were trying to do, and what happened instead, along with the browser or assistive technology you were using.

We take this seriously and we would rather hear about a problem than not. Reports from people using the site are the most reliable information we get.

The standard we are working to

We aim to meet level AA of the Web Content Accessibility Guidelines, version 2.1. Because of the issues listed above, this website is partially conformant with that standard: it meets it in most respects, and we have said where it does not.

This statement was prepared on 5 September 2026 and applies to landscaperesearch.org. Our membership area is a separate service on its own address, and is not covered here.