Skip to main content

J²Adventures

Travel stories, maps, and photo-led field notes from the places we wander.

Back to top

Explore

  • Home
  • Map
  • About
  • Wishlist
  • Accessibility

Discover

  • Tags
  • Categories
  • Series
  • RSS Feed

Stay on the trail

Get notified when we post new stories.

© 2026 J² Adventures

J²Adventures
HomeMapCategoriesTagsAbout
Sign in

Accessibility

Built to be readable for everyone.

J²Adventures is a personal travel blog, but the people reading it come with all kinds of eyes, ears, hands, and browsers. We are committed to making the site usable for as many of you as possible, and to being honest about where it still falls short.

Our commitment

We target WCAG 2.2 Level AA for every public page. That means: meaningful structure, perceivable color contrast, keyboard operability, and clear feedback when something changes. We test with automated tooling, manual keyboard review, and screen reader spot-checks (VoiceOver and NVDA) before shipping changes that touch navigation or content rendering.

Accessibility is not a one-time audit. It is a habit, baked into how we design new features, review pull requests, and respond to feedback from real users.

What you can use today

A non-exhaustive list of accessibility features already shipping on J²Adventures:

  • Skip link

    A 'Skip to main content' link is the first focusable element on every page. It jumps keyboard users past the header and navigation straight to the article body.

  • Semantic landmarks

    Every page exposes a labelled <main> landmark, labelled <nav> blocks, and a labelled <footer>, so screen reader users can orient and jump with a single keystroke.

  • Keyboard navigation

    All interactive elements (links, buttons, form controls, dropdown menus, the mobile nav dialog) are reachable and operable with the keyboard alone. Visible focus rings are preserved on every theme.

  • ARIA labels and roles

    Icon-only buttons, dialogs, and live regions carry descriptive aria-label, aria-live, and role attributes. Decorative SVGs are marked aria-hidden so they aren't announced.

  • Color contrast

    Foreground text against cards and the page background targets WCAG AA contrast in both light and dark themes. The print stylesheet resets to a high-contrast black-on-white palette.

  • Screen reader announcements

    Status changes (form submissions, share feedback, reading progress milestones) are announced via polite aria-live regions rather than announced silently.

  • Respects reduced motion

    A prefers-reduced-motion media query disables non-essential animation and switches the back-to-top button from smooth scroll to instant jumps for users who opt out.

  • Print-friendly articles

    Printing a story strips navigation, the reading-progress bar, share buttons, the comment thread, and the newsletter signup so you get a clean article on paper.

Known limitations

We are honest about what is not yet perfect:

  • Older posts may contain images uploaded without alt text. We are working backwards through the archive to fill these in. If a specific image is blocking you, please tell us.
  • The interactive wishlist map depends on a third-party tile provider. If those tiles fail to load, the surrounding content remains accessible but the map itself will be blank.
  • Caption tracks for any video embeds depend on the source platform (YouTube, etc.). We link to those videos rather than hosting them ourselves.

Found a barrier? Tell us.

If something on J²Adventures is hard to use with your keyboard, screen reader, or any other assistive tech, we want to hear about it. Please include the page URL, what you were trying to do, and the browser or tool you were using. We respond to every accessibility report.

Email: accessibility@jsquaredadventures.com

For everything else, head to the about page for general contact details.

Standards we follow

We build against the W3C Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA, and use the WAI-ARIA Authoring Practices as a reference for custom widgets like the mobile navigation and dropdown filters. The site's content security policy and HTML semantics are reviewed in the same pull requests that change behaviour, so accessibility regressions get caught early.

This statement was last reviewed on 2026-06-15.