Last updated: 4 November 2026
Calmvivo should be usable by anyone who wants a name. This page says where the site stands on accessibility, what we have tested, and what to do when something does not work.
It is a statement of practice rather than a certificate, and it is reviewed on a schedule.
Accessibility Commitment
We want calmvivo.com to work for people using a screen reader, a keyboard, a switch device or a magnifier, and for anyone reading on a small screen in bright light.
Accessibility is a requirement in the build, not a pass at the end. New features are tested with assistive tools before they ship, and barriers found by visitors get fixed rather than logged.
The commitment shapes what we build next as much as how we build it; a filter that cannot be reached by keyboard does not ship.
Compliance Standards
The site targets WCAG 2.1 Level AA. That means content should be perceivable, operable, understandable and robust, and we check against those four headings when something changes.
Markup is semantic, landmarks mark the regions of each page, and contrast ratios meet the AA thresholds in both the light and dark interfaces. Focus indicators are visible rather than suppressed.
We run the checks ourselves and act on what they report; no third-party certification is claimed on this page.
Accessible Features
Images carry alternative text that says what the image shows rather than repeating the caption. Text can be enlarged to two hundred percent without the layout breaking, and the interface reflows instead of scrolling sideways on a narrow screen.
- A high-contrast mode can be switched on without leaving the page.
- Form fields have visible labels, and errors are announced as soon as they appear.
- Generated results are announced by screen readers instead of arriving silently.
A skip link sits at the top of every page so a keyboard user can jump past the navigation into the content.
Keyboard Navigation
Every control can be reached with Tab, activated with Enter or Space, and dismissed with Escape. The order follows the page rather than the source file, so it matches what you see.
There are no keyboard traps. We test with NVDA and VoiceOver as a matter of routine, because a focus ring that disappears is a bug and not a style choice.
Shortcuts, where they exist, are documented and can be turned off so they do not collide with a screen reader’s own keys.
Screen Reader Support
Headings run in order, with one H1 per page and no levels skipped, so the document outline is a usable table of contents. Lists are real lists, tables carry headers, and dynamic results are pushed into a live region as they arrive.
Nothing on the site is timed. Announcements wait for a pause rather than interrupting mid-sentence, and the layout has been checked in the major browsers paired with the main readers.
- Pronunciations are supplied for names that a synthesiser would mangle.
- Results update in place, so a reader is not sent back to the top of the page.
Trademark Notice
Names come from algorithms with no human curation at any step. The platform searches no trademark database, public or private, while generating, so nothing it returns has been checked for conflict of any kind.
No availability or registrability is verified for any generated name, and no warranty of uniqueness is offered. Independent legal due diligence before commercial use is the user’s own responsibility, not ours.
This statement sits alongside our internal data protocols, which explain what the tools do with what you type.
Governing Law
This statement is made under the law of California, United States. Courts in California have exclusive jurisdiction over any accessibility claim, and class action waivers apply as the statutes allow.
No choice-of-law rule moves it elsewhere. Using the site consents to personal jurisdiction in California without objection to venue, and severability keeps the rest standing if a clause falls.
Editorial Review
Our editorial team reviews this statement on a quarterly cycle and whenever a significant change ships. Each pass checks the claims against what the site actually does, not against what the roadmap intends.
Revisions are dated here, and the log of what changed is kept so a reader can tell how current the statement is.
Contact Us
Send accessibility feedback through the Contact Us page or to [email protected]. We answer within two business days and say what we plan to do.
This page describes current practice, not an aspiration.