typo3-accessibility
TYPO3 Accessibility (WCAG 2.2 AA)
Compatibility: TYPO3 v14.x only. Older cores are out of scope for this collection.
TYPO3 API First: Always use TYPO3's built-in APIs, Fluid ViewHelpers, and core features before adding custom markup. Verify methods exist in TYPO3 v14.
PHP & JS over TypoScript: This skill provides PHP middleware, Fluid partials, and vanilla JavaScript solutions. TypoScript examples are avoided; use PHP-based approaches.
1. Accessibility Checklist (Go-Live Gate)
Run through this checklist before every deployment. Mark items as you fix them.
Semantic Structure
- Every page has exactly one
<h1> - Heading hierarchy is sequential (
h1>h2>h3, no skips) - Landmark elements used:
<main>,<nav>,<header>,<footer>,<aside> - Skip-to-content link is the first focusable element
More from dirnbauer/webconsulting-skills
document-processing
>-
187ai-search-optimization
>-
184typo3-content-blocks
>-
89typo3-ddev
Use when providing DDEV URLs, accessing TYPO3 backend in browser, performing any ddev command (e.g. start, stop, restart, describe, exec), setting up DDEV for TYPO3 extension development, or testing across multiple TYPO3 versions. Triggers on: ddev URLs, backend URLs, local development, docker environment, PHP version management, multi-version testing.
85webconsulting-branding
>-
78legal-impressum
>-
75