PPsychology.com Learn

Accessibility

Last updated November 7, 2026.

Psychology.com Learn is meant to work for everyone, whatever you use to read, move and answer. We aim at WCAG 2.2 AA, the Web Content Accessibility Guidelines at level AA, and we do not claim more than that. This page says plainly what works today, what we test, where we know Learn still falls short, and where to write when something is out of reach.

What works

What we test

An automated browser suite drives Learn through onboarding, a lesson of every track, the results, Settings and every route, in Chromium, Firefox and WebKit, at a phone width of 390 pixels and a desktop width of 1280 pixels. It runs the axe accessibility rules on the screens it opens and fails on a violation, on any page error, and on a key that stops working. Since October 23, 2026 the same suite also reads two things the WCAG rules name and a scanner cannot see. With a reader's own text spacing set over ours (line height 1.5, a paragraph gap of two lines, letter spacing 0.12 em and word spacing 0.16 em) no box on the path, on any exercise, on the quit and result sheets, in Settings or on the Plus page may cut its text, and the page may not grow wider than the screen. At 200 percent zoom on a phone the Check or Continue bar must stay on the screen with its button where a finger lands, and no text may be cut. A second suite reads the generated markup without a browser: that every course picture carries alternative text and every decorative drawing is marked as such, and that the live regions, the key hints and the names of the controls are where the code says they are. Since October 23, 2026 one scenario also drives the text path out of a speaking question on a phone screen: Tab reaches Can't speak right now under the microphone, the S key presses it, the question is redrawn as a typed answer with the name of the idea as the answer, and the typed name scores. Since November 5, 2026 the suite also measures touch targets on a phone screen 390 pixels wide. Touch target sizes and the space between them are read on the path, on one exercise of every kind, on the quit and result sheets, and on the Practice page, the Groups tab, Today, Settings and the Plus page. Every button, link and field is measured. One smaller than 24 by 24 CSS pixels fails the suite by name, with the two exceptions WCAG 2.5.8 allows: a target that stands clear of every other target by its own 24 pixel circle, and a link inside a sentence. The reading proves itself on a planted pair of 16 pixel buttons before it reads a screen. Since November 5, 2026 the suite also reads the three column layout on screens 1024 pixels wide and wider. At 1024 by 768 pixels and again at 1280 by 800 it opens the path, an exercise, the result sheet, the profile, the Groups board and Settings. On each screen it scrolls every button, link and field into view and reads its box. The control must sit inside the viewport, and the page may not scroll sideways. The point at the center of the control must land on the control itself, so nothing is drawn over it. The left rail, the middle column and the Today column may not overlap. The same reading runs again in a browser that draws a classic scroll bar fifteen pixels wide, the width a desktop browser takes. That is where the layout is tightest. It proves itself on a planted block drawn over one tab before it reads a screen. Since November 6, 2026 the suite also times the motion. It reads every animation the browser is running on the path, when a sheet opens, and inside a lesson after a right and a wrong answer. It reads them again at the end of a lesson through the streak screen, and on Today when a reward opens. Each animation must end within half a second, its delay included. Only Pip's blink and bob and the pulse of the current lesson may repeat. Then the suite asks for reduced motion twice, through the device setting and through the Reduce motion switch in Settings, and reads the same screens. Under either, every animation may change opacity only, nothing flies across the screen, and every counter shows its final number at once. Since November 6, 2026 the suite also reads the answer box above a phone keyboard at four heights, not one. A phone keeps about 360 by 390, 375 by 420, 390 by 500 or 430 by 560 pixels once its keyboard is up. The browser is set to each in turn. At each height it focuses the four fields a keyboard opens. Those are the typed answer, the written answer, the typed fallback of a speaking question, and the sign-in code field. The field and its Check or Sign in button must sit inside the screen. The pinned bar may not cover the field, and the page may not scroll sideways. Since November 7, 2026 the second suite also reads the structure of every screen and sheet it draws. It names an id used twice, a control inside a button or a link, and a label with no field. It also names a nameless button or link, a reference to nothing on the page, and a picture with no alternative text. Both suites run before a change can go live.

Known limits

Our automated checks cover behavior, not appearance: neither can verify focus delivery with assistive technology or PDF appearance. Two of those gaps closed on October 23, 2026: text spacing and 200 percent zoom are now measured in a browser (see What we test), and the result sheet that ran off the top of a zoomed phone screen now scrolls inside the screen with its Continue button in view. A third closed on November 5, 2026: touch target size and the space between targets are measured on a phone screen, and the four small chips and the check boxes that reading listed were raised to 24 pixels. A fourth closed the same day. The three column layout on screens 1024 pixels wide and wider is read in a browser, every control in view and nothing drawn over it. The left rail began a few pixels off the left edge of a 1280 pixel window with a classic scroll bar, and now starts at the edge. A fifth closed on November 6, 2026. The length of every animation is now read in a browser on the path, in a lesson, at its end and on Today. The Reduce motion switch in Settings now stills exactly what the device setting stills. Before, the switch only made each movement shorter. A sixth closed the same day. The answer box and its button above a phone keyboard are now read in a browser at four heights, not one, and at every field a keyboard opens. No height left a field or a button covered. In plain words, these are the places where a barrier may stand that our tools cannot see:

We work through this list, and we would rather hear about a barrier than guess at one.

How to report a barrier

If something in Learn is out of reach or unclear with your keyboard, screen reader, magnifier, voice control or any other assistive technology, tell us. Email hello@psychology.com and say which screen you were on, what you were using and what you expected to happen. A screenshot or a recording helps, but a sentence is enough. You can also press H on any screen in Learn, or open Help in Settings, and write in the Report a problem box; that note reaches us with the screen name and the app build and nothing else, so write to the address above if you want an answer. We read every report, and we answer from the address you wrote from.

If you are in crisis in the United States, call or text 988. Elsewhere, findahelpline.com. Psychology.com Learn is an educational app, not a crisis service.

Privacy NoticeTerms of UseBack to Learn