Accessibility Statement – Audacity

Audacity is committed to ensuring digital accessibility for people with disabilities. We are continually improving the user experience for everyone and applying the relevant accessibility standards.

Compliance Status

The current Audacity 3 release is partially compliant with EN 301 549, based on findings considered broadly applicable across the Audacity 3.x series. Most applicable WCAG 2.1 Level A and Level AA criteria are met. The criteria that are not fully met are listed below.

Partial compliance means that most accessibility requirements are met, but with some exceptions, and that the necessary measures are to be taken in order to reach full compliance.

Non-accessible Content

The content listed below is not fully accessible in the current Audacity 3 release.

1. Application functionality is only partially accessible via keyboard.
2. Application functionality is only partially accessible to screen readers.
3. Text sizes cannot currently be increased in-app.
4. Audacity does not expose all UI information to OS accessibility APIs. Work is ongoing.

In addition, the following WCAG 2.1 success criteria are not fully met in Audacity 3. Each entry gives the level of support recorded in our conformance report.

Level A

• 1.1.1 Non-text content - partially supports
• 1.3.1 Info and relationships - partially supports
• 1.4.1 Use of color - partially supports
• 2.1.1 Keyboard - partially supports
• 2.1.2 No keyboard trap - partially supports
• 2.5.2 Pointer Cancellation - partially supports
• 2.5.3 Label in name - partially supports
• 3.3.1 Error Identification - partially supports
• 4.1.2 Name, Role, Value - partially supports

Level AA

• 1.4.4 Resize text - partially supports
• 1.4.5 Images of text - partially supports
• 1.4.10 Reflow - does not support
• 1.4.11 Non-text contrast - partially supports
• 1.4.13 Content on hover or focus - does not support
• 2.4.7 Focus visible - partially supports
• 3.1.2 Language of parts - does not support
• 3.3.3 Error Suggestion - partially supports

Audacity 4

Audacity 4 rebuilds the application on a new interface framework, which changes how it presents itself to assistive technology. The items listed above are improved to varying degrees:

• Keyboard access is substantially improved. Tracks, clips and toolbars are navigable.
• Screen reader support has been rebuilt. It improves in some respects, and further work is expected.
• Text resizing is substantially improved. The body text size setting adjusts virtually all text in the application.

Audacity 4 has not yet been assessed against EN 301 549.

Preparation of this Accessibility Statement

This statement was prepared on 09 December 2025. The method used to prepare the statement: self-assessment based on the WCAG 2.1 AA success criteria.

Last reviewed on 20 November 2025 against Audacity version 3.7.6, based on an accessibility conformance report for Audacity 3.7.3 whose findings are considered broadly applicable across Audacity 3.x.

This statement was last revised on 27 August 2026 to correct the compliance status and scope, remove expired remediation dates, and describe Audacity 4.

Feedback and Contact Information

We welcome your feedback on the accessibility of Audacity.

If you encounter any accessibility barriers, or if you are an educational institution requiring more clarification, please let us know.

• Email: accessibility@audacityteam.org
• Postal address: Spyrou Kyprianou, 84, 4004, Limassol, Cyprus

We aim to respond to accessibility feedback within 10 business days.

Enforcement Procedure

If you are not satisfied with our response to your feedback, you can contact the responsible national enforcement body:

Deputy Ministry of Social Welfare Cyprus

• Website: https://www.gov.cy/dmsw/en/
• Phone: +357 22406610
• Email: deputyministry@dmsw.gov.cy

Additional Information

Accessibility issues: Open / Resolved. Current work primarily concerns Audacity 4.

Please note that not every accessibility issue constitutes a compliance issue. In Audacity, we aim to design interfaces that are not only functional but also intuitive, following established design best practices and addressing reported issues in line with their severity and impact.