Accessibility Statement

We want this site to be usable by everyone who needs it, including people using a screen reader, people navigating by keyboard alone, people who magnify the page, and people who find movement on screen difficult.

Conformance

This website has been designed and built to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 at level AA.

What that means here

The following is an account of what has actually been done, and not a restatement of the guidelines:

• Semantic structure. Every page uses real landmarks — a banner, a single main region, navigation regions with distinct accessible names, and a contentinfo footer. Headings run in order and describe the section they open, and there is exactly one first-level heading per page.
• A skip link. The first thing a keyboard user reaches on every page is a visible link that jumps straight to the main content, past the navigation.
• Full keyboard operability. Every link, button, form field and control can be reached and operated with a keyboard alone. Nothing traps focus. The mobile navigation panel can be closed with the Escape key, keeps focus inside itself while it is open, and returns focus to the button that opened it.
• Visible focus. Focus is indicated by a solid two-pixel outline with an offset, in a colour chosen to contrast against both the element and the background behind it. On dark sections the ring changes colour so that it stays visible.
• Contrast. The palette was checked against the AA thresholds. Body text on the paper background measures approximately 7:1, and the muted secondary text approximately 7:1 as well. The gold accent is used at a darker weight for small text on light backgrounds, where it measures approximately 5.3:1, and at a lighter weight on dark backgrounds. Gold is never used for text at a size or weight where it would fall below the threshold.
• Text alternatives. Every photograph carries alt text describing what it shows, written for someone who will not see it. Images that are purely decorative are given an empty alt attribute so that assistive technology skips them instead of announcing scenery.
• No photographs of people. Team members are represented by typographic monograms drawn in CSS. These scale with the page, and are hidden from assistive technology because the person's name always appears beside them in real text.
• Forms. Every field has a visible, permanently associated label — no placeholder-only fields. Required fields say "(required)" in words rather than relying on an asterisk or on colour. Errors are announced, listed at the top of the form as links to the fields concerned, repeated beside each field, and associated with the field programmatically. Focus moves to the first field that needs attention.
• Colour is never the only signal. Errors are conveyed by text, not only by a red border. The current page in the navigation is marked programmatically as well as visually.
• Motion. The only movement on the site is a short fade as a section comes into view. If your system is set to reduce motion, that is switched off entirely, along with smooth scrolling. Nothing moves, flashes, autoplays or scrolls on its own.
• Zoom and reflow. The layout reflows to a single column and remains fully usable at 320 pixels wide and at 400% zoom, without horizontal scrolling. Text can be resized without loss of content or function.
• Language and titles. The page language is declared as British English, and every page has a unique, descriptive title.
• No time limits. Nothing on this site expires, times out or requires you to act within a period.

How this was tested

Testing combined automated checks with manual review: an automated accessibility audit run against the home page and an article page under mobile emulation; a keyboard-only walkthrough of every page template including the full contact form; review of the rendered structure with a screen reader in mind; and manual checks at 375, 768 and 1280 pixel viewport widths, and at 400% zoom.

Known limitations

These are set out so that you do not have to discover them.

• The office map. The map on our contact page is deliberately not interactive, and it is hidden from assistive technology. It contains no focusable controls, so it cannot trap keyboard focus, and it will not hijack scrolling on a touchscreen. Everything the map conveys is published beside it as ordinary text: the full address, and a link that opens the same location on OpenStreetMap where it can be zoomed and explored.
• The contact form needs JavaScript. If JavaScript is unavailable, the form cannot submit. The page says so, and gives our email address and telephone number as alternatives. Both are monitored and neither is a lesser route.
• Third-party map tiles. The map images are served by the OpenStreetMap Foundation and we do not control them.
• Google Analytics. This site loads Google Analytics. We do not control that script, and it is the one piece of code on the site we have not written. It adds no visible interface and no interactive element.

Tell us if we have got something wrong

If you find part of this site difficult or impossible to use, please tell us and we will put it right. You do not need to know why something is a problem in order to report it.

• Email: enquiries@jillingham.com
• Telephone: +44 (0)141 000 0000

Please say which page you were on and what happened. We will acknowledge your message and tell you what we intend to do about it.

If you need information from this site in another format — large print, plain text, or read to you over the telephone — ask, and we will provide it.

Our obligations

As a provider of services we are required to make reasonable adjustments so that disabled people are not placed at a substantial disadvantage.

We treat this statement as a description of what we currently do, not as the limit of what we will do.

Preparation of this statement

This statement was prepared on the date shown at the top of this page, and reflects the site as it stood on that date. It is reviewed whenever the site changes materially and at least annually.