Skip to content
brownie.tools

Accessibility Statement

Last updated:

Our Commitment

brownie.tools is committed to ensuring digital accessibility for people with disabilities. We strive to meet or exceed the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA standard across all tool pages, navigation, and content.

Accessibility is not an afterthought - it is a core design principle built into every component, layout, and interaction from the start. Our goal is that every person, regardless of ability, can use our tools independently and effectively.

Standards We Follow

  • WCAG 2.2 Level AA - Our target conformance level. This includes all Level A and Level AA success criteria.
  • WAI-ARIA 1.2 - Used for dynamic content and custom interactive components where native HTML semantics are insufficient.
  • European Accessibility Act (EAA) - We design with EAA requirements in mind for European users.

What We Do

Keyboard Navigation

All interactive elements - buttons, inputs, links, accordions, and the command palette - are fully keyboard-operable. Tab order follows a logical reading sequence. Focus indicators are visible on all interactive elements using the :focus-visible pseudo-class. The "Skip to content" link is the first focusable element on every page.

Screen Reader Support

Pages use semantic HTML elements (<main>, <nav>, <section>, <article>) for document structure. Dynamic content updates (conversion progress, results, error messages) use aria-live regions so screen readers announce changes without requiring user interaction. Form inputs have associated <label> elements. Error messages use role="alert".

Visual Design

Text color contrast meets the WCAG 2.2 AA minimum ratio of 4.5:1 for normal text and 3:1 for large text. Color is never the sole means of conveying information - icons, text labels, and patterns are used alongside color indicators. Dark mode is supported and maintains the same contrast ratios.

Touch and Pointer

All interactive targets (buttons, links, form controls) have a minimum size of 44x44 CSS pixels, meeting WCAG 2.5.8 (Target Size Minimum). Drag-and-drop file upload always has an equivalent button alternative (WCAG 2.5.7 Dragging Movements).

Motion and Animation

Users who prefer reduced motion (via the prefers-reduced-motion: reduce media query) see simplified or no animations. Essential state changes remain visible without animation.

Testing Methods

We test accessibility using a combination of automated and manual methods:

Method Tool Frequency
Automated scanning axe-core (via Playwright) Every build (CI)
Lighthouse audit Lighthouse CI Every deploy
Keyboard testing Manual Every new component
Screen reader VoiceOver (macOS) Major releases
Color contrast OKLCH design tokens Design system level

Known Limitations

While we work to ensure comprehensive accessibility, the following limitations are currently known:

  • File drag-and-drop feedback: The visual feedback during file drag operations may not be communicated to all screen readers. The button-based upload alternative is always available and fully accessible.
  • Image output preview: Converted image previews do not currently have descriptive alt text beyond the filename. We are working on adding format and dimension information to alt attributes.
  • Command palette (Cmd+K): The keyboard shortcut Ctrl+K may conflict with browser shortcuts in some configurations. The search function is also accessible via the navigation menu.

Reporting Issues

If you encounter any accessibility barrier while using brownie.tools, please let us know. We take all accessibility reports seriously and aim to address issues promptly.

To report an accessibility issue, use the feedback button available on every tool page. Please include:

  • The page URL where you encountered the issue
  • A description of the barrier you experienced
  • The assistive technology you were using (if applicable)
  • Your browser and operating system

Continuous Improvement

Accessibility is an ongoing effort. We regularly review and update our tools and components to improve accessibility. New features are designed with WCAG 2.2 AA compliance from the outset, and existing components are audited as part of our regular development cycle.