Accessibility.

InStone is committed to making our website and our publications accessible to as many people as possible. We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA across everything we publish.

Accessibility is not a separate workstream. It is designed into the site from the start, and every new page is reviewed against the same standard before it ships.

If you use assistive technology and find something on this site that does not work for you, please tell us. We want to fix it.

Semantic HTML throughout. Pages use proper heading hierarchy, landmarks, and list structures so screen readers can navigate them naturally.

Keyboard navigation. Every interactive element on the site can be reached and activated using a keyboard alone. Visible focus states are kept visible.

Text contrast. We aim to meet or exceed the WCAG AA contrast ratios (4.5:1 for body text, 3:1 for large text and interface elements) across both light and dark themes.

Readable type. Body copy is set in a comfortable reading size with generous line height. Long-form essays use a narrow column for readability.

Alt text on meaningful images. Decorative imagery is marked as such so it does not interrupt screen reader flow.

Plain English. Technical and legal writing is written to be understood by a human reader, not just a lawyer.

Reduced motion. Users who prefer reduced motion in their system settings see simplified or disabled animations on pages that include them.

We are honest about where the site falls short. As of the last review date at the top of this page, the following issues are known to us and are on our list to fix:

The horizontal project scroller on the Selected Work page is primarily designed for pointer-based interaction. Keyboard scrolling works through tab navigation, but arrow-key scrolling is not yet wired up.

Some of our GlistenText animations (the scroll-triggered sweep across hero titles) rely on visual timing. They are suppressed for users who set `prefers-reduced-motion`, but we are improving the fallback.

The strategy picker and the Specialist Briefs picker both use a sticky bottom action bar that follows you as you scroll. The bar is keyboard-reachable via the normal tab order, but on shorter viewports it can overlap the last few lines of content underneath. Scroll past the end of the page to reveal anything obscured.

The document preview panels used for sample brief issues use structured HTML rather than PDF. If you need a tagged PDF version of any sample issue, email us.

Subscription forms are not yet integrated with password managers in the same way a standard login form is. They still work with keyboard and screen reader, but the auto-fill experience may be inconsistent.

If you hit anything else, please report it using the section below.

If you find something on this site that is difficult or impossible to use, please email info@instone.one with the details. The more you can tell us, the faster we can reproduce and fix.

Helpful things to include, if you can: the page URL, the assistive technology you are using (screen reader, keyboard only, magnifier, etc.), and what you were trying to do when the problem occurred. None of this is required; a one-line description is also welcome.

We acknowledge every accessibility report within two working days and follow up with either a fix, a workaround, or a clear timeline for when the fix is coming.

If you need any content on this site (essays, briefs, policy pages, case studies) in a different format, email us and we will work with you to provide it.

We can provide plain-text versions and large-print PDFs on request at no charge. Tagged PDFs and audio summaries are available on request, subject to reasonable time to produce. No charge for any accessible format we can provide.

This site embeds content from a small number of third-party services (for example, our subscription form and payment processor). We hold those providers to accessibility standards as part of our procurement, but we do not control every detail of their interfaces.

If you run into an accessibility problem in a third-party embed, please tell us. We will work with the provider to fix it, or, where that is not possible, provide an alternative path through us.

Accessibility is an ongoing commitment, not a one-off audit. We review the full site against WCAG 2.1 AA at least twice a year, and every new page or feature is reviewed before it ships.

When we find gaps, we log them here under Known issues and fix them in priority order: anything blocking a user completely is fixed before anything that merely degrades the experience.

Email info@instone.one with any accessibility question, issue, or request. A human reads every message.

If you have raised an accessibility issue with us and are not satisfied with our response, you have the right to contact the Equality Advisory and Support Service (EASS) in the UK for further advice.