T09 · Insecure Skill Coding Practices
- Location
index.ts:286- Finding
Accessibility Audit Returns False Compliance Results Without Inspecting the Target
- Content
View full analysis
{ // Simulated audit - in real implementation would use browser automation const results = await this.wcagEngine.testAll({}); const keyboardResults = await this.keyboardTester.test({}); const passed = results.filter((r) => r.status === 'pass').length; const failed = results.filter((r) => r.status === 'fail').length; const score = Math.round((passed / results.length) * 100); return { summary: { score, level: failed === 0 ? 'AAA' : failed <= 2 ? 'AA' : 'A', passed, failed, warnings: 0, }, principles: { perceivable: { score: 100, issues: [] }, operable: { score: 100, issues: [] }, understandable: { score: 100, issues: [] }, robust: { score: 100, issues: [] }, }, issues: { critical: results.filter((r) => r.severity === 'critical'), serious: results.filter((r) => r.severity === 'serious'), moderate: results.filter((r) => r.severity === 'moderate'), minor: results.filter((r) => r.severity === 'minor'), }, compliance: { wcag21A: failed === 0, wcag21AA: failed === 0, wcag21AAA: failed === 0, }, }; } } ``` Supporting fail-open behavior appears in `index.ts:92-99`, where the non-text-content rule starts with an empty collection instead of reading the supplied context: ```typescript async testNonTextContent(context: any): Promise { const elements: TestElement[] = []; const failingEleme ...[truncated 3547 chars]- Remediation
View remediation
