Accessibility Statement

Last updated: 30 June 2026

1. Our commitment

Devdwell is committed to making Devdwell Tools usable by everyone, regardless of ability or the assistive technology they rely on. We design with semantic HTML, sufficient color contrast, keyboard navigation, and screen-reader support in mind from the start — not bolted on afterward.

2. Conformance standard

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA, published by the World Wide Web Consortium (W3C). These guidelines explain how to make web content more accessible for people with disabilities, and more usable for everyone.

3. Why there is no accessibility overlay

This site used to load a third-party accessibility widget — a floating button offering larger text, higher contrast and paused animations. We removed it. An overlay asks you to re-declare, on every site you visit, preferences you have already set once in your operating system, and it only helps the people who notice the button and think to press it.

The site reads those system settings directly instead:

• Reduced motion — with “Reduce motion” on in macOS, iOS, Windows or Android, every transition and scroll animation on the site is disabled, including the smooth-scrolling, which is never initialised at all.
• Increased contrast — with “Increase contrast” (macOS/iOS) or a contrast theme (Windows) enabled, text moves to full black or white, the secondary text tiers move closer to the primary, borders become solid rather than suggested, and decorative grain is switched off.
• Text size — text is sized in relative units and the layout is fluid, so your browser's own zoom and minimum-font-size settings enlarge the site without clipping content or forcing sideways scrolling.
• Colour scheme — color-scheme is declared, so form controls and scrollbars are drawn to match each surface rather than defaulting to the wrong one.

These work whether or not you know this page exists, and they carry across every site that implements them — which is the point.

4. Built-in accessibility features

The site itself is built with these practices:

• Semantic structure: proper heading hierarchy, landmark regions (<header>, <main>, <footer>), and descriptive link text instead of vague phrases like "click here"
• Color contrast: text and interactive elements meet or exceed the 4.5:1 contrast ratio required for WCAG AA, checked against every surface they can sit on — the warm paper ground and the dark bands (the editor, the footer and the cookie notice) alike
• Keyboard navigation: every interactive element — buttons, links, form controls, the tool rail, the mobile menu — is reachable and operable using a keyboard alone
• Focus indicators: visible focus outlines on interactive elements so keyboard users can always see where they are on the page
• Reduced motion support: animations and transitions are minimized automatically if your operating system has "reduce motion" enabled
• Alt text: meaningful alternative text on informative images and icons
• Responsive design: the site reflows cleanly at any zoom level or screen size, including 200% browser zoom

5. Known limitations

While we strive for full conformance, some parts of the experience have inherent limitations. The Image Compressor, Font Compressor, and Video Compressor tools involve visual editing interfaces — such as crop handles and waveform previews — that are best experienced visually. We continue working to improve keyboard and screen-reader support for these interactive editing surfaces.

6. Feedback

We welcome feedback on the accessibility of Devdwell Tools. If you encounter a barrier or have a suggestion, please let us know — we treat accessibility reports as a priority.

Email: hidevdwell@gmail.com

7. Compatibility

Devdwell Tools is designed to work with recent versions of major screen readers (such as VoiceOver, NVDA, and JAWS) paired with current versions of Chrome, Firefox, Safari, and Edge. Some compression tools rely on modern browser APIs (WebAssembly, WebCodecs) and may have reduced functionality on older browsers, independent of accessibility support.

8. Ongoing efforts

Accessibility is not a one-time project — it's an ongoing part of how we build. We periodically review the site against WCAG criteria and update this statement as improvements are made.