Company · Corporate profile
The MIRENA visual system uses contrast, hierarchy, and restraint to make complex work readable.
The palette and type system distinguish page background, reading surfaces, controls, evidence, warnings, and status without relying on colour alone.
Verified facts and boundaries.
These fields identify the entity, product, document, or operational boundary without turning related parties into the same entity.
Core palette.
The dark page system provides continuity across product, company, trust, and governance surfaces. Legal documents use a light reading sheet inside the same shell to support long-form reading and printing.
| Token | Hex | Primary use | Restriction |
|---|---|---|---|
| Page | #020B14 | Site background and deep navigation | Do not use for body copy |
| Panel | #071D2D | Cards, registers, navigation surfaces | Requires light text |
| Text | #EEF7FF | Primary text on dark backgrounds | Do not place on light surfaces |
| Cyan | #68E1EF | Primary focus, active routes, brand mark | Not a body-text default |
| Mint | #8FE1B5 | Positive or secondary accent | Do not use as the only success cue |
| Yellow | #FFD56F | Attention, focus, warning support | Check text contrast before use |
| Coral | #FF9F87 | Risk or exception support | Do not imply legal severity by colour alone |
| Violet | #B58CF3 | Entity, product, or supporting accent | Use sparingly |
Typography and hierarchy.
The digital system uses a modern sans-serif stack for body text, navigation, headings, tables, and controls. A system stack is preferred so pages remain fast, readable, and resilient when a custom font is unavailable.
- Page title: large, restrained weight, tight tracking, short measure
- Section heading: clear hierarchy with generous spacing
- Body text: at least 16 CSS pixels with comfortable line height
- Tables and metadata: smaller text only when contrast and spacing remain adequate
- Code and identifiers: monospaced stack for technical material
- All-caps labels: limited to short navigational or status labels
Contrast and non-colour cues.
Colour does not carry a decision alone. Status, risk, evidence, and approval states also use text labels, borders, icons, position, or shape.
Text and interactive controls should be tested against WCAG 2.2 contrast and focus requirements. A brand colour is not automatically an accessible text colour.
Reading surfaces.
Corporate, product, and trust pages can use dark panels for short structured content. Legal agreements, policies, and long governance documents use light paper surfaces with dark text, wider line spacing, printable headings, and stable clause numbering.
Tables require visible headers, clear row relationships, horizontal overflow on small screens, and a non-visual text equivalent when the table is not sufficient by itself.
Responsive and print use.
Heading scale, grid columns, navigation, tables, and metadata must adapt without hiding content or changing the legal or operational meaning.
- Do not remove evidence, limitations, or policy clauses on mobile
- Do not shrink body text to preserve a desktop grid
- Allow tables to scroll or convert to labelled stacks
- Hide navigation and decorative elements in print
- Keep document titles, clause numbers, contacts, and version information printable
Governance.
New tokens, fonts, weights, gradients, and visual statuses should be added only when the existing system cannot express the required meaning. Changes must be checked across product, legal, trust, company, mobile, and print surfaces.
Check the controlling first-party and official sources.
These routes support the current public statement. External platform and legal sources remain subject to their own updates.
MIRENA design theme
Current first-party product visual language.
WCAG 2.2
W3C accessibility guidance for contrast, focus, and readable content.
About Semantec SEO
Current company and product identity.
Move to the page that owns the next question.
Each route has a separate job so company, product, trust, legal, and compliance information does not collapse into one promotional page.
Owned route
Brand Hub
Naming, attribution, and permissions.
Open route →
Owned route
Logo usage
Mark selection, clear space, scale, and contrast.
Open route →
Owned route
Accessibility
Accessibility target, testing, feedback, and limitations.
Open route →
Owned route
Press kit
Approved media assets and descriptions.
Open route →
Owned route
Editorial standards
Readable copy, headings, tables, and disclosure.
Open route →
Owned route
Contact
Brand and accessibility questions.
Open route →