Accessibility

Content does not flash more than three times per second to prevent seizures in users with photosensitive epilepsy.

Animations respect user motion preferences, avoid seizure-triggering flashing, and include warnings for excessive motion.

Parallax scrolling effects have reduced-motion alternatives or can be disabled by users.

Natural scroll behavior is preserved without custom scroll speeds, directions, or hijacked scroll events.

Smooth scroll animations to anchor links respect motion preferences or provide an instant alternative.

Ensures the document body is not set to aria-hidden, which would hide the entire page from screen readers.

Checks that input fields have accessible names so screen reader users know what data each field expects.

Checks that interactive elements have accessible names for clear navigation.

Dynamic content updates are announced to screen readers using appropriate ARIA live regions.

Elements with certain ARIA roles must contain the required child roles or the widget structure will be broken for assistive technologies.

All ARIA attributes must be valid and exist in the WAI-ARIA specification.

IDs referenced by ARIA attributes must be unique to ensure correct accessibility relationships.

Checks that ARIA attributes are allowed on their elements to ensure valid accessibility trees.

Checks that command elements like buttons and links have accessible names for screen reader support.

Checks for deprecated or abstract ARIA roles to ensure long-term compatibility.

Checks that dialog elements have accessible names to orient screen reader users.

Ensures aria-hidden elements do not contain focusable content to avoid "ghost" focus.

Checks that meter elements have accessible names to provide context for measurements.

Checks that progressbar elements have accessible names

Checks that elements have required ARIA attributes for their roles

Checks that elements with certain roles have required parent roles

Checks for valid ARIA role values

Checks that elements with role='text' have no focusable descendants

Checks that toggle fields (checkbox, radio, switch) have accessible names

Checks that tooltip elements have accessible names

All elements with role="treeitem" must have a descriptive accessible name so screen reader users can navigate hierarchical tree widgets.

Checks for valid values in ARIA attributes

Decorative images and visual elements are hidden from screen readers using aria-hidden or empty alt attributes.

Modal dialogs are accessible with proper focus trapping, ARIA attributes, and keyboard dismissal.

Toast notifications and alerts are announced to screen readers using ARIA live regions and appropriate roles.

Tooltips are accessible to keyboard users and screen readers with proper ARIA attributes and focus handling.

Accordion components use proper ARIA attributes and keyboard interactions for screen reader accessibility.

Carousels and sliders are accessible with pause controls, keyboard navigation, and proper ARIA attributes.

Tab components implement the ARIA tabs pattern with proper roles, states, and keyboard navigation.

Link text clearly describes the destination or purpose without relying on surrounding context.

Instructions do not rely solely on sensory characteristics like color, shape, size, location, or sound.

All links contain accessible text content and do not lead to broken destinations.

Content uses inclusive, non-discriminatory language that welcomes all users regardless of ability, gender, race, or background.

Content uses clear, simple language that is easy to understand for users with cognitive disabilities and non-native speakers.

Headings follow a sequential structure (h1 to h6) that reflects the content hierarchy without skipping levels.

Content structure, instructions, and primary tasks remain understandable and operable when author CSS is disabled or replaced by user styles.

All focusable or active elements must have a unique ID attribute.

Page navigation uses nav elements with proper ARIA labels to distinguish multiple navigation regions.

Data tables use proper semantic markup with headers, captions, and scope attributes for screen reader accessibility.

Definition lists (<dl>) must only contain valid <dt> and <dd> elements.

Description terms (<dt>) and details (<dd>) must be contained within a <dl> element.

All heading elements (h1-h6) must have visible, descriptive content.

Heading levels should follow a sequential, hierarchical order.

Lists (ul, ol) should only contain list item elements (li) to ensure they are correctly interpreted by assistive technology.

List item elements (li) must always be direct children of a list container (ul, ol, or menu) to maintain valid HTML structure and correct screen reader announcements.

Groups of related items use ul, ol, or dl elements so screen readers announce list context and item count.

Checks that data tables have unique accessible names

Checks that data tables have proper headers

Checks that td headers attribute references valid th ids

Checks that table headers have associated data cells

Form inputs must have programmatically associated labels.

Input elements of type='image' must have a descriptive alt attribute.

Authentication flows avoid unnecessary cognitive tests and support assistive mechanisms such as password managers, paste, OTP autofill, and passkeys.

Information already provided earlier in a multi-step flow is auto-populated or available for selection instead of being typed again.

Form fields should have exactly one associated <label> element for maximum clarity.

The accessible name of a control should contain its visible label text.

Users should be able to paste content into form fields to improve usability and reduce errors.

All `<select>` elements must have an associated label or an accessible name to be correctly identified by screen readers.

All buttons must have a discernible, descriptive accessible name for screen readers.

Users are warned before session expiry, can extend time when appropriate, and can re-authenticate or resume work without losing entered data.

Drag and drop interfaces provide keyboard alternatives and proper ARIA attributes for accessibility.

All interactive elements are accessible via keyboard with logical focus order and hidden elements excluded from tab sequence.

Focus is programmatically managed during dynamic interactions like modals, page transitions, and content updates.

Sticky headers, footers, banners, and overlays must not fully hide the element that currently has keyboard focus.

Tab focus order follows the visual layout and logical reading sequence of the page.

A skip navigation link is provided to allow keyboard users to bypass repetitive content and navigate directly to main content.

Checks for bypass mechanisms for keyboard navigation

Form fields do not use the autofocus attribute which can disorient screen reader users and cause unexpected page behavior.

Audio and video content does not autoplay, or provides immediate controls to pause or stop playback.

Prerecorded video with audio must have synchronized captions. Live video must have real-time captions. This is required by WCAG 2.1 SC 1.2.2 and SC 1.2.4.

Videos with important visual content include audio descriptions that narrate visual information for blind users.

When help or support mechanisms appear on multiple pages in the same flow, they stay in the same relative order so users can find them predictably.

Pages must be tested with actual screen reader software (NVDA, JAWS, VoiceOver, TalkBack) to verify announcements, focus order, and widget behavior beyond what automated tools can detect.

Content reflows when zoomed to 400% without requiring horizontal scrolling or loss of functionality.

Text and background colors must have sufficient contrast to be readable by users with low vision or color blindness.

Content and functionality work in both portrait and landscape unless a specific orientation is essential to the activity.

Text can be resized up to 200% without loss of content or functionality using browser settings.

Checks that accesskey values are unique to avoid shortcut conflicts.

iframes and frames must have a title attribute to describe their content.

The lang and xml:lang attributes on the html element must have identical values to avoid conflicting language signals across HTML and XML parsers.

Links with the same text must point to the same destination or be distinguishable.

Each page must have one and only one main landmark.

Proper landmark regions (main, nav, footer) help users navigate the page more efficiently.

Links within blocks of text must be distinguishable from surrounding non-link text by more than color alone.

Meta refresh redirects can disorient users and cause accessibility issues by refreshing the page unexpectedly.

The `<object>` element must contain alternative content to ensure accessibility for users who cannot view the primary content.

Checks for appropriate tabindex values

Interactive elements must have large enough touch targets so users with motor impairments can activate them accurately on touchscreen devices.

Alternative text should not contain redundant words like 'image' or 'photo'.

Real text is used instead of images containing text, except for logos or when specific visual presentation is essential.