Accessibility Statement
Last updated: September 5, 2026
VisualDocs is dedicated to ensuring our website and tools are accessible to all users, including those with disabilities. This statement describes our accessibility standards, current features, and how to report issues.
Our Standards
Our Commitment to Accessibility
VisualDocs is committed to making our website and tools accessible to everyone, including people with disabilities. We believe that document and image tools should be usable by all, regardless of ability, device, or assistive technology. We follow the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA as our baseline standard and continuously work to exceed it.
Visual Accessibility
We design VisualDocs with visual accessibility in mind, ensuring that users with low vision, color blindness, and other visual impairments can navigate and use our tools effectively.
- •High contrast ratios between text and background colors that meet WCAG AA standards
- •A dark mode that reduces eye strain and improves readability in low-light environments
- •Text can be resized up to 200% without loss of content or functionality
- •Color is never the sole indicator of meaning — we use icons, text labels, and patterns alongside color
- •All interactive elements have visible focus states for keyboard navigation
Keyboard Navigation
Every feature on VisualDocs can be operated using a keyboard alone. Users who cannot use a mouse or prefer keyboard navigation can access all tools and content without barriers.
- •Logical tab order that follows the visual layout of the page
- •All interactive elements are reachable and operable via Tab, Enter, Space, and arrow keys
- •Skip-to-content links allow keyboard users to bypass repetitive navigation menus
- •No keyboard traps — users can always move focus away from any component
- •Custom components like file upload areas and drag-and-drop zones have keyboard alternatives
Screen Reader Support
VisualDocs is built with semantic HTML and ARIA attributes to ensure compatibility with popular screen readers including NVDA, JAWS, VoiceOver, and TalkBack.
- •All images and icons have descriptive alt text or aria-label attributes
- •Form fields have associated label elements and clear error messaging
- •Dynamic content changes are announced via aria-live regions
- •Page structure uses proper heading hierarchy (h1 through h6) for navigation
- •Landmark roles (banner, main, footer, navigation) help screen reader users orient themselves
Mobile and Responsive Design
VisualDocs is fully responsive and works on devices of all sizes, from phones to tablets to desktop computers. Our tools are designed to be touch-friendly with adequately sized tap targets and intuitive gestures.
- •Responsive layouts that adapt to screen sizes from 320px to 2560px and beyond
- •Touch targets meet the minimum 44x44 pixel recommendation for mobile accessibility
- •No horizontal scrolling required at any viewport width
- •All tools and features are available on mobile, not just desktop
Technical Standards
We build VisualDocs using modern web standards that prioritize accessibility. Our codebase follows semantic HTML practices, and we use ARIA attributes only when semantic HTML alone cannot convey the necessary information.
- •HTML5 semantic elements (header, nav, main, article, section, footer) throughout the site
- •ARIA roles, states, and properties applied where native semantics are insufficient
- •Progressive enhancement ensures core functionality works without JavaScript where possible
- •We test with automated tools (axe, Lighthouse) and manual testing with assistive technologies
Ongoing Improvements
Accessibility is not a one-time effort. We audit our site regularly, respond to user feedback, and continuously improve our accessibility features. When we add new tools or features, accessibility is considered from the design phase through implementation and testing.
- •Quarterly accessibility audits using automated tools and manual testing
- •User feedback drives our accessibility improvement roadmap
- •New features are tested with screen readers and keyboard navigation before release
- •We monitor for regressions with each deployment
Report an Accessibility Issue
If you encounter an accessibility barrier while using VisualDocs, please let us know. We take all reports seriously and will work to resolve the issue as quickly as possible. Include the page URL, a description of the problem, and the assistive technology you are using so we can reproduce and fix it.
- •Email: accessibility@visualdocs.app
- •Support form: Available on our Contact page
- •Response time: Within 2 business days
- •We will acknowledge your report and provide a timeline for resolution
Found an accessibility issue? Let us know — we are committed to fixing it.