Skip to content
Agentic Levels
Start hereLevelsTracksPromptsAbout
Get my levelGet my level

  • Start hereYour first useful task with AI.
  • Level quiz8 questions. No AI needed.
  • Fluency ScoreYour Level and a score, from your own AI.

  • LevelsThe 11 levels, in order.
  • LessonsShort lessons, filter by level.
  • TracksGuided paths by tool, role or goal.
  • Set up your AI tool
  • Starter packFree files that help AI remember.

  • PromptsReady prompts to copy and adapt.
  • ChatGPT vs Claude vs GeminiPick the right one for the job.
  • How-tos
  • ReferenceCommands for Claude Code, Codex, Antigravity.
  • ResourcesHand-picked reading and tools.

  • Your progress
  • Your next moveAn interview that picks your next skill.
  • Your next lessonsThe next lessons at your level.
  • Updates

  • Pricing
  • About
  • FAQ & Feedback
  • Work with us
  • How we handle your data
Sign inPreferences
AboutPricingHow-tosPromptsStarter packMy stackHow we handle your data

© 2026 Fuentes Studio

PrivacyTermsRefundsAccessibilityAI content policyCredits
yourCouncil
Ready to help
✦

What do you want to understand?

Ask anything about what you're learning.

Trust Center›Accessibility Statement

Accessibility Statement

Last updated: August 4, 2026

Agentic Levels teaches AI skills to people of every age, background, and ability. This page explains what we've built to make the site usable for everyone, and where we still have work to do.

On this page

  1. Our approach
  2. Reading and text size
  3. Keyboard navigation
  4. Color and layout
  5. Known limitations
  6. Report a problem
  1. Our approach
  2. Reading and text size
  3. Keyboard navigation
  4. Color and layout
  5. Known limitations
  6. Report a problem

Our approach

We build toward the Web Content Accessibility Guidelines (WCAG), the standard rulebook for accessible websites, targeting level 2.2 AA. We have not run a formal accessibility audit yet, so we cannot claim the site fully conforms. This page is an honest snapshot of what's built today, not a certification.

Reading and text size

Our design system sets a 16 pixel floor for body text, so most of the site reads comfortably without zooming. Some older components still render at 14 or 15 pixels. We are working through them.

Your Preferences page has two kinds of reading help: a Reading setting and a Dyslexia font. They're separate, so you can use one, both, or neither.

You pick one Reading setting at a time. Bionic bolds the first few letters of each word, and Bionic Lite bolds fewer. Wide spacing adds room between letters, words, and lines, and Extra-wide spacing adds more and shows slanted (italic) text upright.

The Dyslexia font switches the text you read to OpenDyslexic. It's free and open source, which means anyone can use and share it at no cost. Headlines, code, and the menus at the top and bottom of the page keep their usual fonts.

Why two choices? Studies of readers with dyslexia link wider spacing to easier reading (Zorzi and colleagues, 2012). Tests of dyslexia fonts haven't shown faster or more accurate reading (Wery and Diliberto, 2016; Kuster and colleagues, 2018).

Some readers still find the font more comfortable, so it's yours to turn on. The site only downloads it if you do.

Whatever you choose applies to the content of every page, not just this one.

Keyboard navigation

Every page includes a skip link, a hidden link that appears when you press Tab. It lets keyboard users jump straight past the navigation menu to the main content.

Buttons and links show a visible outline when you tab to them, so you can see where you are without a mouse. A few of the more complex parts of the site are still catching up. Those are listed below.

Color and layout

Our color and type system is built from a shared set of design tokens, reusable colors and sizes used everywhere. That keeps contrast and spacing consistent across every page. We have not yet run a formal contrast audit against every color combination on the site.

If you have asked your device to reduce motion, the site turns off the animations and transitions that run in CSS. Some interactive pieces are driven by a separate animation library and still move. We are working through those.

Known limitations

We're a small team and accessibility work is ongoing. Here's what we know still needs attention:

  • We haven't completed a formal WCAG audit or extensive screen reader testing (software that reads a page out loud for people who are blind or have low vision)
  • Color contrast hasn't been checked against every element on every page yet
  • Some complex parts of the site, like the chat interface and diagrams, may not be fully keyboard-operable yet
  • Sign-in and payment run through outside services, Clerk and Stripe, whose accessibility we don't control

Report a problem

If something on the site is hard to use, tell us. Email hello@fuentes.studio with the page you were on and what happened. We read every message and do our best to fix it.

Other documents

  • Privacy Policy
  • Terms of Service
  • Refund Policy
  • AI Content Policy
← Trust Center