Skip to content
Tutorials Center
My learning

Topics

Lesson 34 of 37 ยท Publishing and Maintenance

Accessibility and Launch Checklist

Make Wix and Webflow sites accessible and launch-ready: contrast, keyboard use, alt text, labels, focus, legal pages and a final checklist, with runnable contrast and checklist tools.

An accessible site works for people who use screen readers, keyboards, voice control, magnification or who have low vision, color blindness, motor limitations or cognitive differences. It is also better for everyone else: readable text, clear links and predictable pages help on small screens, in sunlight, and for tired people at midnight. In many countries accessibility is also a legal requirement for businesses.

Wix and Webflow are hosted and cannot run here. Accessibility tools and settings differ by product and version, so check their current documentation. Automatic checkers find only some problems; always test with the keyboard and, if you can, a screen reader. The code samples are stand-ins that run the same maths a checker uses.

The standard: WCAG

The Web Content Accessibility Guidelines (WCAG) organize requirements around four principles, abbreviated POUR: Perceivable, Operable, Understandable, Robust. Level AA is the usual goal. You do not need to memorize the document; a handful of practices cover most problems.

Practical checklist: content and design

  1. Color contrast. Normal text needs a contrast ratio of at least 4.5:1 against its background; large text (about 24 px or 19 px bold) needs 3:1. Do not use light gray on white.
  2. Do not rely on color alone. Error states and links need a second cue (text, underline, icon).
  3. Text size and spacing. Body text around 16 px or larger, comfortable line height, and layouts that survive zooming to 200%.
  4. Alt text. Describe meaningful images; leave decorative images with empty alt.
  5. Headings in order, so people can jump by heading (see SEO Fundamentals and Site Settings).
  6. Link text that makes sense alone: "Read the pricing guide", not "Click here".
  7. Captions and transcripts for video, and no autoplaying audio.
  8. Plain language and short paragraphs.

Practical checklist: interaction

  1. Keyboard: every control must work with Tab, Shift+Tab, Enter, Space and the arrow keys where appropriate, in a logical order. Menus, modals and sliders are the usual failures.
  2. Visible focus: never remove the focus outline without replacing it with a visible one. In Webflow, style the :focus-visible state on links and buttons; in Wix, check that the focus ring appears on buttons and menus.
  3. Skip link: a "Skip to content" link at the top lets keyboard users bypass the navigation. Webflow documents how to add one with a link to the main content's ID; in Wix, accessibility settings in the dashboard and editor can enable a skip-to-main-content link.
  4. Forms: every field has a visible label; error messages are text and say how to fix the problem; required fields are marked in more than color.
  5. Touch targets at least about 44 by 44 px.
  6. Motion: provide a pause for moving content and respect reduced motion (see Easing and Motion Performance).
  7. Time limits and popups: avoid timing people out, and make popups closable by Escape and a visible button.

Semantic structure and ARIA

Use real elements: Webflow's Section, Navigation, Header and Footer elements output semantic tags, and you can set tags and roles such as main and nav in the element settings. ARIA attributes (like aria-label) fill gaps, but the first rule of ARIA is to use a native element if one exists. Add custom attributes in Webflow's settings panel; Wix exposes accessibility settings (tag, aria-label, and role) on many elements in Studio and in the Editor's accessibility panel.

Contrast calculator

Contrast ratio is computed from the relative luminance of two colors. This stand-in implements the WCAG formula so you can test your palette.

JS WCAG contrast ratio

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Testing

  • Keyboard test: put the mouse aside and tab through the page. Can you reach and use everything? Can you see where you are?
  • Zoom test: zoom to 200% and 400%; check for overlapping or cut-off content.
  • Screen reader test: try VoiceOver (macOS, iOS), TalkBack (Android) or NVDA (Windows, free).
  • Automated tools: browser extensions and Lighthouse's accessibility audit, plus each platform's built-in checks where they exist (Wix offers an accessibility checker in the editor; Webflow offers an Audit panel in the Designer for items such as missing alt text, heading structure and link names).
  • Real people: if possible, invite users with disabilities to test.

Before launch, prepare: Privacy policy, Terms (especially for stores and members areas), Cookie notice or consent banner where required (and be sure that analytics and marketing scripts respect the choice), Accessibility statement (describe your goals and a contact for problems), Shipping and returns for stores, and your business identity and contact details. Rules vary by country, so consult the requirements that apply to you.

The launch checklist, as code

A checklist works best when each item is explicit. This stand-in tracks items and prints what remains.

JS Stand-in: launch checklist

Press Run (or Ctrl + Enter) to see the console output here.

No output.

After launch

Watch Search Console and analytics for errors, test the live forms and checkout, check on a few real devices, and announce the site. Plan the first maintenance review for the following week.

Common mistakes

  • Removing outlines for looks.
  • Low-contrast placeholder text acting as labels.
  • Forgetting accessibility in animations, popups and sliders.
  • Launching with indexing disabled or with test content still live.
  • Never testing with a keyboard.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What minimum contrast ratio does WCAG AA require for normal text?

    Normal text needs 4.5:1; large text needs 3:1.
  2. 2. What is the purpose of a skip link?

    It lets keyboard and screen reader users jump straight to the main content.
  3. 3. Which element should every form field have?

    Labels identify fields for everyone, including screen reader users; placeholders alone are not enough.
  4. 4. Why test with a keyboard?

    Keyboard operation is a core requirement and a quick way to find many issues.

Summary

  • Aim for WCAG AA: perceivable, operable, understandable, robust.
  • Check contrast, alt text, labels, headings, link text, focus and keyboard operation.
  • Combine automated tools with keyboard, zoom and screen reader tests.
  • Prepare legal pages and use a written launch checklist before going live.

Next: Project: A Portfolio Site