Digital spaces for every human.

folkfox is committed to ensuring digital accessibility for people with disabilities. We treat accessibility as part of our craft, not a compliance afterthought, because a brand strategy only works if everyone can experience it.

We are continually improving the user experience for everyone and applying the relevant accessibility standards. This statement is a living document, reviewed at least twice a year and after any significant change to the site.

The Web Content Accessibility Guidelines (WCAG) define requirements for designers and developers to improve accessibility for people with disabilities, at three levels: A, AA and AAA.

folkfox.com is substantially conformant with WCAG 2.2 Level AA. Substantially conformant means most of the site meets the standard, with minor exceptions noted under Known limitations below. This assessment is a self-evaluation carried out by the folkfox team, most recently on 5 July 2026.

Where the harmonised European standard applies, we align to EN 301 549. The current EN 301 549 v3.2.1 references WCAG 2.1 AA; the forthcoming v4.1.1, expected in 2026, incorporates WCAG 2.2, which we already build to.

We design against the following standards and laws:

• WCAG 2.2 Level AA, published by the W3C Web Accessibility Initiative, is our primary benchmark. See the WCAG 2.2 specification.
• EN 301 549, the harmonised European standard for ICT accessibility.
• The European Accessibility Act (Directive (EU) 2019/882), in force and enforceable across the EU since 28 June 2025.
• WAI-ARIA for accessible rich internet application semantics.
• For international clients we also reference the US Americans with Disabilities Act and Section 508.

When engineering folkfox.com we implemented, among others:

• Semantic structure: HTML5 landmarks (header, nav, main, section, footer), a single logical heading order, and skip links.
• Keyboard operability: every control is reachable and usable by keyboard, with a clearly visible focus indicator that meets the focus-appearance criteria.
• Colour and contrast: body text exceeds the 4.5:1 minimum; information is never conveyed by colour alone.
• Resizable text: content reflows and remains usable at 200% zoom and supports the text-spacing criterion (1.4.12).
• Motion and transparency: we honour prefers-reduced-motion, prefers-contrast and prefers-reduced-transparency, and any looping animation has a visible pause control.
• ARIA and live regions: interactive widgets expose state to assistive technology, and status messages use polite live regions.
• Site-wide toolkit: the folkfox header carries an accessibility menu (text spacing, larger cursor, muted imagery and more), and the toolkit on this page lets you adjust text size, contrast, spacing, link underlines, a readable font and motion.

folkfox.com is designed to be compatible with recent versions of the following, used together with a current browser (Chrome, Edge, Firefox or Safari):

• NVDA and JAWS on Windows
• VoiceOver on macOS and iOS
• TalkBack on Android
• Voice control, switch access and screen magnification

Accessibility relies on the technologies below working as expected. Where an assistive technology or browser is older, some features may degrade gracefully rather than fail.

Despite our efforts, some limitations remain. If you find one not listed here, please tell us.

• Third-party embeds: scheduling widgets, maps and social embeds are provided by external services whose accessibility we do not fully control. We choose accessible partners where possible and provide non-embedded alternatives such as email.
• Legacy documents: a small number of older PDFs and case studies may not be fully tagged for screen readers. We are remediating these and will supply an accessible version on request.
• User-generated and live content: content pulled live from our journal is checked for structure, but we cannot guarantee every historical article meets every criterion.

Accessibility is verified continuously, not once. Our process includes:

• Automated checks with tools such as axe and Lighthouse in our build pipeline.
• Manual keyboard-only walkthroughs of every template.
• Manual screen-reader testing on the technologies listed above.
• A full review before any significant release, and at least twice-yearly audits of the whole site.

We welcome your feedback. If you cannot access something, or you need information in a different format (large print, plain text, a tagged document or a phone walkthrough), contact us:

• Email: [email protected]
• Response: we aim to reply within one business day and to resolve or provide a workaround promptly.

If you are in the EU and are not satisfied with our response, you may raise the matter with the market-surveillance authority responsible for the European Accessibility Act in your country. We would always prefer to put things right directly first.

This accessibility statement was prepared and approved by the folkfox team on the basis of a self-assessment. It was last reviewed on 5 July 2026 and is scheduled for review at least every six months, and after any major change to the site.