“How many sites?” is often the wrong question to consider. Instead, you need to understand how much shared DNA you want across your sites.

At scale, your web architecture will be impacted by the governance model you choose, the level of autonomy required by individual parts of your organization, and the total cost of ownership to maintain whatever configuration you choose.

After reading this article, you should have a better understanding of the benefits, trade-offs, and limitations of choosing a multisite web architecture over a single site or composable architecture. You should also better understand how the vendor you choose plays a role in reducing those tradeoffs and limitations.

Enterprise web architecture patterns: Single-site vs. multisite vs. composable

Most enterprise-scale companies adopt one of three patterns for their web platform architecture, either through organic growth or intentional design. Each of these patterns comes with tradeoffs.

• Single-site web platforms are typically composed of many independent sites, which offer high autonomy but come with trade-offs and limitations in governance and consistency. 
• Multisite architecture typically refers to a WordPress configuration designed to manage a few to hundreds of websites.
• Composable web architecture, including headless or hybrid designs, decouples the presentation layer from the content and services layers.

Comparing web architecture patterns

Choosing which of these patterns makes the most sense for your organization depends on a number of factors, including:

• Business drivers: What are the business outcomes you are trying to achieve, and how aligned are they across individual teams?
• Number of independent product/brand teams: How many different teams make up your organization? How closely are they aligned already?
• Regulatory boundaries: How many teams are bound by unique regulations that don’t overlap with requirements for other teams?
• Expected traffic patterns: What does traffic look like for each of your web properties?

Delivering value with multisite through governance, consistency, and efficiency

Each web architecture comes with specific advantages. Multisite is particularly strong in three key areas.

• Centralized governance and policy enforcement provides a single admin layer for plugins, themes, and security policies. This creates architectural consistency across sites and reduces compliance risk by enforcing specific standards.
• Operational efficiency and cost control through shared code, shared updates, and consolidated hosting translates to reduced per‑site maintenance overhead and lower total cost of ownership.
• Brand and content consistency through the use of shared components, templates, and content blocks helps simplify global campaigns.
• Shared components make the process of automating regional translations easier.

WordPress VIP amplifies these benefits through enterprise hosting and DevOps, including performance monitoring, security monitoring, and proactive vulnerability patching.

Limits and operational tradeoffs of multisite at scale

Multisite architectures are powerful in many circumstances, but like any web architecture, they come with practical limitations and operational tradeoffs.

• One of the most common tensions is between individual team autonomy vs. centralized control. Individual teams may want features or a release cadence that conflicts with the centralized governance model.
• Performance and risk assessment are commonly cited as operational tradeoffs for large organizations. Sharing an improperly tuned common configuration increases the risk that a plugin, theme change, or traffic spike on one site could impact the performance of other sites. 
• Upgrade and testing complexity increase because testing needs to happen across multiple sites to assess any potential impacts. 
• Operational scaling requires thoughtful planning so that monitoring, backup and restore functionality, and incident response are all designed for network-wide visibility and rapid isolation.

There are a few instances where a multisite web architecture might be the wrong choice for your organization. If you have many teams who all require an independent release cadence, some of the benefits of multisite may be reduced. 

If different parts of your organization use their own unique tech stacks, they may not be easily unified. When regional teams require strict regulatory isolation, they may need to be isolated from each other.

WordPress VIP overcomes many of these limitations and tradeoffs through a set of features designed to complement the advantages of multisite:

• A common dashboard provides visibility and access to features based on the roles of each user in your organization.
• Governance across sites allows you to define and customize the level of autonomy available to individual user roles throughout your organization.
• Shared brand assets, themes, and content blocks provide consistency, with the ability to allow these shared assets to be combined independently per site.
• Each site can be backed up or restored independently.
• The Network Sites panel in the WordPress VIP Dashboard offers controls to launch individual sites.
• From a performance perspective, WordPress VIP delivers enterprise SLAs, meets security and compliance demands including FedRAMP certification for government organizations, and offers traffic engineering to tune your multisite configuration to meet the demands of your website traffic.

Governance models and operational tradeoffs

Your organization’s approach to governance can be a key factor to determining the kinds of operational trade-offs you will make with a multisite web architecture. 

Centralized governance allows you to maintain strict standards and communicate them to regional teams, potentially reducing duplication but potentially leading to longer lead times for regional teams. It benefits from a multisite single-pane approach to manage all sites through a common backend.

Federated governance provides platform-level guardrails and shared services while allowing individual teams to retain greater autonomy. This is commonly the structure for a composable web architecture, requiring mature APIs, CI/CD, and clear SLAs.

Hybrid governance approaches come in a variety of configurations, drawing from both centralized and federated models. One common example is leveraging shared components while allowing local teams to control the user experience and content within those components.

When assessing potential web architectures, it’s helpful to have a checklist of must-have capabilities before making a decision. Key items to map out include:

• Roles (platform, product, security)
• Policy enforcement points
• Plugin approval workflows
• Escalation paths

WordPress VIP offers the flexibility to implement a multisite configuration with any of these governance models. Other vendors may have limitations on which of these governance models they are able to support.

Infrastructure and performance considerations for large‑scale site networks

Performance and infrastructure matter regardless of which web architecture you choose. Be sure to assess each of these factors during your evaluation:

• Capacity planning and traffic engineering will dictate how much traffic you can handle and whether a burst in traffic at one site negatively impacts other sites. This includes autoscaling, a CDN strategy, and caching patterns.
• Isolation strategies like containerization and per-site resource quotas can help reduce the “blast radius” of an event that impacts an individual site.
• Observability and SRE practices like network-wide logging and per-site monitoring  can help keep all sites online.
• Backup, restore, and disaster recovery at both the per-site and network level play a role in the total operational cost for your web architecture.
• Security at scale including vulnerability scanning and prevention, coupled with role-based access controls that integrate with your identity management solution helps maintain a secure web architecture.

A decision framework and checklist for platform decision‑makers

When you reach the point where you are considering multisite as a potential web architecture, ask yourself these three questions:

• Do sites need independent release cycles or strict isolation?
• Is centralized governance a strategic priority?
• Can your ops organization support network‑level SRE and observability?

Once you are clear on those answers here is a short checklist of details to run through:

• Governance model alignment: Does the architecture align with how you want to govern?
• Performance and isolation requirements: Will the architecture meet your performance needs and protect individual sites from impacting others?
• Vendor capabilities: Can the vendor meet your expectations around SLA, traffic engineering, and security?
• Migration and rollback plans: How well does the architecture handle migrations and rollbacks?
• Cost and operational staffing model: What’s the total cost of ownership when considering both the platform and the people required to support it?

Thinking of multisite as a strategic decision

Multisite can deliver major efficiency and governance wins when aligned to your organizational structure and the operational maturity of your organization. It also has the potential to concentrate risk and introduce technical debt if you choose convenience over fit.

---

Related content

Website Accessibility Governance for Large Organizations

Read the article

Author

Jake Ludington

Jake is a technology writer and product manager. He started building websites with WordPress in 2005. His writing has appeared in Popular Science, Make magazine, The New Stack, and many other technology publications.

Think about when an employee makes a radical proposal in a business meeting or submits a report filled with dubious claims. “How did you come up with that?” their manager might ask, and once they understand the employee’s research and thought process, they might realize more training and coaching is required.

What AI explainability and auditability actually mean (and why they’re different)

The same is true of AI. Whereas explainable AI (XAI) shows why the technology produced a certain output, AI audit trails break down exactly what happened. The latter means you can either stand behind what the tool produced or at least fine-tune it to prevent negative outcomes in the future.

These are complementary but equally important capabilities because they help tell the full story about how AI is performing. Together, they go way beyond superficial notions of AI transparency, which sometimes implies you need to publish all your code and training data, or that revealing biased or erroneous outputs will erode trust.

Building AI auditability and explainability into your strategy is an essential step in establishing enterprise AI governance, which will let your organization scale the technology without fear.   

Why black-box AI breaks down in enterprise environments

AI can make autonomous decisions, but people remain accountable for them. That could explain why 64% of U.S. adults believe the need for humans reviewing and checking AI outputs will increase. The same research found 42% have experienced AI outputs that missed important details or context.

At its worst, AI can resemble a black box whose inner workings are as difficult to discern as that of the human brain. This only exacerbates the fallout when AI introduces bias or defamatory claims into content, or where AI outputs simply fail to align with brand safety guidelines and use prohibited terms or phrases. Senior leaders will rightfully expect the ability to trace what happened and why.

Organizations may find themselves saddled with black box AI because they were trying to keep up with competitors. While 70% of executives say AI is now at the heart of their business strategy, 45% feel they’re falling behind competitors. There’s no real advantage in being first with an AI platform or tool if you’re unable to debug, justify, or improve the work it produces.    

A lack of AI auditability and explainability is also a big challenge for legal, compliance, and risk teams. Pointing the finger at an AI tool or platform when something goes wrong isn’t enough. AI compliance and risk management means being able to demonstrate that the technology adheres to accepted policies, approved sources, and industry-specific legislation.

If your organization is in enterprise AI governance catch-up mode, here’s what you need to educate stakeholders and begin procuring solutions with the necessary capabilities.

Explainability: trusting AI in the moment

You shouldn’t need to be an AI expert to interpret the technology’s actions. In 2024, 40% of business leaders called out explainability as a key risk in adopting generative AI. That sentiment might even be higher now that agentic AI is allowing platforms and tools to not only produce content but perform tasks on an organization’s behalf.

XAI doesn’t just help content team members work with greater confidence and build trust. It also educates them on how AI tools “think” so they can use better prompts and adjust the suggestions the technology makes in critical workflows. XAI should promote:

• A greater understanding of inputs, signals, and constraints: Some of the most common techniques for explaining AI outputs include SHAP (SHapley Additive exPlanations) and LIME (Local Interpretable Model-agnostic Explanations). These methods help identify which aspects of a piece of content, such as a brief or source document, influences an AI tool’s decision-making.
• Human-in-the-loop decision-making: The conversational nature of AI platforms can help with explainability. For example, using natural language interfaces to ask for an output’s rationale could identify that an AI tool changed a phrase to reduce regulatory risk or align with voice and tone guidelines. This should become a part of employee training as they start using AI.
• Logic that can be retraced: Decision trees are a great example of how to visualize the paths AI tools should take when creating content. For instance, setting up “if/then” rules upfront can help ensure AI tools produce content for the right audience, with keywords, lengths, templates, and human review processes explicitly defined.

Building in explainability might seem like you’re adding extra steps, but it’s less about creating friction than enabling adoption.

Auditability: proving decisions after the fact

It’s the golden rule your teacher probably emphasized when you first learned how to write an essay: be prepared to back up every claim. We need to be just as diligent in using AI in content workflows. As its stands, 66% of business professionals admit they rely on AI output without evaluating accuracy, and 56% say it’s led to mistakes in their work.

Fortunately, AI auditability is achievable through:

• Logs, records, and permission dashboards: Platforms like WordPress VIP provide access to multiple logs and performance monitoring, as well as version controls that let you see post revisions and illustrate what happened to content throughout a workflow. These become part of the audit trail to see who did what (including AI tools), what got changed, and when.
• Supporting investigations, audits, and regulatory inquiries: Using automated, structured metadata can help you govern and verify AI-assisted content. This can begin with a content taxonomy that makes it easier to sort through content types, contributors, access levels, and subject matter. You can also use descriptive alt-text and assign tags automatically through integrations like ClassifAI. This makes it easier to respond to questions that may be asked.
• Confidence scoring: Either manually or with AI’s help, organizations can set up structured checklists for each content asset to be reviewed as needed. This would include source citations, bias flags, brand/tone/alignment, and factual accuracy. It can be a way to document what your human-in-the-loop process looks like and what earns final approval and sign-off.

Audit trails protect both organizations and individuals by promoting enterprise AI governance in a consistent, repeatable fashion.

How to evaluate AI tools for explainability and auditability

Developing responsible AI systems requires building on existing best practices for procuring enterprise-grade technology, with a greater focus on AI compliance and risk management. 

Here are some potential questions you could ask prospective vendors:

1. How are the algorithms/models tested to provide AI auditability and explainability?
2. How does the AI system assess the quality and lineage of the data it uses to produce outputs?
3. How reliably does the tool produce the same output if it’s using a consistent data set?
4. To what extent has the tool been engineered to align with privacy and security laws and regulations such as GDPR, and what kind of customization is available?
5. How have existing customers integrated audit trails and explainability into their workflows?
6. How can you demonstrate a representative example of using your solution to respond to an investigation, audit, or regulatory inquiry?
7. How does your solution integrate with an enterprise CMS to enhance XAI and auditing?

Selecting the best solution may require looking more closely at a vendor’s documentation to understand models or sources it draws upon, any missing policies, or vague promises of explainability and auditability. If there’s no ability to trace decision paths or a lack of automated tools to assist with compliance and versioning, you’re at increased risk of buying a black box.

AI auditability and explainability as an enterprise imperative

AI and AI audit trails need to be functional requirements, not optional extras. Without them, your organization faces increased legal exposure for compliance failures, the potential for costly rework and rollbacks, and erosion of brand trust.

You probably wouldn’t leave a new employee to fend for themselves once they start working with you, and AI tools require a similar level of observation and occasional intervention. Content intelligence tools like Parse.ly can play a big role here by providing transparent, inspectable decision signals and a dashboard that lets you see what’s going on with your content at a glance.

As responsible AI systems become the norm (and an expectation among senior leaders and customers alike), this is an opportune time to make explainability and auditability integral parts of using technology to enhance content creation and management.

---

Related content

Building Editorial Trust in AI-Assisted Workflows

Read the article

Author

Shane Schick

Founder, 360 Magazine

Shane Schick is a longtime technology journalist serving business leaders ranging from CIOs and CMOs to CEOs. His work has appeared in Yahoo Finance, the Globe & Mail and many other publications. Shane is currently the founder of a customer experience design publication called 360 Magazine. He lives in Toronto. 

That inconsistency increases the risk of compliance gaps, which can translate to greater risk for your company. On a lived experience level, your users may find fluctuations in accessibility as they navigate your site, particularly if some parts of the site that were accessible in the past regress after an update.

Without centralized governance of accessibility, there’s also a real risk of accessibility debt. Similar to tech debt, poorly governed accessibility is a problem that compounds and becomes more expensive to fix over time.

Making a mindset shift from viewing accessibility as a one-off project to treating it as core to your website can help address this challenge. When your regional teams understand the benefits of accessibility for their teams and the organization as a whole, it becomes easier to rally all stakeholders. Each team that touches the website needs to develop the muscle to consider accessibility with every change they make.

What accessibility governance includes

Accessibility governance touches on multiple interdependent factors that each add up to a cohesive accessibility strategy.

• Policies and standards alignment: The core of an accessibility plan is alignment with the policies and standards required by user expectations and the legal requirements where you do business. This includes things like supporting the WCAG standard and any geographically specific legal requirements.
• Defined roles and accountability: Every good governance plan defines clear roles for each aspect of accessibility. The RACI framework works well here to spell out who is responsible, who is accountable, who needs to be consulted, and which stakeholders just need to be informed about what’s happening.
• Decision rights and escalation paths: Like governing other parts of your business, accessibility needs clear guidelines around who has the authority to make decisions coupled with clear escalation paths when those decisions are up for debate.
• Documentation and audit readiness: A key part of governance is making sure you have the right documentation in place so that when it comes time to do a site audit, you can easily demonstrate what’s been done.
• Third-party / vendor governance: If your company is like many large organizations, you rely on SaaS products and external agencies to execute on your business objectives. You need a procurement policy that explicitly mandates accessibility to guarantee end-to-end compliance.

Accessibility ownership models that work in large organizations

There are a couple of approaches to accessibility governance that tend to play out in large organizations. Some aim for a fully centralized approach where all accessibility decisions are decided and handed down to the organization. This can be challenging to maintain consistency, particularly when individual teams may have competing priorities.

Another approach is using a federated governance model. This establishes ownership of different aspects of governance within teams instead of having a single central team.

In a federated model, there may still be a center of excellence that shares out best practices. This tends to work best when each individual team has a stakeholder who participates in an accessibility council or “champions” program. These stakeholders engage with the center of excellence and take findings back to their own team for day-to-day execution.

Executive sponsorship is often key to getting the buy-in required to execute in a large organization. When a leader communicates accessibility as a priority, it becomes easier to align individual teams.

One core challenge of any governance model is finding the right balance between autonomy for individual teams and maintaining consistency of experience across all touchpoints.

Embedding accessibility into everyday workflows

Governance is easiest when accessibility is embedded in the daily workflows of every part of your organization. The teams most frequently impacting accessibility are your developers, design team, any QA teams, and the content team.

Each role will require different tools and training to properly support accessibility in their specific knowledge domain.

You can help guarantee consistent application of accessibility guidelines by baking in a review and approval process, coupled with quality gates when something fails review. This looks a little different at each stage. 

• Designers may need to check for things like color contrast in Figma files (or wherever they are designing) prior to handing off to your development team.
• Developers may use automated tooling to catch issues in their code changes before they are merged with the production website. 
• The content team can integrate specific accessibility checks directly into the CMS. It’s also feasible to create required fields in the publishing workflow.

Using a CMS like WordPress that makes it easy to design accessibility requirements into templates and your design system dramatically simplifies enforcement. Instead of needing to use reactive checks to find errors after they are live, templating allows you to provide accessibility-ready components to your team for use as they create new pages.

The design system is a great place to define accessibility requirements. It will get you 80% of the way to maintaining an accessible site if the design is already tested for accessibility before handing off to developers to create your website templates.

Measuring, monitoring, and enforcing accessibility standards

Once you have a set of accessibility guidelines in place, you need to measure and monitor your site for conformance to those guidelines. There are a few key processes that can help maintain accessibility standards.

• Periodic audits are a good way to make sure to catch any substantial breakage in accessibility. Audits can be particularly useful during a major release or migration.
• Continuous monitoring tools can be used between audits to catch issues before something becomes significant.
• Analytics tools are helpful for prioritization. Stack ranking fixes based on how frequently pages are visited can be useful, especially when you have a massive backlog of fixes.

Part of the governance process is tracking progress towards compliance over time. When you first run an accessibility audit, you may discover a significant number of issues. You can track against burning those down to help understand how you are decreasing risk and tracking toward compliance over time.

These tracking efforts are also useful for keeping stakeholders and leadership informed of progress. 

How platform choice impacts accessibility governance

The platform you choose plays a significant role in how easy or difficult it is to govern accessibility. When you choose a CMS like WordPress VIP with configurable role-based permissions and workflow controls, it simplifies determining who can make which accessibility changes.

Another key factor of CMS choice is integration with accessibility tooling. The WordPress plugin architecture makes it easy for many accessibility tools to provide both proactive and reactive feedback to improve accessibility.

WordPress VIP also supports governance of multisite and multibrand environments out of the box. By defining roles and workflows across sites, you can simplify governance for a large, diverse set of content. Depending on how your sites are configured, you can push a single accessibility change across hundreds of websites simultaneously.

All of these factors contribute to maintaining long-term accessibility. When your CMS supports role-based access and accountability, you can more easily include all the right team members in implementing fixes. When your CMS supports a diverse set of tools, you can evolve the types of tools you use as your team matures in its accessibility journey. You can focus on delivering guardrails that give your content team freedom to create without violating the core accessibility principles.

Accessibility governance as risk management and trust building

Strong governance is the foundation on which sustainable accessibility is built. By creating a framework around expectations with clear roles and responsibilities, it’s easy to know who is responsible for what. Compliance risk is often the stick used to initiate an accessibility effort, but at the core, accessibility is about improving your website experience for all users.

By laying out clear goals and defining roles and responsibilities, you can operationalize your accessibility initiative with confidence.

---

Related content

Accessibility Tooling Comparisons: How Enterprises Evaluate and Operationalize Accessibility Tools

Read the article

Author

Jake Ludington

Jake is a technology writer and product manager. He started building websites with WordPress in 2005. His writing has appeared in Popular Science, Make magazine, The New Stack, and many other technology publications.

When your website isn’t accessible, users who would like to interact with it simply won’t be able to. Lack of accessibility causes those users pain.

Like other efforts that span multiple teams, accessibility can be a struggle for enterprises. The scope feels massive and impacts every team involved with your website, from the developers to the content creators, to the designers, to the legal and compliance teams. 

Who owns accessibility when it touches every team in your organization? How are the right expectations set so that each team addresses their part of the problem on a timeline that also considers all the other deadlines already committed?

When you treat an accessibility audit as a one-off event, you don’t bake accessibility into the DNA of your content operation. Everyone will rally around a big push, and the next time you do an audit, you will find many of the same issues all over again. 

A better approach is to start with an audit and use it to evolve your organization into one that embeds accessibility at every stage of your content operation, ensuring every new page, article/post, and update is audited before publication.

What an accessibility audit includes

Web Content Accessibility Guidelines (WCAG) are the internationally recognized standard for making your website accessible. The standards were developed by the W3C’s Web Accessibility Initiative and have gradually evolved over time.

Most accessibility audits start by using automated testing tools to identify gaps between your website and page structures and the WCAG-defined expectations. The best automation tools catch 30-40% of WCAG issues, which means you also need to look at manual testing.

If you want to truly understand a user’s lived experience of engaging with your site, manual testing is essential. Manual testing is best performed by considering personas who use assistive technologies to engage with your content.  

Some examples include:

• Keyboard navigation testing will help you understand the experience of navigating your website without the use of a mouse or touch screen.
• Screen reader testing highlights instances where your website may not perform well when read aloud by assistive technology. Some commonly used screen readers include TalkBack for Android, VoiceOver for both macOS and iOS, and JAWS for Windows.
• Zoom level testing uncovers gaps when some content isn’t correctly magnified for low-vision users. This can be tested by using the zoom function built into the browser and increasing the size to 200% or greater.
• Focus order testing will highlight instances where a user isn’t correctly moved through a sequence of steps, like filling out a check out form while using keyboard navigation. This can be tested by attempting to fill out a form by using only your keyboard.

This WordPress VIP webinar discusses assistive technologies in depth. If you want external users to test your website with assistive technology, companies like Fable provide user experience testing by people who use assistive technology every day.

The content on your pages isn’t the only place you need to check these tools. If you have a chatbot on your pages, you need to understand how it performs for each persona. It’s also vital that compliance-mandated elements, like a cookie banner for EU and California users, be accessible in addition to the underlying content.

To get a clear picture of how assistive technologies perform, expand personas to include popular browsers combined with a technology. For example, maybe you test keyboard navigation in Safari and Chrome.

It’s also important to consider content-level checks for aspects that improve accessibility. Headings, links, the use of alt text on images, table construction, and the availability of captions on video all play a role in how accessible your content is to users.

Design and interaction patterns can also improve or impede accessibility. WCAG offers guidelines on design specific components including: 

• Color contrast between the text on the page and the page background.
• Responsive layouts that adapt depending on the screen size being used.

The output of both the automated and manual checks should be a checklist of issues identified. If you use WordPress VIP, there are accessibility plugins like Equalize Digital Accessibility Checker that can provide a list of issues for you to review.

Who’s involved in an enterprise accessibility audit

Auditing your website for accessibility is everyone’s job within your organization.

• Internal accessibility champions are often at the frontline of accessibility efforts, helping align the organization around why accessibility matters beyond compliance. 
• Engineering and front-end teams will be on the lookout for code-level issues and ways to resolve them. 
• Content and editorial stakeholders will need to evaluate best practices for creating accessible content.
• Design and UX teams will be on the lookout for factors such as color contrast and how individual users navigate a site.
• Legal, compliance, and risk teams will need to be involved to understand the current state of your accessibility efforts and identify where the company may be most at risk for non-compliance, while also balancing other legal and compliance risks mandated by law.
• External auditors can be useful in organizing a thorough accessibility audit. They are also useful in gathering and sharing findings with the broader org. 

Audit outputs: findings, severity, and remediation plans

A completed audit typically breaks issues down into categories and severity levels. WCAG defines three levels of compliance:

• A: Addresses critical barriers like keyboard navigation, image ALT text. Without these bare minimums, users with disabilities have the equivalent of no access to your site.
• AA: Covers common issues like WCAG-compliant contrast ratios and consistent navigation. AA is the level required for most legal regulations throughout the world.
• AAA: Goes beyond the recommended support included in AA to introduce things like sign language support in videos, consistently compliant color contrast, and full support for keyboard-only navigation.

When issues are discovered, they are typically categorized in three buckets:

• Critical: These issues block a user from completing a task.
• Serious: These issues make it difficult for users to complete tasks, but completion is still possible.
• Minor: These issues may be annoying to a user, but don’t impede task completion.

Once your initial audit is complete, you need to look at how to fix those issues. Depending on the type of issue, you may need to engage one of the previously mentioned stakeholders. It’s also important to identify which person or team owns driving the issues to completion. For instance, you might tell the engineering team they have an issue, but how do you make sure it gets into their backlog as a priority with a deadline for implementation?

When it comes time to prioritize issue resolution, in addition to understanding the issue severity, it’s helpful to understand the underlying risks involved. Are some issues business-impacting, like preventing users from completing a paid subscription or checking out of your store? Are there issues on your most visited pages? Do the issues create other types of compliance risks?

How accessibility audits fit into CMS operations

Timing your audits with key events in your CMS operations can help ensure you don’t create extra work for the team while also baking accessibility into your regular approach to maintaining your publishing operation. This means auditing as part of your migration planning, when you scope a redesign, or during major releases of new website features.

One way to scale your accessibility efforts is to leverage component-level audits where possible. Instead of looking at individual pages, look at the components that make up those pages. For the components that are used on more than one page, you can fix the accessibility once and cascade it out to all the places that component is used.

WordPress simplifies component-level auditing with the native Gutenberg Block Editor. You can modify a component of your WordPress theme and cascade the change everywhere it’s used.

You still need to perform page-level auditing in combination with component-level checks. The page context matters just as much as whether the component is accessible. One common example might be the nesting of headings on a page, where an H3 tag is incorrectly placed above an H2 in the presentation.

Like other aspects of your content program, governance is important in accessibility too. Defining roles and workflows around who is accountable for aspects of accessibility makes it easier to keep track of which aspects are being met or not.

Providing clear documentation and reporting out on your accessibility program, including sharing audit trails when relevant, can further promote accountability within the organization.

Adding process steps, like pre-publishing checks for things like ALT tags on images can help prevent regression. It is also possible to put in tooling that will provide error messaging for a user if they missed a step in their part of the workflow.

Making accessibility an ongoing practice

Maintaining an accessible website is best done by baking accessibility into your workflows and processes. Periodic audits are important for understanding a snapshot in time, but continuous monitoring will go further to making sure you are always compliant. It also reduces the overall workload by making accessibility part of daily activities.

Teaching your content creators and editors best practices for publishing, including adding ALT text, is part of your publishing DNA and saves time in the long run while creating a trusted experience. On the developer side, having your engineering team test for accessibility as part of the release process also helps streamline accessibility.

Choosing a platform that integrates accessibility into every layer further simplifies maintaining accessibility. WordPress VIP makes it easy to build accessibility into your page templates, individual blocks, and the underlying design system used for your website.

With ongoing audits, you can report to leadership on where you started in your accessibility journey, the progress you’ve made, and where you plan to continue improving accessibility over time.

Accessibility as an operational capability, not a checkbox

Shifting your team’s mindset around accessibility is critical to maintaining an accessible website over time. Audits are a function of maintaining quality and gaining user trust; they aren’t just an item on a to-do list. Being proactive in your inclusion of accessibility throughout the content lifecycle makes it easier to achieve consistently high accessibility over time.

---

Related content

Accessibility Tooling Comparisons: How Enterprises Evaluate and Operationalize Accessibility Tools

Read the article

Author

Jake Ludington

Jake is a technology writer and product manager. He started building websites with WordPress in 2005. His writing has appeared in Popular Science, Make magazine, The New Stack, and many other technology publications.

It’s a way of operating that respects their preferences and treats them as individuals, which helps deepen relationships and loyalty.

The omnichannel customer journey isn’t limited to purely digital touchpoints but physical interactions that take place in stores or office locations as well. It spans channels you own, like your website, but also channels you don’t, like online marketplaces and social media. AI, meanwhile, is changing the way digital experiences like online search and raising customer expectations across other channels.

As additional channels continue to emerge, orchestrating an omnichannel customer experience has gotten more complex, which explains why some organizations have chosen to invest in a digital experience platform (DXP). They often learn, however, that DXPs can suffer from feature bloat, where many functions are under-utilized, and can present significant integration and maintenance costs.

You can easily avoid those issues by using your CMS to power omnichannel digital experiences, especially if it supports headless or hybrid architectures. This should be a key part of your decision-making criteria as you develop your omnichannel strategy.

What is an omnichannel digital experience?

An omnichannel digital experience gives customers the flexibility to consume content in the modality of their choice, and gives them the freedom to switch channels without sacrificing the quality of a brand interaction. Instead of forcing customers to receive a text or download an app, they can find the content they want on a blog post, via video, on a partner portal, and more.  

The best omnichannel digital experiences are intentionally developed by mapping out where customers tend to look for content and then ensuring they have established:

• A shared content model: Instead of creating content from scratch for each channel, a shared content model lets you repurpose a single asset multiple times without losing the core message or meaning, as well as metadata.
• Unified data: An omnichannel digital strategy depends on breaking down siloes and allowing a single version of the truth to be centrally stored and used in multiple contexts.
• Channel-optimized delivery: A social media post can look a lot different than content appearing on a digital sign or on a landing page. You need an automated way to tailor the story you’re telling to the nuances of the medium where it appears.
• Consistent personalization/rules: To a certain extent, customers should be able to take the way they interact with your brand for granted. That only happens when you create rule-based triggers that shape experiences in the way they expect, regardless of channel.

This represents a big difference from single-channel experiences, where the only way to connect with a company was by visiting a physical location or calling them by phone. It’s also a step beyond multi-channel experiences, where a brand might have social media accounts but only uses them for marketing rather than fielding service enquiries. Omnichannel digital experiences are inherently holistic.

Why traditional DXPs are not the only answer

DXPs promise the world: a CMS, personalization capabilities, marketing automation, analytics, and more. That breadth can come with a hefty price tag attached, however, and fully implementing a DXP can demand significant time and resources.

The danger of a DXP is that while it might enable omnichannel digital experiences, most organizations won’t need all the features it offers. No one can afford to over-buy technology, which can introduce unnecessary complexity into your tech stack.

DXPs also face a crossroads as agentic AI offers the potential for increased productivity and efficiency. Yet AI agents will have to prove they can work within a DXP to manage everything from coordinating content and executing workflows to providing analytics on their performance. This is where the threat of vendor lock-in with a DXP vendor should raise alarm bells. What if you can’t easily make changes?

A leaner but more compelling approach is to think in terms of a CMS-centric composable tech stack, where your CMS provides the foundation for omnichannel digital experiences but you’re still open to add or change out tools based on your business needs. Let’s see what this looks like in practice.

The CMS‑centric architecture for omnichannel

A CMS was traditionally seen as limited in delivering content flexibly across channels until hybrid headless architectures emerged.

By decoupling the CMS from its front end or presentation layer, though, organizations can now easily bring their content to life across apps, kiosks, or smart devices.  

While there has been debate around headless vs. hybrid CMS architectures, the latter letting you use APIs to pursue headless-like content distribution across multiple front ends. That means you get to keep a more traditional authoring experience, preview content, and not lean as heavily on your development team.

A hybrid headless CMS also means you can connect more easily to other tools that pull in data for omnichannel digital experiences, such as a customer data platform (CDP) or CRM.

Powering each channel with a CMS‑first stack

With a CMS anchoring your omnichannel digital strategy, you’re ready to bring content across:

Your site is your calling card, and it should immediately welcome visitors with everything they need to find the products and services they want. That’s why your CMS needs to support content models based on a variety of page layouts and components. These make it easy to repurpose and reuse assets in other channels.

For example, WordPress VIP’s block-based editor, Gutenberg, lets you easily add buttons, columns, and other elements as required. Anyone can use these without having to directly touch any code.

Your CMS should also work with modern front‑end frameworks, such as React, Next.js, Vue, Nuxt, and SvelteKit to render content from APIs.

Exposing content via APIs through your CMS is a fast-track to reaching customers who prefer downloading and installing a branded mobile app too. You can use the same structured content and APIs for both iOS and Android apps, given they consume the same models, data, and logic. You’ll avoid having to maintain separate content stores and streamline your content operations in the process.

Why make customers pull out a phone or a laptop when you can communicate with them through a smart display in your office lobby or monitors set up throughout a store location?

Content modelling plays an important role here as well, where you’ll want to map content types to digital signage or kiosk experiences. For each use case, whether it’s simple wayfinding information or a special promotional offer, your model should include a title, short description, image/video URL, call to action (CTA) text, and more.

Unlike content delivered to your site or app, you may want to fine-tune details such as how long the content should appear, if there’s a priority in terms of messages and any location-specific rules, such as whether content should appear on screens hanging on a specific floor or another geographic region. This is all much easier to do in a CMS than a jumble of siloed systems.

Many large enterprises work with third parties such as resellers, system integrators, or consultants to reach their total addressable audience. This calls for an extension to the omnichannel customer journey.

You can get there by using secure APIs or dedicated front ends that limit the risk of data theft or misuse. Complement that with governance controls that stipulate the roles and permission levels for both partners, as well how approval processes should work before any content goes live. Your brand guidelines need to be woven in here, as should any regulatory compliance considerations.

Integrating a CMS with modern front‑end frameworks

There’s no need to make omnichannel digital experiences more complicated than they already are. Your CMS back end can keep all your posts, pages, and custom content types within the same infrastructure, and then fetch them as needed via REST or GraphQL for server-side and static rendering.

This kind of component-driven design makes sense because you can not only deliver content to all the relevant touchpoints but also offer a consistent user experience (UX) along the way.

For developers in particular, there’s a lot more room to pursue continuous integration and continuous development (CI/DC). Given that extending into additional channels can come with some risks, this approach also lets you test everything thoroughly and optimize performance as required.

Beyond content: orchestration through integrations

Omnichannel customer experiences aren’t an exercise in building so much as orchestrating. DXPs can limit your ability to explore all possible integrations that could enhance your results, which is one of the reasons WordPress VIP has focused on an open, intelligent approach instead.

Instead of simply having a presence across myriad digital channels, for instance, you could go even further by integrating:

• A CDP that lets you work with your audience data to identify customer preferences and segment them to target content more effectively.
• A personalization platform or tool that sets up “if/then” rules based on how customers navigate the omnichannel journey.
• Search and recommendation services that help customers make the most of their time in each channel, whether it be discovering new products and services or simply getting their frequently asked questions answered.
• Commerce and inventory systems to help your content not only educate and inspire customers but convert their activity into orders, purchases, or subscriptions.

A DXP might offer all of this, but it means buying into a monolithic solution rather than enjoying access to an ecosystem of innovative companies that will solve both today’s and tomorrow’s problems.

Implementation roadmap: A practical 5‑step plan to delivering omnichannel digital experiences

Once you opt for a CMS-centric composable tech stack, your omnichannel digital strategy can move forward based on the following steps:

When a CMS‑first approach beats a full DXP

There are still some edge cases where a full DXP may make sense, such as a heavily marketing-led organization that wants a comprehensive, out-of-the-box suite. 

For most, though, nothing beats the ability to pick and choose how you deliver omnichannel digital experiences, and the ability to enhance them as your business and customers’ online behavior evolves.

---

Related content

How WordPress VIP Represents a Complete F1 Racing Program for Your Content Experience Needs

Read the article

Author

Shane Schick

Founder, 360 Magazine

Shane Schick is a longtime technology journalist serving business leaders ranging from CIOs and CMOs to CEOs. His work has appeared in Yahoo Finance, the Globe & Mail and many other publications. Shane is currently the founder of a customer experience design publication called 360 Magazine. He lives in Toronto. 

Omnichannel content management solves this by centralizing content and enabling delivery to any channel from a single source. But not all approaches are equal. Some architectures prioritize delivery at the expense of editorial experience. Others preserve the tools creators love but limit where content can go.

This guide covers what omnichannel content management requires, the architecture options available, and how to measure performance across channels.

What is omnichannel content management?

Omnichannel content management is how you create, organize, and deliver content from one central system to every channel your audience uses, while keeping messaging consistent and on-brand everywhere.

The key word is “unified.” With multichannel, each platform operates on its own. You create content for the website, then recreate it for the app, then again for email. With omnichannel, everything connects. You update once, and it shows up everywhere.

The distinction matters because most organizations think they’re doing omnichannel when they’re really doing multichannel. They publish to multiple platforms, but content lives in separate systems, messaging drifts, and updates require someone to manually copy changes across five different tools.

The four pillars of omnichannel content management

Omnichannel content management rests on four foundational elements. Get these right, and you can deliver consistent experiences across every channel. Miss one, and the whole system breaks down.

Everything starts with a single source of truth. Instead of storing content in separate systems for web, mobile, and email, you manage it all from one place. When you update a product description or brand message, it changes everywhere at once. No more hunting through five platforms to fix a typo.

Your content needs to work anywhere without being rebuilt for each channel. That means structuring it in modular pieces (headlines, body copy, images, CTAs) that can adapt to different formats. A product description might appear as a full page on your website, a card in your app, and a snippet in an email. Same content, different presentations.

Personalization only works when you know who you’re talking to. If your CMS, analytics, and customer data live in silos, you can’t tailor content based on what someone did on another channel. Omnichannel content management connects these systems so context follows the customer wherever they go.

Consistency requires guardrails. You need role-based permissions so the right people can edit the right content. You need approval workflows that keep quality high without slowing teams down. And you need brand guidelines that translate across channels, so your voice sounds the same whether someone reads your blog or opens your app.

Choosing the right architecture for omnichannel content delivery

Your architecture determines what’s possible. Before you commit to a direction, it’s worth understanding what each approach actually involves, and what you might be giving up.

With a traditional CMS, content and presentation are tightly linked. You create a page, design how it looks, and publish it to your website. Content teams get intuitive tools: drag-and-drop layouts, WYSIWYG editing, real-time previews.

The limitation is channel expansion. If you want to push content to a mobile app or digital signage, you’re looking at workarounds or separate systems.

A headless CMS separates content from presentation entirely. Your content lives in a repository and gets delivered to any frontend through APIs. Website, mobile app, kiosk, voice assistant: the same content can go anywhere.

But there are trade-offs. Someone has to build every frontend from scratch. Editorial teams often lose the tools they rely on: no more previews, no more WYSIWYG, no drag-and-drop. And the complexity adds up. You’re essentially maintaining two systems, your content layer and your presentation layer, each with their own dependencies and deployment pipelines.

That’s developer time that could be spent on features that actually differentiate your digital presence.

A hybrid CMS gives you both. Content creators work in a familiar editing environment with live preview and visual tools. Developers get APIs to deliver that same content to any channel that needs it.

This is where WordPress VIP sits. You get the flexibility of headless without sacrificing the editorial experience that makes teams productive. REST API and GraphQL support means the same content can feed decoupled frontends, mobile apps, or third-party systems. But editors aren’t stuck in a stripped-down backend interface.

The question isn’t “headless or not?” It’s which channels need decoupled delivery, and which benefit from a full editorial experience.

How to structure content for omnichannel delivery

Architecture gets you halfway there. The other half is how you structure the content itself. If your content is locked into page-based formats, it won’t travel well across channels. If it’s modular and well-organized, it can go anywhere.

Think of content in components, not pages. A product description, headline, image, and CTA should each exist as separate pieces that can be assembled differently depending on where they appear.

That same product description might show up as a full page on your website, a card in your mobile app, and a two-line snippet in an email. If you’ve built it as one block of text inside a page template, you’ll end up rewriting it for each channel. If you’ve structured it as modular content, you pull the pieces you need and let each channel render them appropriately.

Tags and categories aren’t just for internal organization. They power personalization, search, and content recommendations across channels.

Tag by context: audience segment, funnel stage, content type, product line. The more consistent your taxonomy, the easier it is for systems to surface the right content at the right moment, whether that’s a recommendation engine, a search bar, or an API call from your mobile app.

Here’s a simple test: can you pull your headline, intro paragraph, and featured image separately through an API? Or does your CMS store the whole article as one chunk of HTML?

Blob content (one field, one block of text) is hard to repurpose. Structured content (separate fields for each element) adapts easily.

WordPress VIP’s block-based editor naturally supports this. Gutenberg breaks content into discrete blocks that can be reused, rearranged, and delivered independently. For teams managing multiple sites, reusable blocks can be defined globally and updated across an entire multisite network from one place.

Measuring content performance across channels

You can’t improve what you can’t see. And when content lives across multiple channels, visibility becomes a real challenge.

Most analytics tools are channel-specific. You get website metrics in one dashboard, app engagement in another, email performance somewhere else. Stitching together a complete picture of how your content is performing takes manual effort, and by the time you’ve done it, the moment has passed.

Omnichannel content management requires a different measurement approach. Instead of asking “how did this page perform?” you need to ask “how did this content perform everywhere it appeared?”

That means tracking these metrics:

• Engagement by channel: Where are people spending time with your content? Where are they bouncing?
• Content velocity: How long does it take to get from draft to published across all channels?
• Cross-channel journeys: Are users starting on one channel and converting on another? Which paths actually lead somewhere?
• Consistency gaps: Is the same content performing differently across channels? That might signal formatting issues, timing problems, or audience mismatches.

The goal is a unified view of content performance without requiring your team to manually pull reports from five different systems.

That starts with your CMS. If your content management platform includes built-in analytics, you’re already ahead. If it doesn’t, you’ll need to integrate third-party tools and hope the data lines up.

WordPress VIP includes Parse.ly for exactly this reason. It gives content teams real-time visibility into what’s working, which pieces are driving engagement, which are falling flat, and where to focus next. When you’re publishing across multiple properties, gut instinct isn’t enough. You need data that shows what’s performing where, without waiting for a weekly report.

Omnichannel content management at enterprise scale

Theory is one thing. Execution is another. Here’s how organizations are actually delivering omnichannel content at scale without sacrificing editorial experience or operational sanity.

Publishers operate under constant pressure: breaking news, tight deadlines, content that needs to reach audiences on the web, in apps, through Apple News, Google Discover, social platforms, and syndication partners. Often within minutes.

News Corp Australia manages dozens of media properties across three continents from a single WordPress VIP multisite network. Content created once flows to web, mobile, and partner channels while editors maintain full control over presentation and timing. When you’re publishing at that volume, you can’t afford to manually recreate content for each destination.

Organizations with multiple brands face a different challenge: delivering localized, brand-specific content while maintaining some level of global consistency and governance.

Capgemini runs 38 sites across more than 10 languages on WordPress VIP. Each region gets the flexibility to create content that resonates locally. But global teams retain visibility and control over shared assets, messaging frameworks, and compliance requirements. The CMS becomes the connective tissue between local execution and global strategy.

Public agencies have to reach citizens across web, mobile, accessibility-compliant formats, and sometimes physical kiosks. Consistency isn’t optional when you’re communicating public health guidance or emergency information.

NASA consolidated fragmented web properties into unified content hubs on WordPress VIP, giving distributed teams a shared platform while ensuring consistent, accessible delivery across channels.

These organizations didn’t choose between editorial experience and omnichannel delivery. They found a way to get both. The pattern is the same: centralized content, flexible delivery, and governance that scales.

Getting started with omnichannel content management

You don’t need to overhaul everything at once. The organizations that succeed with omnichannel content management typically start with a clear picture of where they are, then build toward where they need to go.

Map out what you’re working with. Where does content live today? How many systems are involved? Where are the gaps, the duplication, the bottlenecks?

Talk to the people who create and publish content every day. They’ll tell you where the friction is.

Not every channel deserves equal investment. Start by answering three questions:

• Which channels do you serve today?
• Which channels will you need in the next two to three years?
• Which require decoupled delivery, and which work fine with traditional publishing?

This helps you avoid over-engineering for channels you don’t actually need yet.

Match your architecture to your real requirements. If most of your traffic and conversions happen on your website, a hybrid CMS probably makes more sense than going fully headless. You get API flexibility for the channels that need it without giving up editorial tools for the channels that don’t.

Move away from page-based content toward modular, structured components. Establish taxonomy and metadata standards early. Create reusable blocks and templates that can travel across channels without manual rework.

Define roles and permissions. Set up approval workflows that maintain quality without creating bottlenecks. Document how content should adapt for different channels so your brand stays consistent as more people get involved.

The goal isn’t perfection on day one. It’s building a foundation that lets you move faster over time.

Building for what comes next

Omnichannel content management isn’t a destination. It’s an ongoing capability that evolves as your channels, audience, and business needs change.

The organizations that get this right don’t try to solve everything at once. They start with a clear architecture, structure content for reuse, and build governance that scales. They pick a platform that gives them flexibility without forcing trade-offs between editorial experience and multi-channel delivery.

The channels will keep multiplying. Customer expectations will keep rising. What won’t change is the need for a foundation that lets you move quickly, stay consistent, and measure what’s working.If you’re evaluating your options, WordPress VIP offers the flexibility of open source with enterprise-grade security, managed infrastructure, and built-in content analytics. It’s built for teams who need to deliver everywhere without losing control of how they work

---

Related content

Websites FTW, Forever: Why Brands Still Need A Website In 2026

Read the article

Author

Vanessa Hojda García

Vanessa is a writer and content manager. They’ve worked with some of the best SaaS brands like Shopify and Mailchimp. When they’re not working on content, you’ll find them making art, reading a book, or traveling.

One common misconception with accessibility testing is that getting a great accessibility score from a tool means you’re finished. This is sometimes known as “one-tool compliance.” Automated testing tools often miss key accessibility gaps that are only discoverable when users test for the lived experience of using assistive technologies with your website.

To achieve a consistent, accessible experience, you need a system in place, not a silver bullet that magically eliminates any accessibility issues. These systems are built around tools that both easily integrate with your existing workflows and accurately provide you with the actionable feedback required to deliver on accessibility. 

The core categories of accessibility tools

There are several categories of accessibility tools that are useful at different stages of your content publishing lifecycle. They also follow different implementation strategies. 

Preventive tools tend to be part of the website design and development paradigm of shifting left and catching issues before they make it to your production website. Reactive tools monitor accessibility after your website is in production. 

These accessibility tools generally fall into one of the following categories:

Design-phase tools validate things like color contrast before any website coding is done. This could be a Figma plugin if that’s where your site designs start, or a color contrast plugin for WordPress that runs on the non-production version of your site. 

Automated scanning tools assess your live site and offer an effective first pass at accessibility, catching things like color contrast, missing alt text on images, font size, font readability, and link highlighting. Automated scans generally catch about 30-40% of accessibility issues.

Manual testing tools assess the actual lived experience of users who engage your site with assistive technologies. Examples include:

• Using screen readers to test for read-aloud compatibility.
• Keyboard navigation for moving around on the page and assessing the focus order of forms and buttons.
• Zoom levels to understand how well aspects of your site perform for users with low vision.

CI/CD and developer-focused testing tools are the shift-left approach to automated testing. By integrating automated testing before pushing website code to production, you prevent accessibility issues before they occur. Some common developer accessibility tools include:

• Accessibility Insights
• Axe
• Pa11y
• Lighthouse

Monitoring and reporting platforms help ensure your site remains accessible by providing ongoing insights. Some popular accessibility monitoring solutions here include:

• The Axe Platform from Deque
• Level Access
• Siteimprove

A governance layer should work in combination with all these tools to track things like Voluntary Product Accessibility Templates (VPATs), Accessibility Conformance Reports, and any legal settlements or agreements associated with accessibility. 

How enterprises actually compare accessibility tools

When it comes to choosing accessibility tools for your organization, there are several factors to consider. While the core reason for improving accessibility is to enhance user experience, the reality is that accessibility also involves risk mitigation. The following factors are useful when considering both:

Tools promise to catch everything. What they do catch needs to be accurate. There’s a delicate balance to manage between trying to get too much coverage from a single tool vs. making sure what is covered is accurate. One key here is understanding the false positive rate. How often is the tool telling you something is wrong that isn’t?

When it comes to accessibility testing, what’s easy to use for your software developers won’t be the same as what’s easy for your content team, QA team, designers, or anyone else involved in maintaining consistent accessibility standards. It’s important to understand both what a tool does and who will use it.

Identifying which tools are compatible with your CMS, your developers’ CI/CD workflows, and your bug tracking systems helps ensure tools fit into how you work.

Part of mitigating risk is having the documentation to know what changed, when it changed, and who changed it. Supporting this need is a key factor when choosing a tool.

When accessing a vendor, it’s also important to understand how accessible their tools are. A VPAT basically lets you know whether the tool is WCAG-compliant or not.

Understanding both upfront and ongoing tooling costs can be critical to avoiding budget surprises. Operational overhead also contributes to costs when tools add complexity to existing workflows.

Is the tool telling you how to fix the problems it identifies? This is key to keeping operational overhead low.

Why enterprises use multiple accessibility tools

While it would be great to find the one tool to achieve all of your accessibility outcomes, the reality is that most enterprises end up using several tools. Part of this is due to the limits of automation. Automating at the design and code level can catch some issues, but manual testing will still be required. 

When it comes to choosing tools, you will likely end up with some that overlap in functionality. While it’s generally a waste of your budget to pay for two or more things that perform the same function, it can be useful to include intentional redundancy to validate accessibility at different points in your content publishing lifecycle.

One key thing to avoid is any tool that promises to fix your accessibility issues with a “one-line-of-code” solution. These solutions might mask accessibility, but they do not fix the problem at its core. There is an increased risk to your organization in trying to use these shortcuts.

Operationalizing accessibility tooling in CMS workflows

Having an ongoing testing plan in place is important, but key moments in the life of your website, like migrations, redesigns, and major releases, are crucial moments to use accessibility tooling. Without testing, your design team may introduce an incredibly innovative new website look that is entirely inaccessible to anyone who needs assistive technology.

This is where assigning ownership across teams is crucial. Have clear owners at each stage, from design to development, all the way to the team publishing new content on a regular basis. Have clear roles for each of those owners, specifying what they are responsible for.

One way to prevent regressions and operationalize accessibility is to leverage atomic elements of your website. When you maintain accessibility at the source, like at the block or template level, you can cascade accessibility across your site without needing to make page-level changes. It’s still important to validate that page-level accessibility is maintained, but the overhead to check will be much lower.

The same analytics you use to measure your website’s success can also be used to manage your accessibility efforts. The most visited content will have the greatest impact on your site’s accessibility. When you’re looking for a place to start, the top content list is a great place to begin.

What CMS choice changes about accessibility tooling

Choosing the right CMS can make accessibility easier (or more difficult). Platform architecture affects your ability to integrate tools. For example, the WordPress plugin architecture makes it easy to integrate a number of accessibility tools.

Your CMS can also address issues around governance, user roles, and workflow enforcement. When your CMS lets you to dictate who can change which aspects of your website, you maintain better control over who changes elements that affect accessibility. You also get an audit trail to track those changes. Workflow enforcement can further improve accessibility by requiring specific steps prior to submitting content changes.

The previous section mentioned changes at the atomic level. This is another area where the CMS does the heavy lifting. WordPress lets you to create reusable blocks and templates that maintain the same accessibility when used across different parts of your website.

Choosing tools is easy; building a system is hard

It can be tempting to view a high-end accessibility scanner and its scoring system as an easy accessibility fix. In reality, that tool is only as effective as its role in your workflow. If the scanner finds 572 errors but those errors never reach your bug-tracking backlog or the content team’s CMS dashboard, the tool is a failure.

Moving from chasing errors on your pages to proactive digital inclusion is the real sign of accessibility maturity. Most organizations start by finding and fixing errors on their live site. As they mature, they shift left to fixing issues before they go live by updating designs, adding testing to the CI/CD pipeline, and empowering the content team to make fixes at the block and template level.

Focusing on process and platform in your tooling choice and accessibility strategy leads to a more successful accessibility program. A CMS that enforces structured data and accessible components helps reduce the number of errors an accessibility scanner needs to catch. Adding process at the development layer, like requiring an automated check prior to code merge, puts accessibility on equal footing with other quality signals like security and performance.

As your accessibility journey matures, you can be more strategic in how you evaluate new vendors and tools. There is no “perfect” accessibility tool. Look beyond the features a vendor promises and ask:

• Does this tool integrate with the way we work?
• Is the feedback actionable for the intended role (design vs. dev vs. content)?
• Can it scale across our organization without wearing out the team with constant alerting?

---

Related content

Website Accessibility Standards for Businesses

Read the article

Author

Jake Ludington

Jake is a technology writer and product manager. He started building websites with WordPress in 2005. His writing has appeared in Popular Science, Make magazine, The New Stack, and many other technology publications.

Organizations have always been in a race against time, but earlier waves of innovation have been arguably less disruptive. Shifting from on-premises IT to the cloud was a change that was rolled out gradually in many cases. Adopting mobile technologies and embracing social media were signficiant shifts as well, but AI is fundamentally changing how people create content, write code and automate everyday business tasks overnight.

This creates a particular tension where senior leadership teams are trying to balance speedy innovation and delivering differentiated digital experiences with strong security and governance. No wonder 26% of CEOs cite greater agility and faster decision-making as the top leadership capabilities, while 80% say they feel more pressure to ensure the long-term prosperity of the business.

The result can be digital decision paralysis, where decisions to enhance critical assets like websites or invest in a modern CMS are delayed or indefinitely stalled. In fact, 57% of executives feel they’re missing opportunities because they’re not making decisions fast enough. The risk is that competitors will prove quicker and more nimble, using their momentum to steal market share.

WordPress VIP strategic account manager Brant Williams said that to some extent, it’s only natural that business leaders take a beat before committing themselves to a particular AI roadmap.

How can you get senior leaders in a large organization to move forward with strategic investments even when the full implications of AI for business strategy within the next 18-24 months are impossible to know for certain? Read on to understand why decision paralysis arises and what to do about it.

Core causes of AI decision paralysis

Making a decision becomes paralyzing when it feels more likely you’re making a mistake. No one wants to allocate budget towards technology that won’t work as expected or (worse) lead to negative outcomes.

Other root causes include:

• Conflicting stakeholder priorities: Building brand awareness is the top CMO priority, which suggests enhancing your website’s front and back end with AI capabilities is a good idea. However cybersecurity and risk management is the top CIO priority. What if AI adoption somehow leads to a data breach? It can seem easier to put off a decision rather than inflame conflict with one or more business functions.
  
• Unclear AI strategy: Many organizations see value in AI platforms and tools but haven’t thought through their deployment plans. In fact, one study said companies are missing out on 40% of potential AI productivity gains due to talent gaps. Senior leaders might put projects on the back burner until they  have better sense of their future skills and training requirements. 
  
• Fear of vendor lock-in: Market research firm Gartner warned that IT leaders underestimate how closely their data, models or workflows become tied to vendor-specific APIs, data lakes and platform tools. How can you be sure you can trust AI for business strategy if you can’t fully trust your tech partners?

Though it might seem like prudent caution, AI decision paralysis can hurt a company that takes a “wait and see” approach. Not only might rival organizations get ahead of you, but customers may come to expect AI-powered capabilities in the experiences you offer.

How an open and intelligent approach can overcome decision paralysis

Rather than treat every digital decision as an existential choice, set yourself up to pursue structured experimentation to learn and fine-tune your AI for business strategy.

Opting for solutions based on open source, for instance, helps address that fear of vendor lock-in because they offer greater interoperability and data portability. They also provide greater customization to address cybersecurity risks while meeting the needs of business functions like marketing.

Combine that openness with intelligence in the form of data and analytics that can help define the best strategy based on customer behavior, employee needs, and operational considerations. Instead of merely dropping AI into your organization’s workflows, you’re positioning your organization to gather insights and deploy solutions with the flexibility to keep pace with the future.

An open and intelligent approach ultimately helps reduce the risk of regretting your decisions, which makes it easier to move forward.

Balancing speed, security, and unique experiences

Adopting AI, or any other kind of technology, comes down to decisions about where to use it, where not to use it, and when to revisit those choices as tools and business processes mature. What helps is a framework that balances the three key priorities mentioned earlier:

• Speed: Overcome the fear of errors or bad outcomes by investing in platforms that allow for rapid development cycles and the rollout of new interfaces. These are all staples of a truly enterprise-grade CMS, helping content teams establish low-friction creation, review, and publishing workflows.
  
• Security: There’s no need to be paralyzed by the prospect of upgrading or migrating to a new platform if it’s built on zero-trust principles, with strong controls over content approvals and features that ensure regulatory compliance by design.
  
• Unique experiences: What your customers want and need two years from now may be unknown, but you can be sure you’ll need tools like a CMS that can offer a hybrid headless approach to further omnichannel efforts. A platform with plenty of integrations, plug-ins, and expert partners will also make it easier to contend with unexpected future requirements.

Brant suggests looking for common pain points: if your engineers are overloaded with work and your marketing team lacks the autonomy to get ideas and campaigns out the door,

Responding pragmatically to AI innovation

Pushing back AI decision paralysis doesn’t mean you’re throwing due diligence out the door. Monitoring AI tools for bias or hallucinations, developing responsible use policies, and acting with transparency is still important. These should be natural steps in any IT investment evaluation and deployment, not hurdles that the business becomes too wary to jump.

Brant noted that technology standards are also helping ease some of the potential challenges in making an AI-powered CMS work cohesively with a CRM, CDP, and other parts of the tech stack. Model Context Protocol (MCP), for instance, avoids having to redo the same integration work every time a new AI tool emerges.

As you move forward, help senior leaders see technologies like AI as a replaceable service layer, rather than something hard-wired into the core platform. This can make some digital decisions feel less ominous or daunting.

An action plan to defeat AI decision paralysis

Strategic business decisions are rarely made by a single person. Creating an “AI decisions council,” either formally or ad hoc, based on emerging issues, could be another way to avoid getting stuck amid uncertainty.

Use this diagram to lead the discussion, tweaking and customizing it based on the specific nuances of your organization and the form of AI or other technology you’re wrestling with:

The rapid advancement of AI for business strategy proves that any certainty about what the future will look like over the next 18-24 months is unlikely. The only recourse is designing your tech stack with change in mind. Investing in an open and intelligent CMS and web architecture as a starting point? That’s an easy decision to make.

---

Related content

Conversational AI and Article Pages: What the Future Looks Like

Read the article

Author

Shane Schick

Founder, 360 Magazine

Shane Schick is a longtime technology journalist serving business leaders ranging from CIOs and CMOs to CEOs. His work has appeared in Yahoo Finance, the Globe & Mail and many other publications. Shane is currently the founder of a customer experience design publication called 360 Magazine. He lives in Toronto. 

Business and technology leaders within media organizations need the same outside perspective to make sense of new revenue models, shifts in distribution, or the impact of AI. It’s too easy to get so heads-down about your own unique business needs that you overlook important digital publishing trends as they emerge.

That’s why many publishers rely on WordPress VIP and Fueled Digital not merely as sources of innovative technologies, but expert insight.

A research-backed guide for creating a media and publishing strategy

In our new, co-authored whitepaper, we’re breaking down everything you need to develop a media and publishing strategy that can adapt to the sector’s current disruptions. This includes the fragmentation of search amid the rise of AI answer engines, privacy and governance concerns, and the demand for more scalable content operations.

Downloading the report will help you answer questions you and your team might be asking, like:  

Most publishers understand that subscriptions, memberships, ecommerce, events, and licensing will all become part of their monetization mix. We suggest a way forward for diversification that lets you support experimentation, segmentation, and performance measurement across all those revenue streams and more.

Over-reliance on rented audiences from platforms and other intermediaries has been a problem for some time, but we’re now reaching a tipping point. We’re offering ways to understand audience behavior, preferences, and engagement, and boost both personalization and monetization.

Responsibly and effectively using AI starts with identifying where it already exists in your content workflow, and where it’s going. Planning, creation, editing, packaging, distribution, discovery — nothing will be left untouched. 

That makes it vital to begin strengthening content structure and layering on clearer governance. We not only talk about that, but also how to do it with systems designed for reuse and orchestration vs. one-off publishing.

From search and social to newsletters, apps, video, and emerging platforms, publishers are expected to be everywhere. This fragmentation exposes the limits of page-centric workflows, but our report shows how modular content can be adapted across channels without duplicative effort.

Publishers are being pushed to modernize how content is governed and audited while maintaining speed and editorial flexibility. Our report’s framework suggests trust signals you can turn into a competitive advantage.

Many publishers are moving toward cloud-native, API-driven, and composable platforms that better support scale, resilience, and long-term adaptability. Let us show you why migrating is not only necessary but achievable without causing unnecessary disruption to everyday content workflows.

Why publishing trends matter more broadly

Our research shows these digital publishing trends reinforce each other, and call for a broader transformation effort that will prepare media organizations for the future.

That said, the best practices we’re highlighting are applicable well beyond media and publishing. Any organization that relies on content at scale can learn from how publishers are modernizing structure, workflows, and platforms to operate across channels and prepare for continued change. 

Taking the steps outlined in the report will put publishers on par with the largest enterprises.

Publishing often acts as an early indicator for where content operations are headed. What works at publishing scale frequently becomes the blueprint for broader digital teams.

Author

Shane Schick

Founder, 360 Magazine

Shane Schick is a longtime technology journalist serving business leaders ranging from CIOs and CMOs to CEOs. His work has appeared in Yahoo Finance, the Globe & Mail and many other publications. Shane is currently the founder of a customer experience design publication called 360 Magazine. He lives in Toronto. 

When it’s used properly, the technology is not just a faster or more efficient means of producing blog posts, email blasts, and ebooks. Marketers and others within large enterprises should also use AI to help summarize, organize, and analyze data to help leaders make smarter decisions. That only comes when you’ve baked editorial trust in AI-assisted workflows.

By “editorial” we don’t simply mean the kind of articles you read in your favorite newspapers and magazines. Editorial content within an enterprise goes beyond selling products and focuses on educating and even entertaining buyers. It’s often thought leadership content that helps guide people to the products and services that will solve complex and critical business problems.

Adopting AI to create that content is arguably easier than ever now that its features are integrated or built into modern publishing platforms. The danger is in moving so quickly you overlook risks like bias, misinformation, privacy breaches, and failure to comply with industry regulations.

Most companies are trying to do the right thing with AI. A 2025 survey found 77% of organizations are working on AI governance, but marketing departments didn’t show up in any of the functions involved in leading it. Even more worrisome, half of organizations admit difficulty in translating responsible AI principles into scaled operational processes.

Fortunately, there are some responsible AI content practices emerging that can help build editorial trust in AI-assisted workflows. It’s a matter of learning what they are and incorporating them into your strategy as you deploy the technology to your content teams.

From newsrooms to boardrooms: extending governance lessons

AI isn’t just for writing content but helping develop ideas and researching them. At USA Today, for example, news reporters frequently need to file requests to access public records. This has traditionaly been a very manual process of filling out forms, which makes it a prime use case for agentic AI.

As we noted in a building editorial trust in AI-assisted workflows for the media sector, USA Today balances the speed of execution that agentic AI allows with human oversight from both its editors and reporters, as well as its in-house legal team. This helps avoid any mistakes that could compromise its coverage and damage its reputation with subscribers and everyday readers.

This is exactly how AI governance for editorial teams should work outside of media and publishing, too. While journalists always need to back up what they say in print, enterprise marketers are equally accountable to their customers, prospects, partners, and investors.

Whether you work in global marketing, content, or brand communications, you need a similarly rigorous approach to driving system-level trust and scalable governance.

Defining editorial trust in the AI age

AI governance is a set of rules and processes that ensure businesses do the right thing with artificial intelligence, including how they develop, manage, and distribute content. Trust is a key outcome because no one will do business with an organization if they doubt what it says or how it operates.

That means the core pillars of trustworthy AI-assisted content include:

• Integrity: At a basic level people expect the content you publish to be factual, ethical, and checked against bias. This has been a standard in media for a long time but it behooves enterprises to do the same, particularly given some may approach your content with a degree of skepticism.
• Transparency: It’s not always easy for people to tell how AI was used in your content. As appropriate, you should disclose whether you have LLMs pulling from publicly available data, whether you’re taking their data to train an AI model, or whether you’re interacting with them solely through an automated AI agent or chatbot.
• Accountability: Manufacturers often include warranties to convey the fact they stand behind their product. You need to do the same thing with AI-assisted content, demonstrating you’re embedding human oversight and escalations where necessary within workflows.
• Consistency: AI tools can work faster than any human, but that should never result in trade-offs in brand safety or regulatory compliance. Checks need to be built into core processes to avoid unfortunate accidents.

Building governance frameworks for AI-assisted content

AI can introduce a lot of change into content operations. Here’s what shouldn’t change: having clear ownership of who’s responsible for the assets you publish. Even if AI contributes to your thought leadership posts on LinkedIn, for instance, someone should be responsible for the end result.

Responsible, in this case, means you have defined approval workflows that integrate editors and other stakeholders who need to vet content before it goes live. It also means you’re documenting what AI tools are doing within a content workflow and providing the ability to trace it back should the questions or problems arise.

Most importantly, responsible AI content practices define human-in-the-loop workflows. This goes beyond saying employees will intervene when the occasion calls for it. You have to think through specific scenarios where that oversight is non-negotiable.

Humans need to be in the loop when you’re making a contentious (and potentially libellous) claim in a blog post about a competitor, for example, providing medical or legal advice to your target audience, or commenting on regulations that are changing the industry you serve.

Building editorial trust in AI-assisted workflows could begin with a simple process like this:

↓

↓

Those three basic layers could be developed further if you need to bring additional business functions like legal, HR, product, or sales into the “human validation” stage.

“AI generation” might have to be broken down further to reflect the specific tasks AI is handling (like making public records requests in USA Today’s case vs. generating copy). It could also mean making sure you have provenance indicators of where the data informing your content came from and its recency.  

“Sign off” may also eventually get broken down into specific compliance checks, depending on the nature of the content and the level of authority required for final approval. 

Trust-building metrics

Trust not only needs to be built into these workflows, but quantified. Measuring what happens will improve everyone’s overall confidence in what gets published.

Here are some effective enterprise content trust metrics you can weave into your framework:

• The percentage of AI‑assisted content that passes through editorial compliance checks. Some content will be more important to check than others, and it’s important to know which to achieve maximum efficiency, particularly when content velocity is consideration.
• Brand perception scores regarding content authenticity. If your responsible AI content practices are working well, it should show up in how people perceive what you publish.
• Reviewer approval rates, revision ratios, or factual correction rates. This indicates where your content operations may need to be fine-tuned, whether in how AI is used or in the kind of training you provide team members.

Measurement doesn’t mean manual. Tools like Parse.ly can provide a dashboard to monitor governance and flag any drift or trust gaps.

Change management: Embedding trust in culture

Trust isn’t an output of technology — it comes from the people who guide policies and processes. Establishing AI governance for editorial teams requires aligning your culture and encouraging teams to treat responsible use as an enabler of success rather than a blocker or bottleneck.

Cultural changes are reinforced through learning. As you create your framework and set up policies, take the time to train and upskill editors, subject matter experts, and other stakeholders who will be involved or need to be informed.  

This is an opportunity to promote cross-functional collaboration and teamwork by establishing responsible or ethical AI use councils or AI government boards to keep on top of best practices as they’re developed.

You can lean on trusted technology partners to assist with governance, too. For example, AI guidelines for WordPress are now a part of the Make WordPress Core AI Handbook. They don’t ban AI tools, but they set clear expectations on quality, licensing, and transparency. They might help inspire similar guidelines for content operations in your organization.

An enterprise approach to trusted AI workflows

AI offers powerful capabilities, which calls for careful handling. Start by assessing your content operations for any additional risks to determine where to focus your governance efforts.

From there, you can define roles and approval thresholds, but keep in mind you’ll likely want to revisit these as the technology matures and your use of AI expands.

Once you’ve chosen the most appropriate enterprise content metrics, gather enough data to step back and evaluate whether your reviews, approvals, and other checks go far enough or need to be enhanced.

Finally, let building editorial trust in AI-assisted workflows become a regular practice rather than a box you check off. Your organization and your audience deserve nothing less.

---

Related content

Why AI Governance in Journalism Starts with the Right Culture and Mindset

Read the article

Author

Shane Schick

Founder, 360 Magazine

Shane Schick is a longtime technology journalist serving business leaders ranging from CIOs and CMOs to CEOs. His work has appeared in Yahoo Finance, the Globe & Mail and many other publications. Shane is currently the founder of a customer experience design publication called 360 Magazine. He lives in Toronto.