ZoikoNex
Platform Safety & Trust

Acceptable use that protects serious telecom operators.

ZoikoNex is built for responsible telecom monetization, governed API access, secure integrations, and trusted customer operations. Our Acceptable Use rules define the conduct, content, automation, API activity, and telecom practices that are not permitted on the platform.

Accessibility is an enterprise quality signal.

Accessible design improves reach, usability, procurement readiness, customer satisfaction, adoption,
and support efficiency. For a telecom BSS platform, it also helps operational teams act faster and more
accurately inside complex workflows.

Buyer confidence
Shows enterprise and public-sector buyers that accessibility is part of the product governance model.
User productivity
Improves navigation, readability, forms, dashboards, documentation, and task completion for more users.
Retention & less support
Reduces avoidable friction, training burden, abandoned workflows, and accessibility-related escalations.
Platform quality
Reinforces UX discipline: semantic structure, keyboard usability, predictable patterns, and clearer copy.

What ZoikoNex commits to building toward.

Specific, operational, and reviewable commitments — not claims of full conformance.

Perceivable information
Text, labels, states, errors, charts, tables, documents, and controls presented so people and assistive technologies can understand them.
Operable interfaces
Core journeys reachable by keyboard, with visible focus, logical tab order, sufficient target sizes, and reduced-motion options.
Understandable content
Plain language, clear headings, predictable navigation, meaningful buttons, helpful errors, and readable documentation.
Robust implementation
Semantic HTML, ARIA only where appropriate, resilient components, automated checks, manual testing, and assistive-technology review.
Continuous remediation
Issues are triaged, owned, prioritized, tracked, tested, and closed through product governance — not left as one-off tickets.

Designed around recognized accessibility principles.

Our public website and digital experiences are designed with WCAG 2.2 principles in mind — perceivable, operable, understandable, and robust — and we describe our standing carefully.

WCAG 2.2
Design principles
We design with the four WCAG 2.2 principles in mind and target Level AA alignment across key surfaces.
EN 301 549
EU procurement
Relevant for European and public-sector ICT procurement, including websites, documents, and digital services.
ADA Title II
US public sector
References WCAG 2.1 AA for state and local government. We avoid implying it governs every private scenario without legal review.
How we phrase it
“Designed with WCAG principles in mind”
“Targeting WCAG 2.2 AA alignment”
“We continue to improve, and we welcome feedback”
What we don't claim
Fully accessible or guaranteed accessible
WCAG certified
ADA compliant / legally compliant (unless independently verified)

Accessibility across every critical surface.

A broad commitment turned into specifics buyers and users can check.

Public website
Semantic headings & skip links
Readable contrast & reduced motion
Descriptive CTAs & accessible forms
Platform interface
Keyboard controls & visible focus
Non-color-only status indicators
Accessible modals, tables & charts
Documentation
Structured headings & search
Code samples with copy buttons
Descriptive links & reviewed downloads
API & Developer Portal
Keyboard-operable API explorer
No color-only method labels
Semantic error guidance
Forms & support
Clear labels & inline validation
Accessible error summaries
No inaccessible CAPTCHA dependency
Careers
Accessible listings & role filters
Inclusive application path
Accommodation request routing

A clear path for accessibility feedback.

We don't pretend there will never be issues. Here's how a report is handled — from submission to follow-up.

01
Report
Submit via the accessible form, email, or support route.
02
Triage
Classified by severity, surface, journey, and assistive tech.
03
Ownership
A product, design, engineering, or content owner is assigned.
04
Remediation
Fix planned, tested, and released through change control.
05
Follow-up
Where contact is given, you receive an update.
Optional
*

Required so we can follow up.

*
Optional
Optional
*
Optional
Optional
Choose FileNo file chosen

Screenshot or recording (optional).

I agree that ZoikoNex may contact me about this report and process my details per the Privacy Notice.

What happens next

Reports become tracked tickets with severity, surface, and assistive-technology context — not one-off emails.

01Triaged by severity, surface, and affected journey.
02Assigned an accountable owner in product or content.
03Fixed through normal change control, then tested.
04You receive an update where contact details are provided.

Support for enterprise & public-sector review.

Buyers may need accessibility statements, ACR/VPAT-style documentation, policy summaries, and evidence of our design and remediation processes.

We route these requests through the Trust Center or enterprise sales, with gated-document logic where appropriate, to the right review owners across Sales Operations, Product Governance, Legal/Compliance, and Security/Trust.

VPAT/ACR documents, audit results, and remediation details are shared under review — not published publicly.

Accessibility

Help us make ZoikoNex easier for everyone to use.

Whether you're evaluating ZoikoNex, using our documentation, applying for a role, integrating with our APIs, or reporting an access barrier, we want the experience to be clear, usable, and respectful.

Trust CenterPrivacy PolicySecurityComplianceDocumentationContact