Zoom
Increase browser zoom or text size. Report any control that overlaps, clips or becomes unreachable.
Accessibility statement
Nanacam aims to make core information and controls understandable across common devices. This page describes practical options without claiming that every live-video flow is fully accessible.
One-on-one · free to start · leave anytime
Our approach
Accessibility is a continuing product responsibility
Nanacam’s public information pages use semantic headings, visible labels, readable contrast, responsive layouts and links that can be understood out of context. We test representative desktop and mobile widths and work to prevent horizontal overflow, clipped controls and text that depends only on color.
The live application is more complex than a document page. Camera permissions, real-time media, third-party browser behavior, gestures and timed states can create barriers. Support may differ by operating system, browser, assistive technology and whether a participant is in a call or reading guidance.
We do not describe Nanacam as conforming to a specific accessibility standard unless a complete, current audit supports that statement. The target is practical improvement informed by recognized guidance, user reports and repeatable testing.
Keyboard and focus
Use standard controls where available and report focus traps
Links and native buttons on Nanacam’s informational pages should be reachable by keyboard. A visible focus indicator should show the current location. On desktop, some application actions may also respond to common keys, but keyboard behavior can vary across media controls, dialogs and the live-call interface.
Use Tab and Shift+Tab to move, Enter or Space to activate the focused control and Escape to close a dialog when that control supports it. Do not rely on an undocumented shortcut during a safety-critical moment; keep the visible leave or close control available.
If focus disappears, cycles inside the wrong region or lands behind a dialog, note the page, action, browser and assistive technology. That detail is more useful than a general statement that the keyboard “did not work.”
Vision and display01 02 03 04
Browser zoom and operating-system display settings may improve readability
A wide desktop layout and a narrow phone layout do not place controls in exactly the same location. Orientation changes may also reorganize the interface. Finish a critical action, such as ending a call, before rotating the device when possible.
Contrast
Use device contrast or color-filter settings if helpful; meaning should not depend on color alone.
Motion
Enable reduced-motion preferences where your system offers them. Some inherited application animation may still remain.
Screen readers
Public content uses headings and labeled links, but complex live-media flows may contain incomplete announcements.
Hearing and speech
Live automatic captions are not currently promised as a Nanacam feature
Nanacam should not be your only communication method when accurate live captions or a text relay is essential. Some operating systems and browsers provide device-level captioning, transcription or audio-routing features, but availability, language coverage and accuracy belong to those products and may change.
Text messaging inside a product flow may help in some situations, but it is not a guaranteed real-time caption channel and may require account or call state. Agree on a communication method early rather than assuming the other participant can hear, speak or type continuously.
Never treat a speech difference, delayed response, lack of eye contact or use of assistive technology as evidence that a person is not interested or does not meet an age requirement. Ask a simple preference question and allow time for the answer.
Camera and movement
Participation should not depend on a particular posture or performance
A participant may need extra time to position a device, use a switch, change input settings or respond. Do not demand constant eye contact, a different camera angle, a room tour or proof of disability. The camera is a communication tool, not a test of physical behavior.
Browser permission dialogs are controlled partly by the browser and operating system. If camera or microphone access fails, check site permissions and device settings. A separate external camera, microphone, headset or mount may help, but Nanacam does not require expensive equipment for ordinary use.
Leave any interaction that mocks a disability, removes a reasonable communication choice or pressures you to reveal health information. Disability-related harassment belongs under the same community and reporting standards as other targeted abuse.
Tell us about a barrier
A reproducible report helps us separate content, browser and application issues
Contact support with the page URL, approximate time, device, operating system, browser and assistive technology. Explain what you tried, what you expected and what happened. If a screenshot is helpful, remove account, payment and third-party personal information before attaching it.
For an inaccessible safety control, say whether you could end, block or report the interaction and which alternative worked. Do not remain in an unsafe call to reproduce the problem. Immediate danger belongs with local emergency services.
Accessibility feedback is not limited to formal legal language. A clear description such as “keyboard focus moved behind the permission dialog in Safari” gives the team a concrete starting point. We may request more detail through the support thread but should never request your password or one-time code.
A useful accessibility statement says what works, what may not and how to report the gap.
Clear answers
Helpful answers
No. This page describes current practices and limitations; it does not claim complete conformance without a current full audit.
Your pace, your conversation
Contact support →Report the barrier, not private medical details
Tell us the task, technology and result so accessibility work can begin from a reproducible case.