Skip to content →

Accessibility

Reduce Token Costs A product of 2 Degree Shift, Effective date: July 21, 2026 Last updated: July 22, 2026

Accessibility has been my practice for twenty years, as an educator and as founder of 2 Degree Shift since 2004. Our work-based learning books, open source published as Livable Wage Jobs 501(c)(3) ship with near-obsessive accessibility options. When we publish a document here, we release both .docx and .pdf, because braille-based user agents can navigate accessible .docx files and cannot tab well through most PDFs. When I hire apprentices, I hire through platforms that reach candidates other companies overlook. HireAutism.com is one I know. The last time I checked, they had over six thousand people looking for work. There are others reaching candidates with vision, hearing, or mobility differences, and I try to learn about them as I hire. The choices we made building these sites, plain design, high contrast, keyboard navigation, screen reader landmarks, come from the same discipline.

Kelly Cooper, Founder & Educator

Our commitment

Reduce 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 a long-standing practice at 2 Degree Shift, 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 reducetokencosts.com have been mathematically verified. Every pairing exceeds 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

Reduce 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 support 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@ReduceTokenCosts.com if you would like to be notified when this option becomes available.

Executive Priority Track accessibility

Reduce Token Costs offers an Executive Priority Track add-on for finance leaders who want the coaching shaped around their P&L priorities. This add-on introduces three surfaces beyond the standard subscription. Each meets the same accessibility standards described above.

  • Executive Priority Track intake form. The form finance leaders use to submit their monthly coaching priorities meets the same accessibility standards as our standard signup. All fields have visible labels and screen-reader labels. Free-text fields have sufficient character allowance and clear error messages. Progress is saved between steps so no user loses input if their assistive technology requires a page refresh.
  • Personalized SMS from the Executive Priority Track. Custom coaching messages written for Executive Priority Track subscribers follow the same accessibility standards as our standard messages. Plain language at an 8th-grade reading level, no image-only messages, predictable opening and closing structure, and readable by any smartphone screen reader. Reviewer sign-off on every custom message includes an accessibility check before send.
  • Monthly Executive Priority Brief (Excel file). Subscribers to the Executive Priority Track receive a monthly brief as an Excel file. We build these briefs to be accessible in spreadsheet screen readers: every sheet has a descriptive name, every chart has alternative text describing what the chart shows and the underlying numbers, and every color-coded metric has a secondary encoding (a text label or symbol) so the meaning is not dependent on color. If you need the brief in an alternative format (accessible PDF, plain text, or a Google Sheets version), email Connect@ReduceTokenCosts.com and we will provide it.

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.
  • Spreadsheet accessibility for the Executive Priority Brief. Excel is not as fully covered by screen-reader tooling as HTML. We test the monthly brief with the most widely used spreadsheet screen readers (JAWS with Excel, NVDA with Excel, VoiceOver with Numbers, and Google Sheets’ built-in screen-reader mode). If your primary spreadsheet tool is one we do not currently test with, tell us and we will add it to our verification list.
  • 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@ReduceTokenCosts.com if you prefer .docx versions for use with a braille display or a screen reader that navigates by document structure. We will send you a Dropbox link with the .docx versions.
  • 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 Reduce 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.

Reduce Token Costs (a product of 2 Degree Shift, a California C Corporation)
Connect@ReduceTokenCosts.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.

For Executive Priority Track subscribers requesting alternative formats of the monthly brief: please notify us at least 5 business days before your next scheduled brief so we can prepare the alternative format in parallel with the standard delivery.

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: Source Sans 3 (Bold 700), Adobe’s open-source sans-serif designed for user interfaces. Chosen for its high x-height, clearly differentiated letterforms (the lowercase “l” is distinct from uppercase “I,” the “1” is distinct from lowercase “l”), and consistent performance across the major screen readers we test with. Released under the SIL Open Font License.
  • 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;s Office.

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