Legal

Accessibility Statement

Last updated: September 16, 2026

The short version. We want everyone to be able to take the assessment, read their report, and use every tool here. Our target is WCAG 2.2 Level AA. The site is partially conformant: a sampled review in September 2026 fixed most of what it found, and the gaps that remain are listed below, with what is untested. If you hit a barrier, email accessibility@wiredtype.com and we will answer within five business days.

Contents

  1. Our standard
  2. What we do
  3. The September 2026 review: what was checked and fixed
  4. Known gaps and untested areas
  5. Tell us about a barrier
  6. Technical details
  7. Formal complaints

1. Our standard

The Web Content Accessibility Guidelines (WCAG) define how to make web content usable by people with disabilities, at three levels: A, AA, and AAA. WiredType's target is WCAG 2.2 Level AA. As of this statement the site is partially conformant: the pages and flows that were reviewed meet most of the standard, some do not yet, and parts of the site have not been reviewed at all. We do not claim site-wide conformance. Sections 3 and 4 say exactly what was checked, what was fixed, and what is still open.

2. What we do

  • Every page has a skip link to the main content, a visible focus style, and headings in order.
  • Text can be resized to 200 percent without loss of content on the pages reviewed, and the account page was fixed to fit at 320 pixels wide.
  • DISC types are never shown by color alone. We check contrast on new work; a contrast miss found in the September 2026 re-review is in the fix queue (section 4).
  • Reports include a listen button that reads each section aloud, and the reader offers a dyslexia-friendly font.
  • Automated checks (Lighthouse accessibility audits) run against every deploy, and every fix in section 3 was re-checked with a keyboard on the deploy before it shipped.

3. The September 2026 review: what was checked and fixed

On September 16, 2026 an outside accessibility specialist reviewed a sample of the site (the home page and free assessment, the full assessment, the D, I, S and C reports, the account page, the Type Profiler game, and a sample of courses and exercises) with a keyboard and automated tools, and re-checked the fixes on the staged deploy the same day. The sample did not cover every page, every exercise, or every account state, and no native screen reader (VoiceOver, NVDA, TalkBack) was run; those are listed as untested in section 4.

Fixed and re-verified in that review:

  • Ranking a response with the keyboard keeps focus on the response and announces its rank (free and full assessments).
  • Report cards that flip and the edition disclosure buttons open with the keyboard and keep focus.
  • Quiz and scenario answers, and course sorting exercises, work without a pointer (sampled).
  • The report edition dialog contains focus and returns it when it closes; checkout, retake and team dialogs were changed the same way in code.
  • The radar chart has a data table of the same numbers and keyboard access to each point; the Type Profiler accepts and confirms a keyboard guess.
  • Report and share controls announce their selected state, tool labels are connected to their inputs, compatibility results and "copied" notices are announced, and the bypass links work.

4. Known gaps and untested areas

These are the barriers we know about today. Each is in the fix queue; the changelog records each one as it closes.

  • Free assessment timing. With a pointer, the free assessment still advances to the next question on its own after a short pause. Keyboard users get a manual "Next" step automatically, and a checkbox turns automatic advance off for everyone, but manual advance is not yet the default.
  • PDF downloads. Stored report PDFs are not tagged for screen readers. The same content is available as the web report; tagged PDFs are planned.
  • Data Lab charts. Beyond the radar chart, the Data Lab visualizations do not yet have text equivalents.
  • Light theme in reports. Some report content does not switch when the light theme is requested.
  • Contrast. One measured contrast miss from the re-review is being fixed; other pages have not all been measured.
  • Games and exercises not in the sample. DISC Dash and other drag-based games and exercises outside the sampled set may still require a pointer.
  • Untested: native screen readers (VoiceOver, NVDA, TalkBack), 400 percent zoom, and the team admin, team member and site admin pages, which were reviewed from source only.

5. Tell us about a barrier

Email accessibility@wiredtype.com with the page address, what you were trying to do, and the browser and assistive technology you use. We answer within five business days, tell you what we found, and give you the content another way in the meantime if we can (for example, your report as plain text). You can also use the feedback button at the bottom of any page.

6. Technical details

WiredType relies on HTML, CSS, JavaScript, WAI-ARIA, and SVG. It is built to work with current versions of Chrome, Safari, Firefox, and Edge on desktop and phone. The site does not require any plug-in. Assessment approach: a sampled keyboard and automated review against WCAG 2.2 AA by an outside specialist on September 16, 2026, with fixes re-verified on the deploy the same day; automated Lighthouse audits on every deploy; native screen-reader testing not yet done.

7. Formal complaints

If you are not satisfied with our answer, you can contact the New Jersey Division on Civil Rights (New Jersey Law Against Discrimination) or the U.S. Department of Justice's ADA information line (800-514-0301). We would rather hear from you first and fix it.