Skip to content →

Accessibility Statement

Cut Token Costs A product of 2 Degree Shift, Inc. Effective date: July 21, 2026 Last updated: July 21, 2026

Our commitment

Cut Token Costs is making every effort to ensure that our website, our SMS content, and our subscription service are accessible to people with disabilities. We believe that access to information and useful tools should not depend on how you read, hear, type, or navigate. Accessibility is an ongoing practice at 2 Degree Shift, not a one-time compliance exercise, and we welcome your feedback as we improve.

The standard we are working toward

We are working to conform to the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA published by the World Wide Web Consortium (W3C). WCAG 2.1 AA is the standard used by U.S. federal agencies and referenced by the Americans with Disabilities Act (ADA) as the current benchmark for web accessibility.

Meeting this standard means our website is designed to be:

  • Perceivable. Text alternatives for images, captions where applicable, sufficient color contrast between text and background, and content that can be resized without loss of information.
  • Operable.  Full keyboard navigation, no content that flashes in ways that could trigger seizures, and enough time to read and use content.
  • Understandable.  Readable text, predictable page behavior, clear form labels, and helpful error messages.
  • Robust.  Content that works across current and future assistive technologies including screen readers, screen magnifiers, and voice-input tools.

What we have done so far

  • Semantic HTML so screen readers can navigate our pages by headings, landmarks, and lists.
  • Accessible typography. Body text is set in Atkinson Hyperlegible, a typeface designed by the Braille Institute specifically to improve legibility for readers with low vision. Body copy is set at 18px with 1.6 line-height for comfortable reading.
  • Color contrast meeting WCAG AA ratios (4.5:1 for body text, 3:1 for large text) throughout the site. All color pairings on cuttokencosts.com have been mathematically verified, most exceed the stricter WCAG AAA threshold (7:1).
  • Self-hosted fonts. All font files are hosted on our own servers as WOFF2 files. No visitor data (including IP addresses) is transmitted to Google or any third-party font provider when pages load.
  • Keyboard navigation,  every interactive element on the site (links, buttons, form fields, sign-up flow) is reachable and operable using only a keyboard.
  • Descriptive link text, no “click here” or “read more” without context.
  • Form labels,  every input on the sign-up form has a visible label and an associated screen-reader label.
  • Text resizing,  the site remains usable when text is zoomed to 200%.
  • Alternative text for meaningful images; decorative images are marked so screen readers skip them.
  • No motion traps,  we do not use auto-playing video, auto-scrolling carousels, or animations that cannot be paused.
  • Reduced motion, we honor the operating-system-level “reduce motion” preference for users who need less visual movement.

SMS accessibility

Cut Token Costs delivers educational content by text message, which is itself an accessible format for many people who cannot use visual interfaces or who have limited data plans. In addition:

  • Plain language. Messages are written in short sentences at approximately an 8th-grade reading level.
  • No image-only messages. All content is delivered as text, so screen readers on smartphones can read every message.
  • Predictable structure. Every message opens with “Tokens:” and ends with the same reply instructions (“Reply NEXT, BACK, STOP, or HELP”), so users learn what to expect and where to find controls.
  • Human help by text. If you cannot navigate our website, you can subscribe, ask questions, and cancel entirely through SMS by texting HELP at any time.
  • Voice on the roadmap. We plan to offer a voice-delivery option (spoken versions of daily messages) for subscribers who prefer or need audio over text. Email Connect@CutTokenCosts.com if you would like to be notified when this option becomes available.

Areas where we know we have work to do

We are transparent about the fact that we are not yet fully conformant with every WCAG 2.1 AA success criterion. Known gaps we are actively working to close:

  • Video captions. As we add video content (product explainers, apprentice interviews), we will provide human-reviewed captions and transcripts. Auto-generated captions alone are not sufficient.
  • Third-party embedded content. Some tools we embed (payment forms, analytics widgets) may not fully meet WCAG AA. Where we cannot control the embedded content, we work with the vendor and, where possible, provide an accessible alternative path.
  • PDF documents. Any PDF we publish (guides, one-pagers) is being reviewed for tagged-PDF accessibility. We will replace or repair any PDFs that do not meet WCAG standards. Email Connect@CutTokenCosts.com if you prefer .docx versions for braille-based agent shortcut key use. We will send you a Dropbox business link with all .docx.
  • Ongoing testing. We test with keyboard-only navigation and with screen readers (VoiceOver on macOS/iOS and NVDA on Windows) on every major site change. We are working toward regular audits by a qualified accessibility reviewer.

Assistive technologies we test with

  • Screen readers: VoiceOver (macOS, iOS), NVDA (Windows), TalkBack (Android)
  • Browsers: Recent versions of Chrome, Safari, Firefox, and Edge
  • Input methods: Keyboard only, touch, voice input

If you use a specific tool or configuration and encounter a barrier, please tell us, real-world reports from users are the fastest way we learn where our testing has gaps.

How to report an accessibility issue or request an alternative format

If you cannot access any part of Cut Token Costs, if something on our site or in our messages is not working with your assistive technology, or if you need content in an alternative format, please contact us. We treat accessibility requests as priority support.

Cut Token Costs (a product of 2 Degree Shift, Inc.)
Connect@CutTokenCosts.com

When you contact us, please include:

  • What page, message, or feature you were trying to use
  • What device, browser, and assistive technology you were using (if you know)
  • What happened, and what you expected to happen

We will acknowledge your report within 2 business days and give you a plan or timeline for the fix. If a fix will take time, we will offer an alternative way to get the information or complete the task you were trying to do.

Ongoing improvement

We treat accessibility as part of every design and development decision, not as a separate track. When we ship a change to the site or the SMS service, accessibility is part of what we test before release. If you find something we missed, tell us, we want to know.

Actions and implementation details

This section documents the specific technical choices that back up the commitments above. We publish this level of detail because “accessibility-compliant” often means different things at different sites, we want ours to be checkable.

Typography

  • Body font: Atkinson Hyperlegible (Regular 400 and Bold 700), designed by the Braille Institute to maximize character recognition for readers with low vision. Free and open-source under the SIL Open Font License.
  • Heading font: Inter (SemiBold 600), a screen-optimized sans-serif consistently ranked among the most accessible UI typefaces available.
  • Body settings: 18px minimum, line-height 1.6, letter-spacing 0.01em, maximum line length ~65-75 characters. Meets and exceeds WCAG 2.1 success criterion 1.4.8 for visual presentation.
  • Font hosting: All font files are self-hosted as WOFF2 on our own web server. We do not use Google Fonts CDN or any third-party font host. This means no visitor IP addresses are transmitted to third parties for typography purposes, closing a gap that German courts have specifically identified as a GDPR violation for sites using the Google Fonts CDN.
  • font-display: swap is set on all custom fonts, so text is always readable during page load, never hidden waiting on a font download.

Color palette (verified WCAG contrast ratios)

Every color pairing on cuttokencosts.com has been computed using the WCAG 2.1 relative-luminance formula, not eyeballed. The verified ratios:

Body text on the page. Near-black text (#28251D) on warm cream background (#F7F6F2). Contrast ratio 14.15:1 passes WCAG AAA for both body text and large text.

Primary link and button (Hydra teal). Hydra teal (#01696F) on warm cream background (#F7F6F2). Contrast ratio 5.97:1 passes WCAG AA for body text and AAA for large text.

Link hover state. Deeper teal (#0C4E54) on warm cream background (#F7F6F2). Contrast ratio 8.69:1 passes WCAG AAA for both body text and large text.

Surface (cards, containers). Near-black text (#28251D) on surface white (#FBFBF9). Contrast ratio 14.4:1 passes WCAG AAA for both body text and large text.

Additional color rules we follow:

  • No pure black on pure white. Off-white backgrounds reduce visual fatigue for readers with photosensitivity, migraine sensitivity, or Irlen syndrome.
  • Color is never the only signal. Links are underlined in body text. Form errors use both color and an error icon plus a text message. Charts label data points directly, not through color-only legends.
  • Focus indicators use a 2px solid outline in Hydra teal (#01696F) with 2px offset — visible on every focusable element on every background.
  • Reduced motion is honored via the prefers-reduced-motion CSS media query. Users with motion sensitivity get static versions of anything that would otherwise transition.

Verification tools we run before every release

  • axe DevTools (browser extension) automated WCAG 2.1 scan on every page
  • Lighthouse accessibility audit Chrome DevTools built-in
  • WAVE by WebAIM visual overlay of contrast and structural issues
  • Keyboard-only navigation test Tab through every page, confirm focus is always visible and Tab order matches visual order
  • Screen reader spot check VoiceOver (macOS) and NVDA (Windows) on the homepage, pricing page, and sign-up flow

If any of the above surfaces a failure, we fix it before deploying. We do not ship changes that reduce accessibility below the baselines documented in this section.

Feedback and formal complaints

We hope to resolve any accessibility concern directly with you. If you are not satisfied with our response, you may contact the U.S. Department of Justice, Civil Rights Division, or your state’s Attorney General’s office.

For informal feedback, questions, or ideas about accessibility at Cut Token Costs: Connect@CutTokenCosts.com.