Our commitment
VNC.com is intended for people with a wide range of abilities, devices, and ways of interacting with the web. We are committed to meeting Web Content Accessibility Guidelines (WCAG) 2.2 at level AA across shared templates and core user journeys.
Core journeys include finding educational content, comparing VNC options, creating and accessing an account, reading community discussions, posting and replying, and reporting a problem. Accessibility is considered in design, content, implementation, and review rather than treated as a one-time check.
What this means in practice
The shared site templates are designed to support:
- Keyboard navigation without requiring a mouse or touch input.
- A visible focus indicator that shows which control is active.
- Text and interface contrast ratios that meet WCAG 2.2 AA criteria.
- Alternative text for meaningful editorial images and empty alternative text for decorative images.
- Reduced-motion support when a visitor selects that preference in their operating system or browser.
- Pointer targets are commonly 24 by 24 CSS pixels or have adequate spacing.
Pages should use clear headings, descriptive links, labeled form controls, and meaningful status messages. Content should remain usable when text is enlarged or the viewport is narrow. Video or audio published by VNC.com should include the captions, transcripts, or descriptions needed for its format and purpose.
Browsers and assistive technology
VNC.com aims to work with current versions of major browsers and commonly used assistive technologies. Web standards provide the baseline, but combinations of browser, operating system, screen reader, voice control, zoom software, and personal settings can behave differently.
When reporting a problem, information about the page, browser, operating system, assistive technology, and the action you were trying to complete helps us reproduce the barrier. You do not need to disclose a disability or any information you would rather keep private.
Known limitations
Community-posted images may lack useful alternative text because members create that content. The posting experience should encourage authors to describe meaningful images, and moderators or editors may add context where practical, but immediate coverage cannot be guaranteed for every contribution.
Third-party embeds, downloads, and destination sites may not meet the same accessibility standard. Their controls and content are managed by their providers. Where an embed creates a barrier, we aim to provide a title, context, or a direct link when the template and source allow it.
These limitations do not reduce the WCAG 2.2 AA goal for VNC.com templates and core journeys. They identify areas that require continuing content guidance, vendor review, and testing.
Accessibility feedback
If you cannot access content or complete a task, email accessibility@vnc.com. Include the page URL, what you were trying to do, what happened, and your preferred way to receive a response. If you need the information in another format, describe the format that would work for you.
Accessibility feedback is used to identify, prioritize, and test improvements. Reports containing account, billing, or security-critical information should use the relevant official support channel rather than a public community post.
How this statement is reviewed
Material changes to accessibility support or known limitations will be reflected on this page.