TypingMindTypingMindThe best frontend for AI
God Accessibility logo

God Accessibility

Community
cumabozkurt
god-accessibility

Accessibility and inclusive design to WCAG 2.2 AA - contrast, keyboard and focus, semantic HTML and ARIA, screen readers, forms, motion and seizure safety, touch targets, reflow/zoom, alt text, captions, cognitive accessibility, RTL and localisation, plus an audit checklist. Use when building or reviewing any interface, document, slide or social graphic for accessibility or legal compliance (EAA, ADA, Section 508).

Overview

Publishercumabozkurt
Repositorygod-of-design
Skill namegod-accessibility
Stars
7
Forks
1
Bundled files
Instructions only
LicenseMIT
Links
Skill sourceRepositoryHomepage
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by cumabozkurt on GitHub. Read the source before you install it.

Installation

Install the God Accessibility AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/cumabozkurt/god-of-design/tree/main/skills/god-accessibility
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/cumabozkurt/god-of-design.git /tmp/god-of-design
mkdir -p .claude/skills
cp -r /tmp/god-of-design/skills/god-accessibility .claude/skills/god-accessibility
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable God Accessibility in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads God Accessibility on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so God Accessibility is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

God Accessibility

Accessibility is a quality bar, not an add-on. The European Accessibility Act has applied since 28 June 2025 to many consumer digital products and services in the EU. It references EN 301 549, which maps to WCAG 2.1 AA (aim for 2.2 AA).

WCAG 2.2 AA checklist (the high-impact items)

Perceivable

  • Text contrast ≥ 4.5:1 (large ≥ 3:1). Non-text UI and focus indicators ≥ 3:1. (1.4.3, 1.4.11)
  • Information is never conveyed by colour alone. (1.4.1)
  • Meaningful images have alt text; decorative ones use alt="". Complex charts get a text summary or a data table. (1.1.1)
  • Video has captions; audio-only has a transcript. (1.2.x)
  • Content reflows at 320 CSS px width with no 2-D scrolling (except tables, maps). (1.4.10)
  • Text spacing can be increased (line-height 1.5, paragraph spacing 2×, letter-spacing 0.12em, word-spacing 0.16em) without loss. (1.4.12)
  • Text resizes to 200%. Use rem units, not fixed-height text containers. (1.4.4)

Operable

  • Everything works by keyboard; no keyboard traps; logical tab order. (2.1.1, 2.1.2, 2.4.3)
  • Visible focus indicator (:focus-visible, ≥ 2px, ≥ 3:1). Focus is not hidden behind sticky headers. (2.4.7, 2.4.11)
  • Targets ≥ 24×24 CSS px, or enough spacing (2.5.8). Aim for 44px.
  • Dragging has a single-pointer alternative. (2.5.7)
  • No content flashes more than 3 times per second. (2.3.1)
  • Respect prefers-reduced-motion. Parallax, auto-playing carousels and big motion can be paused or disabled. (2.2.2, 2.3.3 AAA)
  • Skip link to main content. Descriptive page titles, headings and link text. (2.4.1, 2.4.2, 2.4.4, 2.4.6)

Understandable

  • lang attribute on <html> and on passages in another language. (3.1.1, 3.1.2)
  • Labels and instructions for inputs. Errors identified in text with suggestions. (3.3.1–3.3.3)
  • Consistent navigation and help location. (3.2.3, 3.2.6)
  • No unexpected context changes on focus or input. (3.2.1, 3.2.2)
  • Accessible authentication: no cognitive puzzles without alternatives; allow paste and password managers. (3.3.8)
  • Don't ask users to re-enter info they already provided in the same flow. (3.3.7)

Robust

  • Semantic HTML first (button, a, nav, main, h1–h6, label, table). ARIA only to fill gaps, following the "No ARIA is better than bad ARIA" rule. (4.1.2)
  • Status messages announced via role="status" / aria-live. (4.1.3)

Design-time habits

  • Design focus states and error states in the mockup, not later.
  • Annotate heading levels, reading order, alt text and landmarks for developers.
  • Use real text instead of text baked into images (social graphics: put key text in the caption/alt too).
  • Write plain language: aim for grade 8 reading level for public content.
  • Inclusive imagery: diverse people represented with dignity; avoid stereotypes.

Testing

  • Automated: axe DevTools / @axe-core/cli, Lighthouse, WAVE. These catch roughly 30–40% of issues.
  • Manual: keyboard-only pass, screen reader (VoiceOver macOS/iOS, NVDA Windows, TalkBack Android), 200% and 400% zoom, Windows high-contrast/forced-colours mode (@media (forced-colors: active)), reduced-motion setting.
  • Colour-blindness simulation (Chrome DevTools > Rendering > Emulate vision deficiencies).

Social and document accessibility

  • Social: alt text on every image post (Instagram, X, LinkedIn, Facebook and Bluesky support it), captions burned in and as an SRT for video, camelCase hashtags (#GodOfDesign), emoji sparingly and never mid-sentence.
  • PDFs/slides: real text, reading order, slide titles, alt text, sufficient contrast, and no information conveyed only by animation.

Frequently asked questions

What does the God Accessibility AI skill do?

Accessibility and inclusive design to WCAG 2.2 AA - contrast, keyboard and focus, semantic HTML and ARIA, screen readers, forms, motion and seizure safety, touch targets, reflow/zoom, alt text, captions, cognitive accessibility, RTL and localisation, plus an audit checklist. Use when building or reviewing any interface, document, slide or social graphic for accessibility or legal compliance (EAA, ADA, Section 508).

Why use God Accessibility on TypingMind?

Because you install it once and use it with any model. God Accessibility is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install God Accessibility in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/cumabozkurt/god-of-design/tree/main/skills/god-accessibility. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use God Accessibility?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with God Accessibility?

As many as you like. As long as a model supports skills, you can use God Accessibility with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the God Accessibility AI skill free?

Yes. It is published on GitHub by cumabozkurt under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

Related AI Skills

View all
affaan-m logo

Api Design

affaan-m
CommunityPopular

Patrones de diseño REST API incluyendo nomenclatura de recursos, códigos de estado, paginación, filtrado, respuestas de error, versionado y rate limiting para APIs de producción.

39.1K
261.1K
Instructions
View
affaan-m logo

Accessibility

affaan-m
CommunityPopular

WCAG 2.2 レベル AA 標準を用いてインクルーシブなデジタルプロダクトを設計・実装・監査します。Web 用のセマンティック ARIA および Web・ネイティブプラットフォーム（iOS/Android）のアクセシビリティトレイトを生成するために使用します。

39.1K
261.1K
Instructions
View
NousResearch logo

Archify

NousResearch
OrganizationPopular

Validated interactive HTML diagrams, upstream-maintained.

53.5K
250.4K
Instructions
View
NousResearch logo

Auteur

NousResearch
OrganizationPopular

Design and build cinematic, award-level web pages.

53.5K
250.4K
25 files
View

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇