Your text size, your contrast, your keyboard. Set them once. Satin applies them in every supported app.
Pre-launch · early access opens soon · Core accessibility is never paywalled · Not an accessibility certification
Atlas · Sprint 14
Today
Text size
Contrast
Spacing
Secondary text contrast in this mock: 3.2:1Text 100%
Illustrative view and example shortcuts. Click the list, then use the arrow keys or J and K.
Defaults suit an average that nobody is. Dense boards, faint grey text, tiny targets, unwanted animation, mouse-only controls, in every tool.
Text size. Scale Satin’s views up without breaking them, with text up to 2× in development. Long titles truncate cleanly instead of overlapping.
Contrast. In development: stronger text, borders and status colours, plus an icon beside each status word, so status is never colour alone.
Spacing. Comfortable, balanced or compact: larger targets, or more on screen. Your choice, in every supported app.
Less motion. In development: switch off animation in Satin’s views. Live updates still arrive, without moving as you read.
Keyboard first. Find, open and change your work without the mouse, with a visible focus ring.
Plain labels. Plain words for statuses and fields when jargon gets in the way, with meaning always kept.
In developmentSatin for People is in development and pre-launch; early access opens soon. Text up to 2×, Satin’s own contrast and motion controls, and the status icon are in development.
Keyboard-first control
Find it, open it, change it. Without reaching for the mouse.
With keyboard-first on, Satin’s views show their shortcuts and let you finish a task from the keyboard. Every change is read back from the source before Satin says it’s done.
- A visible focus ring on every interactive element.
- Your shortcuts travel with you between apps, via Interface DNA.
- The app’s own page is always one action away.
Example shortcuts. Every change is checked against the source before Satin says “Done”.
What Satin is, and what it isn’t. Accessibility claims should be exact. These are ours.
What Satin does
- Applies your text size, spacing and keyboard settings in its views of supported apps, with its own contrast and motion controls in development.
- Builds those views from its own components, which target WCAG 2.2 AA, with keyboard support and screen-reader labels.
- Keeps each app’s own page one click away, so what works there still works.
- Never charges for core accessibility controls, on any plan.
What Satin doesn’t do
- It is not an accessibility-compliance certification, and using it doesn’t make any product compliant.
- It doesn’t replace a product’s own accessibility work, which stays with its team.
- It can’t fix every problem in an app, and never claims a browser layer alone guarantees accessibility.
- It doesn’t touch pages it doesn’t support. There, you see the original.
Built on good work that came before. Browser settings, GPII and Morphic carry your choices. OwnUX takes them inside each app.
- For Satin’s own components
- WCAG 2.2 AAFor Satin’s own componentsA design target, not a certification
- For core accessibility controls
- ₹0 · $0For core accessibility controlsNever behind a paywall, on any plan
- Back to the app’s own page
- 1 clickBack to the app’s own pageOn every Satin view
- The first supported app
- Jira CloudThe first supported appLinear next
PlannedFamiliar mode will apply settings such as contrast, spacing and keyboard shortcuts to an app’s own page, not just Satin’s views. It’s planned for a later phase.
PlannedFor product teams: OwnUX conformance level L3 will include automated accessibility checks of rendered surfaces. It adds to a product’s own accessibility testing and never replaces it.
Questions about accessibility, answered plainly.
No. Satin is not an accessibility-compliance certification, and using it doesn’t make any product compliant with any standard or law. It gives you more control over how supported apps look and work.