Accessibility

Where this statement stands

Shotlingo has never been through an accessibility audit, so this page makes no conformance claim. Nobody has tested the product against WCAG, no screen reader user has reviewed it, and there is no accessibility check in our build pipeline. What follows is a plain description of what the code does today, including the parts that are not good enough yet.

Shotlingo is built and maintained by one person. That is why the list of known gaps below is longer than the list of things that work.

What is in place today

Each item here is something you can check in the product.

• Standard page structure on this site. Pages outside the editor use header, nav, main and footer landmarks, and real heading elements instead of styled text.
• Alt text on images. Every image on this site and in the app carries an alt attribute. Images that carry no information use an empty alt, so a screen reader skips them instead of reading out a file name.
• Text contrast measured by hand. Text colors were checked against their backgrounds and the measured ratios are recorded in the stylesheet beside the values. Secondary and tertiary text were both darkened until they cleared 4.5:1 on the lightest surface. The old tertiary gray measured 2.85:1 and was replaced. Bright brand amber measures 1.76:1 on white, so light backgrounds use a darker amber at 5.52:1 and keep the bright one for fills and borders.
• Keyboard shortcuts in the editor. Selection, copy, paste, duplicate, delete, grouping, layer order, alignment, zoom and arrow key nudging all have shortcuts. Pressing ? opens a panel that lists them.
• Escape closes things. Dialogs, dropdown menus and the onboarding tour close when you press Escape.
• Language and text direction stay correct. The interface is available in English and Turkish, and switching language updates the lang and dir attributes on the page so assistive technology and CSS both follow.
• Theme choice. Light, dark and system themes are available, and the system option follows your operating system setting.
• Reduced motion on the homepage. The scrolling screenshot wall and the homepage hover animations stop when your system asks for reduced motion.

What is not in place

• No audit and no automated testing. There is no automated accessibility scan, no accessibility lint rule, no accessibility job in CI and no screen reader testing. Nothing on this page has been independently verified.
• The canvas editor is effectively closed to screen readers. See the section below.
• The editor is unavailable on small touch screens. See the section below.
• Focus outlines are removed in places. Several text inputs and text areas in the app clear the browser default focus ring and show only a border color change instead. That is a weak indicator, and on a few controls there is nothing at all.
• Dialogs do not trap focus. Tabbing inside an open dialog can move focus to the page behind it, and closing a dialog does not return focus to the control that opened it.
• Reduced motion is honored on the homepage only. Transitions and animations inside the app ignore the setting.
• There is no skip link. You cannot jump past the navigation to the page content with the keyboard.
• Status messages are not announced by our own markup. Saves, exports and errors appear on screen, but we do not put them in a live region, so a screen reader may stay silent.
• Form labels are inconsistent. Sign in and sign up fields are properly associated with their labels. Elsewhere in the app, many fields have visible text beside them that is not connected to the input in code, and a few rely on placeholder text alone.
• Navigation does not mark the current page. Menus do not expose which page you are on to assistive technology.

The editor on small screens

The editor is deliberately blocked on touch devices narrower than 860px. It is a three column layout with a fixed 350px sidebar and a 280px properties panel and no small screen breakpoints, so on a phone the drawing area collapses to zero width and the export button sits off screen. Instead of serving that, we show a notice with the project link ready to copy, so you can open it on a larger screen.

Two details matter if this affects you:

• The check looks for touch input, not window width alone. A desktop browser in a narrow window is not blocked.
• The notice has a "Continue anyway" button. Choose it and the editor loads, and the choice is remembered so you are not asked again.

Everything outside the editor works at phone widths, including the dashboard, the account pages and this site.

The canvas editor and screen readers

The editor draws to an HTML canvas. Every object you place on it, whether text, a device frame or an image, is painted into a single element with no structure behind it. Our canvas exposes no roles, no names and no keyboard focus targets for those objects, so a screen reader announces nothing useful about the design you are building.

This is a hard problem for any visual design tool, and we have not solved it. If your work depends on reading a design canvas with assistive technology, Shotlingo will not serve you well today. We would rather write that here than let you discover it after signing up.

Report an accessibility problem

Email hello@shotlingo.com with "Accessibility" in the subject line. None of the following is required, but each one helps:

• the page or screen where it happened
• what you were trying to do
• your browser, your operating system, and any assistive technology you use

One person answers this address, so here is a commitment that can actually be kept: a reply within 5 business days. That reply will tell you whether the problem is something we can fix, roughly when, and whether there is a workaround in the meantime. Several items on the list above need design work rather than a quick patch, and those will take longer. If a fix is going to be slow, we will say so instead of leaving the message unanswered.

How this page is kept current

This statement is reviewed at least once a year, and again whenever something on either list above changes. If Shotlingo goes through an accessibility audit, the results will be published here, failures included.