Skip to content →

Accessibility

TokenCosts.ai Home base for 2 Degree Shift, a California C Corporation Effective date: July 23, 2026 Last updated: July 27, 2026

A note from Kelly

Accessibility has been my practice for twenty years, as an educator, an author, and as the founder of 2 Degree Shift since 2004. Our work-based learning books 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

TokenCosts.ai is making every effort to ensure that our website, our public content, and (when the subscriber layer launches) our dashboards and subscriber documents 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.

TokenCosts.ai is the home base for the three 2 Degree Shift programs (CutTokenCosts.com, ReduceTokenCosts.com, and TokensHelpdesk.com). Because this site is where returning subscribers reach their data and dashboards, accessibility is not a side concern. It is central to whether the site works for a subscriber at all.

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 useful 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 tokencosts.ai have been mathematically verified. Most pairings 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-in flow when available) is reachable and operable using only a keyboard.
  • Descriptive link text. No “click here” or “read more” without context.
  • 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.

Cross-site consistency

TokenCosts.ai is the fourth site in the 2 Degree Shift family (with CutTokenCosts.com, ReduceTokenCosts.com, and TokensHelpdesk.com). Every site shares:

  • The same body typeface (Atkinson Hyperlegible), so readers who have adjusted to the letterforms on one site read comfortably on the others.
  • The same body settings (18px, line-height 1.6, letter-spacing 0.01em, max line length approximately 65-75 characters).
  • The same accessibility baseline (WCAG 2.1 AA verified, most pairings AAA).
  • Self-hosted fonts on every site. No third-party CDN calls at page load.

TokenCosts.ai has its own heading typeface (Work Sans) and its own accent color (deep amber #8B3D0C) so the parent site reads as distinct from any single product site.

Subscriber layer (coming in a later phase)

TokenCosts.ai will host a subscriber-only layer in a later phase, including a sign-in flow, dashboards, a monthly document archive, and data links. When we ship that layer, it will meet the same accessibility standards described here. Specifically:

  • Sign-in works with keyboard only. No mouse required to sign in, request a password reset, or sign out.
  • Every dashboard has a data-table alternative. Every chart or embedded visualization will be paired with a screen-reader-accessible data table containing the same underlying numbers.
  • Every monthly document is available in alternative formats on request. PDF, accessible Word, plain text, or HTML.
  • Any embedded third-party dashboards (if we use them) will be audited before we embed them. If a vendor’s dashboard does not meet WCAG 2.1 AA, we will either provide an accessible alternative path or replace the vendor.

If you are a subscriber and you need a document in an alternative format before the subscriber layer is live, email Connect@TokenCosts.ai and we will send it to you directly.

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, methodology walkthroughs), we will provide human-reviewed captions and transcripts. Auto-generated captions alone are not sufficient.
  • Third-party embedded content. Some tools we may embed on the subscriber layer (dashboards, analytics widgets, payment forms) may not fully meet WCAG AA at the vendor level. Where we cannot control the embedded content, we will work with the vendor and, where possible, provide an accessible alternative path.
  • PDF accessibility for subscriber documents. PDF is not as fully covered by screen-reader tooling as HTML. We test subscriber documents with the most widely used PDF screen readers (JAWS, NVDA, and VoiceOver). If your primary tool is one we do not currently test with, tell us and we will add it to our verification list. Alternative formats (Word, plain text, HTML) are available on request.
  • 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 visitors and subscribers 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 TokenCosts.ai, if something on our site 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.

TokenCosts.ai (a service of 2 Degree Shift, a California C Corporation) Connect@TokenCosts.ai

When you contact us, please include:

  • What page 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 reach 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, a new subscriber view, a new monthly document template, or a new data embed, 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: Work Sans (SemiBold 600), an open-source neo-grotesque sans-serif designed for user interfaces and long-form editorial. 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 approximately 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 Attorney General’s office. For informal feedback, questions, or ideas about accessibility at TokenCosts.ai: