Analyze UX Heuristics (Not [#2](https://github.com/CyberSpaceEsli/react-ux-analyzer/issues/2) & [#8](https://github.com/CyberSpaceEsli/react-ux-analyzer/issues/8)) |
Run all main heuristics at once (excludes #2 & #8). |
Analyze Breadcrumbs (Nielsen [#1](https://github.com/CyberSpaceEsli/react-ux-analyzer/issues/1): Visibility & System Status) |
Check for missing breadcrumb navigation. |
Analyze Loading States (Nielsen [#1](https://github.com/CyberSpaceEsli/react-ux-analyzer/issues/1): Visibility & System Status) |
Detect missing loading UI elements. |
Analyze Match System with Real World (Nielsen [#2](https://github.com/CyberSpaceEsli/react-ux-analyzer/issues/2): Match Between System & Real World) |
Flag unclear or jargon-heavy terminology. |
Analyze Control Exits (Nielsen [#3](https://github.com/CyberSpaceEsli/react-ux-analyzer/issues/3): User Control & Freedom) |
Ensure modals and destructive actions have exits or undos. |
Analyze Page Consistency (Nielsen [#4](https://github.com/CyberSpaceEsli/react-ux-analyzer/issues/4): Consistency & Standards) |
Ensure consistencies troughout components. |
Analyze Error Prevention (Nielsen [#5](https://github.com/CyberSpaceEsli/react-ux-analyzer/issues/5): Error Prevention) |
Check for error handling with fetch/axios and cancel option for destructive text in modals. |
Analyze Recognition Cues (Nielsen [#6](https://github.com/CyberSpaceEsli/react-ux-analyzer/issues/6): Recognition Rather Than Recall) |
Identify missing placeholders of labels and overloaded navigations. |
Analyze Shortcuts (Nielsen [#7](https://github.com/CyberSpaceEsli/react-ux-analyzer/issues/7): Flexibility & Efficiency of Use) |
Detect keyboard shortcuts missing UI display. |
Analyze Aesthetic & Minimalist Design (Nielsen [#8](https://github.com/CyberSpaceEsli/react-ux-analyzer/issues/8): Aesthetic & Minimalist Design) |
Scan color overload and whitespace ratios. |
Analyze Help for Error Recognition (Nielsen [#9](https://github.com/CyberSpaceEsli/react-ux-analyzer/issues/9): Help Users Recognize, Diagnose, and Recover from Errors) |
Check for technical error messages and missing styling. |
Analyze Help and Documentation (Nielsen [#10](https://github.com/CyberSpaceEsli/react-ux-analyzer/issues/10): Help & Documentation) |
Detect missing help/support links or onboarding actions. |
Analyze Visual Quality (NIMA) |
Capture screenshot and score UI quality from NIMA. |
Analyze Custom UX Rules |
Run your own detectors. |