imbahub
Menu +
EN
Talk to us
IMBAHUB / Knowledge & guides

Buying accessible web design: specify tasks and review evidence

Ask how people will use the website and how the result will be checked. An accessibility promise needs a scope, practical review and a plan for maintaining the work.

Compare the decision, not just the headline
  1. Requirements

    Named tasks and review scope. Agree the expected evidence.

  2. Verification

    Automated and manual checks. Record limitations.

  3. Maintenance

    Editor and component guidance. Assign future review ownership.

Ask how people will use the website and how the result will be checked. An accessibility promise needs a scope, practical review and a plan for maintaining the work.

Try this before deciding

Include a witnessed keyboard journey and a form error-and-correction task in the acceptance process. Combine those checks with appropriate automated review and any specialist assessment needed for your scope.

Describe the important user tasks

Include finding a service, reading conditions, using navigation and completing a form. Consider keyboard operation, readable presentation and understandable feedback alongside the visual design. State any standard or specialist review the project requires. This is a procurement workflow, not a legal determination of which rules apply to your organisation; resolve that question with appropriate expertise when needed.

Distinguish automated checks from a complete review

Automated tools can identify some problems but do not establish that every task is usable. Request manual evidence for representative journeys and record remaining limitations. Content editors also need guidance for later headings, links, images and documents. A technically reviewed launch can still degrade if future material ignores the same principles. Agree who reviews new components and important content changes.

A practical check before you buy

Include a witnessed keyboard journey and a form error-and-correction task in the acceptance process. Combine those checks with appropriate automated review and any specialist assessment needed for your scope.

DecisionWhat to considerWhat to check
RequirementsNamed tasks and review scopeAgree the expected evidence
VerificationAutomated and manual checksRecord limitations
MaintenanceEditor and component guidanceAssign future review ownership

An illustrative business scenario

A UK membership organisation can include its document and registration journeys in the review scope rather than checking only public marketing pages.

This is an illustrative scenario, not a claim about an ImbaHub client or a promised result.

Discuss the right scope with ImbaHub

ImbaHub builds fast static websites with Astro, with editing through Imba CMS and Imba Builder. Start with the customer task described in this guide and ask which content, integrations and ongoing responsibilities your project needs. Agree the scope before comparing the investment.

Questions, answered

Does a clean automated accessibility scan certify the whole website?

No. Automated checks cover only part of the work. Use manual task review and any specialist assessment appropriate to the project, with limitations recorded.

IMBAHUB

What would you like to make possible?

Ask how people will use the website and how the result will be checked. An accessibility promise needs a scope, practical review and a plan for maintaining the work.

Talk to us
Product interface set to English in an isolated environment with fictional English demo content.

Product interface set to English in an isolated environment with fictional English demo content.