Web Development Company in Columbus

Scope and governance set the range. A focused marketing site rebuild on a headless CMS with a design system, ten to twenty templates, a content migration, and a measured performance and accessibility target typically runs USD 45,000 to 120,000 over eight to fourteen weeks. A mid-size enterprise or institutional site with multiple content owners, workflow and approvals, localization, search, and integration into CRM and marketing automation typically runs USD 120,000 to 320,000. Commerce is its own curve: a Shopify or Hydrogen storefront with custom merchandising, search, and order-management integration typically runs USD 100,000 to 350,000, and a composable commerce build on commercetools with complex pricing and fulfilment rules goes higher. Accessibility remediation of an existing large site is usually priced per template family after an audit, since remediating fifteen templates that cover eight hundred pages is very different work from remediating eight hundred bespoke pages. Columbus rates typically sit roughly 30 to 45 percent below San Francisco and New York and slightly above smaller Midwest metros. Codazz quotes fixed fee in USD against a signed statement of work, and we scope the audit separately so you are not buying a remediation before anyone knows how big it is.

The US Department of Justice published its final rule on web and mobile app accessibility under Title II of the Americans with Disabilities Act on April 24, 2024. It sets WCAG version 2.1 Level AA as the technical standard for web content and mobile applications of state and local government entities. An interim final rule published April 20, 2026 extended the compliance dates: public entities with populations of 50,000 or more have until April 26, 2027, and entities with populations under 50,000 along with special district governments have until April 26, 2028. In central Ohio that reaches the City of Columbus, Franklin County, the Central Ohio Transit Authority, public school districts including Columbus City Schools, public higher education including the Ohio State University and Columbus State Community College, and the many smaller municipalities and special districts across the region. The rule includes limited exceptions for archived content, certain preexisting documents, third-party posts, and password-protected individualized documents, but the general ADA duty of effective communication still applies to those. Note that this rule covers Title II entities. Private businesses under Title III remain subject to litigation risk under the general ADA obligation without a codified technical standard, which is why we build every commercial site to the same WCAG 2.1 Level AA bar anyway.

Automated tooling finds somewhere around a quarter to a third of real issues, and accessibility overlays do not create conformance. They frequently make screen reader experiences worse and have been named in litigation. We do the work in four layers instead. First, semantics: correct heading order, landmark regions, native form controls with real labels, tables with header associations, and lists that are lists, which removes most issues before any remediation is needed. Second, interaction: full keyboard operability with a visible focus indicator, logical tab order, no keyboard traps, focus management on modals and route changes, and skip links. Third, presentation: contrast ratios of at least 4.5 to 1 for body text and 3 to 1 for large text and interface components, text that reflows at 400 percent zoom, no information conveyed by colour alone, and respect for reduced-motion preferences. Fourth, verification: axe and Lighthouse in CI to catch regressions on every pull request, plus manual testing with NVDA on Windows and VoiceOver on macOS and iOS, plus keyboard-only runs of every critical flow. We deliver an accessibility conformance report with actual findings, including what remains open and why.

We treat performance as a budget enforced in CI, not a cleanup phase. The targets are Largest Contentful Paint at or below 2.5 seconds, Interaction to Next Paint at or below 200 milliseconds, and Cumulative Layout Shift at or below 0.1, measured at the seventy-fifth percentile of field data rather than on a laptop over office wifi. On retail templates the biggest wins are consistent. Serve the hero image as a properly sized AVIF or WebP with fetchpriority set high and dimensions declared, so it is neither lazy-loaded nor shifting layout. Move product listing and detail pages to server rendering with edge caching so the first byte does not wait on an origin in another region. Cut and defer third-party scripts, which on most commerce sites are the single largest cause of poor Interaction to Next Paint, and load tag managers with a strict allowlist rather than letting marketing add tags without a performance review. Reserve space for every advertisement, banner, and dynamically injected element. Self-host fonts with size-adjust to remove layout shift on swap. Then hold the line with Lighthouse CI budgets and real-user monitoring so a regression is caught in the pull request that caused it.

Choose for the authoring team and the governance model, not the demo. If your marketing team is small and wants speed, a headless CMS such as Sanity, Contentful, or Storyblok paired with Next.js gives structured content, real preview, and scheduled publishing without maintaining a server. If you have dozens of authors across business units with approval workflows, brand governance, and localization, and you already own Sitecore, Optimizely, or Adobe Experience Manager, the honest answer is usually to keep the licence and modernize the delivery layer instead, rendering a decoupled front end from the existing content repository so you get performance and developer experience without a two-year migration and a retraining program. If the site is mostly documents and policy content, as it is for many public entities, the priority shifts to accessible document workflows and a rigorous URL and redirect strategy, since links to a policy PDF last a decade. Where we push back hardest is on page builders that let anyone assemble arbitrary layouts. They feel liberating for a quarter and then produce a site nobody can make accessible or fast. A constrained component library with genuinely flexible content is the better trade.

Ohio has not enacted a comprehensive consumer privacy law. The Ohio Personal Privacy Act has been introduced twice without passing, most recently as House Bill 345 in the 135th General Assembly. So there is no Ohio statute telling you how to configure your cookie banner. Your obligations come from elsewhere: the privacy laws of the states your visitors live in, which is every state once your site is public, plus sector rules. Practically, we implement a consent manager that actually gates tag execution rather than displaying a notice while scripts load anyway, honour Global Privacy Control at the browser level, keep a clear record of consent state, and keep the privacy notice aligned with what the tags actually do, because the mismatch between the two is what regulators and plaintiffs look at first. Session replay and heatmap tools get special scrutiny on any authenticated, healthcare, or financial page, with masking configured before launch rather than after an incident. Ohio does impose a breach duty: Ohio Revised Code 1349.19 requires notice in the most expedient time possible and no later than forty-five days after discovery. We wire that timeline into the incident runbook we hand over.