Accessibility Statement

01Our commitment

SportsGods is committed to making this site usable by as many people as possible, including people with disabilities. We want someone using a screen reader, navigating by keyboard alone, relying on high-contrast or magnified display, or using speech input to be able to read our analysis, check a line, and manage their subscription without hitting a wall.

We treat accessibility as ongoing engineering work rather than a one-time checkbox. This page is a plain-language summary of where the site actually stands today — including the parts that are not there yet.

02Conformance status

The Web Content Accessibility Guidelines (WCAG) define requirements for making web content more accessible. SportsGods targets WCAG 2.1 Level AA, and we have implemented some WCAG 2.2 Level AA criteria as well (for example 2.5.8 Target Size).

SportsGods is partially conformant with WCAG 2.1 Level AA. “Partially conformant” means that most of the site meets the standard, but some content does not yet fully conform. The specific areas we know fall short are listed in Known limitations below.

We are deliberately not claiming full conformance. A blanket claim would be easy to write and, on a site with this much dynamically rendered data, would not be accurate.

03What we have done

Accessibility is built into how the site is written, not bolted on afterward. Measures currently in place across SportsGods:

• Semantic structure. Every page uses real landmarks — <header>, labelled <nav>, <main>, <footer> — so assistive technology can jump between regions instead of reading linearly.
• Skip link. Every content page begins with a “Skip to content” link that becomes visible on keyboard focus, so keyboard and screen-reader users can bypass the navigation.
• Visible keyboard focus. A high-contrast focus ring is applied site-wide through :focus-visible, so you can always see where you are when tabbing.
• Declared language. Every page declares its language, so screen readers use the correct pronunciation.
• Text alternatives. Meaningful images carry descriptive alternative text; decorative icons and emoji are hidden from assistive technology with aria-hidden so they are not read aloud as noise.
• Colour contrast. Body copy and data labels were re-tuned specifically to clear the WCAG 1.4.3 AA contrast ratio — including scoped colour tokens on the analytics views, where the site-wide accent colours did not pass against their backgrounds.
• Not colour alone. Win/loss, hit/miss, and status indicators carry text or shape in addition to colour, so they remain readable with colour vision deficiency (WCAG 1.4.1).
• Announced updates. Pages that load or refresh data announce state changes through dedicated visually-hidden live regions (role="status" / aria-live="polite") instead of moving focus or silently swapping content (WCAG 4.1.3).
• Reduced motion. The site honours the prefers-reduced-motion operating-system setting and suppresses animation and transitions when you have asked for that.
• Target size. In-page navigation links were enlarged to meet the WCAG 2.2 target-size minimum, which matters most on touch devices.
• Accessible controls. Interactive controls such as the mobile menu button expose their name and state (aria-label, aria-expanded) rather than relying on a visual glyph.
• Zoom and reflow. Layouts are responsive and built with relative units, so text can be enlarged without content being clipped on most pages.

04Known limitations

Despite the work above, some parts of SportsGods have known accessibility gaps. We are listing them plainly, with what we intend to do about each. If one of these is blocking you right now, contact us and we will get you the information another way.

• Bet-entry form labels (My Bets). Most fields in the manual bet-entry form identify themselves with placeholder text and nearby visible text rather than a programmatically associated label. A screen reader landing directly on a field may not announce its purpose. Planned fix: associate explicit labels with every control.
• Data grids without table semantics. Several dense views — particularly odds and lines — are laid out with styled containers rather than real tables. A few grids expose table roles, but not all of them do, so row and column relationships may not be announced. Planned fix: extend table semantics across the remaining grids.
• Parlay builder preview. The illustrative sample rows in the parlay builder use unlabelled (disabled) controls. They are not interactive, but they are not well described either. Planned fix: replace the preview with described, non-form markup.
• Horizontal scrolling in dense views. Odds and lines tables scroll horizontally on small screens and at high zoom levels, which requires more panning than we would like (relevant to WCAG 1.4.10 Reflow).
• Third-party components. Checkout is handled by Stripe and web fonts are served by Google. Their accessibility is governed by their own implementations and is outside our direct control. If Stripe Checkout is not usable for you, email us and we will arrange your subscription another way.
• No formal audit yet. The site has not been through a third-party accessibility audit, and we have not yet run structured testing sessions with assistive-technology users. Our assessment is internal — see Section 8.
• Rapidly updating data. Live odds and scores refresh automatically. We announce changes politely rather than interrupting, but frequent updates can still be disruptive in some screen-reader configurations.

05Technical specifications

Accessibility on SportsGods relies on the following technologies working with your browser and any assistive technology you use:

• HTML
• WAI-ARIA
• CSS
• JavaScript

JavaScript is required for most of the site. Games, lines, analytics, and account pages render their data in the browser, so with scripting disabled those pages will not display content. Our static pages — including this one, Terms, Privacy, About, and Methodology — remain readable without JavaScript.

06Browser & assistive technology compatibility

SportsGods is designed to work with current versions of major browsers — Chrome, Safari, Firefox, and Edge — on desktop and mobile, together with the assistive technology built into or commonly paired with those platforms, including VoiceOver, NVDA, JAWS, TalkBack, browser zoom, and operating-system contrast and motion settings.

We have not verified every combination. Older browsers, older assistive-technology versions, and less common pairings may behave differently. If you use a combination that does not work, please tell us which one — that information directly shapes what we fix next.

07Feedback & getting help

We welcome feedback on the accessibility of SportsGods. If you encounter a barrier, or you need information from the site in a different format, contact us:

• Email: support@sportsgods.com
• Subject line: putting “Accessibility” in the subject routes it faster

It helps if you can include the page address, what you were trying to do, and the browser and assistive technology you were using — but send it even if you cannot. A one-line “the bet form does not work with my screen reader” is genuinely useful.

Our commitment to you: we read every accessibility report and respond as quickly as we can. SportsGods is a small operation, so rather than promise a turnaround time we might miss, we will tell you honestly where things stand. Where a fix will take a while, we will say so — and in the meantime we will provide the information or complete the task with you directly, including reading out picks, lines, or account details, or handling a subscription change on your behalf.

08How we assessed this site

SportsGods assessed the accessibility of this site by self-evaluation. That evaluation consisted of an internal review of the markup of every page against WCAG 2.1 Level AA, automated checks for structural issues (language declaration, alternative text, form labelling, heading structure, landmark regions), manual keyboard-only navigation, and targeted colour-contrast measurement of text and data labels.

This is a self-assessment and not an independent conformance audit. It was last carried out on August 2, 2026. We re-run it when the site changes materially, and we update the Known limitations section as items are fixed or discovered.

09Formal complaints

We would much rather hear from you first — most problems are faster to fix than to escalate. If you are not satisfied with how we respond, you may contact the U.S. Department of Justice Civil Rights Division, which enforces the Americans with Disabilities Act, at ada.gov.

This statement describes our accessibility practices and goals. It is not a warranty, a guarantee of conformance, or a legal admission, and it does not create rights beyond those provided by applicable law. Nothing here limits any right you have under law that cannot be waived by agreement.

10Changes to this statement

We update this statement when the site changes, when we fix a listed limitation, or when we discover a new one. The “Last updated” date at the top of this page reflects the most recent revision.