Accessibility on Debut Day: A Premiere for Everyone

Good cinemas think about who is in the audience. There is a space for a wheelchair, a loop for people with hearing aids, screenings with captions, seats with room. Nobody calls this a bonus. It is part of being a place where people can see the film.

A product debut is a public showing, and the same thinking applies. If some of your audience cannot use the debut, it is not truly public. This guide gives you a practical accessibility check for debut day: what to test, how to fix common problems and how to speak honestly about what you could not do yet.

Why at the debut

It is easiest to build accessibility in from the start. Habits formed at the debut, such as using real text, labelling forms and checking contrast, become part of how the team works. Retrofitting is harder, costlier and less likely to happen.

It is also right. People with disabilities use products like everyone else, and a barrier on day one tells them they are not expected. Many accessibility measures help all users: captions help in noisy places, good contrast helps in sunlight and keyboard support helps anyone whose mouse has stopped working.

What the standards say

The Web Content Accessibility Guidelines, produced by the World Wide Web Consortium, are the widely used reference for making web content accessible. They are organised around four principles: content should be perceivable, operable, understandable and robust. Each principle has guidelines, and each guideline has testable success criteria at levels of conformance.

You do not need to memorise them. You need to know that they exist, that they are practical and that many of the most important points are quick to check.

Quick checks you can do in an hour

1. Use only the keyboard

Put the mouse away. Press Tab to move through the page.

• Can you reach every link, button and field?
• Is the order sensible?
• Can you see where the focus is at every step?
• Can you operate menus, dialogs and forms?
• Can you get out of anything you get into?

If you get stuck, so will many users.

2. Enlarge the text

Increase the text size in your browser, to double or more. The guidelines expect that text can be resized up to two hundred per cent without loss of content or function.

• Does the layout hold?
• Is any text cut off or overlapping?
• Do you need to scroll sideways?

3. Check colour contrast

Text needs enough contrast against its background. The guidelines set a minimum contrast ratio for normal text, with a lower threshold for large text. A contrast checker will tell you the numbers.

• Check body text, links, buttons, labels and placeholder text.
• Check text on images and gradients.
• Check both light and dark modes.

Cinematic palettes, dark backgrounds and subtle colours are common culprits. A crimson label on black can look dramatic and fail. Choose the stronger option.

4. Do not rely on colour alone

If colour carries meaning, such as red for an error or green for success, add words or symbols. Check the page in greyscale.

5. Look at images and icons

• Meaningful images need alt text that says what they show and why.
• Decorative images should have empty alt text, so screen readers skip them.
• Icons that act as buttons need a text label that a screen reader can announce.
• Charts need a text summary.

6. Check forms

• Every field has a visible label.
• Instructions are clear.
• Errors are described in text and linked to the field.
• Required fields are marked in words, not only colour.
• Autocomplete helps where appropriate.

7. Check headings and structure

• One main heading, then logical subheadings.
• Lists are real lists.
• Tables have headers.
• Landmarks such as navigation and main content are marked.

A screen reader user often moves by headings. A page without them is like a book without chapters.

8. Check video and audio

• Videos have captions. The guidelines expect captions for prerecorded audio in video.
• Provide a transcript, where useful.
• Audio-only content has a text alternative.
• Nothing plays automatically with sound.

For a debut trailer, captions are not optional.

9. Check motion and flashing

• Avoid content that flashes more than three times in one second. The guidelines set thresholds because flashing can trigger seizures.
• Provide a way to pause, stop or hide moving content that lasts more than a few seconds, as the guidelines recommend.
• Respect the setting that tells browsers a person prefers reduced motion.

Marquee lights and spinning reels are charming. Make them stoppable, or leave them out.

10. Listen to a screen reader

Turn on the screen reader built into your phone or computer and listen to your page for five minutes. You will learn more than from any checklist. Does it read the title? The main content? Buttons? Are there confusing announcements?

Fix the biggest problems first

You will probably find a list. Sort it.

Blockers: things that stop a user completing the main job, such as a keyboard trap or an unlabelled button on the main path.

Serious: things that make the experience much harder, such as low contrast in key text or missing captions.

Moderate: inconvenient but workable.

Minor: polish.

Fix blockers before debut day. Plan the rest, with dates.

Be honest in a statement

An accessibility statement is a short page that says what you have done, what you have not yet done and how to get help. It need not be long.

Include:

• The standard you are aiming for.
• What you tested, and how.
• Known gaps, listed plainly.
• What you are doing about them and roughly when.
• A way to report problems or ask for help, such as an email address.
• The date it was last updated.

Do not claim full conformance unless you have tested it properly. Overclaiming is as bad as ignoring the issue. An honest statement of partial progress earns more respect than a boast.

Accessibility and the debut materials

Your debut involves more than the product.

• The announcement page: structured, readable, with alt text.
• Emails: real text, good contrast, descriptive links.
• Videos: captioned.
• Social posts: alt text on images, a camel-case style for hashtags if you use them, and avoid putting key information only in images.
• Event pages: clear time zones and access details.
• Documents and PDFs: tagged and readable.

Treat every item as part of the premiere.

Make it a habit

Accessibility is easiest as a routine.

• Add checks to your done list.
• Test every new feature with the keyboard and a screen reader.
• Pick colours from a palette you have already checked.
• Write alt text as you add images.
• Caption videos as you make them.
• Ask users to tell you about barriers, and respond.

One person on the team should own it, but everyone should know it.

Common mistakes

• Treating it as an afterthought.
• Low-contrast decorative palettes.
• Text in images.
• Unlabelled buttons and icons.
• Autoplaying media.
• Keyboard traps in custom widgets.
• Overclaiming compliance.
• No way to report problems.

A quick pre-debut checklist

• Keyboard-only run-through done.
• Text enlarged to double, layout holds.
• Contrast checked in light and dark.
• Colour never the only signal.
• Alt text added.
• Forms labelled, errors in text.
• Headings logical.
• Videos captioned.
• Motion stoppable, no flashing.
• Screen reader listen done.
• Statement written, with a contact route.

On this site

The submit page is where you describe your entry, including accessibility notes, the contact page is the way to report an accessibility problem on a page here and the launches page shows how new products present themselves. The categories page helps you find a shelf, and the founders page introduces the people who built this place.

A short story of a late fix

A team preparing a debut tests their page the night before with only a keyboard. They discover that the main call to action, a styled button built from a plain box, cannot be reached with Tab and does nothing when Enter is pressed. A user who relies on a keyboard would have been unable to start. The fix takes twenty minutes: replace the box with a proper button element and check the focus outline.

The same session finds a crimson label on a black background that fails the contrast check, a trailer without captions and an image of the pricing table with no alt text. By midnight the blockers are fixed and the rest are on a dated list in the accessibility statement. On debut day, nobody notices, which is the intended result. Accessibility done well is invisible to those who do not need it and decisive to those who do.

Ask the audience

Finally, invite feedback. A line on the debut page, "If anything here is hard to use, tell us and we will fix it", with a monitored address, turns users into collaborators. Reply promptly, thank people for the report and say when it is fixed. Some of the most valuable improvements to any product come from the people who struggle to use it first.

The short version

A debut is a public showing, so make it usable by as many people as possible. Check the keyboard, text size, contrast, colour use, images, forms, headings, captions, motion and a screen reader, fix blockers first, write an honest accessibility statement with a way to report problems and make the checks a routine. A premiere that everyone can enter is the better premiere.