Umbraco is an open-source .NET CMS widely used in enterprise, government, and public sector organisations - sectors where accessibility compliance is often a legal requirement. Umbraco's flexible content modelling and Razor view engine give developers full control over HTML output, but that flexibility means accessibility is entirely implementation-dependent. Under the EAA, Umbraco sites serving EU consumers must meet EN 301 549 requirements.
Common Umbraco accessibility issues
Razor views don't enforce semantic HTML
Umbraco's Razor view engine renders whatever HTML developers write. Without established accessibility patterns, development teams frequently produce views with div-based layouts, missing landmark roles, and inconsistent heading structure across document types.
Rich Text Editor content lacks accessibility governance
Umbraco's TinyMCE-based Rich Text Editor lets content editors create freeform HTML. Editors can skip heading levels, insert images without alt text, create data tables without headers, and produce styled text without semantic meaning. The editor doesn't validate or enforce accessibility.
Block List and Block Grid editors create nesting complexity
Umbraco's Block List Editor and Block Grid Editor let editors assemble pages from content blocks. Complex block compositions can produce deeply nested markup with broken heading hierarchy, as each block's heading level may not account for its position within the page.
Media library lacks alt text enforcement
Umbraco's media library stores images and documents. Alt text is an optional field on media items and is not enforced at upload or when inserting media into content. Sites with large media libraries commonly have widespread missing alt text.
Multilingual content has inconsistent lang attributes
Umbraco supports multilingual content through its language variant system. The rendered HTML may not correctly set lang attributes on the html element or on inline content fragments in different languages, causing screen readers to use incorrect pronunciation.
How Lumi works with Umbraco
Lumi scans your Umbraco site across all document types and templates - content pages, listing pages, search results, and form pages. Our five engines detect issues in Razor-rendered HTML, Rich Text Editor content, Block List/Grid compositions, and media handling. Monitor continuously to catch regressions from template changes, content updates, and Umbraco upgrades.
Umbraco-specific WCAG gotchas
Government and public sector deployments face strict requirements
Umbraco is popular in government and public sector organisations where WCAG compliance is often a contractual or legal requirement (through the Web Accessibility Directive in the EU). These deployments need comprehensive accessibility validation beyond basic automated scanning.
Umbraco packages extend functionality without accessibility standards
Umbraco's package ecosystem provides pre-built functionality (forms, search, SEO tools) with its own templates. Packages don't have accessibility requirements, and their rendered output may not match the accessibility standards of your custom templates.
Content editor training is essential
Umbraco gives content editors significant control over page content and layout. Even with perfectly accessible templates, editors can introduce failures through poor heading choices, missing alt text, and unstructured rich text content.
Scan your Umbraco site for free
See how your site measures up against WCAG 2.2 and EN 301 549 - in 30 seconds, no signup required.
Frequently asked questions
Is Umbraco accessible?
Umbraco's backend admin interface has been improving accessibility, and the CMS gives developers full control over frontend HTML. However, the accessibility of an Umbraco site depends entirely on the implementation - Razor templates, content modelling, and editorial practices determine whether the output meets WCAG requirements.
Does the EAA apply to Umbraco government sites?
Government sites in EU member states are already subject to the Web Accessibility Directive (Directive 2016/2102), which requires WCAG 2.1 AA compliance. The EAA extends similar requirements to private sector services. Umbraco sites - whether public or private sector - must meet the applicable standard when serving EU users.
How do I enforce alt text in Umbraco?
Configure the Image Media Type to make the Alt Text property mandatory. Use Umbraco's property editors to add required alt text fields to content types that include images. Consider implementing a content validation workflow that flags content published without alt text.
Can Umbraco Forms be made accessible?
Umbraco Forms renders HTML that can be made accessible through theme customisation. Ensure form fields have proper label elements, error messages are associated via aria-describedby, required fields are indicated both visually and programmatically, and multi-step forms announce progress to screen readers.
Related resources
Last reviewed: April 2026. Content is reviewed quarterly for accuracy.