Web Performance & Accessibility

Users may not know whether a link downloads a PDF, spreadsheet, or large file until after opening it. Checks to make Include file type and size where useful, identify language or format variants, and ensure labels make sense out of context. Test keyboard focus and screen reader announcements; avoid relying on icons without text. When to get help...

Instructions shown only after an error or on hover may be unavailable to keyboard, touch, or assistive technology users. Checks to make Place concise instructions before or beside the field, associate them programmatically, and explain format requirements with examples where helpful. Test on mobile and with screen readers before submission and error...

A session timeout can cause users to lose entered work or be redirected without understanding why. Checks to make Warn users before expiry where feasible, explain how to continue or sign in again, preserve non-sensitive form state safely, and make the warning accessible to keyboard and screen reader users. Test both idle timeout and forced...

Product image alternatives should convey information that matters to choosing an item without repeating nearby text. Checks to make Describe distinguishing visual details such as color, shape, or view when not already stated. Use empty alternatives for decorative duplicates, keep wording concise, and test gallery controls with assistive technology....

A table can look clear visually while assistive technology users cannot associate cells with row and column headings. Checks to make Use semantic table markup, identify header relationships, provide a concise caption when useful, and avoid using layout tables for content. Test navigation with a screen reader and confirm responsive behavior preserves...

Generic error pages can leave users unsure what happened or how to return to a working path. Checks to make Use a clear title and explanation, preserve a route back to relevant content, and provide a support path without exposing technical details. Ensure headings, focus order, and links work with keyboard and screen readers. When to get help Web...

A CAPTCHA can block users who cannot solve a visual or audio challenge or operate its controls. Checks to make Provide an accessible alternative, ensure keyboard operation and clear error recovery, and test with assistive technology. Avoid making the challenge the only route to essential services and monitor whether anti-abuse controls create...

Voice input may fail when visible labels do not match accessible names or controls require precise gestures. Checks to make Use labels that include visible text, provide predictable control names, avoid custom widgets without semantic equivalents, and test dictation commands with representative users. Ensure errors and instructions can be activated...