Accessibility Statement

We want Obrasken usable by as many people as possible, and we would rather tell you where it falls short than imply it doesn't.

Obrasken is a visual creative tool, which makes accessibility harder and more important rather than less relevant. We design for keyboard use, screen readers, reduced motion, and low-vision needs from the start, and we treat accessibility defects as ordinary bugs rather than enhancement requests.

Partially conformant with WCAG 2.2 level AA. Self-assessed, not independently audited.

Standard

Web Content Accessibility Guidelines (WCAG) 2.2, level AA

Status

Partially conformant — most of the platform meets the standard, and specific areas do not yet

Assessment method

Internal self-evaluation: keyboard-only walkthroughs, screen-reader spot checks, automated contrast and semantics checks, and reduced-motion emulation

Independent audit

Not yet carried out

Last reviewed

2026-07-29

• Keyboard navigation throughout the account, billing, settings, notification, and content-viewing flows, with visible focus indicators on every interactive control.
• Semantic HTML, landmark regions, and labelled form controls, with errors linked to their fields and announced to screen readers.
• Colour contrast targeted at WCAG AA for body text and interface controls; colour is never the only way information is conveyed.
• Full support for the operating system's reduced-motion preference — scroll effects, parallax, and ambient animation are disabled rather than merely shortened.
• Heavy visual effects such as glass blur and animated backgrounds have simplified fallbacks and never block reading or operation.
• Respect for browser zoom and text resizing up to 200% without loss of content or function.
• Light and dark themes, both meeting the same contrast targets.

Specific gaps, named. We are not going to describe these vaguely.

We aim to support current versions of major browsers (Chrome, Edge, Safari, Firefox) with the screen readers commonly paired with them — NVDA and Narrator on Windows, VoiceOver on macOS and iOS, TalkBack on Android. We test most often with recent Chrome and Edge, so please tell us if something behaves differently in your setup.

Obrasken requires JavaScript. We do not currently offer a non-JavaScript fallback.

If part of the product is unusable for you, we will help you get the result another way.

If an accessibility barrier prevents you from completing something on Obrasken — including anything in the drawing canvas or design workspace — email support@obrasken.com and describe what you are trying to achieve. We will find another route, which may include doing it with you, providing the output directly, or arranging a different way to make the same request.

There is no charge for this, and it does not consume your credits beyond the normal cost of the generation itself.

Where to write

support@obrasken.com, or the in-app Support form

What helps

The page or URL, what you were trying to do, your browser and assistive technology, and what happened instead

Acknowledgement

Within 5 business days

Substantive response

Within 15 business days, including a fix or a timeline

Accessibility reports are triaged as defects. Barriers that block a core task — signing in, paying, exporting, or deleting your data — are treated as high priority.

If you are not satisfied with our response, reply to the same thread asking for escalation and it will be reviewed by the person responsible for the product rather than closed. If you would still rather raise it externally, you may contact the accessibility or human-rights body where you live — in Ontario, the Ontario Human Rights Commission; elsewhere in Canada, your provincial equivalent or the Canadian Human Rights Commission.

For transparency about what does and does not legally bind us: Obrasken is based in Ontario, where the Information and Communications Standards under the Accessibility for Ontarians with Disabilities Act (AODA) require WCAG conformance for organisations at or above a headcount threshold we are well below. We work to WCAG 2.2 AA because it is the right standard for the product, not because we are currently compelled to.