Issue Patterns
Recurring bugs detected across all AgentQA scans. Every pattern is fingerprinted, clustered, and enriched with AI root-cause analysis. Use this to spot systemic issues before they spread.
19 unique patterns tracked
Missing H1 Heading
The Angular component template does not include an <h1> element. In Angular, this is typically either missing from the component's HTML template file or not rendered by *ngIf conditional logic that evaluates to false during page load.
1. Add a single <h1> element to the root component template that contains the primary keyword (e.g., 'Blind Matrix - Software Solutions') 2. Ensure the H1 is placed early in the DOM hierarchy (before other heading levels) and is visible on initial page render without conditional *ngIf directives that could prevent rendering 3. Verify the H1 text matches the page's primary topic and meta description for consistency 4. Run a DOM inspection tool or headless browser audit to confirm the H1 element is present and contains text content
Missing Open Graph Image
The Angular application is missing the <meta property="og:image"> tag in the HTML head. Angular applications typically inject meta tags dynamically via the Meta service or statically in index.html; without explicit configuration, the og:image tag is not rendered.
1. Add <meta property="og:image" content="https://blindmatrix.software/assets/og-image-1200x630.png"> to the <head> section of index.html 2. Ensure the og:image asset is 1200×630 pixels and uploaded to the assets directory 3. For dynamic pages, inject the og:image meta tag using Angular's Meta service: this.meta.updateTag({property: 'og:image', content: imageUrl}) 4. Verify the meta tag renders in the DOM using browser DevTools or a social media link preview debugger
Console Errors Detected
Missing Meta Description
The Angular application is not rendering a <meta name="description"> tag in the document head. In Angular, this typically occurs when the MetaService is not injected and used in the root component or when the index.html template lacks a default description element that gets updated by the application.
1. Inject Angular's Meta service into the root AppComponent and call this.meta.updateTag({ name: 'description', content: 'your 150-160 character description' }) in the ngOnInit lifecycle hook 2. Alternatively, add a default <meta name="description" content="..."> tag directly to index.html with a site-wide fallback description 3. For dynamic per-page descriptions, implement the fix in each routed component's ngOnInit using the same Meta.updateTag() pattern 4. Verify the tag renders in the compiled HTML by inspecting the <head> element in the browser's developer tools
Images Missing Alt Text
Broken Images
Images Missing Alt Text
Angular component templates are rendering <img> elements without alt attributes. This likely stems from either missing alt bindings in component templates or a lack of validation in the image component library defaults that should enforce alt attribute presence.
1. Audit all <img> elements in Angular component templates (.html files) and add descriptive alt attributes or alt="" for decorative images 2. If using a shared image component, update its template to require an @Input() alt property and apply it to the <img> alt attribute binding 3. Run an automated accessibility scanner (e.g., axe-core, Pa11y) in the CI/CD pipeline to catch missing alt attributes before deployment 4. Verify the three identified images at https://blindmatrix.software are updated and re-scan to confirm WCAG 2.1 SC 1.1.1 compliance
Console Errors Detected
The Pusher library is instantiated without passing a required app key parameter, causing the Pusher constructor to throw an error. Additionally, AG Grid Enterprise appears to be loaded but may lack a valid license configuration, generating secondary warnings.
1. Locate the Pusher initialization code and pass the app key as a parameter: new Pusher(appKey, {cluster: 'your-cluster'}) instead of new Pusher() with no arguments 2. Verify the app key is defined in your environment configuration (environment.ts or environment.prod.ts) and is not null or undefined before instantiation 3. If using AG Grid Enterprise, ensure a valid license key is provided via agLicenseKey module configuration or gridOptions.licenseKey property 4. Add null/undefined checks before instantiating third-party libraries and wrap initialization in try/catch blocks to prevent unhandled errors during page load
Broken Images
Broken Images
Images Missing Alt Text
Broken Images
Console Errors Detected
Multiple Console Warnings
Mobile Layout Overflow
A child element or container on /sales exceeds the viewport width (375px) without proper responsive constraints. The element's computed width or padding/margin values exceed 100vw or the parent container's max-width is not constrained to the viewport.
1. Audit the page layout using DevTools at 375px viewport; identify which element(s) overflow by checking computed width and max-width properties in the CSS cascade. 2. Apply max-width: 100% and overflow-x: hidden to overflowing container; verify no child elements use fixed pixel widths that exceed 375px minus padding. 3. Ensure the viewport meta tag is present and correctly configured: <meta name="viewport" content="width=device-width, initial-scale=1">. 4. Test at 375px in Chrome DevTools device emulation to confirm horizontal scroll is eliminated.