SoundWave Central

Accessibility Statement for SoundWave Central

SoundWave Central is committed to ensuring digital accessibility for all users, including those with disabilities. We strive to conform to the Web Content Accessibility Guidelines (WCAG) 2.1, level AA, as our standard for accessibility. These guidelines outline four main principles: content must be Perceivable, Operable, Understandable, and Robust (POUR).

This accessibility statement describes our ongoing efforts to improve the accessibility of SoundWave Central. We are continuously working to enhance our website and audio content to provide an inclusive and seamless experience for everyone.

Our Accessibility Efforts

WCAG 2.1 Compliance

SoundWave Central is committed to adhering to the WCAG 2.1, level AA guidelines. These guidelines cover a wide range of recommendations for making Web content more accessible. While we strive for full compliance, we recognize that some areas may require further improvement. We are continuously working to address these issues and enhance the overall accessibility of our website.

The following table outlines some of the key WCAG 2.1 success criteria and our approach to meeting them:

WCAG 2.1 Success Criteria and Our Implementation
Success Criterion Description Implementation
1.1.1 Non-text Content Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language. All images have descriptive alt text. Audio and video content have transcripts and captions.
1.3.1 Info and Relationships Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. We use semantic HTML elements (e.g., headings, lists, tables) to structure content and ARIA attributes to define relationships between elements.
1.4.3 Contrast (Minimum) The visual presentation of text and images of text has a contrast ratio of at least 4.5:1. We use color contrast tools to ensure sufficient contrast between text and background colors.
2.1.1 Keyboard All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes. Our website is fully navigable using a keyboard. Focus indicators are clearly visible.
2.2.2 Pause, Stop, Hide For moving, blinking, scrolling, or auto-updating information, all of the following are true: (a) Moving, blinking, scrolling: For any moving, blinking or scrolling information that (1) starts automatically, (2) lasts more than five seconds, and (3) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it unless the movement, blinking, or scrolling is part of an activity where it is essential; and (b) Auto-updating: For any auto-updating information that (1) starts automatically and (2) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it or to control the frequency of the update unless the auto-updating is part of an activity where it is essential. Our website minimizes the use of automatically moving content. Where such content is used, controls are provided to pause, stop, or hide it.
2.4.4 Link Purpose (In Context) The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general. We use descriptive link text that clearly indicates the destination of the link.
3.1.1 Language of Page The default human language of each Web page can be programmatically determined. We specify the language of each page using the "lang" attribute in the HTML tag.
4.1.2 Name, Role, Value For all user interface components (including but not limited to form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically determined; and notification of changes to these items is available to user agents, including assistive technologies. We use ARIA attributes to provide additional information about the name, role, and value of user interface components.

Known Limitations

Despite our best efforts to ensure accessibility, some limitations may exist on SoundWave Central. We are aware of the following potential issues and are actively working to address them:

Feedback and Contact Information

We welcome your feedback on the accessibility of SoundWave Central. If you encounter any accessibility barriers or have suggestions for improvement, please contact us:

We will do our best to respond to your inquiries and address any accessibility concerns in a timely manner. Our Accessibility Officer, Dr. Vivian Holloway, is dedicated to ensuring our commitment to accessibility is upheld.

Formal Complaints

If you are not satisfied with our response to your accessibility concerns, you may file a formal complaint with our compliance department. Please submit your complaint in writing, detailing the specific accessibility issue and the steps you have taken to resolve it. Send your complaint to:

Our compliance team will review your complaint and take appropriate action to address the issue. We are committed to resolving accessibility complaints fairly and efficiently.

Updates to This Statement

This accessibility statement will be reviewed and updated regularly to reflect our ongoing efforts to improve accessibility. We encourage you to check this page periodically for the latest information.

Last Updated: October 26, 2023