Effective: September 18, 2026
Last reviewed: September 18, 2026
Hook the Horizon is published by Northern Lantern House LLC. We want the site, Field Shop, and linked field applications to be usable by people with different devices, input methods, vision, hearing, motor abilities, and cognitive needs. Accessibility is treated as an operating requirement, not as a decorative compliance badge.
Our working standard
We use WCAG 2.2 Level AA as the practical reference point for design and remediation where it applies. That does not mean every page, third-party service, embedded tool, or legacy asset is guaranteed to conform perfectly at every moment. It means keyboard access, readable contrast, semantic structure, text alternatives, visible focus, touch-target size, responsive reflow, reduced-motion preferences, and understandable controls are part of the review standard.
What we build for
- Keyboard navigation without requiring a mouse or precise pointer.
- Visible focus states and logical reading and tab order.
- Text that can be enlarged or zoomed without losing the core task.
- Responsive layouts that work on phones, tablets, and desktop screens.
- Meaningful alternative text for editorial images when the image carries information.
- Labels, instructions, and error states for forms and interactive tools.
- Touch targets sized for coarse-pointer use rather than tiny desktop-only controls.
- Reduced-motion support where movement is not essential to the task.
- Color and contrast choices intended to keep meaning available without relying on color alone.
Field applications
Hook the Horizon’s field applications are separate web applications but are part of the same publication system. They are designed around the same accessibility expectations. Because these tools include interactive controls, saved state, diagrams, tables, and changing results, some barriers can appear there that do not exist in ordinary articles. If a tool works visually but fails with a keyboard, screen reader, zoom, voice control, or another assistive technology, we consider that a product defect.
Downloads, diagrams, and visual instruction
Fishing often needs visual explanation. Knot diagrams, rigging illustrations, maps, product plates, and downloadable field materials may contain information that is harder to express in a single alt-text sentence. Where a visual carries essential instruction, we aim to provide adjacent text, steps, labels, or another usable representation rather than treating alt text as a substitute for the whole lesson.
Third-party services
Some functions are supplied by third parties, including payment, advertising, analytics, email, video, maps, and other embedded services. We choose and configure those services with accessibility in mind, but we do not control every interface they render. If a third-party component creates a barrier, report it to us. We can often change the integration, provide another route, or escalate the problem to the provider.
Tell us what is not working
If you encounter an accessibility barrier, use the Hook Us page. If possible, include the page or tool address, what you were trying to do, what happened instead, and the device, browser, or assistive technology involved. You do not need to know the technical name of the problem.
We prioritize barriers that block access to safety information, legal or regulatory material, purchases and order support, privacy controls, core navigation, and the primary task of a field tool. If you need information in another reasonable format while a barrier is being fixed, ask through the same contact route and we will work with you on an alternative.
Company-level accessibility information
Northern Lantern House also maintains a company-level legal and accessibility page covering the broader publishing group.