UI/UX Designer
Accessibility questions
153 questions on Accessibility for ui/ux designers, easiest first.
Easy 42
- Minimum contrast for body texteasy
- Comfortable tap target size on mobileeasy
- Contrast for large texteasy
- Alt text for a decorative imageeasy
- Removing focus outlineseasy
- Placeholder instead of a labeleasy
- The four WCAG principleseasy
- WCAG conformance levelseasy
- The level most regulations targeteasy
- Disability is not only permanenteasy
- How common colour blindness iseasy
- A free screen reader for Windowseasy
- Captions for a product videoeasy
- Making a podcast accessibleeasy
- Page titles across a siteeasy
- Declaring the page languageeasy
- Instructions based on shape and positioneasy
- Purpose of a skip linkeasy
- Stuck inside an embedded widgeteasy
- Enhanced contrast at Level AAAeasy
- Contrast rules for a logoeasy
- The first rule of ARIAeasy
- Button or linkeasy
- Grouping radio buttonseasy
- Header cells in a data tableeasy
- The main landmarkeasy
- Marking a field as requiredeasy
- Alt text on a logo that links homeeasy
- Keys for a quick keyboard testeasy
- How screen reader users scan pageseasy
- Marking the current page in a menueasy
- Landmark for the site footereasy
- Screen reader on an iPhoneeasy
- Tools for automated checkseasy
- Relying on the title attributeeasy
- Emoji in a headingeasy
- The European Accessibility Acteasy
- Accessibility law in Indiaeasy
- Minimum touch target sizeeasy
- Why components need a focus stateeasy
- What belongs in a tooltipeasy
- Checking with a screen readereasy
Medium 57
- Status shown only by colourmedium
- WCAG 2.2 target size minimummedium
- Focus hidden by a sticky barmedium
- Drag-only reorderingmedium
- Blocking paste in password fieldsmedium
- Typing the same address twicemedium
- Focus in a modal dialogmedium
- Icon-only buttonsmedium
- The criterion WCAG 2.2 removedmedium
- Reflow at high zoommedium
- Text that breaks when enlargedmedium
- Faint borders on form fieldsmedium
- Contrast of disabled buttonsmedium
- Promo text inside a banner imagemedium
- Visual-only information in a videomedium
- Captions for a live webinarmedium
- Background music that plays on loadmedium
- A carousel that never stopsmedium
- A flashing sale bannermedium
- An app locked to portraitmedium
- Shake to undomedium
- A map that needs pinch to zoommedium
- A sum to solve at loginmedium
- Where the help link livesmedium
- A dropdown that jumps to a new pagemedium
- A vague form errormedium
- Preventing mistakes in a transfermedium
- Headings made with bold textmedium
- Linking a hint to an inputmedium
- State of a show/hide buttonmedium
- A mute toggle buttonmedium
- Polite or assertive live regionsmedium
- What role="alert" doesmedium
- Exposing a field errormedium
- Autocomplete tokens on personal fieldsmedium
- Two navigation menus on a pagemedium
- Marking up a site searchmedium
- Using tabindex="3"medium
- What tabindex="-1" is formedium
- Hiding text but keeping it for screen readersmedium
- Making the page behind a dialog inactivemedium
- Keyboard behaviour for tabsmedium
- Markup for an accordion headermedium
- An icon next to a text labelmedium
- Naming a data tablemedium
- The accessibility treemedium
- Focus styles only for keyboard usersmedium
- Common screen reader and browser pairsmedium
- What a VPAT is formedium
- Accessibility overlay widgetsmedium
- EN 301 549medium
- Usability tests with disabled usersmedium
- Contrast for text and UI partsmedium
- Icon font or inline SVGmedium
- Accessibility notes for developersmedium
- Testing with large textmedium
- Highest possible contrast ratiomedium
Hard 54
- Accessibility blocker before launchhard
- A brand button that fails contrasthard
- Text over a photohard
- Errors on a long formhard
- Announcing a cart updatehard
- Motion and vestibular disordershard
- A red and green charthard
- Swipe-only actionshard
- Visible label and accessible namehard
- Working out a contrast ratiohard
- Lightening a grey by one stephard
- Text spacing a user may applyhard
- Rules for hover and focus pop-upshard
- Focus Appearance at Level AAAhard
- One-letter keyboard shortcutshard
- Warning before a session expireshard
- Actions fired on mousedownhard
- Focus that opens a new windowhard
- Visual order changed with CSShard
- Links shown only by colourhard
- Focus rings in Windows high contrasthard
- Wide data tables at 400% zoomhard
- Text that does not need contrasthard
- Claiming conformance for one pagehard
- Which name winshard
- aria-hidden on a focusable controlhard
- A live region added with its messagehard
- Roving tabindex in a toolbarhard
- Highlighting options in an autocompletehard
- role="menu" for a site menuhard
- aria-label on a plain divhard
- Labelling from hidden texthard
- A component rendered twicehard
- Tables with two levels of headershard
- Screen reader browse and focus modeshard
- role="presentation" on a tablehard
- A button inside a linkhard
- Route changes in a single page apphard
- Explaining why a button is disabledhard
- Toast messages that disappear fasthard
- Keeping submit disabled until the form is validhard
- A greyed-out Submit buttonhard
- Keyboard behaviour of a modalhard
- Error state shown only in redhard
- Headless component librarieshard
- Tab order that jumps aroundhard
- A CAPTCHA blocking real usershard
- A custom dropdown built from divshard
- An automated scan shows zero errorshard
- Testing a shared date pickerhard
- Research with screen reader usershard
- Lightest grey text on white for AAhard
- Very faint disabled controlshard
- Yellow brand text on whitehard