How the system automatically discovers, tracks, and classifies unknown UI patterns during multi-engine accessibility scans.
This module acts as a lightweight tracking database. It monitors incoming DOM patterns that the analyzer fails to recognize. If an unknown pattern appears frequently enough across the estate, the engine attempts to auto-guess its component type and saves it to a persistent JSON file for future runs.
Step-by-step instructions for reviewing, verifying, and manually editing learned component definitions via the inspector interface.
Access the inspector view to inspect raw DOM snippets and selectors flagged by the tracking database. Review the occurrence count and frequency distribution across your scanned pages.
Examine the engine's preliminary classification. Verify whether the component has been correctly assigned a functional category (e.g., interactive button, modal overlay, or navigation list).
Use the built-in editor controls to manually correct component classifications, refine selector matching rules, or assign custom tags for bespoke design system elements.
Save your verified adjustments directly back to the persistent JSON storage layer, ensuring future audit runs instantly recognize and correctly classify the updated component signatures.
Fundamental building blocks for user interaction, ensuring proper keyboard operability, semantic markup, and clear focus states.
Must use native <button> elements with clear, descriptive accessible names. Avoid
styling generic divs as buttons unless explicit ARIA roles (role="button"), tab indexing, and
keyboard event handlers (Space/Enter) are fully implemented.
Must use native <a href="..."> elements for navigation. Links change page location or
jump to anchors, whereas buttons trigger in-page actions. Ensure link text clearly describes the
destination.
Every form control requires an explicit, associated <label> element using `for`/`id`
association or explicit wrapping, combined with descriptive error messaging and aria-describedby attributes.
Require robust label associations and keyboard toggle support. Custom-styled checkboxes must maintain visible focus rings and preserve native state semantics via ARIA attributes.
Advanced UI patterns requiring precise keyboard trap management, focus containment, and ARIA state management.
Must trap keyboard focus within the modal dialog while open, return focus to the triggering element upon
closure, support Esc-key dismissal, and hide background content using aria-hidden.
Require arrow-key navigation between menu items, ESC-key closure, and proper use of ARIA attributes like
aria-haspopup and aria-expanded to convey state to screen readers.
Utilize header buttons controlling collapsible panels with explicit aria-expanded states and
unique ID linkages via aria-controls for reliable screen reader announcements.
Implement roving tabindex or arrow key navigation across tab headers, with explicit
aria-selected states linking each tab to its corresponding tabpanel region.