TechnicalCollectible prompt

Web accessibility audit against WCAG 2.2

Find accessibility barriers in a page or component and get code-level fixes.

ClaudeChatGPTCursor

Curated by Nvoka

Nvoka wordmark logo
Nvoka wordmark logoTechnical

Web accessibility audit against WCAG 2.2

Act as a web accessibility specialist. Audit {{page_or_component}} against WCAG 2.2 level AA. Here is the code or a detailed description: {{page_code_or_description}} Check headings and landmarks, accessible names for controls, keyboard access and focus order, visible focus, color contrast, text alternatives, form labels and error messages, motion and timing, zoom to 200 percent, reflow at 320px width, target size, announcements for content that updates, and the page language attribute. Return a table with columns: issue, WCAG success criterion, who is affected, severity, and the fix with corrected code. Then list the three changes with the biggest impact. Finish with what can't be confirmed from code alone and needs manual testing with a keyboard, a screen reader, or disabled users. Don't call the page compliant; a review like this can find issues but can't certify it.
Technicalnvoka.com/library/nvoka-wcag-accessibility-auditScan to open
Technical

Web accessibility audit against WCAG 2.2

Find accessibility barriers in a page or component and get code-level fixes.

Nvoka logo

Curated by Nvoka

ClaudeChatGPTCursor
Add to my library

Make it yours

Fill in the blanks and change any word. Only your copy changes, never the card.

Fill in the blanks

0 of 2 filled

Your prompt

Act as a web accessibility specialist. Audit {{page_or_component}} against WCAG 2.2 level AA. Here is the code or a detailed description: {{page_code_or_description}} Check headings and landmarks, accessible names for controls, keyboard access and focus order, visible focus, color contrast, text alternatives, form labels and error messages, motion and timing, zoom to 200 percent, reflow at 320px width, target size, announcements for content that updates, and the page language attribute. Return a table with columns: issue, WCAG success criterion, who is affected, severity, and the fix with corrected code. Then list the three changes with the biggest impact. Finish with what can't be confirmed from code alone and needs manual testing with a keyboard, a screen reader, or disabled users. Don't call the page compliant; a review like this can find issues but can't certify it.
See all