Target
WCAG 2.1 Level AA
Our aim is an experience that works well for keyboard users, screen-reader users, and people who need strong visual clarity.
Linket Connect
Legal
Accessibility statement
We want Linket to be understandable, navigable, and usable for people with a wide range of access needs and assistive technologies.
What This Page Covers
Accessibility work at Linket is centered on practical usability: keyboard access, readable interfaces, clear form behavior, and predictable page structure. This statement explains what we aim for and how to report problems when the experience falls short.
Support
accessibility@linketconnect.com
If something is hard to use, send the page URL and a short description so we can investigate the exact issue.
Approach
Iterative review and improvement
Accessibility is part of ongoing product work, not a one-time pass before launch.
What we aim for
These principles shape how we evaluate accessibility across the site and product.
Navigation
Keyboard-first interaction
Interactive elements should be reachable, understandable, and operable without requiring a mouse or touch interaction.
Structure
Clear headings and landmarks
Pages should expose a predictable structure so assistive technologies can move through content without confusion.
Readability
Contrast and content clarity
Copy, controls, and status cues should stay readable and understandable across different devices and visual needs.
What this means in practice
A clean interface only works if it stays usable for the people interacting with it.
- Visible focus states help people understand where they are on the page as they tab through the interface.
- Labels, helper text, and inline error cues are used to make forms easier to complete and correct.
- Meaningful images and icons should include text alternatives when they convey information beyond decoration.
- Consistent button language, spacing, and section hierarchy reduce cognitive load across the product.
Review and improvement
Accessibility quality is maintained by checking important tasks repeatedly as the product evolves.
- We review accessibility during normal design and engineering work rather than treating it as a separate afterthought.
- When issues are reported, we prioritize the fixes that block core tasks such as signing in, navigating, saving contact information, or submitting forms.
- As the product changes, we re-check important flows because accessibility regressions often appear during routine feature work.
Feedback and support
Support
Need help using Linket?
Email accessibility@linketconnect.com with the page URL, the device or browser you were using, and a short description of what made the experience difficult.
Email accessibility