IntermediateAccessibilityFree prompt

Complete WCAG 2.2 Accessibility Audit for Digital Products

Audit checklist based on WCAG 2.2 Level AA criteria, adapted to Brazilian regulatory context (Lei Brasileira de Inclusão - LBI, Law 13.146/2015, which mandates digital accessibility for organizations serving Brazilian users).

Conduct a comprehensive accessibility audit that identifies WCAG 2.2 AA non-conformities and generates a prioritized remediation plan, with consideration for Brazilian accessibility law requirements.

At a glance

Access

Free prompt

Open to copy without upgrading.

Prompt objective

Conduct a comprehensive accessibility audit that identifies WCAG 2.2 AA non-conformities and generates a prioritized remediation plan, with consideration for Brazilian accessibility law requirements.

Real use case

A major Brazilian bank's digital banking platform needs to comply with Lei Brasileira de Inclusão before a Federal Public Ministry audit. The current site has 847 accessibility violations detected by axe DevTools and requires a structured plan to resolve within 3 months.

Customize these fields first

PRODUCT NAME/URLWEB/IOS APP/ANDROID APPTECHNOLOGYLIST OF PAGES

Replace the placeholders with your own context before you run the prompt. That usually improves the first output more than adding more instructions later.

Prompt

Conduct a WCAG 2.2 Level AA accessibility audit for [PRODUCT NAME/URL], considering Brazilian accessibility requirements under Lei Brasileira de Inclusão (Law 13.146/2015).\\\\\\\\n\\\\\\\\nType: [WEB/IOS APP/ANDROID APP]. Framework: [TECHNOLOGY].\\\\\\\\nPriority pages/screens: [LIST OF PAGES].\\\\\\\\n\\\\\\\\n**1) Automated Testing (axe DevTools + Lighthouse):**\\\\\\\\nFor each page, evaluate:\\\\\\\\n- Images without alt text or with inadequate alt\\\\\\\\n- Insufficient color contrast (minimum ratio 4.5:1 text, 3:1 UI)\\\\\\\\n- Forms without associated labels\\\\\\\\n- Broken heading hierarchy (h1 -> h3 without h2)\\\\\\\\n- Links without descriptive text (\\\\\\\\

Open directly in an AI — the text is pre-filled:

How to use this prompt

  1. 1Replace the key placeholders first: PRODUCT NAME/URL, WEB/IOS APP/ANDROID APP, TECHNOLOGY, LIST OF PAGES.
  2. 2Replace any bracketed placeholders like [this] with your own context.
  3. 3Add extra background information when you want more tailored results.
  4. 4Combine multiple prompts in one conversation when you need a richer output.
  5. 5Save your best-performing prompts so they are easy to reuse later.

Next best step

Open the guide first, then branch only if you still need more.

A starter guide to the first prompt categories and patterns worth using when you need better output without prompt guesswork.

If this prompt is close but not quite right, generate variants next. If the job is recurring, move into the course library after the guide.

Related prompts

View all

Screen Reader Optimization with ARIA and Semantic HTML

Practical guide for implementing landmarks, live regions, and ARIA roles and properties to make rich interfaces accessible via screen readers.

AdvancedFree prompt

Best for

Implement full screen reader support (NVDA, JAWS, VoiceOver, TalkBack) using semantic HTML as the foundation and ARIA as a supplement, following the rule 'no ARIA is better than bad ARIA'.

Copy-ready promptOpen prompt

Accessible Color System with Universal Contrast Compliance

Color palette redesign ensuring WCAG AA/AAA contrast across all contexts, including dark mode and color blindness.

BeginnerFree prompt

Best for

Create a color system that is accessible for all types of vision, maintaining brand visual identity and ensuring WCAG AA compliance across all text/background combinations.

Copy-ready promptOpen prompt

Full Keyboard Navigation for Single-Page Applications

Keyboard navigation implementation for SPAs with focus management, skip links, shortcuts, and assistive technology support.

AdvancedFree prompt

Best for

Ensure the entire product is 100% operable via keyboard, serving users with motor disabilities, screen reader users, and power users who prefer keyboard shortcuts.

Copy-ready promptOpen prompt

Advanced ARIA Patterns for Rich Custom Interface Components

Implementation of WAI-ARIA Authoring Practices for complex components: combobox, treegrid, date picker, drag-and-drop, and rich text editor.

AdvancedFree prompt

Best for

Implement advanced ARIA patterns for rich interface components that lack native HTML equivalents, following WAI-ARIA Authoring Practices 1.2.

Copy-ready promptOpen prompt

Explore other prompt categories

Move sideways into adjacent libraries when the current category is not the full answer.

Free browsing stays open. Premium prompts unlock the reusable workflow layer.

Use the guides and role paths to validate the job first. Upgrade when you want the full prompt text, editable premium prompts, and the surrounding course paths in one place.

Free access

  • Browse guides, role paths, and category pages.
  • Preview prompts before you decide to upgrade.
  • Find the right starting point without friction.

Membership access

  • Unlock premium prompts and the full copy text.
  • See more workflow paths and course connections.
  • Keep the reusable templates in one place.
Chat on WhatsApp