Lanternfox Lanternfox Back to home

Accessibility Statement

Last updated: 3 June 2025

1. Our commitment

Lanternfox wants everyone to be able to use this website comfortably, regardless of how they access it. We are working towards conformance with the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA — a widely adopted international standard for web accessibility. This statement covers the site at lanternfox.blog.

2. Conformance target

Our target is WCAG 2.1 Level AA. We apply this standard to all pages we publish, including this one. Where we fall short, we note it under "Known limitations" below and aim to address it in our next round of updates.

3. Measures we have taken

Specific steps built into the current version of the site:

  • Semantic HTML: pages use proper heading hierarchies, landmark regions (<header>, <main>, <footer>, <nav>), and native HTML elements (<details>, <dialog>) where appropriate.
  • Keyboard navigation: all interactive elements — links, buttons, form fields, the mobile navigation, and cookie preference toggles — are reachable and operable using a keyboard alone.
  • Colour contrast: text and interactive elements use colour combinations that meet the 4.5:1 contrast ratio required for normal text under WCAG 2.1 AA. The design system was chosen with this in mind.
  • Reduced-motion support: any motion on the site respects the prefers-reduced-motion media query. All content is visible without animation.
  • Descriptive alt text: every content image has an alt attribute that describes what is shown in context. Decorative images use empty alt attributes.
  • Labelled form fields: all form inputs have associated <label> elements. Required fields are indicated both visually and programmatically.
  • Focus indicators: visible focus outlines are retained on all interactive elements so keyboard users can track their position on the page.
  • ARIA attributes: where native semantics are insufficient, ARIA roles, states, and properties are used — for example on the cookie dialog and toggle switches.

4. Known limitations

We are aware of a few areas that are not yet fully resolved:

  • The Google Maps iframe embedded on the main page has limited accessibility for screen reader users. We display the full address as text alongside the map as a workaround.
  • Third-party fonts loaded from Google Fonts may not render in all assistive technology environments; body copy falls back to system-native sans-serif fonts in those cases.
  • We have not yet completed formal automated or manual auditing against every WCAG 2.1 AA success criterion. Self-assessment is the basis of this statement.

If you encounter an issue not listed here, please let us know (see Section 5).

5. Reporting an accessibility issue

We welcome feedback. If you find something on the site that creates a barrier — a page that is difficult to navigate with a keyboard, content that a screen reader cannot interpret, or a colour combination that is hard to read — please get in touch:

  • Email: [email protected]
  • Phone: +66 2 663 4179 (Monday – Friday, 08:00–18:00 Bangkok time)
  • Post: 315 Charoen Krung Road, Bang Rak, Bangkok 10500, Thailand

We aim to respond to accessibility queries within five working days and to address confirmed issues in the next scheduled update cycle.

6. Statement date

This statement was prepared in June 2025, based on self-assessment. We intend to review it annually and after any significant change to the site's structure or technology.