Color Contrast: WCAG Accessibility Guide for Ecommerce Stores
Text and its background fall below the 4.5:1 ratio for normal text (3:1 for large text), so low-vision users cannot read it.
Read the guide2,000 practical playbooks that pair 50 accessibility topics with 40 audiences, each with code fixes and a zero-setup audit path.
Showing 50 topic guides. Every topic has 40 audience editions.
Text and its background fall below the 4.5:1 ratio for normal text (3:1 for large text), so low-vision users cannot read it.
Read the guideInput borders, icons, and focus indicators are too faint against their surroundings to be perceived.
Read the guideInformative images have missing or meaningless alt attributes, so screen reader users get no information.
Read the guideMenus, sliders, and custom widgets respond only to a mouse, which blocks keyboard-only and switch users.
Read the guideStylesheets remove the focus outline, so keyboard users cannot tell which element is active.
Read the guideSticky headers and cookie bars cover the focused element as users tab through the page.
Read the guideKeyboard users must tab through the whole navigation on every page before reaching the content.
Read the guideHeading levels skip or appear out of order, which breaks the page outline screen reader users rely on.
Read the guideInputs rely on placeholders only, so the field purpose disappears once users start typing and assistive tech gets no name.
Read the guideInvalid fields turn red with no text, so color-blind and screen reader users miss the error.
Read the guideLogin relies on memorizing or transcribing codes and puzzle CAPTCHAs, which excludes users with cognitive disabilities.
Read the guideTiny links and icon buttons are hard to hit for people with tremors or on touch screens.
Read the guideCustom components expose no accessible name or role, or use ARIA incorrectly, so assistive tech cannot announce them.
Read the guidePages lack header, nav, main, and footer landmarks, so screen reader users cannot jump between regions.
Read the guideThe html element has no lang attribute, so screen readers may pronounce content with the wrong voice.
Read the guideMany pages share a generic title, so users cannot tell tabs and history entries apart.
Read the guideLinks read "click here" or "read more", which is meaningless when announced out of context.
Read the guidePrerecorded videos have no captions, so deaf and hard-of-hearing users miss the content.
Read the guideVideos convey important visual information that is never described in audio.
Read the guideContent forces horizontal scrolling when zoomed to 400 percent, which is painful for low-vision users.
Read the guideFixed-height containers clip text when users increase line height, letter, or word spacing.
Read the guideThe page locks to portrait or landscape, which blocks users who mount their device in one orientation.
Read the guideOpening a dialog leaves focus behind the overlay, and closing it drops focus to the top of the page.
Read the guideDropdown menus open on hover only and cannot be reached or closed with the keyboard.
Read the guideData tables use styled cells instead of header cells, so screen readers cannot associate values with columns.
Read the guideCart updates and success notices appear visually but are never announced to screen reader users.
Read the guidePersonal data fields lack autocomplete tokens, so users cannot fill them automatically.
Read the guideNavigation links change order between pages, forcing users to relearn the layout each time.
Read the guideContact and help options move around, so users who need support struggle to find it.
Read the guideMulti-step forms ask users to retype information they already provided.
Read the guideSliders, sortable lists, and drag-and-drop uploads require dragging with no alternative.
Read the guideActions fire on pointer down, so a slip of the finger triggers purchases or deletions with no way to cancel.
Read the guideAuto-playing carousels and animations cannot be paused, which distracts and disorients users.
Read the guideEmbedded widgets capture focus and give keyboard users no way to tab out.
Read the guideSessions expire without warning, losing form data for users who need more time.
Read the guideAnimated banners flash more than three times per second, which can trigger seizures.
Read the guideRotating banners lack controls and labels, so keyboard and screen reader users cannot browse them.
Read the guideDownloadable PDFs are untagged scans, so screen readers cannot read them.
Read the guideThe site has no accessibility statement or contact route for users who hit barriers.
Read the guideA one-line overlay script is marketed as a fix but leaves the underlying markup, labels, and keyboard flow unchanged.
Read the guideTeams cannot show dated evidence of what they audited and fixed when a demand letter arrives.
Read the guideA single audit goes stale as soon as new releases ship, and regressions go unnoticed.
Read the guideAudit reports list problems in prose and leave engineers to guess the exact change.
Read the guideAccessibility fixes get undone by later commits because nothing checks them before release.
Read the guideChat, payment, and map embeds lack titles and keyboard support, and the vendor controls the code.
Read the guideConsent banners trap focus, cover content, or cannot be dismissed with the keyboard.
Read the guideLive filters update results silently and filter checkboxes have no group labels.
Read the guideCheckout steps hide errors, reset fields, and use inaccessible payment widgets, costing completed orders.
Read the guidePinch, swipe, and multi-finger gestures are the only way to perform an action.
Read the guideIcon-only buttons have no text, so a screen reader announces them as just "button".
Read the guide