AI Prompts for Inclusive Design

You are designing and building a digital product for Deaf users, including those who identify as part of the Deaf community.

Review the interface and:
- Identify every instance where audio is the sole means of conveying information
- Ensure captions are available, accurate, and synchronized for all video and audio content
- Replace audio-only alerts with persistent visual equivalents
- Eliminate voice-only verification or authentication steps
- Ensure meeting and video transcripts are available, not just captions
- Validate WCAG 2.2 AA compliance for 1.2.1, 1.2.2, 1.2.4, and 1.4.2

Return:
1. Audio-only barriers and their visual alternatives
2. Caption and transcript implementation recommendations
3. Visual alert and notification patterns
4. Engineering fixes for audio-dependent interactions

You are designing and building a digital product for hard of hearing users.

Review the interface and:
- Identify audio content that lacks accurate captions or transcripts
- Ensure volume controls are keyboard accessible and clearly labeled
- Replace sound-only notifications with visible, persistent visual alerts
- Provide transcripts for all meeting and collaborative audio content
- Avoid auto-playing audio without user control
- Validate WCAG 2.2 AA compliance for 1.2.1, 1.2.2, and 1.4.2

Return:
1. Audio accessibility gaps and visual equivalents
2. Caption quality and transcript availability improvements
3. Notification and alert design recommendations
4. Engineering patterns for audio-independent interactions

You are designing and building a digital product for users in environments where audio cannot be relied upon.

Review the interface and:
- Identify every interaction that depends on audio feedback or sound alerts
- Ensure all confirmations, errors, and status updates are conveyed visually
- Provide captions and transcripts for all audio and video content
- Ensure critical actions do not require the user to hear a prompt or response
- Support silent or vibration notification modes
- Validate WCAG 2.2 AA compliance for 1.2.1, 1.2.2, and 1.4.2

Return:
1. Audio-dependent interaction risks
2. Visual feedback and alert patterns
3. Caption and transcript recommendations
4. Engineering fixes for sound-reliant flows

You are designing and building a digital product for people experiencing brain fog, a symptom associated with conditions including Long COVID, fibromyalgia, and chronic fatigue.

Review the interface and:
- Identify flows that require sustained concentration or multi-step memory
- Simplify navigation to reduce the number of decisions required per screen
- Use plain, direct language with no jargon or implied knowledge
- Provide clear visual markers for current position within a workflow
- Support autosave and allow users to resume incomplete tasks easily
- Avoid timed sessions or interactions that punish slow response
- Validate WCAG 2.2 AA compliance for 2.2.1, 3.1.5, and 3.3.1

Return:
1. Cognitive load and complexity risks
2. Navigation simplification recommendations
3. Autosave and task resumption patterns
4. Engineering fixes for time-sensitive or memory-dependent interactions

You are designing and building a digital product to reduce cognitive overload across all users, particularly in high-stakes financial contexts.

Review the interface and:
- Identify screens with excessive information density or too many simultaneous choices
- Apply progressive disclosure to surface only what is needed at each step
- Use clear visual hierarchy with headings, spacing, and grouping to guide attention
- Reduce the number of decisions required per screen to the minimum necessary
- Provide clear confirmation before irreversible actions
- Ensure error recovery is straightforward and does not require restarting
- Validate WCAG 2.2 AA compliance for 1.3.1, 2.4.6, and 3.3.1

Return:
1. Information density and decision complexity risks
2. Progressive disclosure and hierarchy improvements
3. Error prevention and recovery patterns
4. Engineering recommendations for simplified, focused layouts

You are designing and building a digital product for people with learning disabilities.

Review the interface and:
- Identify financial or technical terminology that lacks plain language explanation
- Break multi-step processes into single, clearly sequenced tasks
- Provide visual cues and icons that reinforce written instructions
- Avoid multi-column layouts that disrupt linear reading order
- Support adjustable reading pace with no timed interactions
- Ensure error messages explain what went wrong and how to fix it in plain terms
- Validate WCAG 2.2 AA compliance for 3.1.3, 3.1.5, 3.3.1, and 3.3.2

Return:
1. Language and complexity barriers
2. Step sequencing and layout improvements
3. Plain language and visual support recommendations
4. Engineering patterns for paced, linear task flows

You are designing and building a digital product for people with memory loss.

Review the interface and:
- Identify steps that require users to recall information from earlier in the flow
- Ensure autosave is present throughout all multi-step workflows
- Provide visible progress indicators showing where the user is and what remains
- Display previously entered information as confirmation before submission
- Avoid session timeouts that clear form data without warning
- Support re-entry minimization by pre-filling known information
- Validate WCAG 2.2 AA compliance for 3.3.1, 3.3.4, and 3.3.7

Return:
1. Memory-dependent interaction risks
2. Autosave and progress indicator patterns
3. Session and data persistence recommendations
4. Engineering implementation for re-entry minimization

You are designing and building a digital product for users in bright light or high-glare environments.

Review the interface and:
- Identify text and UI elements that rely on low contrast or subtle color differences
- Ensure all text meets WCAG AA contrast ratios and ideally targets AAA for body text
- Support high contrast mode and dark mode as first-class display options
- Avoid light gray on white and other low-contrast combinations throughout the UI
- Use bold, legible typography at sufficient size for outdoor readability
- Ensure interactive elements are distinguishable without relying on subtle visual cues
- Validate WCAG 2.2 AA compliance for 1.4.3, 1.4.6, and 1.4.11

Return:
1. Contrast and visibility risks in bright conditions
2. High contrast and dark mode implementation patterns
3. Typography and color recommendations
4. Engineering fixes for glare-resilient UI

You are designing and building a digital product for users on constrained devices including older phones, low-memory hardware, and small screens.

Review the interface and:
- Identify JavaScript-heavy interactions that fail or degrade on low-memory devices
- Optimize image and asset loading for slow processors and limited storage
- Ensure all core tasks are completable on small screens without horizontal scrolling
- Avoid animations and visual effects that consume CPU or GPU resources unnecessarily
- Test responsive layouts at 320px minimum viewport width
- Provide a functional baseline experience that works without the latest browser features
- Validate WCAG 2.2 AA compliance for 1.4.4, 1.4.10, and 2.5.5

Return:
1. Performance and rendering risks on constrained devices
2. Asset optimization and loading strategies
3. Responsive layout recommendations
4. Engineering fixes for lightweight, progressive experiences

You are designing and building a digital product that must be safe for people with photosensitive epilepsy.

Review the interface and:
- Identify any content that flashes more than 3 times per second
- Remove or replace all strobing, flickering, or rapidly cycling visual elements
- Ensure animated content defaults to off or reduced and can be fully disabled
- Apply the prefers-reduced-motion media query as a default safe state, not an opt-in
- Avoid large areas of high-contrast flashing, particularly red
- Test all animated components against WCAG photosensitivity thresholds
- Validate WCAG 2.2 AA compliance for 2.3.1 and AAA compliance for 2.3.2

Return:
1. Seizure risk elements and their frequency
2. Safe animation defaults and removal patterns
3. Testing methodology for photosensitive content
4. Engineering implementation for flash-safe UI

You are designing and building a digital product for users experiencing situational fatigue due to exhaustion, illness, caregiving, or burnout.

Review the interface and:
- Identify workflows that require sustained effort or cannot be paused and resumed
- Implement autosave throughout all multi-step tasks
- Break long forms into shorter, clearly labeled sections
- Minimize required inputs by pre-filling or inferring known information
- Provide forgiving error recovery that does not clear previously entered data
- Reduce the number of steps needed to complete high-frequency tasks
- Validate WCAG 2.2 AA compliance for 2.2.1, 3.3.1, and 3.3.7

Return:
1. Effort and complexity barriers
2. Autosave and task resumption patterns
3. Input minimization and pre-fill recommendations
4. Engineering fixes for low-effort, recoverable workflows

You are designing and building a digital product for users with low bandwidth or unstable internet connections.

Review the interface and:
- Identify resources that block rendering or require large downloads before interaction is possible
- Implement progressive loading so core content and actions are available immediately
- Provide graceful degradation when assets fail to load
- Avoid auto-loading video, large images, or non-essential scripts on page entry
- Support offline or cached states for key tasks where feasible
- Ensure session timeouts are generous and data is preserved if a connection drops
- Validate WCAG 2.2 AA compliance for 2.2.1 and performance best practices

Return:
1. Render-blocking and heavy asset risks
2. Progressive loading and degradation patterns
3. Offline and retry state recommendations
4. Engineering fixes for bandwidth-resilient experiences

You are designing and building a digital product for users with low literacy needs.

Review the interface and:
- Identify content written above a Grade 8 reading level
- Rewrite instructions, labels, and error messages in plain, direct language
- Support text-to-speech for all content including form labels and error messages
- Replace jargon and financial terminology with plain equivalents or include clear definitions
- Use icons and visual cues alongside text to reinforce meaning
- Structure content in short sentences with one idea per sentence
- Validate WCAG 2.2 AA compliance for 3.1.3, 3.1.5, and 3.3.2

Return:
1. Reading complexity and jargon risks
2. Plain language rewrite recommendations
3. Visual support and iconography patterns
4. Engineering fixes for readable, scannable content

You are designing and building a digital product for people with migraine sensitivity.

Review the interface and:
- Identify flashing content, flickering elements, and high-frequency visual patterns
- Support dark mode and low-brightness display options
- Avoid stark white backgrounds and high-contrast strobing patterns
- Minimize required steps so tasks can be completed during limited screen time
- Ensure all motion respects the prefers-reduced-motion media query
- Avoid bright color combinations that create visual vibration
- Validate WCAG 2.2 AA compliance for 2.3.1 and 2.3.3

Return:
1. Visual trigger risks
2. Dark mode and low-stimulation design patterns
3. Task efficiency improvements for limited screen time
4. Engineering fixes for flicker and high-contrast motion

You are designing and building a digital product for people with motion sensitivity, including those with vestibular disorders, migraine, or anxiety triggered by screen motion.

Review the interface and:
- Identify all animations, transitions, parallax effects, and auto-playing motion
- Ensure the prefers-reduced-motion media query disables or reduces all non-essential motion
- Replace motion-based feedback with static visual alternatives
- Avoid auto-playing carousels and looping animations
- Provide user controls to pause or disable motion independently of system settings
- Validate WCAG 2.2 AA compliance for 2.3.3 and 2.2.2

Return:
1. Motion and animation risks
2. Reduced-motion implementation patterns
3. Static alternative feedback designs
4. Engineering fixes using prefers-reduced-motion

You are designing and building a digital product for users whose primary language differs from the product's default language.

Review the interface and:
- Identify idioms, culturally specific references, and financial jargon with no plain equivalent
- Ensure all UI labels, error messages, and instructions translate accurately without truncation
- Set the correct lang attribute on the HTML element and on any language-specific content
- Avoid relying on culturally specific metaphors or expressions in microcopy
- Test layouts with translated strings, which are often significantly longer than English
- Support right-to-left text rendering where relevant
- Validate WCAG 2.2 AA compliance for 3.1.1 and 3.1.2

Return:
1. Language and localization risks
2. Translation-safe label and microcopy patterns
3. Layout recommendations for variable text length
4. Engineering fixes for multilingual and RTL support

You are designing and building a digital product for users operating with one hand, whether due to a permanent condition, temporary injury, or situational constraint.

Review the interface and:
- Identify interactions requiring simultaneous inputs, two-finger gestures, or both hands
- Position primary actions within the thumb-reachable zone for single-handed mobile use
- Provide single-tap or single-key alternatives for every multi-input interaction
- Ensure all gestures have a single-point activation alternative
- Avoid long-press as the only trigger for important actions
- Test all critical flows using only one finger on a mobile device
- Validate WCAG 2.2 AA compliance for 2.5.1 and 2.5.4

Return:
1. Two-handed interaction risks
2. Thumb-zone and single-tap design patterns
3. Gesture alternative recommendations
4. Engineering fixes for single-input operability

You are designing and building a digital product for users with a temporary injury affecting their ability to use standard input methods.

Review the interface and:
- Ensure all tasks are completable using keyboard only, voice control, or a single pointing device
- Identify interactions that assume standard two-handed or fine motor input
- Provide clear onboarding for alternative input methods without requiring prior experience
- Avoid reliance on drag-and-drop, multi-key shortcuts, or precise pointer interactions
- Ensure focus order is logical and all interactive elements are reachable by Tab
- Test all critical flows without a mouse using keyboard and voice navigation only
- Validate WCAG 2.2 AA compliance for 2.1.1, 2.1.2, and 2.5.1

Return:
1. Input dependency risks for users without fine motor control
2. Keyboard and voice navigation patterns
3. Alternative input onboarding recommendations
4. Engineering fixes for mouse-independent task completion

You are designing and building a digital product for people with anxiety, particularly in high-stakes financial contexts.

Review the interface and:
- Identify error messages that use alarming, urgent, or ambiguous language
- Ensure every destructive or irreversible action requires explicit confirmation
- Provide clear feedback after every user action so the system state is always known
- Avoid unexpected system behavior, modal interruptions, or surprise redirects
- Use calm, plain, non-threatening language throughout all system messages
- Ensure undo is available wherever possible for actions that feel high-risk
- Validate WCAG 2.2 AA compliance for 3.3.1, 3.3.4, and 3.2.1

Return:
1. Alarming language and uncertainty risks
2. Confirmation and feedback pattern recommendations
3. Calm microcopy and error message rewrites
4. Engineering fixes for predictable, low-pressure interactions

You are designing and building a digital product for people with bipolar disorder whose interaction needs shift across depressive and manic episodes.

Review the interface and:
- Require explicit confirmation for all high-value or irreversible financial actions
- Provide undo or reversal options wherever technically feasible
- Break complex workflows into small, manageable steps accessible during low-energy states
- Avoid design patterns that encourage rapid sequential decisions without pause points
- Do not require users to self-disclose or identify their current state to access support features
- Ensure autosave protects partially completed work during session interruption
- Validate WCAG 2.2 AA compliance for 2.2.1, 3.3.4, and 3.2.2

Return:
1. Impulsivity and irreversibility risks
2. Confirmation and undo implementation patterns
3. Low-effort workflow recommendations for depressive states
4. Engineering guardrails for high-stakes financial actions

You are designing and building a digital product for people with depression, where motivation and energy to complete tasks may be significantly reduced.

Review the interface and:
- Identify workflows that require more steps than necessary to complete a core task
- Implement autosave so incomplete sessions can be resumed without data loss
- Show visible progress indicators throughout all multi-step flows
- Pre-fill known information to minimize repeated data entry
- Use plain, encouraging language that does not shame errors or abandoned sessions
- Avoid dark patterns that add friction or require extra effort to complete a task
- Validate WCAG 2.2 AA compliance for 2.2.1, 3.3.1, and 3.3.7

Return:
1. Effort and motivation barriers
2. Progress and autosave implementation patterns
3. Encouraging microcopy recommendations
4. Engineering fixes for streamlined, low-effort task completion

You are designing and building a digital product for people with panic disorder.

Review the interface and:
- Remove or replace countdown timers and urgency-inducing UI patterns
- Ensure every screen has a clear, visible exit or back path
- Use calm, measured language in all system messages, errors, and confirmations
- Avoid high-density screens that present many options or warnings simultaneously
- Never use language that implies irreversible consequences without a confirmation step
- Provide session extension options before any timeout rather than abrupt termination
- Validate WCAG 2.2 AA compliance for 2.2.1, 2.2.4, and 3.3.4

Return:
1. Urgency and pressure trigger risks
2. Calm interaction and exit pattern recommendations
3. Microcopy tone and language improvements
4. Engineering fixes for low-pressure, escapable flows

You are designing and building a digital product using trauma-informed design principles for people managing sobriety and recovery from substance use.

Review the interface and:
- Identify content that uses shame-based, urgent, or high-pressure language around finances
- Ensure debt notices, overdue alerts, and upsell prompts are delivered calmly and constructively
- Avoid normalizing alcohol or substance use in imagery, language, or promotional content
- Provide clear, calm error recovery that does not amplify stress or assign blame
- Design notification timing and frequency to avoid overwhelming users during vulnerable moments
- Support user control over when and how sensitive financial information is surfaced
- Reference Intuit trauma-informed design principles throughout

Return:
1. Stress trigger and shame language risks
2. Calm, constructive communication patterns
3. Content sensitivity recommendations
4. Engineering controls for user-managed sensitive content display

You are designing and building a digital product for people with ADHD.

Review the interface and:
- Identify autoplay media, ambient animations, and visual noise that compete for attention
- Provide clear progress indicators that show current position and remaining steps
- Break tasks into short, focused steps with one primary action per screen
- Ensure transcripts are available for all video and meeting content for self-paced review
- Implement autosave so interrupted sessions can be resumed without penalty
- Use clear visual hierarchy to direct focus to the most important action on each screen
- Validate WCAG 2.2 AA compliance for 2.2.2, 2.4.6, and 3.3.1

Return:
1. Distraction and attention fragmentation risks
2. Focus and progress indicator patterns
3. Transcript and self-paced content recommendations
4. Engineering fixes for low-distraction, resumable workflows

You are designing and building a digital product for Autistic users.

Review the interface and:
- Identify ambiguous labels, vague calls to action, and microcopy that implies rather than states
- Ensure every action clearly communicates what will happen before the user commits
- Remove unexpected modal interruptions, layout shifts, and autoplay animations
- Use literal, direct language throughout and avoid idioms, metaphors, or implied social norms
- Maintain consistent navigation, layout, and interaction patterns across all screens
- Provide advance warning before any action that changes the current state significantly
- Validate WCAG 2.2 AA compliance for 2.2.2, 3.2.1, 3.2.2, and 3.3.2

Return:
1. Ambiguity, unpredictability, and sensory risks
2. Literal language and clear action pattern recommendations
3. Layout consistency and predictability improvements
4. Engineering fixes for warning-first, stable interfaces

You are designing and building a digital product for people with dyslexia.

Review the interface and:
- Identify justified text, small fonts, tight line spacing, and dense text blocks
- Use left-aligned text, generous line height, and adequate letter spacing throughout
- Support text-to-speech for all content including labels, instructions, and error messages
- Break content into short paragraphs with clear headings and white space between sections
- Avoid italics for body text and use underline only for links, not emphasis
- Ensure font size meets minimum requirements and is scalable without layout breakage
- Validate WCAG 2.2 AA compliance for 1.4.4, 1.4.8, and 1.4.12

Return:
1. Typography and reading difficulty risks
2. Font, spacing, and layout improvement recommendations
3. Text-to-speech support patterns
4. Engineering fixes for dyslexia-friendly reading environments

You are designing and building a digital product for people managing acute pain who need to complete tasks quickly with minimal physical effort.

Review the interface and:
- Identify flows requiring sustained fine motor input, extended session time, or repeated actions
- Minimize the number of interactions required to complete each core task
- Ensure all interactions are operable by keyboard or voice with no mouse dependency
- Provide large, well-spaced touch targets that reduce precision requirements
- Implement autosave so sessions can be abandoned and resumed without loss
- Prioritize task efficiency over feature richness on critical paths
- Validate WCAG 2.2 AA compliance for 2.1.1, 2.5.5, and 2.5.8

Return:
1. Fine motor and effort barriers
2. Task efficiency and input minimization patterns
3. Large target and keyboard navigation recommendations
4. Engineering fixes for low-effort, pain-tolerant interactions

You are designing and building a digital product for people with chronic fatigue conditions including ME/CFS, multiple sclerosis, and lupus.

Review the interface and:
- Identify workflows that cannot be paused, saved, and resumed across multiple sessions
- Implement autosave as a default throughout all multi-step tasks
- Minimize required inputs by pre-filling known data and reducing redundant steps
- Avoid session timeouts that clear form data without prior warning and save option
- Provide clear progress indicators so users know how much effort remains
- Ensure all core tasks are completable in the fewest possible steps
- Validate WCAG 2.2 AA compliance for 2.2.1, 3.3.7, and 3.3.1

Return:
1. Energy and effort barrier risks
2. Autosave and session resumption patterns
3. Input minimization and pre-fill recommendations
4. Engineering fixes for energy-efficient, resumable workflows

You are designing and building a digital product for people with limited dexterity due to tremors, reduced grip strength, or restricted hand movement.

Review the interface and:
- Identify touch targets smaller than 44x44px and increase them to meet minimum size requirements
- Remove drag-and-drop as the only method for any interaction and provide button alternatives
- Eliminate hover-only menus and ensure all content is accessible without hover
- Remove time limits on interactions or provide generous extension options
- Implement undo for all destructive or hard-to-reverse actions
- Ensure accidental activation of adjacent targets does not cause irreversible actions
- Validate WCAG 2.2 AA compliance for 2.5.5, 2.5.8, 2.2.1, and 2.5.2

Return:
1. Small target and precision interaction risks
2. Touch target sizing and spacing recommendations
3. Drag-and-drop alternative patterns
4. Engineering fixes for forgiving, error-tolerant input

You are designing and building a digital product for people with limb loss who rely on voice input, switch access, or single-handed keyboard navigation.

Review the interface and:
- Identify multi-key shortcuts, two-handed gestures, and simultaneous input requirements
- Ensure all tasks are fully operable using keyboard only or voice control alone
- Replace drag-and-drop interactions with keyboard-accessible alternatives
- Test all critical flows using a single input device including switch access simulation
- Ensure focus order is logical and all interactive elements are reachable without a mouse
- Provide voice control labels for all interactive elements that match their visible label
- Validate WCAG 2.2 AA compliance for 2.1.1, 2.1.2, 2.5.1, and 2.5.3

Return:
1. Multi-input and two-handed interaction risks
2. Single-input and voice navigation patterns
3. Switch access and keyboard-only flow recommendations
4. Engineering fixes for fully single-input operable interfaces

You are designing and building a digital product for people with paralysis who rely on eye tracking, switch access, voice control, or head pointer devices.

Review the interface and:
- Ensure every interaction is fully operable without a mouse or touchscreen
- Verify logical, efficient focus order across all interactive elements
- Test all flows using switch access simulation with single and dual switch modes
- Ensure focus indicators are clearly visible and meet WCAG 2.2 AA contrast requirements
- Avoid keyboard traps and ensure users can always navigate forward and backward
- Minimize the number of Tab stops required to reach critical actions
- Validate WCAG 2.2 AA compliance for 2.1.1, 2.1.2, 2.4.3, 2.4.7, and 2.4.11

Return:
1. Mouse and touch dependency risks
2. Focus order and keyboard navigation patterns
3. Switch access and eye tracking compatibility recommendations
4. Engineering fixes for fully alternative-input operable interfaces

You are designing and building a digital product for people with aphasia who have difficulty producing, retrieving, or organizing language.

Review the interface and:
- Identify free-text input fields and replace or supplement them with structured options where possible
- Use short, simple sentences for all labels, instructions, and error messages
- Reinforce all text labels with icons to reduce language processing load
- Avoid open-ended text entry as the only method for completing a task
- Support AAC device compatibility by ensuring all interactive elements have accessible names
- Provide ample time for input with no session timeouts on forms
- Validate WCAG 2.2 AA compliance for 2.2.1, 3.1.3, 3.1.5, and 3.3.2

Return:
1. Language production and input barriers
2. Structured input alternative patterns
3. Icon reinforcement and plain language recommendations
4. Engineering fixes for low-text, AAC-compatible interactions

You are designing and building a digital product for people with speech disabilities including stuttering, dysarthria, and selective mutism.

Review the interface and:
- Identify every voice-dependent interaction including authentication, commands, and input fields
- Provide a text or keyboard alternative for every voice interaction at equal prominence
- Do not use voice recognition as the sole method for authentication or verification
- Ensure AI assistants and voice features fail gracefully with a clear non-voice fallback
- Avoid penalizing slow, interrupted, or atypical speech patterns in voice recognition systems
- Test voice input features with non-standard speech patterns where possible
- Validate WCAG 2.2 AA compliance for 2.1.1 and 3.3.2

Return:
1. Voice-only dependency risks
2. Text and keyboard alternative patterns
3. Authentication fallback recommendations
4. Engineering fixes for speech-independent task completion

You are designing and building a digital product for Blind users who navigate entirely without visual reference using screen readers, Braille displays, and keyboard navigation.

Review the interface and:
- Ensure every interactive element has a descriptive, meaningful accessible name
- Provide alt text for all images, icons, and non-text content
- Verify logical reading and focus order that reflects visual layout intent
- Use semantic HTML elements so screen readers can communicate structure correctly
- Ensure all functionality is operable by keyboard with no mouse dependency
- Provide transcripts for all video and audio content as a navigation-friendly alternative
- Validate WCAG 2.2 AA compliance for 1.1.1, 1.3.1, 2.1.1, 2.4.3, and 4.1.2

Return:
1. Screen reader and keyboard navigation barriers
2. Semantic structure and alt text recommendations
3. Focus order and ARIA implementation patterns
4. Engineering fixes for fully non-visual task completion

You are designing and building a digital product for people with cataracts who experience reduced contrast sensitivity and increased glare.

Review the interface and:
- Identify text and UI elements that fall below WCAG AA contrast thresholds
- Avoid pure white backgrounds and consider off-white or light gray base colors to reduce glare
- Use bold, legible fonts at sufficient size with adequate line spacing
- Provide a high-contrast mode that significantly increases contrast ratios throughout
- Ensure thin icon strokes and light UI borders are thickened for visibility
- Support dark mode as an alternative to bright backgrounds
- Validate WCAG 2.2 AA compliance for 1.4.3, 1.4.6, and 1.4.11

Return:
1. Contrast and glare risks
2. Typography and contrast improvement recommendations
3. High contrast and dark mode implementation patterns
4. Engineering fixes for glare-reduced, high-legibility interfaces

You are designing and building a digital product for people with color blindness including red-green, blue-yellow, and monochromacy variants.

Review the interface and:
- Identify every instance where color is the sole means of conveying information
- Add text labels, icons, or patterns alongside all color-coded status indicators
- Ensure error and success states are distinguishable without relying on red and green alone
- Test all data visualizations, charts, and graphs using a color blindness simulator
- Verify that form validation, alerts, and required field indicators use non-color cues
- Check that link text is distinguishable from body text by more than color alone
- Validate WCAG 2.2 AA compliance for 1.4.1 and 1.4.3

Return:
1. Color-only information risks
2. Pattern, label, and icon alternative recommendations
3. Data visualization accessible color patterns
4. Engineering fixes for color-independent status communication

You are designing and building a digital product for people with glaucoma who have reduced or absent peripheral vision.

Review the interface and:
- Identify critical actions, alerts, and error messages positioned at screen edges
- Move primary navigation, calls to action, and error indicators to the central visual zone
- Avoid placing time-sensitive notifications only in peripheral screen locations
- Ensure toast notifications and inline errors are positioned centrally or announced by screen reader
- Test all critical flows by masking peripheral screen areas to simulate tunnel vision
- Ensure screen reader announcements provide equivalent access to peripherally placed content
- Validate WCAG 2.2 AA compliance for 1.3.1, 1.4.3, and 4.1.3

Return:
1. Peripheral placement risks for critical content
2. Central zone layout and alert positioning recommendations
3. Screen reader announcement patterns for edge-placed content
4. Engineering fixes for central-vision-friendly interface layout

You are designing and building a digital product for low vision users who rely on magnification, high contrast settings, and scalable text.

Review the interface and:
- Ensure all layouts reflow correctly at 400% zoom without horizontal scrolling
- Use relative units for font sizes so text scales with user browser settings
- Verify all text meets WCAG AA contrast ratios and test at AAA for body text
- Ensure all icons have visible text labels and are not the sole means of conveying action
- Test the interface using browser zoom and OS magnification tools at multiple levels
- Support high contrast mode without loss of content or functionality
- Validate WCAG 2.2 AA compliance for 1.4.3, 1.4.4, 1.4.10, and 1.4.11

Return:
1. Zoom, reflow, and contrast risks
2. Scalable layout and text resizing patterns
3. Icon labeling and high contrast mode recommendations
4. Engineering fixes for magnification-compatible interfaces

You are designing and building a digital product for people experiencing temporary blindness due to surgery, injury, or medical treatment, many of whom are using a screen reader for the first time.

Review the interface and:
- Ensure all tasks are completable by keyboard and screen reader without prior experience
- Provide clear, consistent heading structure that allows screen reader navigation by heading
- Ensure focus indicators are visible and focus order is logical throughout
- Avoid custom interaction patterns that deviate from expected screen reader behavior
- Test all critical flows using a screen reader in browse mode and forms mode
- Provide transcripts as an alternative to audio and video for users new to screen readers
- Validate WCAG 2.2 AA compliance for 1.3.1, 2.1.1, 2.4.3, 2.4.6, and 4.1.2

Return:
1. First-time screen reader experience barriers
2. Heading structure and keyboard navigation patterns
3. Onboarding and discoverability recommendations for assistive technology
4. Engineering fixes for standard, predictable screen reader behavior

You are designing and building a digital product for people with visual field loss, including central, peripheral, and patchy field damage.

Review the interface and:
- Identify error messages, tooltips, and status updates placed outside the central content area
- Ensure all critical feedback is positioned adjacent to the triggering element and announced by screen reader
- Avoid relying on peripheral screen locations for time-sensitive or error-state content
- Test all form validation patterns to confirm errors appear in the user's likely focus zone
- Provide screen reader announcements as a redundant channel for all visual feedback
- Avoid requiring users to scan the full screen to confirm an action was successful
- Validate WCAG 2.2 AA compliance for 1.3.1, 3.3.1, 3.3.3, and 4.1.3

Return:
1. Out-of-field content placement risks
2. Inline error and feedback positioning patterns
3. Screen reader announcement recommendations for visual feedback
4. Engineering fixes for field-loss-tolerant content placement