Skip to main content

Accessibility

We want everyone to be able to read and use the UltraCart documentation, whatever device or assistive technology they rely on. This page explains what we aim for, where we stand today, and how to tell us when something falls short.

Our target​

This site targets WCAG 2.2 Level AA. That standard covers things like readable color contrast, full keyboard operation, text that reflows when you zoom, and content that doesn't depend on color or motion alone to make sense.

What we do​

  • Keyboard first. Every link, button, menu, and search control works without a mouse. A "Skip to main content" link is the first thing you reach with the Tab key, and focused elements show a visible outline.
  • Contrast. Text and interactive elements are checked against the AA contrast ratios in both the light and dark themes.
  • Reduced motion. If your system is set to reduce motion, we honor it: the animated background on the home pages renders as a single still frame, and hover and scroll animations are turned off.
  • Higher contrast. If your system asks for more contrast, borders firm up and secondary text darkens toward the main text color.
  • Structure. Pages use real headings, lists, and landmarks so screen readers can navigate by structure, and text resizes and reflows instead of overflowing.

No accessibility overlay​

We do not use an accessibility overlay or a "one-click accessibility" widget. Those tools often get in the way of the assistive technology you already use. We build accessibility into the site itself instead.

Known limitations​

This site is mid-migration. We are moving roughly 1,600 pages over from our previous documentation system, and some imported pages have not been through a full accessibility review yet. On those pages you may still find:

  • Images that are missing descriptive alternative text.
  • Color contrast that has not yet been corrected.
  • Tables or headings that need restructuring.

We are working through these as part of the migration. The newer, hand-built pages, the home pages, and the generated API reference meet our AA target.

Tell us about a problem​

If you hit a barrier anywhere in these docs, we want to fix it. Please report an issue and include the page address and a short description of what went wrong. Mention that it's an accessibility issue so it reaches the right people quickly.

We review accessibility reports alongside our other documentation issues and will let you know when a fix ships.