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.
Research basis
Legal and standards benchmark
The W3C Web Content Accessibility Guidelines are the technical reference used for the site's accessibility work. U.S. Department of Justice ADA guidance is used as a practical compliance benchmark for web accessibility expectations.
The DOJ's 2024 Title II web rule specifically applies to state and local governments, not to Macro by Mark as a private solo-operated product, but WCAG 2.1 Level AA and DOJ guidance are still useful benchmarks for building a serious accessibility program.
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 and drag interactions, such as dragging a curve on a model graph or panning the concept map, 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 third-party content, or browser extensions are governed by their own accessibility implementations.
- Some simulators, early-release model pages, 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, 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, use our contact form.
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. Choose “Accessibility barrier” in the form so we can route your report.
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, 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.
主な参照先
このページの作成に使用した資料です。掲載によって法的助言になるものではありません。
- W3C WCAG 2 Level AA Conformance
Technical conformance reference used for Level AA accessibility posture.
- DOJ ADA Web Accessibility Guidance
U.S. Department of Justice guidance on making web content accessible to people with disabilities.
- DOJ 2024 Title II Web Rule Fact Sheet
Used as a benchmark for WCAG 2.1 Level AA expectations, while noting its government-entity scope.
- DOJ 2026 Interim Final Rule
Current DOJ update referenced for tracking federal accessibility-rule developments.
関連ページ
Macro by Mark の方針とサービスに関する追加情報です。
プライバシーポリシー
ブラウザ保存の使い方と、アカウントに保存した情報の保護について説明します。
Cookie ポリシー
必須 Cookie、任意の分析、同意の更新、Global Privacy Control の扱いについて。
プライバシー選択
エクスポート、訂正、削除、Cookie 管理、GPC、手動リクエストの手順。
サブプロセッサ
現在のベンダー、データ分類、地域メモ、機関審査の経路。
利用規約
利用ルール、助言ではないこと、知的財産の範囲、サービス保護について。
許容される利用
安全境界、自動化の制限、制裁対応、ソース利用ルール、執行手順。
返金ポリシー
サブスクリプションの解約、原則返金不可、試用移行の確認、サポート窓口。
契約
DPA、MSA、注文書、セキュリティ審査、保険、機関購入者の依頼経路。
著作権
著作権、帰属表示、ソース表記、削除申請、プロバイダー権利、DMCA 代理人の状況。
SOC 2 への道筋
現在の未認証状態、対応済みランブック、証拠ギャップ、購入者審査の経路。
公開ステータス
手動の障害連絡方針、監視するサービス領域、サポートとセキュリティ窓口。
法務変更履歴
法務、プライバシー、セキュリティ、信頼ポリシー更新の公開索引。
倫理とコンプライアンス
ソース透明性、非推奨表明、モデルの抑制、研究公正のルール。