Accessibility
Netrix should be understandable and usable with different ways of navigating and reading.
Netrix uses semantic HTML, keyboard-accessible controls, visible focus, skip navigation, responsive layouts, text that does not rely on color alone, and automated axe testing on public and signed-in pages. Automated checks help find issues; they do not certify conformance.
- Evidence
- 01
- Decision
- 02
- Action
- 03
- Proof
- 04
How the work moves
Observed100% Reviewed78% Applied52% Verified48%What to look for
Get the answer without losing sight of where it came from.
Accessible components
Shared components include accessible names, written statuses, associated errors, sensible heading order, and touch-sized controls.
Several kinds of testing
Request, browser, visual, responsive, and axe checks cover core screens in both color themes.
Tell us when something gets in the way
Email [email protected] with the URL, task, device, browser, and assistive technology when relevant. A company name is not required.
How Netrix handles it
Look past the promise and see what the product actually does.
- 01Accessible components
- Shared components include accessible names, written statuses, associated errors, sensible heading order, and touch-sized controls.
- 02Several kinds of testing
- Request, browser, visual, responsive, and axe checks cover core screens in both color themes.
- 03Tell us when something gets in the way
- Email [email protected] with the URL, task, device, browser, and assistive technology when relevant. A company name is not required.
From finding to follow-up
See where the work stands—and what still needs to happen.
- 01Found
Netrix records the page and the issue it found.
- 02Reviewed
Someone checks the finding in context.
- 03Approved
The right person chooses what should change.
- 04Applied
A supported connection accepts the change.
- 05Checked
Netrix reads the public page again.
- 06Shared
The report summarizes the audit and fixes currently marked applied.
A few things worth knowing
Netrix can prepare the work. Your team still makes the call.
- 01Nothing publishes itself
AI drafts and supported SEO changes wait for an authorized person to act.
- 02A write is not proof
Netrix records when a provider accepts a change, then checks the public page separately. If it cannot read the page, the result stays unknown.
- 03Limits belong in the open
When a feature depends on another provider or stops short of a complete workflow, the page should say so.
Keep exploring
More on this part of the work
Security
Security starts with limiting who can reach an account, a credential, or a live site.
Learn how Netrix separates accounts, protects credentials, authenticates connections, gates site changes, and secures production traffic.
Data protection
To protect data well, you first need to know where it lives.
See what Netrix stores, how account data and credentials are separated, how traffic is protected, and what deletion does not reach.
Retention
Some records expire automatically. Others remain until the account or an operator removes them.
Review how long reports, audit history, crawl files, logs, and connection records remain, and what account deletion removes.
See how it fits your team