Skip to main content
INK'D

Legal

Accessibility

Last updated April 15, 2026

INK'D is committed to making our platform usable by as many people as possible, including users with disabilities. Our design target is the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. We have not yet completed a third-party audit, and we are aware of areas that do not currently meet that target. This statement describes where we are today, the gaps we know about, and how to reach us.

Standards We Design Toward

  • Web Content Accessibility Guidelines (WCAG) 2.2, targeting Level AA.
  • The accessibility principles of Title III of the Americans with Disabilities Act (ADA).
  • Section 508 of the Rehabilitation Act, where applicable.

We describe these as design targets rather than current attestations. INK'D is in active development and we treat accessibility as an ongoing effort rather than a finished deliverable.

What We Do Today

  • Use semantic HTML with landmark regions, headings, and form labels.
  • Provide a skip-to-content link at the top of every page.
  • Maintain visible keyboard focus styles on interactive elements.
  • Label inputs, buttons, and controls with descriptive text and aria-* attributes where needed.
  • Avoid relying on color, shape, or position alone to convey meaning.
  • Provide alternative text for meaningful images and empty alt for decorative ones.
  • Honor prefers-reduced-motion for animated flows where feasible.

Known Limitations

INK'D is a work in progress. We want you to know about the specific gaps we are aware of:

  • Color contrast. Some secondary and helper text uses a muted gray that does not meet WCAG 2.2 AA contrast (4.5:1 for normal text). This affects form labels, eyebrow headings, and metadata across many pages. We are migrating to higher-contrast tokens.
  • Motion. Reduced-motion support is honored for the brief-creation flow but not uniformly across all animations.
  • Third-party embeds. Components from payment processors, map/address autocomplete, and analytics tools may not match our accessibility target. We work within what those vendors expose.
  • Formal testing. We have not yet commissioned an independent WCAG audit, and we do not currently maintain an automated accessibility test suite. Claims about specific assistive-technology combinations should not be read as conformance attestations.

Assistive Technologies

INK'D is built with standards-based HTML, so it should function with common assistive technologies including screen readers (VoiceOver, NVDA, JAWS), keyboard-only navigation, and browser zoom up to 200%. We do not guarantee defect-free behavior with every combination.

Report an Accessibility Issue

If you encounter a barrier or have a suggestion, please let us know. We take accessibility feedback seriously and will respond as quickly as we can. We are a small team, so response times vary.

When reporting an issue, please include the page URL, the assistive technology you were using, the browser and device, and a brief description of the problem so we can reproduce it.