Skip to main content

Accessibility Statement

Effective date: May 17, 2026.

Our commitment

Dynamanic LLC, the operator of Railfans Live (the “Service”), is committed to providing a website that is accessible to the widest possible audience, regardless of technology or ability. We work toward conformance with the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA as our internal target, and we treat accessibility as an ongoing engineering responsibility rather than a one-time audit. We also recognize the considerations applicable to public-accommodation websites under Title III of the Americans with Disabilities Act, and we aim to operate Railfans Live consistent with those principles.

What we’ve done

Accessibility is part of how we build. Ongoing measures include the use of semantic HTML throughout pages and components, keyboard-navigable controls and skip targets, visible focus indicators on interactive elements, color-contrast review during design and code review, ARIA attributes where a native HTML semantic isn’t sufficient, alt text on user-uploaded photos when the uploader provides a description, and form labels associated with their inputs. Pages that depend on a map provide a parallel non-map list view of the same underlying records so that the same information can be reached without interacting with the canvas.

Known limitations

We try to be candid about where the current product falls short of our target, and we are actively working on these areas:

  • The interactive MapLibre map relies on visual rendering. Live train markers, in particular, are best experienced visually. To make the same data reachable without the map, we provide list views for stations, railfan spots, and sightings; screen-reader users can read full station and sighting details on their corresponding pages.
  • Live railcam streams are embedded from YouTube and inherit YouTube’s accessibility characteristics, including caption availability. We don’t author or control captions on third-party railcam feeds.
  • User-uploaded photos may not always carry uploader-supplied descriptions. We encourage submitters to include them, but we cannot guarantee descriptive alt text on every community-contributed image.
  • Some third-party components, including Stripe Checkout, PostHog analytics widgets, and OpenStreetMap tile rendering, have their own accessibility characteristics that are outside our direct control. We monitor those vendors’ published accessibility postures and prefer vendors with active programs.

Feedback and assistance

If you encounter an accessibility barrier on Railfans Live, or if you need content that isn’t reachable in your current setup, please contact us at accessibility@railfans.live. We commit to acknowledging accessibility reports within five (5) business days and to making good-faith efforts to resolve identified barriers in a reasonable timeframe. You may also reach us by mail at: Dynamanic LLC, 179 Walnut Crest Run, Sanford, FL 32771.

Alternate formats

On request through the feedback channel above, we will provide informational content from this site in an alternate format reasonably suited to the requester’s needs — for example, a plain-text rendering of a station or spot detail page, or a written description of map content for a specific area.

Compatibility

Railfans Live is designed to be compatible with current versions of major web browsers, including the latest versions of Google Chrome, Apple Safari, Mozilla Firefox, and Microsoft Edge, used together with current versions of common assistive technologies, including NVDA, JAWS, VoiceOver (macOS and iOS), and TalkBack (Android). Older browsers and unsupported assistive-tech versions may produce degraded results.

Scope and disclaimer

This statement is informational. It describes our active, good-faith accessibility program and our target conformance level; it is not a representation, warranty, or contractual commitment that every page, view, third-party embed, or user-contributed item on Railfans Live meets WCAG 2.1 Level AA at every moment. We revise this statement from time to time as the Service and our practices evolve, and the “Effective date” above reflects the most recent revision.