UIUXAnywhere

Remote UI/UX & product design jobs, worldwide.

Guides

Accessibility for product designers: what remote employers expect

By the UIUXAnywhere team · Published November 8, 2026

Accessibility is now part of the job description

Accessibility used to be a specialist topic. In remote design hiring it is now a standard expectation. On 8 November 2026, among the 153 design listings on UIUXAnywhere with a full description, 50 mentioned accessibility, about one in three. Only 7 named the Web Content Accessibility Guidelines (WCAG) explicitly, which suggests most employers expect designers to know the standards without being told.

There are good reasons. In the European Union, the European Accessibility Act has applied to many digital products and services since June 2025, and legal requirements apply in many other countries, especially for public sector, finance and e-commerce. And accessible design is simply better design: clearer, more robust and easier for everyone.

Yet many portfolios show no accessibility work at all. That makes it one of the easiest ways to stand out.

The WCAG basics every designer should know

WCAG 2.2 is the current version, and level AA is the usual target. You do not need to memorise every success criterion, but you should know the ones designers control:

Colour and contrast

  • Text contrast: at least 4.5:1 against its background for normal text, and 3:1 for large text.
  • Non-text contrast: at least 3:1 for interface components (input borders, icons that carry meaning) and focus indicators.
  • Do not rely on colour alone: errors need text or an icon, not only red; charts need labels or patterns.

Focus and keyboard

  • Every interactive element must be reachable and usable with a keyboard.
  • Focus must be visible. Design a clear focus state for every component, not just hover.
  • Focus order should follow the visual order; in modals and menus, focus moves in and returns sensibly.

Target size

  • WCAG 2.2 sets a minimum target size of 24 by 24 CSS pixels (with some exceptions), and many design systems use 44 by 44 as a comfortable default for touch.

Structure and content

  • Headings that reflect the page structure.
  • Visible labels for inputs (placeholders are not labels).
  • Clear error messages that say how to fix the problem.
  • Meaningful link and button text ("Download invoice", not "Click here").
  • Alternative text for meaningful images, and decorative images marked as such.

Motion and timing

  • Respect reduced-motion preferences; avoid flashing content.
  • Avoid time limits, or let users extend them.

Text resizing and reflow

  • Layouts should work when text is enlarged to 200% and at narrow widths (equivalent to 320 CSS pixels) without losing content or requiring horizontal scrolling.

Annotating designs for engineers

Many accessibility problems come from information that never reaches engineers. Good annotations include:

  • the heading levels on each screen;
  • the focus order for complex layouts, modals and menus;
  • accessible names for icon-only buttons and controls;
  • states and announcements: what a screen reader should announce for loading, errors and success messages;
  • alternative text for images, or that they are decorative;
  • keyboard behaviour for custom components (arrow keys in menus, Escape to close).

Figma plugins and annotation kits help, but the decisions are yours. Annotated files are also excellent portfolio material.

Testing your own work

Designers should test, not only specify:

  • check contrast with a contrast tool while designing;
  • tab through prototypes or the built product with a keyboard;
  • try a screen reader (VoiceOver on macOS and iOS, NVDA on Windows, TalkBack on Android) on the built product;
  • zoom to 200% and resize the window;
  • turn on reduced motion and dark mode.

Better still, include disabled people in research. No checklist replaces watching someone use your product with assistive technology.

Accessibility in design systems

The most effective accessibility work happens in the design system: if the button, input, modal and menu components are accessible, every product team benefits. Design systems roles almost always include accessibility; see design systems roles.

Showing accessibility in your portfolio

  • In each case study, mention accessibility decisions where they mattered: contrast choices, focus design, error handling, structure.
  • Include one annotated screen showing headings, focus order and accessible names.
  • If you ran an accessibility audit or improved a component, make it a case study: the issues, the fixes, and the result.
  • Make your portfolio site itself accessible. Reviewers notice low-contrast grey text and missing alt text.

Beyond compliance

Meeting WCAG AA is a floor, not the goal. Products can pass an audit and still be hard to use for disabled people. Good accessibility work also considers:

  • Cognitive load: plain language, predictable layouts, one main action per screen, and forgiving error handling.
  • Low vision and magnification: layouts that still make sense when zoomed, without key information pushed off screen.
  • Motor differences: generous targets, no precise drag-only interactions, and alternatives to complex gestures on mobile.
  • Temporary and situational limits: a broken arm, bright sunlight, a noisy train. Designing for permanent disabilities helps everyone in these situations too.
  • Time and attention: saving progress in long forms, and not hiding critical information in transient toasts.

The strongest accessibility stories in interviews describe a real person's experience that changed a design, not only a contrast ratio that was fixed.

Accessibility in remote teams

Remote teams need accessibility to be part of shared processes, not one person's memory: accessible components in the design system, accessibility notes in every handoff, a short checklist in design review, and testing included in the definition of done. If you can help set that up, you add value far beyond your own designs.

Interview questions to expect

  • How do you make sure a design is accessible before it goes to engineering?
  • How would you design an accessible data table, date picker or modal?
  • A stakeholder wants a light grey text style that fails contrast. What do you do?
  • Have you tested with assistive technology? What did you learn?

Specific answers with real examples matter more than reciting guidelines.

The roles below are the newest on the board. Each one shows where you can work from.

Open remote UI/UX roles

  1. Senior Product Designer (Remote)SeekOut · Remote
  2. Head of DesignLedgy · Remote
  3. Lead Product DesignerFlying Bisons · Poland
  4. Product Designer, Docs & LearningTailscale · Remote (United States)
  5. UI Designer - Casual Games (Freelance Remote)SOFTGAMES · Remote job

More guides