Accessibility

Accessibility Statement

The current accessibility posture for Macro by Mark: WCAG target, DOJ/W3C research basis, supported patterns, known gaps in charts and complex tools, testing approach, remediation priorities, and barrier reporting.

Effective
May 13, 2026
Last reviewed
May 13, 2026
Target
WCAG 2.2 Level AA for core routes
VPAT/ACR
Not published today
Barrier reports
accessibility@macrobymark.com

Operational policy text for Macro by Mark. Not a substitute for advice from counsel.

Access goal

Commitment

Macro by Mark is intended to be usable by as many people as practical across desktop and mobile browsers, keyboard navigation, assistive technology, zoom, reduced-motion preferences, and varied contrast needs. Accessibility is treated as a product-quality requirement, not only a legal page.

The current working target is WCAG 2.2 Level AA for core public pages, account flows, legal pages, and high-use product navigation. Older work may have been checked against WCAG 2.1 Level AA, but this statement is not a certification that every page or third-party flow fully conforms.

Implemented practices

Current support

The product is designed to support:

  • Semantic headings, landmarks, links, and form labels across public pages and account surfaces.
  • Keyboard-focusable navigation, buttons, controls, tabs, inputs, menus, and route links.
  • Visible focus states, readable type sizes, responsive layouts, and reduced reliance on hover-only interactions.
  • Color contrast checks for primary text and controls, especially in the newer account, admin, and trust-page surfaces.
  • Accessible metadata and structured page titles for major routes.

Current gaps

Known limitations

Macro by Mark contains complex economic visualizations and tools that need ongoing accessibility work. Current risk areas include:

  • Charts, maps, SVG/canvas visuals, DSGE diagrams, and model graphs may need stronger text alternatives or data-table equivalents.
  • Large data tables, nested dashboards, watchlist tools, and drag-heavy workflows may need more keyboard and screen-reader refinement.
  • Older pages may still use legacy layouts or contrast choices that predate the current design system.
  • Third-party surfaces such as Stripe Checkout, Google sign-in, embedded provider content, or browser extensions are governed by their own accessibility implementations.
  • Some experimental labs, simulators, beta model routes, and visual tests may not yet meet the same accessibility bar as production account and legal pages.

Verification

Testing approach

Accessibility review is handled through a mix of code review, keyboard checks, responsive viewport checks, automated tests where available, visual regression tests, browser inspection, and targeted review of account, admin, paywall, dashboard, indicator, model, and legal routes.

Automated tests are useful, but they do not prove full accessibility. Manual keyboard, screen-reader, zoom, contrast, and user-feedback checks remain necessary for complex product workflows.

Macro by Mark does not publish a VPAT or Accessibility Conformance Report today. If an institutional buyer requires one, it should be handled as a separate review rather than inferred from this public statement.

Support path

How to report a barrier

If you encounter a missing label, keyboard trap, unreadable contrast, inaccessible chart, broken focus order, screen-reader issue, motion problem, or another barrier that prevents use of the site, contact accessibility@macrobymark.com.

Include the page URL, browser/device, assistive technology if relevant, what you were trying to do, what happened, and the format or accommodation that would help. If that mailbox is not available, use privacy@macrobymark.com.

Remediation

Accessibility priorities

Remediation priority is based on severity, user impact, route importance, and whether the issue blocks account access, billing, privacy choices, admin workflows, dashboard use, indicator access, or core learning pages.

Highest priority issues include keyboard traps, inaccessible sign-in or account-management flows, broken billing or cancellation access, unreadable legal pages, missing labels on forms, and charts or data tables that cannot be interpreted at all without vision.

Statement maintenance

Updates

This statement may be updated as the product, design system, accessibility testing, and applicable standards evolve. The effective date will be updated when material changes are made.

Primary references

Sources that informed the current posture. Included for transparency; this doesn't turn the page into legal advice.

Related policies

The other pages that round out the trust posture for Macro by Mark.