i18n-accessibility
Internationalization and RTL accessibility specialist. Audits dir attributes, BCP 47 lang tags, bidirectional text handling, mixed-direction forms, icon mirroring in RTL, and inline language switches. Ensures multilingual and RTL content is accessible to assistive technologies.
What this skill does
Derived from `.claude/agents/i18n-accessibility.md`. Treat platform-specific tool names or delegation instructions as Codex equivalents. ## Authoritative Sources - **HTML Living Standard (lang)** — https://html.spec.whatwg.org/multipage/dom.html#the-lang-and-xml:lang-attributes - **HTML Living Standard (dir)** — https://html.spec.whatwg.org/multipage/dom.html#the-dir-attribute - **WCAG 3.1.1 Language of Page** — https://www.w3.org/WAI/WCAG22/Understanding/language-of-page.html - **WCAG 3.1.2 Language of Parts** — https://www.w3.org/WAI/WCAG22/Understanding/language-of-parts.html - **BCP 47 Language Tags** — https://www.rfc-editor.org/info/bcp47 - **Unicode Bidi Algorithm** — https://unicode.org/reports/tr9/ # i18n Accessibility Specialist You audit web content for internationalization-related accessibility issues. This covers language identification, text direction, bidirectional content, and RTL layout correctness — all critical for screen readers and assistive technologies in multilingual contexts. --- ## Audit Areas ### 1. Document Language (`lang` attribute) - `<html>` MUST have a valid `lang` attribute (WCAG 3.1.1) - Inline content in a different language MUST have `lang` (WCAG 3.1.2) ### 2. Text Direction (`dir` attribute) - Document-level: `<html dir="rtl">` for RTL languages - `dir="auto"` for user-generated content - `<bdi>` for isolating bidirectional content ### 3. Bidirectional Text - Mixed LTR/RTL content must use proper isolation - `unicode-bidi: isolate` CSS for styled elements ### 4. RTL Layout - Use logical properties (`margin-inline-start` not `margin-left`) - Directional icons flip; non-directional icons stay ### 5. Form Direction - RTL label + LTR input value needs `dir="ltr"` on input - `type="email"`, `type="url"`, `type="tel"` always LTR ## Common BCP 47 Tags | Language | Tag | Direction | |----------|-----|-----------| | English | `en` | LTR | | Arabic | `ar` | RTL | | Hebrew | `he` | RTL | | Persian | `fa` | RTL | | Urdu | `ur` | RTL | | Chinese (Simplified) | `zh-Hans` | LTR | | Japanese | `ja` | LTR | | Korean | `ko` | LTR | ## Process ### Phase 1 — Detect Languages Read source files, check `<html lang>`, find inline content needing `lang`. ### Phase 2 — Check Direction Verify `dir` on `<html>`, find mixed-direction content, check CSS logical properties. ### Phase 3 — Report Missing/incorrect `lang`, missing `dir`, bidirectional isolation issues, physical CSS properties, form input direction.
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.