LyricVueLyricVue

Accessibility Statement

Last reviewed: June 2026

Our Commitment

LyricVue is committed to making its website usable by as many people as possible, including those who rely on assistive technologies such as screen readers, keyboard navigation, or browser zoom. We are actively working toward conformance with the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA.

Conformance Status

LyricVue is partially conformant with WCAG 2.1 Level AA. Partially conformant means that some parts of the content do not fully conform to the accessibility standard, but we are addressing them incrementally.

What We Support

Keyboard Navigation

  • All interactive controls — buttons, inputs, links, and file upload areas — are reachable and operable using the keyboard alone.
  • All modals and dialogs trap keyboard focus while open. Pressing Escape closes them and returns focus to the element that triggered them.
  • Preset and video clip cards support Enter and Space to select.

Focus Visibility

  • A visible purple focus ring appears on every interactive element when navigating by keyboard.
  • Focus rings are suppressed for mouse users to avoid visual clutter, using the :focus-visible CSS pseudo-class.

Screen Reader Support

  • All icon-only buttons (download, close, fullscreen, preview, remove) have accessible labels readable by screen readers.
  • All form inputs have correctly associated labels.
  • Dialogs are marked with role="dialog" and aria-modal="true" so screen readers announce them correctly.
  • Toggle switches use role="switch" and aria-checked to communicate their state.
  • Required fields are announced as required to assistive technology.

Dynamic Content Announcements

  • Error and success messages are announced immediately to screen readers via an ARIA assertive live region.
  • Video creation progress (step name and percentage) is announced periodically via an ARIA polite live region, so screen reader users are kept informed without interruption.

Visual Adjustment Support

  • The interface supports browser zoom up to 200% without horizontal scrolling or content clipping on core flows.
  • System font size preferences and operating system text scaling are respected — we do not override them.
  • Scrollable containers are used for lists that could overflow, rather than clipping content.

Semantic Structure

  • Pages use proper HTML heading hierarchy (h1 → h2 → h3) for navigation by heading.
  • Native HTML elements (button, input, label, select) are used wherever possible instead of custom ARIA widgets.
  • The FAQ section on the landing page uses aria-expanded to communicate open/closed state.

Known Limitations

We are transparent about areas that are not yet fully accessible. We are actively working to address these:

  • Filter pills and format toggles — the video category filters, background mode tabs, and format selector buttons do not yet expose their selected state via aria-pressed or aria-selected. Sighted users can identify the active state visually.
  • User account menu — the dropdown menu in the app header does not yet support arrow key navigation. All items are reachable by Tab, and the menu closes on focus loss.
  • Video preview thumbnails — the visual preset and video clip gallery is primarily a visual selection experience. The name of each option is available as an accessible label but the preview thumbnails themselves have no text equivalent beyond the name.
  • In-browser video processing — the WebAssembly-based video generation runs entirely in the browser. Progress is reported as a percentage and step name, but granular timing estimates are not available.

Technologies Used

LyricVue relies on the following technologies for accessibility support: HTML5, CSS3, WAI-ARIA 1.1, and JavaScript. The interface is built with React and Next.js and is tested with keyboard-only navigation and VoiceOver (macOS/iOS).

Feedback & Contact

If you experience any accessibility barrier on LyricVue, or if a page or feature does not work as expected with your assistive technology, please let us know. We aim to respond within 2 business days.

Send Accessibility Feedback

You can also use the feedback button in the bottom-right corner of the app at any time.