Generative engine optimization: how to get cited by AI search
What generative engine optimization really is, what the research shows, and a step-by-step plan to get your pages cited by AI search.
Your key page templates checked against WCAG 2.2 AA, with the fixes made on your site, not just listed.
Many websites block some visitors without anyone noticing: a form that cannot be used by keyboard, text that is too faint, a menu a screen reader cannot follow. We review up to 10 of your page templates against WCAG 2.2 AA, by scan and by hand. Then we fix the issues in the site itself, with no overlay widgets, re-test every fix and draft an accessibility statement.

Accessibility Audit and Fixes reviews up to 10 page templates against WCAG 2.2 AA, by automated scan and by hand. You get an issue log with severity, fixes made in the site itself, a re-test of every fix and a drafted statement. No overlay widgets are used. It suits sites preparing for the European Accessibility Act.
Most accessibility audits end with a long report and no one to act on it. Issues sit in a spreadsheet while visitors still struggle with the site. This package goes further: we fix what we find on the templates we review and then re-test each fix the same way. Because templates drive many pages, one fix often helps a whole section of the site. You finish with a clear issue log, a drafted statement and a site that more people can use. It is aligned to WCAG 2.2 AA and does not certify legal compliance.
We review up to 10 page templates against WCAG 2.2 AA with manual keyboard and screen reader checks. Issues are logged with severity, then fixed on the reviewed templates.
An issue log lists each problem with its severity and the pages it affects. You can see what was found, what was fixed and what sits outside the reviewed templates.
Contrast and form checks are part of the manual review, alongside an automated scan. Fixes are applied to the reviewed templates, and every fixed issue is re-tested before handover.
We draft an accessibility statement from the audit for you to review and publish. It describes the standard the work is aligned to; it does not certify legal compliance.
Your portal lists these the moment you order. Delivery starts the working day after everything is in and your access is checked.
| Option | Delivery time | Price |
|---|---|---|
| Standard | 20–30 working days | $3,875 |
Before you start: Run a free automated accessibility scan on your main templates and save the results. Note any accessibility complaints or requests you have received.
These are things to track, not promised results. Outcomes depend on your data, your team and your market.
There are no running costs. The audit and fixes are paid once, and no tools need to be bought to keep the fixes in place. Any accessibility tools you choose to use later are your own decision.
Ask about running costsMore than 10 templates, PDF and document remediation, video captions or a mobile app? Add a note at checkout for a written Change Quote. Very large projects use the Custom AI enquiry form instead.
Request a custom versionThere is nothing to keep running, and the issue log, statement and fixes are yours. Follow-up questions are answered during the support period. New pages and content can bring issues back, so use the log as a checklist, and order a fresh review when you add templates.
| Do it yourself | Hire a traditional agency | Upmark Labs | |
|---|---|---|---|
| Price | An overlay or scanner subscription, billed monthly | Quoted after a discovery call, often for the audit alone | Ours is one fixed price for the audit and fixes, shown before you buy |
| Checks | An automated scan, which misses many issues | Manual checks to the agency's method | Ours combines a scan with keyboard, screen reader, contrast and form checks |
| Fixes | Left for you to work out | Often a separate project after the report | Ours applies fixes to the reviewed templates and re-tests them |
| Statement | You write one yourself | Sometimes included | Ours drafts an accessibility statement for you to review and publish |
No. The work is aligned to WCAG 2.2 AA, which covers the level that the European Accessibility Act points to. It does not certify legal compliance, and laws differ by country. You get a clear record of what was checked, fixed and left. That helps if you later speak to a legal adviser.
A page template is a layout shared by many pages, such as a product page, a blog post or a contact page. Fixing the template fixes every page built from it, which is why we review up to 10 templates rather than single pages. At intake you list your key page types and journeys, and we agree which templates to cover.
Both. An automated scan quickly catches issues such as missing labels and low contrast, but it misses many problems. So we also check by hand with a keyboard and a screen reader, test forms, and review focus order, headings and link text. Every fixed issue is re-tested the same way before we hand over.
They stay in the issue log with their severity, the affected pages and a recommended fix. Some issues sit in third-party widgets we cannot edit, such as chat tools or embedded forms. For those, the log explains what to raise with the supplier. PDFs, documents and video captions are outside this scope and can be quoted through a Change Quote.
The draft describes the standard you aimed for, what was checked, known issues that remain and how visitors can report a problem or ask for help. You review it and publish it under your name. It is a starting point, so we suggest a legal adviser reads it if your business has specific obligations.
The delivery time is shown in the price panel before you order. It starts once your website access and list of key page types and journeys arrive, which should be within 72 hours. Every day of delay beyond that moves delivery by 3 working days. Fixes go live only after the person you name approves them.
You get 14 days of follow-up questions after delivery, plus the issue log and a written walkthrough of the fixes to keep. Accessibility can slip as new pages and content are added, so the log doubles as a checklist for your editors. If you later redesign or add templates, a fresh review can be ordered for them.
No. Overlay widgets add a toolbar on top of the page but leave the code underneath unchanged. Many disabled visitors find them unhelpful. We fix the templates themselves, so the improvements work with the screen readers and keyboards people already use. If your site has an overlay installed now, the issue log notes whether to remove it.
Order the Accessibility Audit and Fixes and get your key templates reviewed against WCAG 2.2 AA, fixed on your site and re-tested, with a statement drafted for you.

A clickable Figma prototype of up to 8 screens for your website, app or portal, refined over 2 revision rounds and handed…