About

Accessibility statement

We want everyone to be able to use Admit Path, including people who use a screen reader, a keyboard instead of a mouse, magnification, voice control or other assistive technology.

Last reviewed:

Looking for testing or classroom accommodations? This page is about using the Admit Path website itself. For extra time on tests, support in class and how to ask for them, see our guide to learning differences and disabilities.

Our goal

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. We don’t claim that every page meets every requirement: the work is ongoing, and this statement is based on our own testing, not an outside audit.

This statement covers the website at admitpath.org: the guides, the free tools, the assessment, sign-in and your account. It doesn’t cover our iPhone, iPad, Apple TV and Android apps, but you can report a problem in an app the same way (see Tell us about a problem).

What we’ve done

  • Contrast: we check text against a contrast ratio of at least 4.5:1, and graphics such as chart bars and timeline dots against at least 3:1, in both the light and dark themes, and we’ve fixed the places that fell short.
  • Light, dark and motion: the site follows your device’s light or dark setting. If your device is set to reduce motion, the site turns off its animations and transitions.
  • Keyboard: every page starts with a “Skip to content” link, and the link or control you’re on has a visible outline. Wide tables scroll sideways inside a box you can reach and scroll with the keyboard.
  • Focus in the tools: when something changes, focus goes where you need it. For example, the aid appeal letter builder moves focus to the list of problems to fix or to your finished letter, and My college list keeps focus on a school you move up or down.
  • Screen readers: each page has one main heading and headings in order, landmarks for the menu, the main content and the footer, labelled form fields, and links that say where they go. In the free tools, results that update as you type, saves and errors are announced. Charts and diagrams drawn as images have a text description, and table header cells are never empty.
  • Breadcrumbs: the trail at the top of each page (“Home / About / Accessibility statement” on this one) is a labelled navigation landmark that marks the page you’re on.
  • Not by colour alone: where colour carries meaning, such as a shortfall in the student budget or a finished step in your account, words or symbols say it too.
  • Small screens and zoom: pages are laid out to work 320 pixels wide without sideways scrolling, about the width of a small phone or of a laptop screen zoomed to 400%. Small controls, such as the checkboxes in the application checklists and the switches in account settings, are at least 24 by 24 pixels.
  • Signing in: there’s no password to remember. We email you a sign-in link, and on the website you can also type or paste the 6-digit code from the same email.

How we test

  • Automated checks on every change: our test suite runs on every proposed change before it goes live. Among other things, it fails if a page doesn’t have exactly one main heading or skips a heading level, if a link says only “Learn more” or “Click here”, if a table header cell is empty, if a breadcrumb isn’t a labelled list that marks the current page, or if key graphics fall below 3:1 contrast against their background in either theme. The tests for tools such as the aid appeal letter builder and the student budget check that every field has a label and that results are announced.
  • axe in a browser: we check pages and tools with axe-core, an open-source accessibility checker, in a headless browser (Chrome, and WebKit, the engine behind Safari), at phone and desktop widths and in the dark theme.
  • By hand: we try new pages and tools with the keyboard alone, at 320 pixels wide, and in both themes.

Known limitations

  • Documents on other websites: our guides link to their sources, such as Federal Student Aid, the Common App and the College Board, and some of those are PDF files. We don’t control how accessible they are. If one doesn’t work for you, tell us which one and what you needed from it.
  • Our apps: the iPhone, iPad, Apple TV and Android apps aren’t covered by this statement.
  • Our own testing: automated checkers find only some problems, and this statement isn’t the result of an outside audit. Reports from people who use assistive technology every day are the best way for us to find what we’ve missed.

Tell us about a problem

If something on the site is hard or impossible to use, please tell us:

It helps to include the page’s address, what you were trying to do, what happened, and the device, browser and any assistive technology you use (for example, VoiceOver on an iPhone, or NVDA with Firefox on Windows). You don’t need to tell us about any disability. Please don’t send sign-in codes or other sensitive documents by email.

A person on our team reads every report. Our support page has more ways to get help.