Use semantic, accessible HTML: real buttons, labelled forms and a logical heading order

Google's guide for generative AI features says browser agents may read a site through screenshots, the DOM and the accessibility tree, and recommends semantic HTML; attendees were also told to check ARIA and accessibility, and a community speaker added that an unlabelled div tells an agent nothing about its purpose and that no ARIA is better than bad ARIA. Google has not called accessibility a ranking signal, and its SEO Starter Guide says headings out of order help screen readers less but do not matter to Google Search.

Buttons are button elements and links are a elements with href; form fields have labels; headings follow a logical h1 to h3 order; images have alt text; ARIA roles are used only where no native element exists, and only when they are correct (a div acting as a toggle gets role=button, an aria-label and aria-pressed). Avoid layout shifts that move buttons after load. Do not block agents you want to allow (DEV-AIF-04).

Regensbot proposes a verdict with the evidence; a person on your team confirms it.

The evidence comes from your verified site: its pages, its profile and the files you upload.

You verify the site by a DNS TXT record, a meta tag or a file. Regensbot then keeps a checklist item for this requirement, with a state, a guide, an evidence upload and reminders.

How verdicts workWhat you connect