Skip to content →

Accessibility Statement

TokensHelpdesk The Learning Circle. Figure AI out together. A product of 2 Degree Shift, Inc. Effective date: July 22, 2026 Last updated: July 22, 2026

Our commitment

TokensHelpdesk is making every effort to ensure that our website, our SMS content, our monthly team PDF, 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.

TokensHelpdesk is the home of the Learning Circle, a small-group AI learning subscription for teams of 2 to 4 friends or colleagues. Because the Learning Circle depends on team members communicating with each other about AI-generated content, accessibility is not a side concern. It is central to whether the product works for a Circle 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, SMS content, and monthly PDF are 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 and message 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 tokenshelpdesk.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

The Learning Circle delivers 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 Circle post opens with a clear label (“Circle: Tuesday post” or “Circle: Question response”) 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. Circle hosts can also invite and remove Circle members through SMS commands.
  • Voice on the roadmap. We plan to offer a voice-delivery option (spoken versions of Circle posts and question responses) for Circle members who prefer or need audio over text. Email Connect@TokensHelpdesk.com if you would like to be notified when this option becomes available.

Learning Circle accessibility

The Learning Circle is a small-group product where 2 to 4 Circle members receive daily texts, twice-a-week Circle texts and share up to 12 Circle questions per month. Because Circle members communicate with each other about AI-generated content, the product introduces accessibility surfaces beyond a standard SMS subscription. Each meets the same accessibility standards described above.

  • Circle text formats. Twice-a-week Circle texts arrive Tuesday and Thursday. All three current text formats (three-truths-and-a-lie, split-response puzzles, and three-part habit builders) are delivered entirely as text with no image-only content. Split-response Circle texts, in which each Circle member receives different cues intended to be combined, are written so that each member’s message stands on its own as a readable SMS. No cue depends on visual formatting, color, or emoji to be understood.
  • Synchronized delivery for equal participation. All Circle members receive Circle texts at the same moment. If a Circle member uses a screen reader that takes longer to read a message than a sighted reader, the Circle text still gives every member the same time window to respond. Circle challenges do not have countdown timers or time-pressured mechanics that would disadvantage members who read at different speeds or who use assistive technology.
  • Circle communication is offloaded to the tools members already use. Circle members communicate with each other about Circle texts using their own group chats (iMessage, WhatsApp, Signal, or SMS group threads). We do not require Circle members to use a proprietary app or interface for peer discussion. This means every Circle member uses the messaging tool that is already accessible to them, in the configuration they already have.
  • Question submission and review process. Any Circle member can text a question to the Helpdesk at any time. The question submission works entirely by SMS, so no web form is required to participate. Reviewed answers are delivered by SMS within 24 hours, in plain language, with no image-only content. Every reply includes the reviewer’s initials so Circle members know the message was human-reviewed.
  • Monthly Circle progress PDF. Every Circle receives a monthly PDF on the 1st of each month that summarizes the previous month’s activity. We build these PDFs to be accessible in PDF screen readers: proper tagged-PDF structure, every heading marked as a heading, every list marked as a list, every chart with alternative text describing what the chart shows and the underlying numbers, and no color-only signals. If you need the monthly PDF in an alternative format (accessible Word document, plain text, or an HTML page), email Connect@TokensHelpdesk.com and we will provide it.
  • Monthly IRL Circle Challenge. Every month your Circle receives a Challenge designed to bring the Circle together in person (or on a synchronous video call for long-distance Circles). Accessibility considerations for the IRL Challenges:
    • Physical accessibility of Circle meetups is the Circle’s responsibility, not TokensHelpdesk’s. Circle members decide together where to meet. Our role is to design Challenges that work in a range of physical settings, from a kitchen table to a park bench to a video call, so the Circle can pick the setting that works for every member.
    • Alternative Challenge formats on request. When a specific Challenge is not suitable for a Circle member with a particular disability, tell us and we will send an alternative that lets the whole Circle participate. Email Connect@TokensHelpdesk.com. We keep a running library of alternative Challenges tuned for mobility, sensory, and cognitive accessibility considerations.
    • Synchronous video call as an equal path. Circles that cannot meet in person for any reason (geographic distance, disability, caregiving responsibilities, scheduling) can complete every Challenge on a synchronous video call. The Challenge design does not privilege in-person over video. The monthly PDF gives the same credit either way.
    • No time pressure. Challenges do not have deadlines within the month. Your Circle picks when to meet. If a Challenge takes longer than one month to complete, we count it in the month you finish.
  • Circle roster changes by SMS. Circle hosts can invite new members and remove departing members entirely through SMS commands. No web form is required for roster management. This matters when a host uses assistive technology that works better with SMS than with web forms.

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, Circle testimonial recordings), 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 accessibility for the monthly Circle progress PDF. PDF is not as fully covered by screen-reader tooling as HTML. We test the monthly PDF 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. Email Connect@TokensHelpdesk.com for a Dropbox link with the alternative format.
  • Circle text format accessibility research. The Circle text formats (three-truths, split-response, habit builders) are new. We are actively learning how members with different disabilities experience them and adapting the formats as we learn. If a Circle text format does not work well for you, we want to know so we can improve it.
  • 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 Circle members are the fastest way we learn where our testing has gaps.

How to report an accessibility issue or request an alternative format

TokensHelpdesk (a product of 2 Degree Shift, Inc.)
Connect@TokensHelpdesk.com

When you contact us, please include:

  • TokensHelpdesk (a product of 2 Degree Shift, Inc.)
  • Connect@TokensHelpdesk.com
  • When you contact us, please include:

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, the SMS service, the monthly PDF template, or a new Circle text format, 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: DM Sans (SemiBold 600), an open-source sans-serif designed for user interfaces with friendlier, rounder letterforms than more institutional sans-serifs. Chosen for the Learning Circle because a helpdesk and small-group learning product should feel welcoming, not clinical. 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 Attorney General’s office.

    For informal feedback, questions, or ideas about accessibility at TokensHelpdesk: Connect@TokensHelpdesk.com.