Accessibility

ShaderGif aims to be usable by as many people as possible, including people who rely on assistive technologies. This accessibility statement explains how we approach accessibility across ShaderGif, what we know is not yet perfect, and how to ask for help.

Scope

This statement applies to the ShaderGif website and web app at shadergif.com, including the GIF gallery, individual GIF pages, account pages, and the shader/code editor.

Accessibility standards

We aim for practical alignment with WCAG 2.1 Level AA. Some areas partially conform today, particularly where interactive code editing, canvas-based rendering, and user-generated content introduce additional constraints.

What we do to support accessibility

  • Keyboard support: core navigation and primary actions are designed to be reachable without a mouse.
  • Semantic structure: headings and page landmarks are used to help screen reader navigation.
  • Responsive layout: content is designed to reflow on different screen sizes and zoom levels.
  • Readable UI defaults: we aim for clear focus states, sufficient contrast, and predictable interaction patterns.
  • Accessible content guidance: where users can add titles/descriptions, we encourage clear, descriptive text that helps everyone.

Known limitations and workarounds

  • Animated content (GIFs / previews): some pages may autoplay animations and may not provide a consistent “pause animation” control everywhere.
    Workaround: use your browser’s reduced motion settings where available, scroll past the animation, or open the “raw GIF” link (if provided) to control playback with your viewer.
  • Canvas/WebGL rendering: shader output is rendered visually and may not have equivalent text alternatives for the generated imagery.
    Workaround: rely on the GIF title/description and any accompanying code comments; if you need a text summary for a specific GIF, contact us with the page link.
  • Code editor complexity: focus order, keyboard shortcuts, and screen reader announcements can vary depending on the editor component and browser/assistive tech combination.
    Workaround: try a different browser (Chromium-based or Firefox), and use standard text navigation keys inside the editor. If a shortcut conflicts with your assistive tech, let us know which combination is affected.
  • User-generated content quality: titles or descriptions may be brief, missing, or non-descriptive on some GIFs.
    Workaround: check any available code snippet and comments on the page; we also encourage creators to improve titles/descriptions over time.

Animation, flashing, and motion safety

ShaderGif contains animated artwork that may include flicker, rapid contrast changes, or bright patterns. If you are sensitive to flashing content (including photosensitive epilepsy), we recommend taking extra care:

  • Reduce screen brightness and avoid full-screen playback for unfamiliar GIFs.
  • Use browser or OS settings such as Reduce Motion where supported.
  • Stop scrolling on a static area of the page if an animation is distracting or uncomfortable.

Using ShaderGif with a keyboard

  • Use Tab and Shift + Tab to move through interactive controls.
  • Use Enter or Space to activate buttons and links (depending on your browser).
  • In the editor, standard text navigation keys (arrows, Home/End, Page Up/Down) should work inside the code area.

Feedback and help

If you have difficulty accessing any part of ShaderGif, please tell us what happened and we’ll do our best to help. Include:

  • the page you were trying to use (URL)
  • what you were trying to do
  • your browser and device
  • any assistive technology you use (optional, but helpful)

You can reach us via the Contact page, or by emailing [email protected].

Statement preparation

  • Preparation method: internal review and periodic spot-checks (keyboard navigation, automated audits, and manual UI review).
  • Review cycle: updated as the editor, gallery, and theme evolve.

Related pages

Last updated: 28 December 2025