Accessibility
WordPress accessibility: a checklist for themes, forms and plugins
An accessible WordPress website depends on its theme, plugins, editorial work and testing. One plugin is not enough. This checklist helps define a relaunch or a targeted improvement programme.
1. Test the theme and navigation with a keyboard
Use the header, submenus, search and footer without a mouse. Focus must remain visible and open menus and dialogs must be dismissible. A skip link to the main content avoids repeated navigation. Include mobile menus and overlaying cookie dialogs, not just the homepage.
2. Use the block editor and headings meaningfully
Use real heading blocks rather than enlarged paragraphs. Their order should explain the content, not follow visual preferences. Links should describe their destination. Informative images need suitable alternatives; decorative images should be treated accordingly. Editorial templates make these decisions repeatable.
3. Test forms and error messages
Labels need to stay visible and be programmatically associated with fields. Placeholders are not labels. Required inputs, errors and successful submission must be understandable and perceivable. Test invalid input and the next step after submission with a keyboard and screen reader. Include CAPTCHAs and third-party form services.
4. Assess plugins and WooCommerce as complete journeys
Sliders, booking tools, language switches and payment services can introduce barriers. For a shop, assess the complete purchase journey: product selection, variants, basket, sign-in, payment and confirmation. An accessible product page does not compensate for an unusable checkout. Document limitations of third-party integrations too.
5. Check contrast, zoom and media
Check contrast of text and controls, zoom and reflow on narrow screens. Depending on their content, videos need captions and other alternatives. Include essential downloads: provide key information in accessible HTML where possible and assess necessary PDFs.
6. Supplement automated scans with manual assessment
Tools such as axe and WAVE identify issues but cannot judge every barrier to use. A representative sample should cover relevant page types and complete journeys. Document the standard, tested version, locations and corrections. Retest critical journeys after theme and plugin updates.
What applies to WordPress in Austria?
BaFG applicability depends on the product or service, not the CMS. Consumer shops and certain booking services can be covered; information-only websites are not automatically in scope. See our guide to accessible websites in Austria for details and the disputed contact-form question.
Audit or relaunch?
A sound theme can make targeted fixes practical. If navigation, content structure and essential plugins are fundamentally unsuitable, compare remediation with a relaunch. Zensations connects WordPress development, WCAG audits and accessible design and implementation support. Bring your website address, priority journeys and existing reports to an initial discussion.
Sources
General guidance, not individual legal advice.
