# Block validations prevent inaccessible content at source > [!quote] > "We would lock the publishing from the posts or pages." Two lines: context and use. This supports treating accessibility checks as part of CI for content. ## Links - [[Lit · Block attributes require explicit content role marking for accessibility]] — role marking declares the editable surface that these validations then enforce against - [[Lit · Accessibility work shapes product and culture]] — publish-blocking a11y checks are that culture hardened into product policy - [[Lit · Beta releases require extensive community testing]] — complementary pre-release gate: validation at authoring time, community testing before launch, both catching defects before users do - [[Encoding What Good Looks Like Is What Makes Agent Verification Trustworthy]] — a publish-blocking accessibility check is "encoding what good looks like" as an automated gate - [[DevRel MOC]] — publish-time validation turns accessibility guidance into an enforceable developer and author workflow ## Source - [[3. Resources/Readwise/Articles/Empowering WordPress Accessibility With Community, Practical Tools, Education, and Real-World Impact]]