WBI Consulting Group Work With Us

Chapter 05

How We Build Websites

Accessible from the first block, tested before launch, and editable by the people who own it.

The studio builds institutional websites on WordPress with its own automated builder. This chapter sets out the approach in the order a request for proposals usually asks: accessibility, process, performance, search, content management, and what happens after launch.

Most websites become inaccessible the same way they become slow: one reasonable exception at a time. Our answer is to make the rules part of the machinery. The builder that generates a page is the same one that refuses a heading out of order, an image without a description, or a button too small to tap. What a rule cannot decide, a person reviews.On claimsNobody can certify a website accessible for good. Conformance belongs to a page on a given day, and one uploaded image without a description changes it. We describe what we build and what we test. We do not sell a badge.

WCAG 2.2 AA is the brief, not a retrofit.

Every site we build targets the Web Content Accessibility Guidelines 2.2 at Level AA. We enforce it in two layers. The first is prevention: the templates and rules that generate each page produce accessible markup by default. The second is verification: rendered pages are scanned, reviewed and tested before launch.

Built in from the first block

  • One H1 per page, headings in order, and labeled landmark regions (1.3.1)
  • A text alternative on every image; decorative icons hidden from assistive technology (1.1.1)
  • Text contrast of at least 4.5:1, and 3:1 for large text and interface components (1.4.3, 1.4.11)
  • Every interactive element reachable and operable by keyboard, menus and tabs included (2.1.1)
  • A skip link on every page (2.4.1)
  • A visible focus indicator at least 2px thick with 3:1 contrast (2.4.7, 2.4.11)
  • Tap and click targets of at least 24 by 24 CSS pixels (2.5.8)
  • Never color alone to carry meaning (1.4.1)
  • Motion that switches off when a visitor’s device asks for reduced motion
  • Body text never smaller than 16 pixels

Before launch, pages are scanned with axe-core against the WCAG 2.0 A, 2.0 AA and 2.2 AA rule sets, in a browser, against the page as it actually renders. Critical and serious findings are fixed before the site goes live. Then people take over: rendered pages are reviewed at desktop and mobile widths, and tested with screen readers, VoiceOver and NVDA.

Automated scanners find only part of what the guidelines cover. A scanner cannot tell whether an image description is accurate, or whether a link’s text makes sense out of context, so those checks are done by reading and listening to the page.

After launch, accessibility depends on the people adding content. The editor is set up so that the accessible choice is the default one: colors, type sizes and components come from the shared design system instead of per-page styling. That leaves editors responsible for a short list (image descriptions, heading order, link text), and the handover covers each of them. On request we provide an accessibility statement for the site and a VPAT, also called an Accessibility Conformance Report, for procurement.

Five stages, each with something to look at.

  1. Discovery

    A conversation about the institution, its audiences and its existing content. We agree which pages carry over, merge or retire.

    You receive Scoped proposal and page list

  2. Design preview

    Layout, type and real copy are worked out as plain HTML previews first, where a change takes minutes. Each client gets its own design direction.

    You receive Preview pages to approve

  3. Build

    The builder generates the pages in WordPress’s own block editor on a private staging site. People, programs and news become structured entries, written once.

    You receive Staging site

  4. Review

    You pin comments to the exact block they concern. We run the accessibility scan, the screen-reader pass, the editor validation and the desktop and mobile review.

    You receive Resolved comments

  5. Launch

    Old addresses are redirected to their new pages, search indexing is switched on, and the live site is checked against staging.

    You receive Live site and handover

Fast because there is less of it.

The sites are built on GeneratePress and GenerateBlocks, a lightweight theme and block library, with no page-builder layer on top. Styling lives in one shared set of Global Styles instead of being repeated on every block, so a design change is made once and pages carry less CSS.

Images declare their dimensions and load lazily. Fonts are loaded so that text is readable while they arrive. A video hero paints a still frame first and loads the video only when it is needed. Motion is used sparingly, never on every element.

We do not quote speed scores here. They depend on the hosting, the content and the third-party scripts a site carries, and a number from someone else’s site tells you little about yours.

Search engines and screen readers read the same structure.

Much of search optimization is the same work as accessibility: one clear H1, headings in order, descriptive link text, described images. On top of that, each site ships with an SEO plugin (Yoast SEO or Rank Math) set up for page titles and meta descriptions, readable page addresses, and, on a rebuild, redirects from the old addresses so that existing links keep working. The staging site stays hidden from search engines until launch day.

We do not promise rankings. Nobody honestly can.

Your staff edit the site. That is the point.

Everything is built with WordPress’s own block editor. There is no proprietary page builder and nothing that only we can change. Menus are ordinary WordPress menus, edited under Appearance. And every site is handed over with a style map: a plain document that answers, for each thing you can see on a page, where it is edited.

Three decisions keep a site manageable after we leave.

  • Design in one place. Colors, type and components are shared styles. Change one and every page that uses it follows.
  • Write it once. A section that repeats across pages, such as a call to action, is a single synced pattern. Edit it once.
  • Content as content. People, programs and news are entries with fields, and the pages that list them update on their own. Adding a faculty member means filling in a form, not rebuilding a page.

Hosting, security, and someone to ask.

A managed WordPress engagement includes a year of managed hosting and security updates. Every site launches with a security baseline: login attempts are limited, remote-access endpoints nothing uses are closed, and usernames are not exposed to the public. Managed sites are backed up automatically every day, with backups kept for 30 days, and again before every update.

Training is practical. Your editors get a live walkthrough of the finished site, training videos, and written documentation that includes the style map. Change requests can be pinned to the exact block they concern, on the live site, so nobody has to describe where something is.

After the first year, support continues as hourly blocks or a monthly retainer: security patching, upgrades, small feature work, and incident response in business hours. Terms are in Chapter 04.

Three sites built this way.

Recent sites built on this foundation include Sunshine Bible Academy, Mayer Consulting and Window Seat Selections: a school, an investigative firm and a wine importer, each with its own design.

What we commit to

  • WCAG 2.2 AA as the build target on every page we generate
  • An axe-core scan of rendered pages, with critical and serious findings fixed before launch
  • Screen-reader testing with VoiceOver and NVDA, and a human review at desktop and mobile widths
  • An accessibility statement and a VPAT/ACR on request
  • Standard WordPress that your staff can edit and another developer can take over
  • A written style map at handover

What we won’t claim

  • A certificate, or a permanent “compliant” badge
  • That an automated scan proves conformance
  • Guaranteed rankings or speed scores
  • That third-party embeds (forms, maps, video players) meet the standard without checking them
Ch. 04 · Working Together →

Start a conversation.

Write to us with a paragraph on what you need, and who referred you, if anyone did. We reply within two business days with a scoped proposal or a polite decline. Prose both ways.

hello@wbicg.com → Work With Us