AI Readiness Assessment
Registered identity from official sources
Listing
FCA Official List (Equity shares (commercial companies), LSE) · London Stock Exchange, SETS list (trading identifiers as at 10 February 2020) · GLEIF (legal identity, matched on ISIN) · retrieved 2026-07-31 16:39 UTC
64 judgements need a named person in the organisation to confirm, because they turn on what you know to be true rather than anything measurement can settle: whether a claim is supported, whether a page is still current, which of two versions is the one to quote. In order, they cover: who is answerable for this content; is it still true today; can each claim be backed; does our published content agree; will the right meaning come across; can someone reach it and act on it. An answer recorded against each, with a name and a date, is what turns published content into governed content.
Once the foundations are sound and the content is governed, the visibility stage measures how AI systems and agents actually find the estate: which pages they reach, how often, and how the organisation is represented when they answer questions about it, tracked over time. Building visibility on unconfirmed foundations only amplifies whatever is wrong, which is why it comes last.
How much of your content is reachable and readable, rather than blocked, buried or missing. Higher is better.
Where your content could lead an AI system to state something incorrect. Only direct routes to a wrong answer count here.
Anyone asking for this site, a person on a phone or an AI system building an answer, is either let in or turned away, in milliseconds, by machinery most organisations never see. An AI system refused here gets nothing at all: to that system the organisation simply does not answer.
The door changes without notice: a security setting, a network change or a new crawler policy can close it silently. It is measured live on the day of assessment, and it is worth watching continuously rather than once.
People are served in full; 14 of the 15 AI systems are turned away at the door.
Whether the estate can be reached and read at all: access rules, links, redirects, sitemap, transport.
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| DS04 | fail | 1 of 120 crawled URLs returned an error status (not found, or a server error) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Addresses that answered with an error, not found or gone or a server failure, during the visit. What good looks like The addresses visited answer successfully, without error, not-found or server-failure statuses. Why it matters Each errored address is content the visit proved unavailable, so it is missing from anything built on what came back. What we found on this page 1 of 120 crawled URLs returned an error status (not found, or a server error) The evidence, taken from the page as served Each crawled URL that returned an error status
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the addresses visited answer successfully, without error, not-found or server-failure statuses. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 5 out of a possible 5, because it is one of the checks that decide whether content can be reached and read at all, so it carries the heaviest weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| DS03 | fail | 14 of 15 AI crawlers asking for the site are refused by the security layer in front of it, while an ordinary browser is served, so the content is closed to nearly all AI systems before page quality even matters. AI readiness is capped accordingly. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The same page loads for a browser but is refused when the request names itself as an AI service. What good looks like The page returns the same response to a named AI service as to a browser, with no edge block. Why it matters The block sits in front of the site and leaves no trace in its own logs, so the estate is closed off unnoticed. What we found on this page 14 of 15 AI crawlers asking for the site are refused by the security layer in front of it, while an ordinary browser is served, so the content is closed to nearly all AI systems before page quality even matters. AI readiness is capped accordingly. The evidence, taken from the page as served Each crawler's own request to the entry page, and the status it received
Hostwww.aviva.com · resolves to 23.215.224.114 · an Akamai edge hostname
Address trailwww.aviva.com › cert10.uk.aviva.com.ksd.edgekey.net › e5059.ksd.akamaiedge.net
Checked2026-07-31 16:33 UTC · request sent from 10.100.100.212 (our checker)
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page returns the same response to a named AI service as to a browser, with no edge block. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 5 out of a possible 5, because it is one of the checks that decide whether content can be reached and read at all, so it carries the heaviest weight in the figure for this item. It also sets a ceiling on that figure: while this stands, the item cannot read as more ready than 25%, however well it is built elsewhere. Why it moves the misinformation reading This failure is a real and common route to a wrong answer for the content it affects, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| DS16 | fail | 1 URL group(s) are reachable under more than one form (case, trailing slash, or query variants) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The same page served at several addresses, varying by capitals, slashes or query strings. What good looks like Each page is served at a single address, not several varying by capitals, slashes or query strings. Why it matters The site cedes the choice of which address is stored and cited, so links and credit scatter across the variants. What we found on this page 1 URL group(s) are reachable under more than one form (case, trailing slash, or query variants) The evidence, taken from the page as served The URLs that serve the same page under more than one form
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: each page is served at a single address, not several varying by capitals, slashes or query strings. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MX12 | fail | 1 pair(s) of pages carry near-identical text (at least 90% of the same words) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Distinct URLs among the assessed pages that carry near-identical body text. What good looks like No two assessed pages carry near-identical body text. Why it matters Duplicates collapse to a single surviving version, and which one survives is not the publisher's choice. What we found on this page 1 pair(s) of pages carry near-identical text (at least 90% of the same words) The evidence, taken from the page as served Each page pair whose visible text is near-identical (at least 90% shared vocabulary)
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: no two assessed pages carry near-identical body text. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 1 out of a possible 5, because it is one of the supporting checks, so it carries the lightest weight in the figure for this item. Why it moves the misinformation reading This failure is a real and common route to a wrong answer for the content it affects, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT34 | fail | 11 page(s) read as near-identical to other pages in the text a machine ingests (up to 96% shared), but the overlap is shared navigation and footer rather than content: the worst affected page has 15 words of its own out of 351. Distinct pages can then be taken as duplicates and the real content passed over; the pages are listed in the view. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether a page's own words are so few against a large shared navigation and footer that it reads as near-identical to other pages. What good looks like A page carries enough of its own words that a shared navigation and footer do not make it read as a copy of other pages. Why it matters When shared furniture is most of the text, distinct pages look like copies of each other and the little real content is easily passed over. What we found on this page 11 page(s) read as near-identical to other pages in the text a machine ingests (up to 96% shared), but the overlap is shared navigation and footer rather than content: the worst affected page has 15 words of its own out of 351. Distinct pages can then be taken as duplicates and the real content passed over; the pages are listed in the view. The evidence, taken from the page as served Pages whose own words are lost in a shared navigation and footer (near-identical to a machine)
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: a page carries enough of its own words that a shared navigation and footer do not make it read as a copy of other pages. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 1 out of a possible 5, because it is one of the supporting checks, so it carries the lightest weight in the figure for this item. Why it moves the misinformation reading This failure is a real and common route to a wrong answer for the content it affects, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR27 | fail | the front door answers Google inconsistently: Google's GoogleOther crawler is served the page (HTTP 200) while a request named Googlebot is refused (HTTP 403), and 10 of 10 AI answer services' own crawlers are refused. Search results are fed the site's current content; the AI answer services are not, so a person asking Google Search and a person asking an AI assistant receive different information, and the two answers can conflict. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the front door answers Google consistently: the crawling that feeds search results on one side, and the paths that feed AI answers on the other. What good looks like Search crawling and the AI answer services are given the same access, so both speak from the site's current content. Why it matters Google search shows the site's current content while the AI services are turned away and answer from older or outside sources, so the same question brings back different information depending on which door the public uses, and the two answers can conflict. What we found on this page the front door answers Google inconsistently: Google's GoogleOther crawler is served the page (HTTP 200) while a request named Googlebot is refused (HTTP 403), and 10 of 10 AI answer services' own crawlers are refused. Search results are fed the site's current content; the AI answer services are not, so a person asking Google Search and a person asking an AI assistant receive different information, and the two answers can conflict. The evidence, taken from the page as served Google's own crawler family at the same door, in the same minute, answered differently
Googlebot and Bingbot verify themselves by network address, so the refusal of the name alone may be the door refusing impersonation. The divergence rests on what is beyond doubt: a Google crawler served beside 10 refused AI services, measured at the same door within the same minute (the full grid is in DS03).
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: search crawling and the AI answer services are given the same access, so both speak from the site's current content. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 5 out of a possible 5, because it is one of the checks that decide whether content can be reached and read at all, so it carries the heaviest weight in the figure for this item. Why it moves the misinformation reading This failure is a real and common route to a wrong answer for the content it affects, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| DS08 | fail | SEVERE: 42% of the links to the site's own pages did not open when they were checked. 28 were refused, meaning the page is still published but the other site turns away requests that do not come from a person using a browser. That is 28 of the 40 checked, which stand for the 252 links to the site's own pages across the pages checked | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The share of links to the site's own pages, from a sample, whose targets do not resolve. What good looks like The site's own links open, leading to live pages. Where one no longer does, the page either carries the point in its own words or stops presenting a route that does not open. Why it matters Routes into the site's own material dead-end, so content that exists is never reached from the pages pointing at it. What we found on this page SEVERE: 42% of the links to the site's own pages did not open when they were checked. 28 were refused, meaning the page is still published but the other site turns away requests that do not come from a person using a browser. That is 28 of the 40 checked, which stand for the 252 links to the site's own pages across the pages checked The evidence, taken from the page as served The internal links checked, with the status each returned
A link that did not open appears here in two forms. A DEAD link points at a page that has gone. A REFUSED link points at a page that is still published, but the other site turns away requests that do not come from a person using a browser, so our request was declined. Both land in the same place: the material this page offers as its support did not come back when it was asked for. The consequence is not a matter of tidiness. Where a link carries the weight of a claim, a figure, a policy or a regulatory statement, and the target does not open, the support behind that claim is missing at the moment it is needed. Three things follow, and each of them costs the organisation. The same fact gets taken from somewhere else, which hands a third party control of how the claim is worded. Or the claim is treated as unsupported and set aside. Or an answer is drawn from what remains on the page, and a partial account is presented as a complete one. A refused link is the worst of the three, because the page still reads as though the evidence sits one step away, so the gap is invisible and the answer carries false confidence. A refusal by another site is still this site's matter to resolve, because this site chose to rest a claim on it. Three practical ways close it. Carry the fact being relied on in the page's own words, so the claim stands without the visit. Keep the reference but stop making it a link, showing the address as plain text, so nothing promises a route that does not open. Or point to a source that answers any reader. Where the reference has to stay live, say beside it what a reader will meet, so no one is sent to a closed door without warning. Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the site's own links open, leading to live pages. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 5 out of a possible 5, because it is one of the checks that decide whether content can be reached and read at all, so it carries the heaviest weight in the figure for this item. It also sets a ceiling on that figure: while this stands, the item cannot read as more ready than 60%, however well it is built elsewhere. Why it moves the misinformation reading This failure is a real and common route to a wrong answer for the content it affects, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| DS12 | fail | one link to sources on other sites was refused when it was checked. The page is still published, but the other site turns away requests that do not come from a person using a browser. It is listed in the view | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The share of links pointing off the site, from a sample, whose targets no longer resolve. What good looks like Sources the page relies on open for any reader. Where one refuses or has gone, the page carries the fact in its own words, shows the reference without making it a link, or points somewhere that answers. A refusal by another site is still this site's to resolve, because this site chose to rest a claim on it. Why it matters A source the page leans on did not answer when it was asked for. The claim is left standing with nothing behind it, so the same fact gets taken from elsewhere, the claim is set aside as unsupported, or a partial account is presented as a complete one. Where the source is still published but declined the request, the page still reads as though the evidence sits one step away, so the gap is invisible. What we found on this page one link to sources on other sites was refused when it was checked. The page is still published, but the other site turns away requests that do not come from a person using a browser. It is listed in the view The evidence, taken from the page as served The external links checked, with the status each returned
A link that did not open appears here in two forms. A DEAD link points at a page that has gone. A REFUSED link points at a page that is still published, but the other site turns away requests that do not come from a person using a browser, so our request was declined. Both land in the same place: the material this page offers as its support did not come back when it was asked for. The consequence is not a matter of tidiness. Where a link carries the weight of a claim, a figure, a policy or a regulatory statement, and the target does not open, the support behind that claim is missing at the moment it is needed. Three things follow, and each of them costs the organisation. The same fact gets taken from somewhere else, which hands a third party control of how the claim is worded. Or the claim is treated as unsupported and set aside. Or an answer is drawn from what remains on the page, and a partial account is presented as a complete one. A refused link is the worst of the three, because the page still reads as though the evidence sits one step away, so the gap is invisible and the answer carries false confidence. A refusal by another site is still this site's matter to resolve, because this site chose to rest a claim on it. Three practical ways close it. Carry the fact being relied on in the page's own words, so the claim stands without the visit. Keep the reference but stop making it a link, showing the address as plain text, so nothing promises a route that does not open. Or point to a source that answers any reader. Where the reference has to stay live, say beside it what a reader will meet, so no one is sent to a closed door without warning. Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: sources the page relies on open for any reader. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 5 out of a possible 5, because it is one of the checks that decide whether content can be reached and read at all, so it carries the heaviest weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT07 | warning | 1 page title(s) are used on more than one page: โAviva corporate website - Aviva plcโ; the pages are listed in the view | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Any title string that is shared by more than one of the assessed pages. What good looks like Each assessed page carries its own distinct title. Why it matters Pages sharing one title carry the same label, so nothing distinguishes them at the point one is picked. What we found on this page 1 page title(s) are used on more than one page: โAviva corporate website - Aviva plcโ; the pages are listed in the view The evidence, taken from the page as served The pages that share a title, grouped by the title they share
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT30 | warning | The word โgamblingโ appears on 16 pages (16 instances). Although these look like news articles, the density of use of the word โgamblingโ could misinform and then be misrepresented by AI engines. A possible fix is to use the secure tag to restrict AiSC access to certain news articles where the risk of misclassification is high. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check How often a charged or out-of-sector term recurs in the words a machine reads across the site. What good looks like Charged or out-of-sector terms appear only in proportion to the organisation's actual business, not densely across the estate. Why it matters A word that recurs across many pages can come to define the organisation by it, whatever the human context around each mention. What we found on this page The word โgamblingโ appears on 16 pages (16 instances). Although these look like news articles, the density of use of the word โgamblingโ could misinform and then be misrepresented by AI engines. A possible fix is to use the secure tag to restrict AiSC access to certain news articles where the risk of misclassification is high. The evidence, taken from the page as served Each page where โgamblingโ appears, with the surrounding text
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Passing checks are omitted here; the full record is in the exports.
The highest-priority pages, chosen from the site's own signals of importance.
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| DS03 | fail | an AI crawler asking for this page is refused by the security layer in front of the site, while an ordinary browser is served, so the page's content never reaches the AI and answers about it are left to memory or guesswork | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The same page loads for a browser but is refused when the request names itself as an AI service. What good looks like The page returns the same response to a named AI service as to a browser, with no edge block. Why it matters The block sits in front of the site and leaves no trace in its own logs, so the estate is closed off unnoticed. What we found on this page an AI crawler asking for this page is refused by the security layer in front of the site, while an ordinary browser is served, so the page's content never reaches the AI and answers about it are left to memory or guesswork The evidence, taken from the page as served The estate's edge tested with each AI crawler: a browser is served, the crawlers are refused
Hostwww.aviva.com · resolves to 23.215.224.114 · an Akamai edge hostname
Address trailwww.aviva.com › cert10.uk.aviva.com.ksd.edgekey.net › e5059.ksd.akamaiedge.net
Checked2026-07-31 16:33 UTC · request sent from 10.100.100.212 (our checker)
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page returns the same response to a named AI service as to a browser, with no edge block. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 5 out of a possible 5, because it is one of the checks that decide whether content can be reached and read at all, so it carries the heaviest weight in the figure for this item. Why it moves the misinformation reading This failure is a real and common route to a wrong answer for the content it affects, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR13 | warning | the page does not mark out its main content, so what is unique to this page cannot be told apart from the menus and foot-of-page text repeated across the site | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page's main content is marked off from the navigation and footer around it. What good looks like A main or article region marks the primary content off from the navigation and footer around it. Why it matters Pulling the page's text returns menus and legal footers mixed with the substance, so the answer arrives buried in noise. What we found on this page the page does not mark out its main content, so what is unique to this page cannot be told apart from the menus and foot-of-page text repeated across the site The evidence, taken from the page as served The blocks this page marks out, as served
The page was read for the block that marks out its main content. <meta itemprop="name" content="Aviva plc"/> <meta itemprop="url" content="https://www.aviva.com/"/> <div class="l-whole-page" data-back-to-top="Back to start of main content" data-component="back-to-top-es6"> <script> <span data-module="app/init-es6" data-module-load="true"/> <script id="js-init" src="https://static.aviva.io/assets/themes-managed/v6.1.0/shared/extensions/requirejs/init.js" asynโฆ <script src="https://static.aviva.io/etc.clientlibs/settings/wcm/designs/aviva-corporate/clientlibs/resources/2-20260728โฆ <script type="application/ld+json"> | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS10 | fail | the page's first heading is not its top-level heading, so the structure starts part way down | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check A page's headings start at the top level and step down without skipping a level. What good looks like The page's headings start at the top level and step down without skipping a level. Why it matters Content under a skipped level has no clear parent section, so structure taken from the page misplaces its text. What we found on this page the page's first heading is not its top-level heading, so the structure starts part way down The evidence, taken from the page as served The page's heading outline, in document order (a jump in level is marked)
H3 Recommendation to reject "mini-tender" offers by Litani LLC level jumped H1 Ready for Tomorrow starts with financial confidence H2 Aviva plc Q1 2026 Trading Update H2 Discover our investment case and strategy H2 Aviva plc 2025 results announcement H2 We are the UK's leading diversified insurer, with businesses spanning insurance, H2 Half year results 2026 H2 Watch our 2025 full year results video with Group CEO, Amanda Blanc DBE H3 Transcriptย for video Watch our 2025 full year results video with Group CEO, Ama H2 Featured stories from the UK, Canada and Ireland H2 The รยฃ300m Cambridge investment H2 The one who stands behind the promise H2 A city worth investing in H3 Share price * H3 Final dividend H3 Financial calendar H2 Quick links H2 Customer support H3 Aviva UK H3 Aviva Ireland H3 Aviva Canada H3 Aviva Investors H2 News from the UK, Canada and Ireland H2 Aviva has successfully completed its รยฃ350m share buyback programme H2 Aviva to rebrand Probitas 1492 as รขยยAviva Syndicatesรขยย H2 Aviva receives FCA approval to deliver targeted support H2 Aviva plc Q1 2026 Trading Update H2 Aviva Canada media centre H2 Aviva Investors company news H2 Aviva Ireland media centre H2 Reports and documents H3 Q1 2026 announcement H3 Full year results 2025 announcement H3 Annual Report and Accounts 2025 H3 Business Model 2025 H2 Login or register H2 Site navigation H3 About us H4 Our purpose and priorities H4 Our customers and people H4 Our Board and Executives H4 2025 Annual Report H4 Get support H3 Investors H4 Strategy and performance H4 Institutional investors H4 Shareholder services H4 Corporate governance H4 Risk governance and management H4 2025 Annual Report H4 Get support H3 Newsroom H4 News and research H4 Resources H4 About Aviva H4 Get support H3 Careers H4 Careers at Aviva H4 Life at Aviva H4 Diversity and inclusion H4 Get support H3 Sustainability H4 Sustainability at Aviva H4 Sustainability news H4 Sustainability resources H4 Aviva Foundation H4 Get support H4 Get support H2 Footer H3 Useful information H4 Products in our locations H4 Use MyAviva H4 How to make a complaint H3 On this site H3 Media H3 Corporate H3 Other links H3 Social H3 Legal H3 Copyright
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page's headings start at the top level and step down without skipping a level. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS14 | fail | 1 video(s) on the page with no captions on the video and no written transcript on the page: nothing spoken is available as text in any form | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether each video carries captions of its own, timed text on the video itself, judged together with whether the page holds a written transcript. What good looks like Captions carried on the video. A WARNING means the video has no captions but a written transcript on the page holds the words. A FAIL means neither exists, so nothing spoken is available as text in any form; that total absence is marked here once, not spread across two findings. Why it matters Spoken content that exists only as sound is invisible to a reader, human or machine: nothing said in the video can be found, read or quoted. What we found on this page 1 video(s) on the page with no captions on the video and no written transcript on the page: nothing spoken is available as text in any form The evidence, taken from the page as served Each video on the page, as served: its code, source file and caption track
No caption track on the video and no transcript link on the page. <video id="video6390041787112" data-embed="default" class="video-js" controls=""/> Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: captions carried on the video. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS16 | warning | 1 media resource(s) are named as a technical code, not human-meaningful words, so a machine cannot tell what the resource is from its name | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The name a video, audio clip or image is served under, and whether it is human-meaningful words or a technical code. What good looks like Video, audio and image files carry names made of words that say what they are, not a technical code. Why it matters A resource named as a code or a bare number says nothing about what it is, so a machine cataloguing it has only the code to go on. What we found on this page 1 media resource(s) are named as a technical code, not human-meaningful words, so a machine cannot tell what the resource is from its name The evidence, taken from the page as served The media resources whose name is a technical code, as served
A meaningful name (words that say what it is) lets a machine identify the resource; a code or a bare number cannot. <video id="video6390041787112" data-embed="default" class="video-js" controls=""/> | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR03 | warning | 14% of the words a person sees are missing from the page as first delivered (12095 characters delivered, 15012 once the page finishes building itself) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check How much of the page's content exists only once JavaScript has run. What good looks like The page's content is present in the served HTML, so it does not depend on JavaScript to appear. Why it matters The page is fetched successfully but the answer is missing from what comes back, so the content is absent rather than wrong. What we found on this page 14% of the words a person sees are missing from the page as first delivered (12095 characters delivered, 15012 once the page finishes building itself) The evidence, taken from the page as served Content present only after JavaScript runs (absent from the served HTML)
The served HTML carries 12095 characters of text; after JavaScript runs the page carries 15012. 14% of the rendered page's words are absent from the HTML the server sends. What the server sends (raw HTML text, first 280 chars) Aviva corporate website - Aviva plc Skip to content Recommendation to reject "mini-tender" offers by Litani LLC We want to make you aware that a company called Litani may write, or may already have written, to you offering to buy some or all of your Aviva shares. Our warning to s…
Words present only after JavaScript runs
activeadvertisementsadvertisingallowallowedalwaysapplyautomaticallybackbelowblockbrowserbuttoncannotcategorychoicesclearcollectconfirmconsentcorecrimecustomisedetectdevicedifferentenableenablesenhancedexampleexperiencefilesfilterfiltersfraudfunctionfunctionalfunctionalityhelphowevericonimpactimproveincludesinterestkeepleastmarketingmovenecessaryoptionalpersonalisationpersonalisedpopularpreferenceprovidereceiverecogniserefusingrelevant
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR11 | warning | 14% of the words a person sees are missing from the page as first delivered, which is 0.81 of its finished size | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The measured gap between the page as served and the page after the browser has built it. What good looks like The served page and the fully built page carry the same words, with little gap between them. Why it matters Two versions of the same page exist, and which words come back depends on which version was fetched. What we found on this page 14% of the words a person sees are missing from the page as first delivered, which is 0.81 of its finished size The evidence, taken from the page as served This page as first delivered, against the page once its scripts have run
Both were taken from the same request. The first is what the site sent; the second is what a person ends up looking at.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS04 | warning | the page's naming markup is faulty: 1 name label(s) point at nothing: the code that should hold the name is absent | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Accessibility markup faults: invented roles, labels pointing at nothing, live controls marked hidden. What good looks like The page's accessibility markup is sound, with valid roles and no labels pointing at nothing. Why it matters The page's own description of its controls is wrong, so what it offers and what it declares do not match. What we found on this page the page's naming markup is faulty: 1 name label(s) point at nothing: the code that should hold the name is absent The evidence, taken from the page as served The faulty markup, as the page serves it once loaded
<input type="checkbox" name="storage-access" id="ot-group-id-C0001-toggle" aria-expanded="false" ot-accordion="true" role="button" aria-controls="ot-desc-id-C0001" aria-labelledby="ot-header-id-C0001 ot-status-id-C0001"/> | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AJ08 | warning | focus order: the first 12 Tab stops do not follow document order | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether pressing Tab moves through the page in the order its content is written. What good looks like Pressing Tab moves through the page in the order its content is written. Why it matters The keyboard jumps around the page out of sequence, so a form is worked through in an order nobody intended. What we found on this page focus order: the first 12 Tab stops do not follow document order The evidence, taken from the page as served How the keyboard moves through this page
Read on the page once its scripts had run, following the keyboard from the top.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| DS03 | fail | an AI crawler asking for this page is refused by the security layer in front of the site, while an ordinary browser is served, so the page's content never reaches the AI and answers about it are left to memory or guesswork | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The same page loads for a browser but is refused when the request names itself as an AI service. What good looks like The page returns the same response to a named AI service as to a browser, with no edge block. Why it matters The block sits in front of the site and leaves no trace in its own logs, so the estate is closed off unnoticed. What we found on this page an AI crawler asking for this page is refused by the security layer in front of the site, while an ordinary browser is served, so the page's content never reaches the AI and answers about it are left to memory or guesswork The evidence, taken from the page as served The estate's edge tested with each AI crawler: a browser is served, the crawlers are refused
Hostwww.aviva.com · resolves to 23.215.224.114 · an Akamai edge hostname
Address trailwww.aviva.com › cert10.uk.aviva.com.ksd.edgekey.net › e5059.ksd.akamaiedge.net
Checked2026-07-31 16:33 UTC · request sent from 10.100.100.212 (our checker)
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page returns the same response to a named AI service as to a browser, with no edge block. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 5 out of a possible 5, because it is one of the checks that decide whether content can be reached and read at all, so it carries the heaviest weight in the figure for this item. Why it moves the misinformation reading This failure is a real and common route to a wrong answer for the content it affects, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT32 | warning | length 44 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The meta description's length is usable, between 50 and 170 characters. What good looks like The meta description's length is usable, long enough to say something and short enough not to be cut. Why it matters Too short says nothing and too long gets cut, so the summary field is spent without doing its job. What we found on this page length 44 The evidence, taken from the page as served The page's description, as served
<meta name="description" content="Explore our Investors section on aviva.com. "/> | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT09 | fail | 3 skipped heading level(s) in document order | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Heading levels step down one at a time, rather than jumping from an H2 straight to an H5. What good looks like Heading levels step down one at a time, without jumping a level. Why it matters A skipped level breaks the trail that says which section a passage belongs to, so it is filed under the wrong one. What we found on this page 3 skipped heading level(s) in document order The evidence, taken from the page as served The page's heading outline, in document order (a jump in level is marked)
H3 Recommendation to reject "mini-tender" offers by Litani LLC H1 Investors H3 Latest share price (GBp) level jumped H3 Final dividend (GBp) H3 Market capitalisation (GBP) H3 Dividends H3 Manage your shares H3 Strategy and investment case H3 Contact us H2 Share price performance H2 Reports and results H2 Annual Report and Accounts 2025 H2 Results, presentations and reports H2 Regulatory announcements H2 In focus presentations H2 Latest results and trading updates H4 For the full dividend timetable see our Dividends page. level jumped H2 Our governance H2 Shareholder services H2 Dividends H2 Manage your shares H2 Shareholder updates H2 Communication H2 Shareholder meetings and archives H2 Share capital H2 Warning to shareholders H2 Institutional investors H2 Credit ratings and debt H2 Shareholder profile H2 Equity analysts H2 Regulatory returns H2 Discover more H3 About us H3 Sustainability H3 Newsroom H2 Disclaimer H4 Investis - terms of use level jumped H2 Login or register H2 Site navigation H3 About us H4 Our purpose and priorities H4 Our customers and people H4 Our Board and Executives H4 2025 Annual Report H4 Get support H3 Investors H4 Strategy and performance H4 Institutional investors H4 Shareholder services H4 Corporate governance H4 Risk governance and management H4 2025 Annual Report H4 Get support H3 Newsroom H4 News and research H4 Resources H4 About Aviva H4 Get support H3 Careers H4 Careers at Aviva H4 Life at Aviva H4 Diversity and inclusion H4 Get support H3 Sustainability H4 Sustainability at Aviva H4 Sustainability news H4 Sustainability resources H4 Aviva Foundation H4 Get support H4 Get support H2 Footer H3 Useful information H4 Products in our locations H4 Use MyAviva H4 How to make a complaint H3 On this site H3 Media H3 Corporate H3 Other links H3 Social H3 Legal H3 Copyright
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: heading levels step down one at a time, without jumping a level. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT16 | warning | the page carries no structured data block stating what it is (not required; a hygiene signal) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The page carries structured data, the machine-readable summary of what it describes. What good looks like The page carries structured data summarising what it describes. Why it matters Vendors document this as optional rather than required, so its absence is a small forfeit and no more. What we found on this page the page carries no structured data block stating what it is (not required; a hygiene signal) The evidence, taken from the page as served The head of this page, as served
The page was read for a structured data block describing what the page is. <head> <title>Investors - Aviva plc</title> <script defer="defer" type="text/javascript" src="https://rum.hlx.page/.rum/@adobe/helix-rum-js@%5E2/dist/rum-standalone.js" data-routing="env=prod,tier=publish,ams=Aviva Group"/> <link rel="preconnect" href="https://static.aviva.io/"/> <link rel="preconnect" href="https://static.aviva.io/" crossorigin="anonymous"/> <link rel="preconnect" href="https://dpm.demdex.net/"/> <link rel="preconnect" href="https://assets.adobedtm.com/"/> <link rel="preload" href="https://static.aviva.io/assets/fonts/sourcesans3-variable-roman-base.woff2" as="font" crossorigin="anonymous"/> <link rel="preload" href="https://cdn-ukwest.onetrust.com/scripttemplates/otSDKStub.js" as="script" crossorigin="anonymous"/> <link rel="preload" href="https://static.aviva.io/assets/fonts/avivacurve-regular.woff2" as="font" crossorigin="anonymous"/> <meta content="width=device-width,initial-scale=1" name="viewport"/> <meta property="templatename" content="categorypage"/> <meta property="article:published_time" content="2017-10-18T10:21:34"/> <meta property="og:description" content="Explore our Investors section on aviva.com. "/> <meta property="og:title" content="Investors"/>โฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR13 | warning | the page does not mark out its main content, so what is unique to this page cannot be told apart from the menus and foot-of-page text repeated across the site | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page's main content is marked off from the navigation and footer around it. What good looks like A main or article region marks the primary content off from the navigation and footer around it. Why it matters Pulling the page's text returns menus and legal footers mixed with the substance, so the answer arrives buried in noise. What we found on this page the page does not mark out its main content, so what is unique to this page cannot be told apart from the menus and foot-of-page text repeated across the site The evidence, taken from the page as served The blocks this page marks out, as served
The page was read for the block that marks out its main content. <meta itemprop="name" content="Investors"/> <meta itemprop="url" content="https://www.aviva.com/investors/"/> <div class="l-whole-page" data-back-to-top="Back to start of main content" data-component="back-to-top-es6"> <script> <span data-module="app/init-es6" data-module-load="true"/> <script id="js-init" src="https://static.aviva.io/assets/themes-managed/v6.1.0/shared/extensions/requirejs/init.js" asynโฆ <script src="https://static.aviva.io/etc.clientlibs/settings/wcm/designs/aviva-corporate/clientlibs/resources/2-20260728โฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS01 | fail | 1 of 1 boxes in the page's forms carry no name saying what each is for, so which answer belongs in which box rests on layout alone | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Each box, dropdown and text area in a form carries a name saying what it is for. What good looks like Each field in a form carries a name saying what it is for. Why it matters Unnamed fields leave the tie between a question and its box resting on layout, which shifts as the page reflows. What we found on this page 1 of 1 boxes in the page's forms carry no name saying what each is for, so which answer belongs in which box rests on layout alone The evidence, taken from the page as served The form boxes that carry no name, as served
<input type="search" name="q" id="search-site" value="" class="m-site-search__input" placeholder="Enter a keyword"/> Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: each field in a form carries a name saying what it is for. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS08 | fail | 1 link wording(s) are used for more than one destination, so the same words point at different pages: โcontact usโ; the links are listed in the view | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Links that share exactly the same wording on one page while pointing at different destinations. What good looks like Links that share the same wording lead to the same destination. Why it matters The wording no longer settles the target, so the wrong one gets followed at the point where the choice matters. What we found on this page 1 link wording(s) are used for more than one destination, so the same words point at different pages: โcontact usโ; the links are listed in the view The evidence, taken from the page as served Links that share the same text but point to different destinations, as served
<a href="/corporate-contacts/">Contact us</a> <a aria-describedby="75e34eb3-16f0-4b95-a579-c737ace77740" class="m-card__link" href="/investors/institutional-investors-overview/investor-relations-contacts/">Contact us</a> Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: links that share the same wording lead to the same destination. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS10 | fail | the page's first heading is not its top-level heading, so the structure starts part way down; the heading structure skips a level in 3 place(s), so the order does not follow | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check A page's headings start at the top level and step down without skipping a level. What good looks like The page's headings start at the top level and step down without skipping a level. Why it matters Content under a skipped level has no clear parent section, so structure taken from the page misplaces its text. What we found on this page the page's first heading is not its top-level heading, so the structure starts part way down; the heading structure skips a level in 3 place(s), so the order does not follow The evidence, taken from the page as served The page's heading outline, in document order (a jump in level is marked)
H3 Recommendation to reject "mini-tender" offers by Litani LLC level jumped H1 Investors H3 Latest share price (GBp) level jumped H3 Final dividend (GBp) H3 Market capitalisation (GBP) H3 Dividends H3 Manage your shares H3 Strategy and investment case H3 Contact us H2 Share price performance H2 Reports and results H2 Annual Report and Accounts 2025 H2 Results, presentations and reports H2 Regulatory announcements H2 In focus presentations H2 Latest results and trading updates H4 For the full dividend timetable see our Dividends page. level jumped H2 Our governance H2 Shareholder services H2 Dividends H2 Manage your shares H2 Shareholder updates H2 Communication H2 Shareholder meetings and archives H2 Share capital H2 Warning to shareholders H2 Institutional investors H2 Credit ratings and debt H2 Shareholder profile H2 Equity analysts H2 Regulatory returns H2 Discover more H3 About us H3 Sustainability H3 Newsroom H2 Disclaimer H4 Investis - terms of use level jumped H2 Login or register H2 Site navigation H3 About us H4 Our purpose and priorities H4 Our customers and people H4 Our Board and Executives H4 2025 Annual Report H4 Get support H3 Investors H4 Strategy and performance H4 Institutional investors H4 Shareholder services H4 Corporate governance H4 Risk governance and management H4 2025 Annual Report H4 Get support H3 Newsroom H4 News and research H4 Resources H4 About Aviva H4 Get support H3 Careers H4 Careers at Aviva H4 Life at Aviva H4 Diversity and inclusion H4 Get support H3 Sustainability H4 Sustainability at Aviva H4 Sustainability news H4 Sustainability resources H4 Aviva Foundation H4 Get support H4 Get support H2 Footer H3 Useful information H4 Products in our locations H4 Use MyAviva H4 How to make a complaint H3 On this site H3 Media H3 Corporate H3 Other links H3 Social H3 Legal H3 Copyright
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page's headings start at the top level and step down without skipping a level. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR03 | warning | 15% of the words a person sees are missing from the page as first delivered (22372 characters delivered, 24918 once the page finishes building itself) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check How much of the page's content exists only once JavaScript has run. What good looks like The page's content is present in the served HTML, so it does not depend on JavaScript to appear. Why it matters The page is fetched successfully but the answer is missing from what comes back, so the content is absent rather than wrong. What we found on this page 15% of the words a person sees are missing from the page as first delivered (22372 characters delivered, 24918 once the page finishes building itself) The evidence, taken from the page as served Content present only after JavaScript runs (absent from the served HTML)
The served HTML carries 22372 characters of text; after JavaScript runs the page carries 24918. 15% of the rendered page's words are absent from the HTML the server sends. What the server sends (raw HTML text, first 280 chars) Investors - Aviva plc Skip to content Recommendation to reject "mini-tender" offers by Litani LLC We want to make you aware that a company called Litani may write, or may already have written, to you offering to buy some or all of your Aviva shares. Our warning to shareholders pa…
Words present only after JavaScript runs
acceptactiveadvertisementsadvertisingallowallowedalwaysapplyaroundautomaticallybecausebelowblockbrowserbuttoncannotcategorycentrechoiceschooseclearclosecollectconfirmcorecrimecustomisedeliverdetectdeviceenableenablesenhancedexampleexperiencefilesfilterfiltersfraudfunctionfunctionalfunctionalityholdhowevericonimpactimproveincludesinterestkeepleastmainmarketingmovenecessaryoptionalpersonalisationpersonalisedplacedpopular
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR11 | warning | 15% of the words a person sees are missing from the page as first delivered, which is 0.90 of its finished size | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The measured gap between the page as served and the page after the browser has built it. What good looks like The served page and the fully built page carry the same words, with little gap between them. Why it matters Two versions of the same page exist, and which words come back depends on which version was fetched. What we found on this page 15% of the words a person sees are missing from the page as first delivered, which is 0.90 of its finished size The evidence, taken from the page as served This page as first delivered, against the page once its scripts have run
Both were taken from the same request. The first is what the site sent; the second is what a person ends up looking at.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR12 | warning | 79% of the page's text (19901 of 24918 characters) is not visible before interaction | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check How much of the page's text is hidden behind a click or an expander before anyone interacts. What good looks like The page's text is visible as it loads, not held behind a click or an expander. Why it matters Half or more of the page's text is present but never shown, so what readers see and what it contains diverge. What we found on this page 79% of the page's text (19901 of 24918 characters) is not visible before interaction The evidence, taken from the page as served How much of this page is hidden until something is clicked
Counted on the page once its scripts had run, before anything was clicked.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT28 | warning | 4 expandable section(s) only put their 203 characters of content on the page once clicked, so the text is absent until then | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check On sampled pages, whether clicking expandable controls adds text that was not there before. What good looks like The page's text is present before interaction, not added only on a click. Why it matters Text that appears only on a click sits outside any route that does not click, so it is simply not there. What we found on this page 4 expandable section(s) only put their 203 characters of content on the page once clicked, so the text is absent until then The evidence, taken from the page as served The expanding sections on this page, as they behaved
Each control was clicked once on the loaded page, and the text before and after was compared.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT29 | warning | content inside the page's expanding sections and tabs is only added when a person clicks, so it is not there to be read otherwise | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Accordion and tab content already present in the page collapsed, or arriving only on a click. What good looks like Accordion and tab content is already present in the page, collapsed, rather than arriving on a click. Why it matters Collapsed content costs nothing, but content injected on a click is absent from the page as first served. What we found on this page content inside the page's expanding sections and tabs is only added when a person clicks, so it is not there to be read otherwise The evidence, taken from the page as served The expanding sections on this page, as they behaved
Each control was clicked once on the loaded page, and the text before and after was compared.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS02 | warning | 1 of 81 buttons, links and controls on the loaded page carry no name in the page's code saying what each is for | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page's buttons, links and form controls each carry a name once the page has loaded. What good looks like The page's buttons, links and form controls each carry a name once the page has loaded. Why it matters Unnamed controls are identified by their position on the screen alone, so a redesign moves what they refer to. What we found on this page 1 of 81 buttons, links and controls on the loaded page carry no name in the page's code saying what each is for The evidence, taken from the page as served The controls on this page that carry no name
Read on the page once its scripts had run.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS04 | warning | the page's naming markup is faulty: 1 name label(s) point at nothing: the code that should hold the name is absent; 103 working control(s) sit inside a section the code marks as hidden, so they work on screen but are absent from what is read out | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Accessibility markup faults: invented roles, labels pointing at nothing, live controls marked hidden. What good looks like The page's accessibility markup is sound, with valid roles and no labels pointing at nothing. Why it matters The page's own description of its controls is wrong, so what it offers and what it declares do not match. What we found on this page the page's naming markup is faulty: 1 name label(s) point at nothing: the code that should hold the name is absent; 103 working control(s) sit inside a section the code marks as hidden, so they work on screen but are absent from what is read out The evidence, taken from the page as served The faulty markup, as the page serves it once loaded
<input type="checkbox" name="storage-access" id="ot-group-id-C0001-toggle" aria-expanded="false" ot-accordion="true" role="button" aria-controls="ot-desc-id-C0001" aria-labelledby="ot-header-id-C0001 ot-status-id-C0001"/> <input type="search" name="q" id="search-site" value="" class="m-site-search__input" placeholder="Enter a keyword"/> <button id="submit" type="submit" class="m-site-search__button"> Search </button> <a class="a-button a-button--primary a-button--full-width" href="/about-us/myaviva/">MyAviva</a> <a class="m-primary-navigation-sub-section__link a-button a-button--tertiary" href="/about-us/"> Explore About us </a> <a class="a-button a-button--tertiary" href="/about-us/our-purpose-and-priorities-overview/"> Our purpose and priorities overview </a> <a class="a-button a-button--tertiary" href="/about-us/our-purpose-and-priorities-overview/our-purpose-and-values/"> Our purpose and values </a> <a class="a-button a-button--tertiary" href="/about-us/our-purpose-and-priorities-overview/how-we-are-organised/"> How we're organised </a> <a class="a-button a-button--tertiary" href="/about-us/our-purpose-and-priorities-overview/helping-the-uk-get-ready/"> Helping the UK Get Ready </a> <a class="a-button a-button--tertiary" href="/about-us/our-purpose-and-priorities-overview/innovation/"> Innovation at Aviva </a> …and 94 more like it. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| DS03 | fail | an AI crawler asking for this page is refused by the security layer in front of the site, while an ordinary browser is served, so the page's content never reaches the AI and answers about it are left to memory or guesswork | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The same page loads for a browser but is refused when the request names itself as an AI service. What good looks like The page returns the same response to a named AI service as to a browser, with no edge block. Why it matters The block sits in front of the site and leaves no trace in its own logs, so the estate is closed off unnoticed. What we found on this page an AI crawler asking for this page is refused by the security layer in front of the site, while an ordinary browser is served, so the page's content never reaches the AI and answers about it are left to memory or guesswork The evidence, taken from the page as served The estate's edge tested with each AI crawler: a browser is served, the crawlers are refused
Hostwww.aviva.com · resolves to 23.215.224.114 · an Akamai edge hostname
Address trailwww.aviva.com › cert10.uk.aviva.com.ksd.edgekey.net › e5059.ksd.akamaiedge.net
Checked2026-07-31 16:33 UTC · request sent from 10.100.100.212 (our checker)
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page returns the same response to a named AI service as to a browser, with no edge block. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 5 out of a possible 5, because it is one of the checks that decide whether content can be reached and read at all, so it carries the heaviest weight in the figure for this item. Why it moves the misinformation reading This failure is a real and common route to a wrong answer for the content it affects, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR13 | warning | the page does not mark out its main content, so what is unique to this page cannot be told apart from the menus and foot-of-page text repeated across the site | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page's main content is marked off from the navigation and footer around it. What good looks like A main or article region marks the primary content off from the navigation and footer around it. Why it matters Pulling the page's text returns menus and legal footers mixed with the substance, so the answer arrives buried in noise. What we found on this page the page does not mark out its main content, so what is unique to this page cannot be told apart from the menus and foot-of-page text repeated across the site The evidence, taken from the page as served The blocks this page marks out, as served
The page was read for the block that marks out its main content. <meta itemprop="name" content="Aviva plc"/> <meta itemprop="url" content="https://www.aviva.com/"/> <div class="l-whole-page" data-back-to-top="Back to start of main content" data-component="back-to-top-es6"> <script> <span data-module="app/init-es6" data-module-load="true"/> <script id="js-init" src="https://static.aviva.io/assets/themes-managed/v6.1.0/shared/extensions/requirejs/init.js" asynโฆ <script src="https://static.aviva.io/etc.clientlibs/settings/wcm/designs/aviva-corporate/clientlibs/resources/2-20260728โฆ <script type="application/ld+json"> | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS10 | fail | the page's first heading is not its top-level heading, so the structure starts part way down | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check A page's headings start at the top level and step down without skipping a level. What good looks like The page's headings start at the top level and step down without skipping a level. Why it matters Content under a skipped level has no clear parent section, so structure taken from the page misplaces its text. What we found on this page the page's first heading is not its top-level heading, so the structure starts part way down The evidence, taken from the page as served The page's heading outline, in document order (a jump in level is marked)
H3 Recommendation to reject "mini-tender" offers by Litani LLC level jumped H1 Ready for Tomorrow starts with financial confidence H2 Aviva plc Q1 2026 Trading Update H2 Discover our investment case and strategy H2 Aviva plc 2025 results announcement H2 We are the UK's leading diversified insurer, with businesses spanning insurance, H2 Half year results 2026 H2 Watch our 2025 full year results video with Group CEO, Amanda Blanc DBE H3 Transcriptย for video Watch our 2025 full year results video with Group CEO, Ama H2 Featured stories from the UK, Canada and Ireland H2 The รยฃ300m Cambridge investment H2 The one who stands behind the promise H2 A city worth investing in H3 Share price * H3 Final dividend H3 Financial calendar H2 Quick links H2 Customer support H3 Aviva UK H3 Aviva Ireland H3 Aviva Canada H3 Aviva Investors H2 News from the UK, Canada and Ireland H2 Aviva has successfully completed its รยฃ350m share buyback programme H2 Aviva to rebrand Probitas 1492 as รขยยAviva Syndicatesรขยย H2 Aviva receives FCA approval to deliver targeted support H2 Aviva plc Q1 2026 Trading Update H2 Aviva Canada media centre H2 Aviva Investors company news H2 Aviva Ireland media centre H2 Reports and documents H3 Q1 2026 announcement H3 Full year results 2025 announcement H3 Annual Report and Accounts 2025 H3 Business Model 2025 H2 Login or register H2 Site navigation H3 About us H4 Our purpose and priorities H4 Our customers and people H4 Our Board and Executives H4 2025 Annual Report H4 Get support H3 Investors H4 Strategy and performance H4 Institutional investors H4 Shareholder services H4 Corporate governance H4 Risk governance and management H4 2025 Annual Report H4 Get support H3 Newsroom H4 News and research H4 Resources H4 About Aviva H4 Get support H3 Careers H4 Careers at Aviva H4 Life at Aviva H4 Diversity and inclusion H4 Get support H3 Sustainability H4 Sustainability at Aviva H4 Sustainability news H4 Sustainability resources H4 Aviva Foundation H4 Get support H4 Get support H2 Footer H3 Useful information H4 Products in our locations H4 Use MyAviva H4 How to make a complaint H3 On this site H3 Media H3 Corporate H3 Other links H3 Social H3 Legal H3 Copyright
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page's headings start at the top level and step down without skipping a level. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS14 | fail | 1 video(s) on the page with no captions on the video and no written transcript on the page: nothing spoken is available as text in any form | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether each video carries captions of its own, timed text on the video itself, judged together with whether the page holds a written transcript. What good looks like Captions carried on the video. A WARNING means the video has no captions but a written transcript on the page holds the words. A FAIL means neither exists, so nothing spoken is available as text in any form; that total absence is marked here once, not spread across two findings. Why it matters Spoken content that exists only as sound is invisible to a reader, human or machine: nothing said in the video can be found, read or quoted. What we found on this page 1 video(s) on the page with no captions on the video and no written transcript on the page: nothing spoken is available as text in any form The evidence, taken from the page as served Each video on the page, as served: its code, source file and caption track
No caption track on the video and no transcript link on the page. <video id="video6390041787112" data-embed="default" class="video-js" controls=""/> Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: captions carried on the video. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS16 | warning | 1 media resource(s) are named as a technical code, not human-meaningful words, so a machine cannot tell what the resource is from its name | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The name a video, audio clip or image is served under, and whether it is human-meaningful words or a technical code. What good looks like Video, audio and image files carry names made of words that say what they are, not a technical code. Why it matters A resource named as a code or a bare number says nothing about what it is, so a machine cataloguing it has only the code to go on. What we found on this page 1 media resource(s) are named as a technical code, not human-meaningful words, so a machine cannot tell what the resource is from its name The evidence, taken from the page as served The media resources whose name is a technical code, as served
A meaningful name (words that say what it is) lets a machine identify the resource; a code or a bare number cannot. <video id="video6390041787112" data-embed="default" class="video-js" controls=""/> | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR03 | warning | 15% of the words a person sees are missing from the page as first delivered (12095 characters delivered, 14646 once the page finishes building itself) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check How much of the page's content exists only once JavaScript has run. What good looks like The page's content is present in the served HTML, so it does not depend on JavaScript to appear. Why it matters The page is fetched successfully but the answer is missing from what comes back, so the content is absent rather than wrong. What we found on this page 15% of the words a person sees are missing from the page as first delivered (12095 characters delivered, 14646 once the page finishes building itself) The evidence, taken from the page as served Content present only after JavaScript runs (absent from the served HTML)
The served HTML carries 12095 characters of text; after JavaScript runs the page carries 14646. 15% of the rendered page's words are absent from the HTML the server sends. What the server sends (raw HTML text, first 280 chars) Aviva corporate website - Aviva plc Skip to content Recommendation to reject "mini-tender" offers by Litani LLC We want to make you aware that a company called Litani may write, or may already have written, to you offering to buy some or all of your Aviva shares. Our warning to s…
Words present only after JavaScript runs
acceptactiveadvertisementsadvertisingallowallowedalwaysapplyautomaticallybackbelowblockbrowserbuttoncannotcategorychangechoiceschooseclearclosecollectconfirmconsentcorecrimecustomisedetectdevicedifferentenableenablesenhancedexampleexperiencefilesfilterfiltersfraudfunctionfunctionalfunctionalityhelphowevericonimpactimproveincludesinterestkeepleastmainmarketingmovenecessaryoptionalpersonalisationpersonalisedpopularpreference
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR11 | warning | 15% of the words a person sees are missing from the page as first delivered, which is 0.83 of its finished size | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The measured gap between the page as served and the page after the browser has built it. What good looks like The served page and the fully built page carry the same words, with little gap between them. Why it matters Two versions of the same page exist, and which words come back depends on which version was fetched. What we found on this page 15% of the words a person sees are missing from the page as first delivered, which is 0.83 of its finished size The evidence, taken from the page as served This page as first delivered, against the page once its scripts have run
Both were taken from the same request. The first is what the site sent; the second is what a person ends up looking at.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR12 | warning | 63% of the page's text (9230 of 14646 characters) is not visible before interaction | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check How much of the page's text is hidden behind a click or an expander before anyone interacts. What good looks like The page's text is visible as it loads, not held behind a click or an expander. Why it matters Half or more of the page's text is present but never shown, so what readers see and what it contains diverge. What we found on this page 63% of the page's text (9230 of 14646 characters) is not visible before interaction The evidence, taken from the page as served How much of this page is hidden until something is clicked
Counted on the page once its scripts had run, before anything was clicked.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS04 | warning | the page's naming markup is faulty: 1 name label(s) point at nothing: the code that should hold the name is absent; 103 working control(s) sit inside a section the code marks as hidden, so they work on screen but are absent from what is read out | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Accessibility markup faults: invented roles, labels pointing at nothing, live controls marked hidden. What good looks like The page's accessibility markup is sound, with valid roles and no labels pointing at nothing. Why it matters The page's own description of its controls is wrong, so what it offers and what it declares do not match. What we found on this page the page's naming markup is faulty: 1 name label(s) point at nothing: the code that should hold the name is absent; 103 working control(s) sit inside a section the code marks as hidden, so they work on screen but are absent from what is read out The evidence, taken from the page as served The faulty markup, as the page serves it once loaded
<input type="checkbox" name="storage-access" id="ot-group-id-C0001-toggle" aria-expanded="false" ot-accordion="true" role="button" aria-controls="ot-desc-id-C0001" aria-labelledby="ot-header-id-C0001 ot-status-id-C0001" data-di-id="#ot-group-id-C0001-toggle"/> <input type="search" name="q" id="search-site" value="" itemprop="query-input" class="m-site-search__input" placeholder="Enter a keyword" data-di-id="#search-site"/> <button id="submit" type="submit" class="m-site-search__button" data-di-id="#submit"> Search </button> <a class="a-button a-button--primary a-button--full-width" href="/about-us/myaviva/" data-di-id="di-id-71c90199-ed344a8f">MyAviva</a> <a class="m-primary-navigation-sub-section__link a-button a-button--tertiary" href="/about-us/" data-di-id="di-id-6bd3a2bf-eef86a21"> Explore About us </a> <a class="a-button a-button--tertiary" href="/about-us/our-purpose-and-priorities-overview/" data-di-id="di-id-15d4a7a5-93b5857e"> Our purpose and priorities overview </a> <a class="a-button a-button--tertiary" href="/about-us/our-purpose-and-priorities-overview/our-purpose-and-values/" data-di-id="di-id-be45d8a2-aa1d300a"> Our purpose and values </a> <a class="a-button a-button--tertiary" href="/about-us/our-purpose-and-priorities-overview/how-we-are-organised/" data-di-id="di-id-41a2c235-daf2e78f"> How we're organised </a> <a class="a-button a-button--tertiary" href="/about-us/our-purpose-and-priorities-overview/helping-the-uk-get-ready/" data-di-id="di-id-36b2655e-83d3cbef"> Helping the UK Get Ready </a> <a class="a-button a-button--tertiary" href="/about-us/our-purpose-and-priorities-overview/innovation/" data-di-id="di-id-570dcf79-adddfcac"> Innovation at Aviva </a> …and 94 more like it. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| DS03 | fail | an AI crawler asking for this page is refused by the security layer in front of the site, while an ordinary browser is served, so the page's content never reaches the AI and answers about it are left to memory or guesswork | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The same page loads for a browser but is refused when the request names itself as an AI service. What good looks like The page returns the same response to a named AI service as to a browser, with no edge block. Why it matters The block sits in front of the site and leaves no trace in its own logs, so the estate is closed off unnoticed. What we found on this page an AI crawler asking for this page is refused by the security layer in front of the site, while an ordinary browser is served, so the page's content never reaches the AI and answers about it are left to memory or guesswork The evidence, taken from the page as served The estate's edge tested with each AI crawler: a browser is served, the crawlers are refused
Hostwww.aviva.com · resolves to 23.215.224.114 · an Akamai edge hostname
Address trailwww.aviva.com › cert10.uk.aviva.com.ksd.edgekey.net › e5059.ksd.akamaiedge.net
Checked2026-07-31 16:33 UTC · request sent from 10.100.100.212 (our checker)
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page returns the same response to a named AI service as to a browser, with no edge block. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 5 out of a possible 5, because it is one of the checks that decide whether content can be reached and read at all, so it carries the heaviest weight in the figure for this item. Why it moves the misinformation reading This failure is a real and common route to a wrong answer for the content it affects, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT09 | fail | 1 skipped heading level(s) in document order | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Heading levels step down one at a time, rather than jumping from an H2 straight to an H5. What good looks like Heading levels step down one at a time, without jumping a level. Why it matters A skipped level breaks the trail that says which section a passage belongs to, so it is filed under the wrong one. What we found on this page 1 skipped heading level(s) in document order The evidence, taken from the page as served The page's heading outline, in document order (a jump in level is marked)
H3 Recommendation to reject "mini-tender" offers by Litani LLC H1 Investor and shareholder contacts H2 Explore page H2 Institutional investor contact H2 Shareholder services - contacting us about your shares H2 Manage your shares H4 Group General Counsel level jumped H4 Neil Harrison H4 Group Company Secretary H4 Susan Adams H2 Login or register H2 Site navigation H3 About us H4 Our purpose and priorities H4 Our customers and people H4 Our Board and Executives H4 2025 Annual Report H4 Get support H3 Investors H4 Strategy and performance H4 Institutional investors H4 Shareholder services H4 Corporate governance H4 Risk governance and management H4 2025 Annual Report H4 Get support H3 Newsroom H4 News and research H4 Resources H4 About Aviva H4 Get support H3 Careers H4 Careers at Aviva H4 Life at Aviva H4 Diversity and inclusion H4 Get support H3 Sustainability H4 Sustainability at Aviva H4 Sustainability news H4 Sustainability resources H4 Aviva Foundation H4 Get support H4 Get support H2 Footer H3 Useful information H4 Products in our locations H4 Use MyAviva H4 How to make a complaint H3 On this site H3 Media H3 Corporate H3 Other links H3 Social H3 Legal H3 Copyright
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: heading levels step down one at a time, without jumping a level. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT16 | warning | the page carries no structured data block stating what it is (not required; a hygiene signal) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The page carries structured data, the machine-readable summary of what it describes. What good looks like The page carries structured data summarising what it describes. Why it matters Vendors document this as optional rather than required, so its absence is a small forfeit and no more. What we found on this page the page carries no structured data block stating what it is (not required; a hygiene signal) The evidence, taken from the page as served The head of this page, as served
The page was read for a structured data block describing what the page is. <head> <title>Investor and shareholder contacts - Aviva plc</title> <script defer="defer" type="text/javascript" src="https://rum.hlx.page/.rum/@adobe/helix-rum-js@%5E2/dist/rum-standalone.js" data-routing="env=prod,tier=publish,ams=Aviva Group"/> <link rel="preconnect" href="https://static.aviva.io/"/> <link rel="preconnect" href="https://static.aviva.io/" crossorigin="anonymous"/> <link rel="preconnect" href="https://dpm.demdex.net/"/> <link rel="preconnect" href="https://assets.adobedtm.com/"/> <link rel="preload" href="https://static.aviva.io/assets/fonts/sourcesans3-variable-roman-base.woff2" as="font" crossorigin="anonymous"/> <link rel="preload" href="https://cdn-ukwest.onetrust.com/scripttemplates/otSDKStub.js" as="script" crossorigin="anonymous"/> <link rel="preload" href="https://static.aviva.io/assets/fonts/avivacurve-regular.woff2" as="font" crossorigin="anonymous"/> <meta content="width=device-width,initial-scale=1" name="viewport"/> <meta property="templatename" content="featurelitepage"/> <meta property="article:published_time" content="2021-07-15T03:35:44"/> <meta property="og:description" content="Contact information for investors and shareholders. "/> <meta properโฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR13 | warning | the page does not mark out its main content, so what is unique to this page cannot be told apart from the menus and foot-of-page text repeated across the site | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page's main content is marked off from the navigation and footer around it. What good looks like A main or article region marks the primary content off from the navigation and footer around it. Why it matters Pulling the page's text returns menus and legal footers mixed with the substance, so the answer arrives buried in noise. What we found on this page the page does not mark out its main content, so what is unique to this page cannot be told apart from the menus and foot-of-page text repeated across the site The evidence, taken from the page as served The blocks this page marks out, as served
The page was read for the block that marks out its main content. <meta itemprop="name" content="Investor and shareholder contacts"/> <meta itemprop="url" content="https://www.aviva.com/investors/institutional-investors-overview/investor-relations-contacโฆ <div class="l-whole-page" data-back-to-top="Back to start of main content" data-component="back-to-top-es6"> <script> <span data-module="app/init-es6" data-module-load="true"/> <script id="js-init" src="https://static.aviva.io/assets/themes-managed/v6.1.0/shared/extensions/requirejs/init.js" asynโฆ <script src="https://static.aviva.io/etc.clientlibs/settings/wcm/designs/aviva-corporate/clientlibs/resources/2-20260728โฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS01 | fail | 1 of 1 boxes in the page's forms carry no name saying what each is for, so which answer belongs in which box rests on layout alone | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Each box, dropdown and text area in a form carries a name saying what it is for. What good looks like Each field in a form carries a name saying what it is for. Why it matters Unnamed fields leave the tie between a question and its box resting on layout, which shifts as the page reflows. What we found on this page 1 of 1 boxes in the page's forms carry no name saying what each is for, so which answer belongs in which box rests on layout alone The evidence, taken from the page as served The form boxes that carry no name, as served
<input type="search" name="q" id="search-site" value="" class="m-site-search__input" placeholder="Enter a keyword"/> Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: each field in a form carries a name saying what it is for. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS10 | fail | the page's first heading is not its top-level heading, so the structure starts part way down; the heading structure skips a level in 1 place(s), so the order does not follow | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check A page's headings start at the top level and step down without skipping a level. What good looks like The page's headings start at the top level and step down without skipping a level. Why it matters Content under a skipped level has no clear parent section, so structure taken from the page misplaces its text. What we found on this page the page's first heading is not its top-level heading, so the structure starts part way down; the heading structure skips a level in 1 place(s), so the order does not follow The evidence, taken from the page as served The page's heading outline, in document order (a jump in level is marked)
H3 Recommendation to reject "mini-tender" offers by Litani LLC level jumped H1 Investor and shareholder contacts H2 Explore page H2 Institutional investor contact H2 Shareholder services - contacting us about your shares H2 Manage your shares H4 Group General Counsel level jumped H4 Neil Harrison H4 Group Company Secretary H4 Susan Adams H2 Login or register H2 Site navigation H3 About us H4 Our purpose and priorities H4 Our customers and people H4 Our Board and Executives H4 2025 Annual Report H4 Get support H3 Investors H4 Strategy and performance H4 Institutional investors H4 Shareholder services H4 Corporate governance H4 Risk governance and management H4 2025 Annual Report H4 Get support H3 Newsroom H4 News and research H4 Resources H4 About Aviva H4 Get support H3 Careers H4 Careers at Aviva H4 Life at Aviva H4 Diversity and inclusion H4 Get support H3 Sustainability H4 Sustainability at Aviva H4 Sustainability news H4 Sustainability resources H4 Aviva Foundation H4 Get support H4 Get support H2 Footer H3 Useful information H4 Products in our locations H4 Use MyAviva H4 How to make a complaint H3 On this site H3 Media H3 Corporate H3 Other links H3 Social H3 Legal H3 Copyright
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page's headings start at the top level and step down without skipping a level. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR03 | warning | 21% of the words a person sees are missing from the page as first delivered (8037 characters delivered, 10583 once the page finishes building itself) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check How much of the page's content exists only once JavaScript has run. What good looks like The page's content is present in the served HTML, so it does not depend on JavaScript to appear. Why it matters The page is fetched successfully but the answer is missing from what comes back, so the content is absent rather than wrong. What we found on this page 21% of the words a person sees are missing from the page as first delivered (8037 characters delivered, 10583 once the page finishes building itself) The evidence, taken from the page as served Content present only after JavaScript runs (absent from the served HTML)
The served HTML carries 8037 characters of text; after JavaScript runs the page carries 10583. 21% of the rendered page's words are absent from the HTML the server sends. What the server sends (raw HTML text, first 280 chars) Investor and shareholder contacts - Aviva plc Skip to content Recommendation to reject "mini-tender" offers by Litani LLC We want to make you aware that a company called Litani may write, or may already have written, to you offering to buy some or all of your Aviva shares. Our wa…
Words present only after JavaScript runs
acceptactiveadvertisementsadvertisingallowallowedalwaysapplyaroundautomaticallybackbecausebelowblockbrowserbuttoncannotcategorychangechoiceschooseclearclosecollectconfirmconsentcorecrimecustomisedeliverdetectdevicedifferentenableenablesenhancedexampleexperiencefilesfilterfiltersfraudfunctionfunctionalfunctionalityhelpholdhowevericonimpactimproveincludesinterestkeepleastmainmarketingmovenecessaryoptional
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR11 | warning | 21% of the words a person sees are missing from the page as first delivered, which is 0.76 of its finished size | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The measured gap between the page as served and the page after the browser has built it. What good looks like The served page and the fully built page carry the same words, with little gap between them. Why it matters Two versions of the same page exist, and which words come back depends on which version was fetched. What we found on this page 21% of the words a person sees are missing from the page as first delivered, which is 0.76 of its finished size The evidence, taken from the page as served This page as first delivered, against the page once its scripts have run
Both were taken from the same request. The first is what the site sent; the second is what a person ends up looking at.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR12 | warning | 62% of the page's text (6664 of 10583 characters) is not visible before interaction | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check How much of the page's text is hidden behind a click or an expander before anyone interacts. What good looks like The page's text is visible as it loads, not held behind a click or an expander. Why it matters Half or more of the page's text is present but never shown, so what readers see and what it contains diverge. What we found on this page 62% of the page's text (6664 of 10583 characters) is not visible before interaction The evidence, taken from the page as served How much of this page is hidden until something is clicked
Counted on the page once its scripts had run, before anything was clicked.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS04 | warning | the page's naming markup is faulty: 1 name label(s) point at nothing: the code that should hold the name is absent; 103 working control(s) sit inside a section the code marks as hidden, so they work on screen but are absent from what is read out | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Accessibility markup faults: invented roles, labels pointing at nothing, live controls marked hidden. What good looks like The page's accessibility markup is sound, with valid roles and no labels pointing at nothing. Why it matters The page's own description of its controls is wrong, so what it offers and what it declares do not match. What we found on this page the page's naming markup is faulty: 1 name label(s) point at nothing: the code that should hold the name is absent; 103 working control(s) sit inside a section the code marks as hidden, so they work on screen but are absent from what is read out The evidence, taken from the page as served The faulty markup, as the page serves it once loaded
<input type="checkbox" name="storage-access" id="ot-group-id-C0001-toggle" aria-expanded="false" ot-accordion="true" role="button" aria-controls="ot-desc-id-C0001" aria-labelledby="ot-header-id-C0001 ot-status-id-C0001"/> <input type="search" name="q" id="search-site" value="" class="m-site-search__input" placeholder="Enter a keyword"/> <button id="submit" type="submit" class="m-site-search__button"> Search </button> <a class="a-button a-button--primary a-button--full-width" href="/about-us/myaviva/">MyAviva</a> <a class="m-primary-navigation-sub-section__link a-button a-button--tertiary" href="/about-us/"> Explore About us </a> <a class="a-button a-button--tertiary" href="/about-us/our-purpose-and-priorities-overview/"> Our purpose and priorities overview </a> <a class="a-button a-button--tertiary" href="/about-us/our-purpose-and-priorities-overview/our-purpose-and-values/"> Our purpose and values </a> <a class="a-button a-button--tertiary" href="/about-us/our-purpose-and-priorities-overview/how-we-are-organised/"> How we're organised </a> <a class="a-button a-button--tertiary" href="/about-us/our-purpose-and-priorities-overview/helping-the-uk-get-ready/"> Helping the UK Get Ready </a> <a class="a-button a-button--tertiary" href="/about-us/our-purpose-and-priorities-overview/innovation/"> Innovation at Aviva </a> …and 94 more like it. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| DS03 | fail | an AI crawler asking for this page is refused by the security layer in front of the site, while an ordinary browser is served, so the page's content never reaches the AI and answers about it are left to memory or guesswork | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The same page loads for a browser but is refused when the request names itself as an AI service. What good looks like The page returns the same response to a named AI service as to a browser, with no edge block. Why it matters The block sits in front of the site and leaves no trace in its own logs, so the estate is closed off unnoticed. What we found on this page an AI crawler asking for this page is refused by the security layer in front of the site, while an ordinary browser is served, so the page's content never reaches the AI and answers about it are left to memory or guesswork The evidence, taken from the page as served The estate's edge tested with each AI crawler: a browser is served, the crawlers are refused
Hostwww.aviva.com · resolves to 23.215.224.114 · an Akamai edge hostname
Address trailwww.aviva.com › cert10.uk.aviva.com.ksd.edgekey.net › e5059.ksd.akamaiedge.net
Checked2026-07-31 16:33 UTC · request sent from 10.100.100.212 (our checker)
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page returns the same response to a named AI service as to a browser, with no edge block. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 5 out of a possible 5, because it is one of the checks that decide whether content can be reached and read at all, so it carries the heaviest weight in the figure for this item. Why it moves the misinformation reading This failure is a real and common route to a wrong answer for the content it affects, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT16 | warning | the page carries no structured data block stating what it is (not required; a hygiene signal) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The page carries structured data, the machine-readable summary of what it describes. What good looks like The page carries structured data summarising what it describes. Why it matters Vendors document this as optional rather than required, so its absence is a small forfeit and no more. What we found on this page the page carries no structured data block stating what it is (not required; a hygiene signal) The evidence, taken from the page as served The head of this page, as served
The page was read for a structured data block describing what the page is. <head> <title>Our locations - Aviva plc</title> <script defer="defer" type="text/javascript" src="https://rum.hlx.page/.rum/@adobe/helix-rum-js@%5E2/dist/rum-standalone.js" data-routing="env=prod,tier=publish,ams=Aviva Group"/> <link rel="preconnect" href="https://static.aviva.io/"/> <link rel="preconnect" href="https://static.aviva.io/" crossorigin="anonymous"/> <link rel="preconnect" href="https://dpm.demdex.net/"/> <link rel="preconnect" href="https://assets.adobedtm.com/"/> <link rel="preload" href="https://static.aviva.io/assets/fonts/sourcesans3-variable-roman-base.woff2" as="font" crossorigin="anonymous"/> <link rel="preload" href="https://cdn-ukwest.onetrust.com/scripttemplates/otSDKStub.js" as="script" crossorigin="anonymous"/> <link rel="preload" href="https://static.aviva.io/assets/fonts/avivacurve-regular.woff2" as="font" crossorigin="anonymous"/> <meta content="width=device-width,initial-scale=1" name="viewport"/> <meta property="templatename" content="standardpage"/> <meta property="article:published_time" content="2025-04-08T14:23:03"/> <meta property="og:description" content="We operate through businesses in the UK, Ireland and Canada. We also have international invโฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR13 | warning | the page does not mark out its main content, so what is unique to this page cannot be told apart from the menus and foot-of-page text repeated across the site | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page's main content is marked off from the navigation and footer around it. What good looks like A main or article region marks the primary content off from the navigation and footer around it. Why it matters Pulling the page's text returns menus and legal footers mixed with the substance, so the answer arrives buried in noise. What we found on this page the page does not mark out its main content, so what is unique to this page cannot be told apart from the menus and foot-of-page text repeated across the site The evidence, taken from the page as served The blocks this page marks out, as served
The page was read for the block that marks out its main content. <meta itemprop="name" content="Our locations"/> <meta itemprop="url" content="https://www.aviva.com/our-locations/"/> <div class="l-whole-page" data-back-to-top="Back to start of main content" data-component="back-to-top-es6"> <script> <span data-module="app/init-es6" data-module-load="true"/> <script id="js-init" src="https://static.aviva.io/assets/themes-managed/v6.1.0/shared/extensions/requirejs/init.js" asynโฆ <script src="https://static.aviva.io/etc.clientlibs/settings/wcm/designs/aviva-corporate/clientlibs/resources/2-20260728โฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS01 | fail | 1 of 1 boxes in the page's forms carry no name saying what each is for, so which answer belongs in which box rests on layout alone | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Each box, dropdown and text area in a form carries a name saying what it is for. What good looks like Each field in a form carries a name saying what it is for. Why it matters Unnamed fields leave the tie between a question and its box resting on layout, which shifts as the page reflows. What we found on this page 1 of 1 boxes in the page's forms carry no name saying what each is for, so which answer belongs in which box rests on layout alone The evidence, taken from the page as served The form boxes that carry no name, as served
<input type="search" name="q" id="search-site" value="" class="m-site-search__input" placeholder="Enter a keyword"/> Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: each field in a form carries a name saying what it is for. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS08 | fail | 1 link wording(s) are used for more than one destination, so the same words point at different pages: โaviva investorsโ; the links are listed in the view | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Links that share exactly the same wording on one page while pointing at different destinations. What good looks like Links that share the same wording lead to the same destination. Why it matters The wording no longer settles the target, so the wrong one gets followed at the point where the choice matters. What we found on this page 1 link wording(s) are used for more than one destination, so the same words point at different pages: โaviva investorsโ; the links are listed in the view The evidence, taken from the page as served Links that share the same text but point to different destinations, as served
<a aria-describedby="e0666154-06c8-4461-ab1d-11224bd99f9f" class="m-card__link" href="https://careers.avivainvestors.com/">Aviva Investors</a> <a aria-describedby="4c4ca16a-4290-48ff-b1d0-0bec8e92d6cb" class="m-card__link" href="https://www.avivainvestors.com/en-gb/">Aviva Investors</a> <a class="a-button a-button--tertiary a-button-icon a-button-icon--external" href="https://www.avivainvestors.com/en-gb/"> Aviva Investors </a> Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: links that share the same wording lead to the same destination. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS10 | fail | the page's first heading is not its top-level heading, so the structure starts part way down | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check A page's headings start at the top level and step down without skipping a level. What good looks like The page's headings start at the top level and step down without skipping a level. Why it matters Content under a skipped level has no clear parent section, so structure taken from the page misplaces its text. What we found on this page the page's first heading is not its top-level heading, so the structure starts part way down The evidence, taken from the page as served The page's heading outline, in document order (a jump in level is marked)
H3 Recommendation to reject "mini-tender" offers by Litani LLC level jumped H1 Our locations H2 Explore page H2 Our locations H3 UK customer website H3 Ireland customer website H3 Canada customer website - English H3 Canada customer website - French H3 China customer website H3 India customer website H2 MyAviva H2 MyAviva UK H2 MyAviva Ireland H2 MyAviva Canada H2 Jobs H3 Canada H3 China H3 India H3 Ireland H3 Poland H3 United Kingdom H3 Aviva Investors H2 Media H2 Are you a journalist? H2 Still searching? H3 Aviva Investors H3 Aviva suppliers H3 Corporate contacts H2 Login or register H2 Site navigation H3 About us H4 Our purpose and priorities H4 Our customers and people H4 Our Board and Executives H4 2025 Annual Report H4 Get support H3 Investors H4 Strategy and performance H4 Institutional investors H4 Shareholder services H4 Corporate governance H4 Risk governance and management H4 2025 Annual Report H4 Get support H3 Newsroom H4 News and research H4 Resources H4 About Aviva H4 Get support H3 Careers H4 Careers at Aviva H4 Life at Aviva H4 Diversity and inclusion H4 Get support H3 Sustainability H4 Sustainability at Aviva H4 Sustainability news H4 Sustainability resources H4 Aviva Foundation H4 Get support H4 Get support H2 Footer H3 Useful information H4 Products in our locations H4 Use MyAviva H4 How to make a complaint H3 On this site H3 Media H3 Corporate H3 Other links H3 Social H3 Legal H3 Copyright
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page's headings start at the top level and step down without skipping a level. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR03 | warning | 25% of the words a person sees are missing from the page as first delivered (7527 characters delivered, 10073 once the page finishes building itself) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check How much of the page's content exists only once JavaScript has run. What good looks like The page's content is present in the served HTML, so it does not depend on JavaScript to appear. Why it matters The page is fetched successfully but the answer is missing from what comes back, so the content is absent rather than wrong. What we found on this page 25% of the words a person sees are missing from the page as first delivered (7527 characters delivered, 10073 once the page finishes building itself) The evidence, taken from the page as served Content present only after JavaScript runs (absent from the served HTML)
The served HTML carries 7527 characters of text; after JavaScript runs the page carries 10073. 25% of the rendered page's words are absent from the HTML the server sends. What the server sends (raw HTML text, first 280 chars) Our locations - Aviva plc Skip to content Recommendation to reject "mini-tender" offers by Litani LLC We want to make you aware that a company called Litani may write, or may already have written, to you offering to buy some or all of your Aviva shares. Our warning to shareholder…
Words present only after JavaScript runs
acceptactiveadvertisementsadvertisingallowallowedalwaysapplyaroundautomaticallybackbecauseblockbrowserbuttoncannotcategorycentrechangechoiceschooseclearclosecollectconfirmconsentcorecrimecustomisedeliverdetectdevicedifferentenableenablesenhancedexampleexperiencefilesfilterfiltersfraudfunctionfunctionalfunctionalityhelpholdhowevericonimpactimproveincludesinterestkeepleastmainmarketingmostmovenecessary
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR11 | warning | 25% of the words a person sees are missing from the page as first delivered, which is 0.75 of its finished size | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The measured gap between the page as served and the page after the browser has built it. What good looks like The served page and the fully built page carry the same words, with little gap between them. Why it matters Two versions of the same page exist, and which words come back depends on which version was fetched. What we found on this page 25% of the words a person sees are missing from the page as first delivered, which is 0.75 of its finished size The evidence, taken from the page as served This page as first delivered, against the page once its scripts have run
Both were taken from the same request. The first is what the site sent; the second is what a person ends up looking at.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR12 | warning | 65% of the page's text (6622 of 10073 characters) is not visible before interaction | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check How much of the page's text is hidden behind a click or an expander before anyone interacts. What good looks like The page's text is visible as it loads, not held behind a click or an expander. Why it matters Half or more of the page's text is present but never shown, so what readers see and what it contains diverge. What we found on this page 65% of the page's text (6622 of 10073 characters) is not visible before interaction The evidence, taken from the page as served How much of this page is hidden until something is clicked
Counted on the page once its scripts had run, before anything was clicked.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS04 | warning | the page's naming markup is faulty: 1 name label(s) point at nothing: the code that should hold the name is absent; 103 working control(s) sit inside a section the code marks as hidden, so they work on screen but are absent from what is read out | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Accessibility markup faults: invented roles, labels pointing at nothing, live controls marked hidden. What good looks like The page's accessibility markup is sound, with valid roles and no labels pointing at nothing. Why it matters The page's own description of its controls is wrong, so what it offers and what it declares do not match. What we found on this page the page's naming markup is faulty: 1 name label(s) point at nothing: the code that should hold the name is absent; 103 working control(s) sit inside a section the code marks as hidden, so they work on screen but are absent from what is read out The evidence, taken from the page as served The faulty markup, as the page serves it once loaded
<input type="checkbox" name="storage-access" id="ot-group-id-C0001-toggle" aria-expanded="false" ot-accordion="true" role="button" aria-controls="ot-desc-id-C0001" aria-labelledby="ot-header-id-C0001 ot-status-id-C0001"/> <input type="search" name="q" id="search-site" value="" class="m-site-search__input" placeholder="Enter a keyword"/> <button id="submit" type="submit" class="m-site-search__button"> Search </button> <a class="a-button a-button--primary a-button--full-width" href="/about-us/myaviva/">MyAviva</a> <a class="m-primary-navigation-sub-section__link a-button a-button--tertiary" href="/about-us/"> Explore About us </a> <a class="a-button a-button--tertiary" href="/about-us/our-purpose-and-priorities-overview/"> Our purpose and priorities overview </a> <a class="a-button a-button--tertiary" href="/about-us/our-purpose-and-priorities-overview/our-purpose-and-values/"> Our purpose and values </a> <a class="a-button a-button--tertiary" href="/about-us/our-purpose-and-priorities-overview/how-we-are-organised/"> How we're organised </a> <a class="a-button a-button--tertiary" href="/about-us/our-purpose-and-priorities-overview/helping-the-uk-get-ready/"> Helping the UK Get Ready </a> <a class="a-button a-button--tertiary" href="/about-us/our-purpose-and-priorities-overview/innovation/"> Innovation at Aviva </a> …and 94 more like it. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MX02 | fail | loaded-and-settled in 10.6s (raw response 240ms): rendering adds substantial work beyond the served HTML | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check On sampled pages, how long the browser work takes before the content is finally present. What good looks like The browser finishes building the page quickly, so its content settles without a long wait. Why it matters A snapshot stores what exists at the moment it is taken, so content arriving later is stored as absent. What we found on this page loaded-and-settled in 10.6s (raw response 240ms): rendering adds substantial work beyond the served HTML The evidence, taken from the page as served How long this page took to finish building itself
Timed from the request being made to the page going quiet, in a browser, before anything was clicked.
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the browser finishes building the page quickly, so its content settles without a long wait. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT34 | fail | the page's own words are thin: 335 of its 381 words are shared navigation and footer, so it reads as 87% identical to another page, which a machine can then take as a duplicate and pass over, missing the little content that is its own; the matching page is named in the view | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether a page's own words are so few against a large shared navigation and footer that it reads as near-identical to other pages. What good looks like A page carries enough of its own words that a shared navigation and footer do not make it read as a copy of other pages. Why it matters When shared furniture is most of the text, distinct pages look like copies of each other and the little real content is easily passed over. What we found on this page the page's own words are thin: 335 of its 381 words are shared navigation and footer, so it reads as 87% identical to another page, which a machine can then take as a duplicate and pass over, missing the little content that is its own; the matching page is named in the view The evidence, taken from the page as served This page's own words, lost in shared navigation and footer
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: a page carries enough of its own words that a shared navigation and footer do not make it read as a copy of other pages. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 1 out of a possible 5, because it is one of the supporting checks, so it carries the lightest weight in the figure for this item. Why it moves the misinformation reading This failure is a real and common route to a wrong answer for the content it affects, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| DS03 | fail | an AI crawler asking for this page is refused by the security layer in front of the site, while an ordinary browser is served, so the page's content never reaches the AI and answers about it are left to memory or guesswork | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The same page loads for a browser but is refused when the request names itself as an AI service. What good looks like The page returns the same response to a named AI service as to a browser, with no edge block. Why it matters The block sits in front of the site and leaves no trace in its own logs, so the estate is closed off unnoticed. What we found on this page an AI crawler asking for this page is refused by the security layer in front of the site, while an ordinary browser is served, so the page's content never reaches the AI and answers about it are left to memory or guesswork The evidence, taken from the page as served The estate's edge tested with each AI crawler: a browser is served, the crawlers are refused
Hostwww.aviva.com · resolves to 23.215.224.114 · an Akamai edge hostname
Address trailwww.aviva.com › cert10.uk.aviva.com.ksd.edgekey.net › e5059.ksd.akamaiedge.net
Checked2026-07-31 16:33 UTC · request sent from 10.100.100.212 (our checker)
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page returns the same response to a named AI service as to a browser, with no edge block. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 5 out of a possible 5, because it is one of the checks that decide whether content can be reached and read at all, so it carries the heaviest weight in the figure for this item. Why it moves the misinformation reading This failure is a real and common route to a wrong answer for the content it affects, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT16 | warning | the page carries no structured data block stating what it is (not required; a hygiene signal) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The page carries structured data, the machine-readable summary of what it describes. What good looks like The page carries structured data summarising what it describes. Why it matters Vendors document this as optional rather than required, so its absence is a small forfeit and no more. What we found on this page the page carries no structured data block stating what it is (not required; a hygiene signal) The evidence, taken from the page as served The head of this page, as served
The page was read for a structured data block describing what the page is. <head> <title>Latest news and articles - Aviva plc</title> <script defer="defer" type="text/javascript" src="https://rum.hlx.page/.rum/@adobe/helix-rum-js@%5E2/dist/rum-standalone.js" data-routing="env=prod,tier=publish,ams=Aviva Group"/> <link rel="preconnect" href="https://static.aviva.io/"/> <link rel="preconnect" href="https://static.aviva.io/" crossorigin="anonymous"/> <link rel="preconnect" href="https://dpm.demdex.net/"/> <link rel="preconnect" href="https://assets.adobedtm.com/"/> <link rel="preload" href="https://static.aviva.io/assets/fonts/sourcesans3-variable-roman-base.woff2" as="font" crossorigin="anonymous"/> <link rel="preload" href="https://cdn-ukwest.onetrust.com/scripttemplates/otSDKStub.js" as="script" crossorigin="anonymous"/> <link rel="preload" href="https://static.aviva.io/assets/fonts/avivacurve-regular.woff2" as="font" crossorigin="anonymous"/> <meta content="width=device-width,initial-scale=1" name="viewport"/> <meta property="templatename" content="categorypage"/> <meta property="article:published_time" content="2017-10-19T09:23:30"/> <meta property="og:description" content="Explore Aviva news and research, opinions and podcasts. "/> <meta property="og:tโฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR13 | warning | the page does not mark out its main content, so what is unique to this page cannot be told apart from the menus and foot-of-page text repeated across the site | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page's main content is marked off from the navigation and footer around it. What good looks like A main or article region marks the primary content off from the navigation and footer around it. Why it matters Pulling the page's text returns menus and legal footers mixed with the substance, so the answer arrives buried in noise. What we found on this page the page does not mark out its main content, so what is unique to this page cannot be told apart from the menus and foot-of-page text repeated across the site The evidence, taken from the page as served The blocks this page marks out, as served
The page was read for the block that marks out its main content. <meta itemprop="name" content="Newsroom"/> <meta itemprop="url" content="https://www.aviva.com/newsroom/"/> <div class="l-whole-page" data-back-to-top="Back to start of main content" data-component="back-to-top-es6"> <script> <span data-module="app/init-es6" data-module-load="true"/> <script id="js-init" src="https://static.aviva.io/assets/themes-managed/v6.1.0/shared/extensions/requirejs/init.js" asynโฆ <script src="https://static.aviva.io/etc.clientlibs/settings/wcm/designs/aviva-corporate/clientlibs/resources/2-20260728โฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS01 | fail | 1 of 1 boxes in the page's forms carry no name saying what each is for, so which answer belongs in which box rests on layout alone | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Each box, dropdown and text area in a form carries a name saying what it is for. What good looks like Each field in a form carries a name saying what it is for. Why it matters Unnamed fields leave the tie between a question and its box resting on layout, which shifts as the page reflows. What we found on this page 1 of 1 boxes in the page's forms carry no name saying what each is for, so which answer belongs in which box rests on layout alone The evidence, taken from the page as served The form boxes that carry no name, as served
<input type="search" name="q" id="search-site" value="" class="m-site-search__input" placeholder="Enter a keyword"/> Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: each field in a form carries a name saying what it is for. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS10 | fail | the page's first heading is not its top-level heading, so the structure starts part way down | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check A page's headings start at the top level and step down without skipping a level. What good looks like The page's headings start at the top level and step down without skipping a level. Why it matters Content under a skipped level has no clear parent section, so structure taken from the page misplaces its text. What we found on this page the page's first heading is not its top-level heading, so the structure starts part way down The evidence, taken from the page as served The page's heading outline, in document order (a jump in level is marked)
H3 Recommendation to reject "mini-tender" offers by Litani LLC level jumped H1 Newsroom H2 Latest results and trading updates H2 Proportion of new homes built in flood areas rises to one in nine H2 Investment case and strategy H3 Media contacts H3 Photography and social media H3 Search news releases H3 Subscribe to news alerts H2 Latest news H2 Sun, sea and sickness: Stomach-related travel claims on the rise H2 Aviva expands access to Tembo mortgage support for workplace pension customers H2 The Aviva Foundation and Mencap launch financial confidence programme... H2 Aviva completes รยฃ180m full buy-in with Aston Martin Lagonda Pension Scheme H2 Aviva issues warning as value of shed theft claims increases by 9% to over รยฃ4,5 H2 Millions rely on inheritance money to fund retirement, but few have any idea how H2 Regional teams delivering brokersรขยย most valued sources of insurer support H2 Aviva and Age UK announce launch of industry-first mid-retirement MOT... H2 Retro revival: 18.8 million Brits own vintage music players H2 Aviva strengthens cyber offering to help businesses tackle evolving threat H2 Stop-motion film gives a sneak peek into the future of Aviva Arena H2 Aviva agrees to purchase remaining 26% stake in India joint venture H2 Aviva and AXIS launch new Lloydรขยยs consortium to power UK renewable energy grow H2 Aviva has successfully completed its รยฃ350m share buyback programme H2 Brits held back from investing by fears of risk and lack of financial education H2 Can't get enough? H2 Canada H2 Ireland H2 Aviva Investors H2 Facts and figures about Aviva H2 Take a look at these useful links: H3 Aviva plc Annual Report and Accounts 2025 H3 Aviva plc Business model 2025 H2 Latest features from the UK, Canada and Ireland H2 Home-makers: how investing in housing helps Britain get ready for growth H2 Getting ready for work H2 The one who stands behind the promise H2 The one who rebuilt her life H2 The one who gives an extra scoop H2 The one who hosts tea H2 The รยฃ300m Cambridge investment H2 The one who studies storms H2 The one who found balance H2 The one who came back stronger H2 A city worth investing in H2 The one who never thought sheรขยยd work for an insurer H2 The future is looking up H2 Nature isnรขยยt always a walk in the park H2 The story behind everything you own H2 "You can't teach someone to budget their way out of poverty." H2 Discover more H3 About us H3 Careers H3 Investors H2 Login or register H2 Site navigation H3 About us H4 Our purpose and priorities H4 Our customers and people H4 Our Board and Executives H4 2025 Annual Report H4 Get support H3 Investors H4 Strategy and performance H4 Institutional investors H4 Shareholder services H4 Corporate governance H4 Risk governance and management H4 2025 Annual Report H4 Get support H3 Newsroom H4 News and research H4 Resources H4 About Aviva H4 Get support H3 Careers H4 Careers at Aviva H4 Life at Aviva H4 Diversity and inclusion H4 Get support H3 Sustainability H4 Sustainability at Aviva H4 Sustainability news H4 Sustainability resources H4 Aviva Foundation H4 Get support H4 Get support H2 Footer H3 Useful information H4 Products in our locations H4 Use MyAviva H4 How to make a complaint H3 On this site H3 Media H3 Corporate H3 Other links H3 Social H3 Legal H3 Copyright
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page's headings start at the top level and step down without skipping a level. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR03 | warning | 12% of the words a person sees are missing from the page as first delivered (14815 characters delivered, 17361 once the page finishes building itself) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check How much of the page's content exists only once JavaScript has run. What good looks like The page's content is present in the served HTML, so it does not depend on JavaScript to appear. Why it matters The page is fetched successfully but the answer is missing from what comes back, so the content is absent rather than wrong. What we found on this page 12% of the words a person sees are missing from the page as first delivered (14815 characters delivered, 17361 once the page finishes building itself) The evidence, taken from the page as served Content present only after JavaScript runs (absent from the served HTML)
The served HTML carries 14815 characters of text; after JavaScript runs the page carries 17361. 12% of the rendered page's words are absent from the HTML the server sends. What the server sends (raw HTML text, first 280 chars) Latest news and articles - Aviva plc Skip to content Recommendation to reject "mini-tender" offers by Litani LLC We want to make you aware that a company called Litani may write, or may already have written, to you offering to buy some or all of your Aviva shares. Our warning to …
Words present only after JavaScript runs
acceptactiveadvertisementsadvertisingallowallowedapplyautomaticallybelowblockbrowserbuttoncannotcategorychangechoiceschooseclearclosecollectconfirmconsentcorecrimecustomisedeliverdetectdevicedifferentenablesenhancedexampleexperiencefilesfilterfiltersfraudfunctionfunctionalfunctionalityholdhowevericonimpactimproveincludesinterestleastmainmarketingmovenecessaryoptionalpersonalisationpersonalisedplacedpleasepopularpreferencepreferences
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR11 | warning | 12% of the words a person sees are missing from the page as first delivered, which is 0.85 of its finished size | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The measured gap between the page as served and the page after the browser has built it. What good looks like The served page and the fully built page carry the same words, with little gap between them. Why it matters Two versions of the same page exist, and which words come back depends on which version was fetched. What we found on this page 12% of the words a person sees are missing from the page as first delivered, which is 0.85 of its finished size The evidence, taken from the page as served This page as first delivered, against the page once its scripts have run
Both were taken from the same request. The first is what the site sent; the second is what a person ends up looking at.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS04 | warning | the page's naming markup is faulty: 1 name label(s) point at nothing: the code that should hold the name is absent; 103 working control(s) sit inside a section the code marks as hidden, so they work on screen but are absent from what is read out | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Accessibility markup faults: invented roles, labels pointing at nothing, live controls marked hidden. What good looks like The page's accessibility markup is sound, with valid roles and no labels pointing at nothing. Why it matters The page's own description of its controls is wrong, so what it offers and what it declares do not match. What we found on this page the page's naming markup is faulty: 1 name label(s) point at nothing: the code that should hold the name is absent; 103 working control(s) sit inside a section the code marks as hidden, so they work on screen but are absent from what is read out The evidence, taken from the page as served The faulty markup, as the page serves it once loaded
<input type="checkbox" name="storage-access" id="ot-group-id-C0001-toggle" aria-expanded="false" ot-accordion="true" role="button" aria-controls="ot-desc-id-C0001" aria-labelledby="ot-header-id-C0001 ot-status-id-C0001" data-di-id="#ot-group-id-C0001-toggle"/> <input type="search" name="q" id="search-site" value="" class="m-site-search__input" placeholder="Enter a keyword" data-di-id="#search-site"/> <button id="submit" type="submit" class="m-site-search__button" data-di-id="#submit"> Search </button> <a class="a-button a-button--primary a-button--full-width" href="/about-us/myaviva/" data-di-id="di-id-71c90199-ed344a8f">MyAviva</a> <a class="m-primary-navigation-sub-section__link a-button a-button--tertiary" href="/about-us/" data-di-id="di-id-cf5feb21-eef86a21"> Explore About us </a> <a class="a-button a-button--tertiary" href="/about-us/our-purpose-and-priorities-overview/" data-di-id="di-id-aa477673-93b5857e"> Our purpose and priorities overview </a> <a class="a-button a-button--tertiary" href="/about-us/our-purpose-and-priorities-overview/our-purpose-and-values/" data-di-id="di-id-15b2a4dd-aa1d300a"> Our purpose and values </a> <a class="a-button a-button--tertiary" href="/about-us/our-purpose-and-priorities-overview/how-we-are-organised/" data-di-id="di-id-67e3e41a-daf2e78f"> How we're organised </a> <a class="a-button a-button--tertiary" href="/about-us/our-purpose-and-priorities-overview/helping-the-uk-get-ready/" data-di-id="di-id-f6a3fe8f-83d3cbef"> Helping the UK Get Ready </a> <a class="a-button a-button--tertiary" href="/about-us/our-purpose-and-priorities-overview/innovation/" data-di-id="di-id-53582fa2-adddfcac"> Innovation at Aviva </a> …and 94 more like it. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AJ08 | warning | focus order: the first 12 Tab stops do not follow document order | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether pressing Tab moves through the page in the order its content is written. What good looks like Pressing Tab moves through the page in the order its content is written. Why it matters The keyboard jumps around the page out of sequence, so a form is worked through in an order nobody intended. What we found on this page focus order: the first 12 Tab stops do not follow document order The evidence, taken from the page as served How the keyboard moves through this page
Read on the page once its scripts had run, following the keyboard from the top.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MX02 | fail | loaded-and-settled in 10.9s (raw response 221ms): rendering adds substantial work beyond the served HTML | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check On sampled pages, how long the browser work takes before the content is finally present. What good looks like The browser finishes building the page quickly, so its content settles without a long wait. Why it matters A snapshot stores what exists at the moment it is taken, so content arriving later is stored as absent. What we found on this page loaded-and-settled in 10.9s (raw response 221ms): rendering adds substantial work beyond the served HTML The evidence, taken from the page as served How long this page took to finish building itself
Timed from the request being made to the page going quiet, in a browser, before anything was clicked.
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the browser finishes building the page quickly, so its content settles without a long wait. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| DS03 | fail | an AI crawler asking for this page is refused by the security layer in front of the site, while an ordinary browser is served, so the page's content never reaches the AI and answers about it are left to memory or guesswork | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The same page loads for a browser but is refused when the request names itself as an AI service. What good looks like The page returns the same response to a named AI service as to a browser, with no edge block. Why it matters The block sits in front of the site and leaves no trace in its own logs, so the estate is closed off unnoticed. What we found on this page an AI crawler asking for this page is refused by the security layer in front of the site, while an ordinary browser is served, so the page's content never reaches the AI and answers about it are left to memory or guesswork The evidence, taken from the page as served The estate's edge tested with each AI crawler: a browser is served, the crawlers are refused
Hostwww.aviva.com · resolves to 23.215.224.114 · an Akamai edge hostname
Address trailwww.aviva.com › cert10.uk.aviva.com.ksd.edgekey.net › e5059.ksd.akamaiedge.net
Checked2026-07-31 16:33 UTC · request sent from 10.100.100.212 (our checker)
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page returns the same response to a named AI service as to a browser, with no edge block. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 5 out of a possible 5, because it is one of the checks that decide whether content can be reached and read at all, so it carries the heaviest weight in the figure for this item. Why it moves the misinformation reading This failure is a real and common route to a wrong answer for the content it affects, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT16 | warning | the page carries no structured data block stating what it is (not required; a hygiene signal) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The page carries structured data, the machine-readable summary of what it describes. What good looks like The page carries structured data summarising what it describes. Why it matters Vendors document this as optional rather than required, so its absence is a small forfeit and no more. What we found on this page the page carries no structured data block stating what it is (not required; a hygiene signal) The evidence, taken from the page as served The head of this page, as served
The page was read for a structured data block describing what the page is. <head> <title>About Us - Aviva plc</title> <script defer="defer" type="text/javascript" src="https://rum.hlx.page/.rum/@adobe/helix-rum-js@%5E2/dist/rum-standalone.js" data-routing="env=prod,tier=publish,ams=Aviva Group"/> <link rel="preconnect" href="https://static.aviva.io/"/> <link rel="preconnect" href="https://static.aviva.io/" crossorigin="anonymous"/> <link rel="preconnect" href="https://dpm.demdex.net/"/> <link rel="preconnect" href="https://assets.adobedtm.com/"/> <link rel="preload" href="https://static.aviva.io/assets/fonts/sourcesans3-variable-roman-base.woff2" as="font" crossorigin="anonymous"/> <link rel="preload" href="https://cdn-ukwest.onetrust.com/scripttemplates/otSDKStub.js" as="script" crossorigin="anonymous"/> <link rel="preload" href="https://static.aviva.io/assets/fonts/avivacurve-regular.woff2" as="font" crossorigin="anonymous"/> <meta content="width=device-width,initial-scale=1" name="viewport"/> <meta property="templatename" content="categorypage"/> <meta property="article:published_time" content="2019-03-07T07:00:00"/> <meta property="og:description" content="Serving customers in insurance, wealth and retirement."/> <meta property="og:title" content="Aboโฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR13 | warning | the page does not mark out its main content, so what is unique to this page cannot be told apart from the menus and foot-of-page text repeated across the site | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page's main content is marked off from the navigation and footer around it. What good looks like A main or article region marks the primary content off from the navigation and footer around it. Why it matters Pulling the page's text returns menus and legal footers mixed with the substance, so the answer arrives buried in noise. What we found on this page the page does not mark out its main content, so what is unique to this page cannot be told apart from the menus and foot-of-page text repeated across the site The evidence, taken from the page as served The blocks this page marks out, as served
The page was read for the block that marks out its main content. <meta itemprop="name" content="About Us"/> <meta itemprop="url" content="https://www.aviva.com/about-us/"/> <div class="l-whole-page" data-back-to-top="Back to start of main content" data-component="back-to-top-es6"> <script> <span data-module="app/init-es6" data-module-load="true"/> <script id="js-init" src="https://static.aviva.io/assets/themes-managed/v6.1.0/shared/extensions/requirejs/init.js" asynโฆ <script src="https://static.aviva.io/etc.clientlibs/settings/wcm/designs/aviva-corporate/clientlibs/resources/2-20260728โฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS01 | fail | 1 of 1 boxes in the page's forms carry no name saying what each is for, so which answer belongs in which box rests on layout alone | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Each box, dropdown and text area in a form carries a name saying what it is for. What good looks like Each field in a form carries a name saying what it is for. Why it matters Unnamed fields leave the tie between a question and its box resting on layout, which shifts as the page reflows. What we found on this page 1 of 1 boxes in the page's forms carry no name saying what each is for, so which answer belongs in which box rests on layout alone The evidence, taken from the page as served The form boxes that carry no name, as served
<input type="search" name="q" id="search-site" value="" class="m-site-search__input" placeholder="Enter a keyword"/> Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: each field in a form carries a name saying what it is for. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS08 | fail | 1 link wording(s) are used for more than one destination, so the same words point at different pages: โgroup executive committeeโ; the links are listed in the view | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Links that share exactly the same wording on one page while pointing at different destinations. What good looks like Links that share the same wording lead to the same destination. Why it matters The wording no longer settles the target, so the wrong one gets followed at the point where the choice matters. What we found on this page 1 link wording(s) are used for more than one destination, so the same words point at different pages: โgroup executive committeeโ; the links are listed in the view The evidence, taken from the page as served Links that share the same text but point to different destinations, as served
<a aria-describedby="1608c05b-7b6e-4e98-a7bc-48eb077c7095" class="m-card__link" href="/about-us/our-board-and-executives-overview/our-group-executive-committee/">Group Executive Committee</a> <a href="https://www.aviva.com/about-us/our-group-executive-committee/" title="Go to our Group Executive Committee page">Group Executive Committee</a> Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: links that share the same wording lead to the same destination. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS10 | fail | the page's first heading is not its top-level heading, so the structure starts part way down | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check A page's headings start at the top level and step down without skipping a level. What good looks like The page's headings start at the top level and step down without skipping a level. Why it matters Content under a skipped level has no clear parent section, so structure taken from the page misplaces its text. What we found on this page the page's first heading is not its top-level heading, so the structure starts part way down The evidence, taken from the page as served The page's heading outline, in document order (a jump in level is marked)
H3 Recommendation to reject "mini-tender" offers by Litani LLC level jumped H1 About us H2 Our purpose and values H2 Our customers H2 Our people H3 Investment case and strategy H3 Group Executive Committee H3 Our products and services H3 Job search H2 Aviva at a glance H3 About Aviva H3 Latest news H3 Latest results H2 Our Annual Report 2025 H2 Annual Report and Accounts 2025 H2 Helping the UK Get Ready H2 How are we helping the UK Get Ready for the future? H2 Our sustainability ambition H2 Building a more sustainable future H2 Get to know us H2 How we're organised H2 Our heritage H2 Our Board H2 Diversity, equity and inclusion H2 Growing with impact H3 Innovation at Aviva H3 Aviva Capital Partners H3 Acting for a better tomorrow H3 Our venues H2 Discover more H3 Newsroom H3 Investors H3 Careers H3 Sustainability H2 Login or register H2 Site navigation H3 About us H4 Our purpose and priorities H4 Our customers and people H4 Our Board and Executives H4 2025 Annual Report H4 Get support H3 Investors H4 Strategy and performance H4 Institutional investors H4 Shareholder services H4 Corporate governance H4 Risk governance and management H4 2025 Annual Report H4 Get support H3 Newsroom H4 News and research H4 Resources H4 About Aviva H4 Get support H3 Careers H4 Careers at Aviva H4 Life at Aviva H4 Diversity and inclusion H4 Get support H3 Sustainability H4 Sustainability at Aviva H4 Sustainability news H4 Sustainability resources H4 Aviva Foundation H4 Get support H4 Get support H2 Footer H3 Useful information H4 Products in our locations H4 Use MyAviva H4 How to make a complaint H3 On this site H3 Media H3 Corporate H3 Other links H3 Social H3 Legal H3 Copyright
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page's headings start at the top level and step down without skipping a level. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR03 | warning | 18% of the words a person sees are missing from the page as first delivered (11683 characters delivered, 14432 once the page finishes building itself) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check How much of the page's content exists only once JavaScript has run. What good looks like The page's content is present in the served HTML, so it does not depend on JavaScript to appear. Why it matters The page is fetched successfully but the answer is missing from what comes back, so the content is absent rather than wrong. What we found on this page 18% of the words a person sees are missing from the page as first delivered (11683 characters delivered, 14432 once the page finishes building itself) The evidence, taken from the page as served Content present only after JavaScript runs (absent from the served HTML)
The served HTML carries 11683 characters of text; after JavaScript runs the page carries 14432. 18% of the rendered page's words are absent from the HTML the server sends. What the server sends (raw HTML text, first 280 chars) About Us - Aviva plc Skip to content Recommendation to reject "mini-tender" offers by Litani LLC We want to make you aware that a company called Litani may write, or may already have written, to you offering to buy some or all of your Aviva shares. Our warning to shareholders pag…
Words present only after JavaScript runs
acceptactiveadvertisementsadvertisingallowallowedalwaysapplyautomaticallybackbecausebelowblockbrowserbuttoncannotcategorycentrechangechoiceschooseclearclosecollectconfirmconsentcrimecustomisedetectdevicedismissenableenablesenhancedescapeexampleexperiencefilesfilterfiltersfraudfunctionfunctionalfunctionalityhowevericonimproveincludesinterestinvitationkeepleastlovemainmarketingminutemovenecessaryopensoptional
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR11 | warning | 18% of the words a person sees are missing from the page as first delivered, which is 0.81 of its finished size | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The measured gap between the page as served and the page after the browser has built it. What good looks like The served page and the fully built page carry the same words, with little gap between them. Why it matters Two versions of the same page exist, and which words come back depends on which version was fetched. What we found on this page 18% of the words a person sees are missing from the page as first delivered, which is 0.81 of its finished size The evidence, taken from the page as served This page as first delivered, against the page once its scripts have run
Both were taken from the same request. The first is what the site sent; the second is what a person ends up looking at.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS04 | warning | the page's naming markup is faulty: 1 name label(s) point at nothing: the code that should hold the name is absent; 103 working control(s) sit inside a section the code marks as hidden, so they work on screen but are absent from what is read out | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Accessibility markup faults: invented roles, labels pointing at nothing, live controls marked hidden. What good looks like The page's accessibility markup is sound, with valid roles and no labels pointing at nothing. Why it matters The page's own description of its controls is wrong, so what it offers and what it declares do not match. What we found on this page the page's naming markup is faulty: 1 name label(s) point at nothing: the code that should hold the name is absent; 103 working control(s) sit inside a section the code marks as hidden, so they work on screen but are absent from what is read out The evidence, taken from the page as served The faulty markup, as the page serves it once loaded
<input type="checkbox" name="storage-access" id="ot-group-id-C0001-toggle" aria-expanded="false" ot-accordion="true" role="button" aria-controls="ot-desc-id-C0001" aria-labelledby="ot-header-id-C0001 ot-status-id-C0001"/> <input type="search" name="q" id="search-site" value="" class="m-site-search__input" placeholder="Enter a keyword"/> <button id="submit" type="submit" class="m-site-search__button"> Search </button> <a class="a-button a-button--primary a-button--full-width" href="/about-us/myaviva/">MyAviva</a> <a class="m-primary-navigation-sub-section__link a-button a-button--tertiary" href="/about-us/"> Explore About us </a> <a class="a-button a-button--tertiary" href="/about-us/our-purpose-and-priorities-overview/"> Our purpose and priorities overview </a> <a class="a-button a-button--tertiary" href="/about-us/our-purpose-and-priorities-overview/our-purpose-and-values/"> Our purpose and values </a> <a class="a-button a-button--tertiary" href="/about-us/our-purpose-and-priorities-overview/how-we-are-organised/"> How we're organised </a> <a class="a-button a-button--tertiary" href="/about-us/our-purpose-and-priorities-overview/helping-the-uk-get-ready/"> Helping the UK Get Ready </a> <a class="a-button a-button--tertiary" href="/about-us/our-purpose-and-priorities-overview/innovation/"> Innovation at Aviva </a> …and 94 more like it. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AJ08 | warning | focus order: the first 12 Tab stops do not follow document order | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether pressing Tab moves through the page in the order its content is written. What good looks like Pressing Tab moves through the page in the order its content is written. Why it matters The keyboard jumps around the page out of sequence, so a form is worked through in an order nobody intended. What we found on this page focus order: the first 12 Tab stops do not follow document order The evidence, taken from the page as served How the keyboard moves through this page
Read on the page once its scripts had run, following the keyboard from the top.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MX02 | fail | loaded-and-settled in 11.3s (raw response 217ms): rendering adds substantial work beyond the served HTML | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check On sampled pages, how long the browser work takes before the content is finally present. What good looks like The browser finishes building the page quickly, so its content settles without a long wait. Why it matters A snapshot stores what exists at the moment it is taken, so content arriving later is stored as absent. What we found on this page loaded-and-settled in 11.3s (raw response 217ms): rendering adds substantial work beyond the served HTML The evidence, taken from the page as served How long this page took to finish building itself
Timed from the request being made to the page going quiet, in a browser, before anything was clicked.
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the browser finishes building the page quickly, so its content settles without a long wait. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| DS03 | fail | an AI crawler asking for this page is refused by the security layer in front of the site, while an ordinary browser is served, so the page's content never reaches the AI and answers about it are left to memory or guesswork | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The same page loads for a browser but is refused when the request names itself as an AI service. What good looks like The page returns the same response to a named AI service as to a browser, with no edge block. Why it matters The block sits in front of the site and leaves no trace in its own logs, so the estate is closed off unnoticed. What we found on this page an AI crawler asking for this page is refused by the security layer in front of the site, while an ordinary browser is served, so the page's content never reaches the AI and answers about it are left to memory or guesswork The evidence, taken from the page as served The estate's edge tested with each AI crawler: a browser is served, the crawlers are refused
Hostwww.aviva.com · resolves to 23.215.224.114 · an Akamai edge hostname
Address trailwww.aviva.com › cert10.uk.aviva.com.ksd.edgekey.net › e5059.ksd.akamaiedge.net
Checked2026-07-31 16:33 UTC · request sent from 10.100.100.212 (our checker)
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page returns the same response to a named AI service as to a browser, with no edge block. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 5 out of a possible 5, because it is one of the checks that decide whether content can be reached and read at all, so it carries the heaviest weight in the figure for this item. Why it moves the misinformation reading This failure is a real and common route to a wrong answer for the content it affects, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT32 | warning | length 35 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The meta description's length is usable, between 50 and 170 characters. What good looks like The meta description's length is usable, long enough to say something and short enough not to be cut. Why it matters Too short says nothing and too long gets cut, so the summary field is spent without doing its job. What we found on this page length 35 The evidence, taken from the page as served The page's description, as served
<meta name="description" content="Become our newest email subscriber."/> | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT09 | fail | 1 skipped heading level(s) in document order | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Heading levels step down one at a time, rather than jumping from an H2 straight to an H5. What good looks like Heading levels step down one at a time, without jumping a level. Why it matters A skipped level breaks the trail that says which section a passage belongs to, so it is filed under the wrong one. What we found on this page 1 skipped heading level(s) in document order The evidence, taken from the page as served The page's heading outline, in document order (a jump in level is marked)
H3 Recommendation to reject "mini-tender" offers by Litani LLC H1 Latest news and updates by email H3 Subscribe to all or choose just what interests you. level jumped H2 Login or register H2 Site navigation H3 About us H4 Our purpose and priorities H4 Our customers and people H4 Our Board and Executives H4 2025 Annual Report H4 Get support H3 Investors H4 Strategy and performance H4 Institutional investors H4 Shareholder services H4 Corporate governance H4 Risk governance and management H4 2025 Annual Report H4 Get support H3 Newsroom H4 News and research H4 Resources H4 About Aviva H4 Get support H3 Careers H4 Careers at Aviva H4 Life at Aviva H4 Diversity and inclusion H4 Get support H3 Sustainability H4 Sustainability at Aviva H4 Sustainability news H4 Sustainability resources H4 Aviva Foundation H4 Get support H4 Get support H2 Footer H3 Useful information H4 Products in our locations H4 Use MyAviva H4 How to make a complaint H3 On this site H3 Media H3 Corporate H3 Other links H3 Social H3 Legal H3 Copyright
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: heading levels step down one at a time, without jumping a level. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT16 | warning | the page carries no structured data block stating what it is (not required; a hygiene signal) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The page carries structured data, the machine-readable summary of what it describes. What good looks like The page carries structured data summarising what it describes. Why it matters Vendors document this as optional rather than required, so its absence is a small forfeit and no more. What we found on this page the page carries no structured data block stating what it is (not required; a hygiene signal) The evidence, taken from the page as served The head of this page, as served
The page was read for a structured data block describing what the page is. <head> <title>Get news alerts - Aviva plc</title> <script defer="defer" type="text/javascript" src="https://rum.hlx.page/.rum/@adobe/helix-rum-js@%5E2/dist/rum-standalone.js" data-routing="env=prod,tier=publish,ams=Aviva Group"/> <link rel="preconnect" href="https://static.aviva.io/"/> <link rel="preconnect" href="https://static.aviva.io/" crossorigin="anonymous"/> <link rel="preconnect" href="https://dpm.demdex.net/"/> <link rel="preconnect" href="https://assets.adobedtm.com/"/> <link rel="preload" href="https://static.aviva.io/assets/fonts/sourcesans3-variable-roman-base.woff2" as="font" crossorigin="anonymous"/> <link rel="preload" href="https://cdn-ukwest.onetrust.com/scripttemplates/otSDKStub.js" as="script" crossorigin="anonymous"/> <link rel="preload" href="https://static.aviva.io/assets/fonts/avivacurve-regular.woff2" as="font" crossorigin="anonymous"/> <meta content="width=device-width,initial-scale=1" name="viewport"/> <meta property="templatename" content="standardpage"/> <meta property="article:published_time" content="2019-08-23T10:49:52"/> <meta property="og:description" content="Become our newest email subscriber."/> <meta property="og:title" content="Latest news andโฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR13 | warning | the page does not mark out its main content, so what is unique to this page cannot be told apart from the menus and foot-of-page text repeated across the site | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page's main content is marked off from the navigation and footer around it. What good looks like A main or article region marks the primary content off from the navigation and footer around it. Why it matters Pulling the page's text returns menus and legal footers mixed with the substance, so the answer arrives buried in noise. What we found on this page the page does not mark out its main content, so what is unique to this page cannot be told apart from the menus and foot-of-page text repeated across the site The evidence, taken from the page as served The blocks this page marks out, as served
The page was read for the block that marks out its main content. <meta itemprop="name" content="Get news alerts"/> <meta itemprop="url" content="https://www.aviva.com/newsroom/resources-overview/get-our-latest-news-and-updates-by-emailโฆ <div class="l-whole-page" data-back-to-top="Back to start of main content" data-component="back-to-top-es6"> <script> <span data-module="app/init-es6" data-module-load="true"/> <script id="js-init" src="https://static.aviva.io/assets/themes-managed/v6.1.0/shared/extensions/requirejs/init.js" asynโฆ <script src="https://static.aviva.io/etc.clientlibs/settings/wcm/designs/aviva-corporate/clientlibs/resources/2-20260728โฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS01 | fail | 1 of 1 boxes in the page's forms carry no name saying what each is for, so which answer belongs in which box rests on layout alone | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Each box, dropdown and text area in a form carries a name saying what it is for. What good looks like Each field in a form carries a name saying what it is for. Why it matters Unnamed fields leave the tie between a question and its box resting on layout, which shifts as the page reflows. What we found on this page 1 of 1 boxes in the page's forms carry no name saying what each is for, so which answer belongs in which box rests on layout alone The evidence, taken from the page as served The form boxes that carry no name, as served
<input type="search" name="q" id="search-site" value="" class="m-site-search__input" placeholder="Enter a keyword"/> Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: each field in a form carries a name saying what it is for. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS08 | fail | 2 link wording(s) are used for more than one destination, so the same words point at different pages: โprivacy policyโ, โuk customer data charterโ; the links are listed in the view | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Links that share exactly the same wording on one page while pointing at different destinations. What good looks like Links that share the same wording lead to the same destination. Why it matters The wording no longer settles the target, so the wrong one gets followed at the point where the choice matters. What we found on this page 2 link wording(s) are used for more than one destination, so the same words point at different pages: โprivacy policyโ, โuk customer data charterโ; the links are listed in the view The evidence, taken from the page as served Links that share the same text but point to different destinations, as served
<a href="https://www.aviva.co.uk/services-and-support/about-our-business/products-and-services/privacy-policy/">privacy policy</a> <a href="https://www.aviva.co.uk/services-and-support/about-our-business/products-and-services/privacy-policy/">privacy policy</a> <a href="https://www.aviva.co.uk/services-and-support/about-our-business/about-us/customer-data-charter/">UK Customer Data Charter</a> <a class="a-button a-button--tertiary a-button-icon a-button-icon--external" href="https://www.aviva.co.uk/services/about-our-business/about-us/customer-data-charter/"> UK Customer Data Charter </a> <a class="a-button a-button--tertiary" href="https://www.aviva.co.uk/services/about-our-business/products-and-services/privacy-policy/"> Privacy policy </a> Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: links that share the same wording lead to the same destination. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS10 | fail | the page's first heading is not its top-level heading, so the structure starts part way down; the heading structure skips a level in 1 place(s), so the order does not follow | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check A page's headings start at the top level and step down without skipping a level. What good looks like The page's headings start at the top level and step down without skipping a level. Why it matters Content under a skipped level has no clear parent section, so structure taken from the page misplaces its text. What we found on this page the page's first heading is not its top-level heading, so the structure starts part way down; the heading structure skips a level in 1 place(s), so the order does not follow The evidence, taken from the page as served The page's heading outline, in document order (a jump in level is marked)
H3 Recommendation to reject "mini-tender" offers by Litani LLC level jumped H1 Latest news and updates by email H3 Subscribe to all or choose just what interests you. level jumped H2 Login or register H2 Site navigation H3 About us H4 Our purpose and priorities H4 Our customers and people H4 Our Board and Executives H4 2025 Annual Report H4 Get support H3 Investors H4 Strategy and performance H4 Institutional investors H4 Shareholder services H4 Corporate governance H4 Risk governance and management H4 2025 Annual Report H4 Get support H3 Newsroom H4 News and research H4 Resources H4 About Aviva H4 Get support H3 Careers H4 Careers at Aviva H4 Life at Aviva H4 Diversity and inclusion H4 Get support H3 Sustainability H4 Sustainability at Aviva H4 Sustainability news H4 Sustainability resources H4 Aviva Foundation H4 Get support H4 Get support H2 Footer H3 Useful information H4 Products in our locations H4 Use MyAviva H4 How to make a complaint H3 On this site H3 Media H3 Corporate H3 Other links H3 Social H3 Legal H3 Copyright
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page's headings start at the top level and step down without skipping a level. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR03 | warning | 27% of the words a person sees are missing from the page as first delivered (6148 characters delivered, 8694 once the page finishes building itself) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check How much of the page's content exists only once JavaScript has run. What good looks like The page's content is present in the served HTML, so it does not depend on JavaScript to appear. Why it matters The page is fetched successfully but the answer is missing from what comes back, so the content is absent rather than wrong. What we found on this page 27% of the words a person sees are missing from the page as first delivered (6148 characters delivered, 8694 once the page finishes building itself) The evidence, taken from the page as served Content present only after JavaScript runs (absent from the served HTML)
The served HTML carries 6148 characters of text; after JavaScript runs the page carries 8694. 27% of the rendered page's words are absent from the HTML the server sends. What the server sends (raw HTML text, first 280 chars) Get news alerts - Aviva plc Skip to content Recommendation to reject "mini-tender" offers by Litani LLC We want to make you aware that a company called Litani may write, or may already have written, to you offering to buy some or all of your Aviva shares. Our warning to sharehold…
Words present only after JavaScript runs
acceptactiveadvertisementsadvertisingallowallowedalwaysapplyaroundautomaticallybackbecausebelowblockbrowserbuttoncannotcategorycentrechangechoicesclearclosecollectconfirmconsentcorecrimecustomisedeliverdetectdevicedifferentenableenablesenhancedexampleexperiencefilesfilterfiltersfraudfunctionfunctionalfunctionalityhelpholdhowevericonimpactimproveincludesinterestkeepleastmainmarketingmostmovenecessary
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR11 | warning | 27% of the words a person sees are missing from the page as first delivered, which is 0.71 of its finished size | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The measured gap between the page as served and the page after the browser has built it. What good looks like The served page and the fully built page carry the same words, with little gap between them. Why it matters Two versions of the same page exist, and which words come back depends on which version was fetched. What we found on this page 27% of the words a person sees are missing from the page as first delivered, which is 0.71 of its finished size The evidence, taken from the page as served This page as first delivered, against the page once its scripts have run
Both were taken from the same request. The first is what the site sent; the second is what a person ends up looking at.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR12 | warning | 76% of the page's text (6625 of 8694 characters) is not visible before interaction | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check How much of the page's text is hidden behind a click or an expander before anyone interacts. What good looks like The page's text is visible as it loads, not held behind a click or an expander. Why it matters Half or more of the page's text is present but never shown, so what readers see and what it contains diverge. What we found on this page 76% of the page's text (6625 of 8694 characters) is not visible before interaction The evidence, taken from the page as served How much of this page is hidden until something is clicked
Counted on the page once its scripts had run, before anything was clicked.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS04 | warning | the page's naming markup is faulty: 1 name label(s) point at nothing: the code that should hold the name is absent; 103 working control(s) sit inside a section the code marks as hidden, so they work on screen but are absent from what is read out | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Accessibility markup faults: invented roles, labels pointing at nothing, live controls marked hidden. What good looks like The page's accessibility markup is sound, with valid roles and no labels pointing at nothing. Why it matters The page's own description of its controls is wrong, so what it offers and what it declares do not match. What we found on this page the page's naming markup is faulty: 1 name label(s) point at nothing: the code that should hold the name is absent; 103 working control(s) sit inside a section the code marks as hidden, so they work on screen but are absent from what is read out The evidence, taken from the page as served The faulty markup, as the page serves it once loaded
<input type="checkbox" name="storage-access" id="ot-group-id-C0001-toggle" aria-expanded="false" ot-accordion="true" role="button" aria-controls="ot-desc-id-C0001" aria-labelledby="ot-header-id-C0001 ot-status-id-C0001"/> <input type="search" name="q" id="search-site" value="" class="m-site-search__input" placeholder="Enter a keyword"/> <button id="submit" type="submit" class="m-site-search__button"> Search </button> <a class="a-button a-button--primary a-button--full-width" href="/about-us/myaviva/">MyAviva</a> <a class="m-primary-navigation-sub-section__link a-button a-button--tertiary" href="/about-us/"> Explore About us </a> <a class="a-button a-button--tertiary" href="/about-us/our-purpose-and-priorities-overview/"> Our purpose and priorities overview </a> <a class="a-button a-button--tertiary" href="/about-us/our-purpose-and-priorities-overview/our-purpose-and-values/"> Our purpose and values </a> <a class="a-button a-button--tertiary" href="/about-us/our-purpose-and-priorities-overview/how-we-are-organised/"> How we're organised </a> <a class="a-button a-button--tertiary" href="/about-us/our-purpose-and-priorities-overview/helping-the-uk-get-ready/"> Helping the UK Get Ready </a> <a class="a-button a-button--tertiary" href="/about-us/our-purpose-and-priorities-overview/innovation/"> Innovation at Aviva </a> …and 94 more like it. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MX02 | fail | loaded-and-settled in 12.7s (raw response 211ms): rendering adds substantial work beyond the served HTML | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check On sampled pages, how long the browser work takes before the content is finally present. What good looks like The browser finishes building the page quickly, so its content settles without a long wait. Why it matters A snapshot stores what exists at the moment it is taken, so content arriving later is stored as absent. What we found on this page loaded-and-settled in 12.7s (raw response 211ms): rendering adds substantial work beyond the served HTML The evidence, taken from the page as served How long this page took to finish building itself
Timed from the request being made to the page going quiet, in a browser, before anything was clicked.
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the browser finishes building the page quickly, so its content settles without a long wait. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT34 | fail | the page's own words are thin: 336 of its 365 words are shared navigation and footer, so it reads as 90% identical to another page, which a machine can then take as a duplicate and pass over, missing the little content that is its own; the matching page is named in the view | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether a page's own words are so few against a large shared navigation and footer that it reads as near-identical to other pages. What good looks like A page carries enough of its own words that a shared navigation and footer do not make it read as a copy of other pages. Why it matters When shared furniture is most of the text, distinct pages look like copies of each other and the little real content is easily passed over. What we found on this page the page's own words are thin: 336 of its 365 words are shared navigation and footer, so it reads as 90% identical to another page, which a machine can then take as a duplicate and pass over, missing the little content that is its own; the matching page is named in the view The evidence, taken from the page as served This page's own words, lost in shared navigation and footer
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: a page carries enough of its own words that a shared navigation and footer do not make it read as a copy of other pages. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 1 out of a possible 5, because it is one of the supporting checks, so it carries the lightest weight in the figure for this item. Why it moves the misinformation reading This failure is a real and common route to a wrong answer for the content it affects, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| DS03 | fail | an AI crawler asking for this page is refused by the security layer in front of the site, while an ordinary browser is served, so the page's content never reaches the AI and answers about it are left to memory or guesswork | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The same page loads for a browser but is refused when the request names itself as an AI service. What good looks like The page returns the same response to a named AI service as to a browser, with no edge block. Why it matters The block sits in front of the site and leaves no trace in its own logs, so the estate is closed off unnoticed. What we found on this page an AI crawler asking for this page is refused by the security layer in front of the site, while an ordinary browser is served, so the page's content never reaches the AI and answers about it are left to memory or guesswork The evidence, taken from the page as served The estate's edge tested with each AI crawler: a browser is served, the crawlers are refused
Hostwww.aviva.com · resolves to 23.215.224.114 · an Akamai edge hostname
Address trailwww.aviva.com › cert10.uk.aviva.com.ksd.edgekey.net › e5059.ksd.akamaiedge.net
Checked2026-07-31 16:33 UTC · request sent from 10.100.100.212 (our checker)
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page returns the same response to a named AI service as to a browser, with no edge block. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 5 out of a possible 5, because it is one of the checks that decide whether content can be reached and read at all, so it carries the heaviest weight in the figure for this item. Why it moves the misinformation reading This failure is a real and common route to a wrong answer for the content it affects, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT16 | warning | the page carries no structured data block stating what it is (not required; a hygiene signal) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The page carries structured data, the machine-readable summary of what it describes. What good looks like The page carries structured data summarising what it describes. Why it matters Vendors document this as optional rather than required, so its absence is a small forfeit and no more. What we found on this page the page carries no structured data block stating what it is (not required; a hygiene signal) The evidence, taken from the page as served The head of this page, as served
The page was read for a structured data block describing what the page is. <head> <title>Careers - Aviva plc</title> <script defer="defer" type="text/javascript" src="https://rum.hlx.page/.rum/@adobe/helix-rum-js@%5E2/dist/rum-standalone.js" data-routing="env=prod,tier=publish,ams=Aviva Group"/> <link rel="preconnect" href="https://static.aviva.io/"/> <link rel="preconnect" href="https://static.aviva.io/" crossorigin="anonymous"/> <link rel="preconnect" href="https://dpm.demdex.net/"/> <link rel="preconnect" href="https://assets.adobedtm.com/"/> <link rel="preload" href="https://static.aviva.io/assets/fonts/sourcesans3-variable-roman-base.woff2" as="font" crossorigin="anonymous"/> <link rel="preload" href="https://cdn-ukwest.onetrust.com/scripttemplates/otSDKStub.js" as="script" crossorigin="anonymous"/> <link rel="preload" href="https://static.aviva.io/assets/fonts/avivacurve-regular.woff2" as="font" crossorigin="anonymous"/> <meta content="width=device-width,initial-scale=1" name="viewport"/> <meta property="templatename" content="categorypage"/> <meta property="article:published_time" content="2019-03-26T09:58:25"/> <meta property="og:description" content="Search for a job and find out what you can expect from Aviva as an employer."/> <meta property="oโฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR13 | warning | the page does not mark out its main content, so what is unique to this page cannot be told apart from the menus and foot-of-page text repeated across the site | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page's main content is marked off from the navigation and footer around it. What good looks like A main or article region marks the primary content off from the navigation and footer around it. Why it matters Pulling the page's text returns menus and legal footers mixed with the substance, so the answer arrives buried in noise. What we found on this page the page does not mark out its main content, so what is unique to this page cannot be told apart from the menus and foot-of-page text repeated across the site The evidence, taken from the page as served The blocks this page marks out, as served
The page was read for the block that marks out its main content. <meta itemprop="name" content="Careers"/> <meta itemprop="url" content="https://www.aviva.com/careers/"/> <div class="l-whole-page" data-back-to-top="Back to start of main content" data-component="back-to-top-es6"> <script> <span data-module="app/init-es6" data-module-load="true"/> <script id="js-init" src="https://static.aviva.io/assets/themes-managed/v6.1.0/shared/extensions/requirejs/init.js" asynโฆ <script src="https://static.aviva.io/etc.clientlibs/settings/wcm/designs/aviva-corporate/clientlibs/resources/2-20260728โฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS01 | fail | 1 of 1 boxes in the page's forms carry no name saying what each is for, so which answer belongs in which box rests on layout alone | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Each box, dropdown and text area in a form carries a name saying what it is for. What good looks like Each field in a form carries a name saying what it is for. Why it matters Unnamed fields leave the tie between a question and its box resting on layout, which shifts as the page reflows. What we found on this page 1 of 1 boxes in the page's forms carry no name saying what each is for, so which answer belongs in which box rests on layout alone The evidence, taken from the page as served The form boxes that carry no name, as served
<input type="search" name="q" id="search-site" value="" class="m-site-search__input" placeholder="Enter a keyword"/> Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: each field in a form carries a name saying what it is for. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS10 | fail | the page's first heading is not its top-level heading, so the structure starts part way down | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check A page's headings start at the top level and step down without skipping a level. What good looks like The page's headings start at the top level and step down without skipping a level. Why it matters Content under a skipped level has no clear parent section, so structure taken from the page misplaces its text. What we found on this page the page's first heading is not its top-level heading, so the structure starts part way down The evidence, taken from the page as served The page's heading outline, in document order (a jump in level is marked)
H3 Recommendation to reject "mini-tender" offers by Litani LLC level jumped H1 Careers H2 Better and brighter together H2 Lighting everyone's path H2 Find your spark H3 Smart & flexible working H3 Volunteering H3 LinkedIn H3 Instagram H2 Ignite your future at Aviva H3 Transcriptย for video Our Colleague Value Proposition H3 Who we are and what we do H3 Be you H3 Embedding sustainability H2 Meet our people H2 The one who hosts tea H2 The one who studies storms H2 The one who found balance H2 The one who never thought sheรขยยd work for an insurer H2 Great Place to Work H2 Our locations H2 United Kingdom H2 Ireland H2 Canada H2 Aviva Investors H2 Discover more H3 About us H3 Sustainability H3 Newsroom H2 Login or register H2 Site navigation H3 About us H4 Our purpose and priorities H4 Our customers and people H4 Our Board and Executives H4 2025 Annual Report H4 Get support H3 Investors H4 Strategy and performance H4 Institutional investors H4 Shareholder services H4 Corporate governance H4 Risk governance and management H4 2025 Annual Report H4 Get support H3 Newsroom H4 News and research H4 Resources H4 About Aviva H4 Get support H3 Careers H4 Careers at Aviva H4 Life at Aviva H4 Diversity and inclusion H4 Get support H3 Sustainability H4 Sustainability at Aviva H4 Sustainability news H4 Sustainability resources H4 Aviva Foundation H4 Get support H4 Get support H2 Footer H3 Useful information H4 Products in our locations H4 Use MyAviva H4 How to make a complaint H3 On this site H3 Media H3 Corporate H3 Other links H3 Social H3 Legal H3 Copyright
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page's headings start at the top level and step down without skipping a level. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS14 | fail | 1 video(s) on the page with no captions on the video and no written transcript on the page: nothing spoken is available as text in any form | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether each video carries captions of its own, timed text on the video itself, judged together with whether the page holds a written transcript. What good looks like Captions carried on the video. A WARNING means the video has no captions but a written transcript on the page holds the words. A FAIL means neither exists, so nothing spoken is available as text in any form; that total absence is marked here once, not spread across two findings. Why it matters Spoken content that exists only as sound is invisible to a reader, human or machine: nothing said in the video can be found, read or quoted. What we found on this page 1 video(s) on the page with no captions on the video and no written transcript on the page: nothing spoken is available as text in any form The evidence, taken from the page as served Each video on the page, as served: its code, source file and caption track
No caption track on the video and no transcript link on the page. <video id="video6346405076112" data-embed="default" class="video-js" controls=""/> Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: captions carried on the video. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS16 | warning | 1 media resource(s) are named as a technical code, not human-meaningful words, so a machine cannot tell what the resource is from its name | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The name a video, audio clip or image is served under, and whether it is human-meaningful words or a technical code. What good looks like Video, audio and image files carry names made of words that say what they are, not a technical code. Why it matters A resource named as a code or a bare number says nothing about what it is, so a machine cataloguing it has only the code to go on. What we found on this page 1 media resource(s) are named as a technical code, not human-meaningful words, so a machine cannot tell what the resource is from its name The evidence, taken from the page as served The media resources whose name is a technical code, as served
A meaningful name (words that say what it is) lets a machine identify the resource; a code or a bare number cannot. <video id="video6346405076112" data-embed="default" class="video-js" controls=""/> | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR03 | warning | 17% of the words a person sees are missing from the page as first delivered (10368 characters delivered, 12919 once the page finishes building itself) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check How much of the page's content exists only once JavaScript has run. What good looks like The page's content is present in the served HTML, so it does not depend on JavaScript to appear. Why it matters The page is fetched successfully but the answer is missing from what comes back, so the content is absent rather than wrong. What we found on this page 17% of the words a person sees are missing from the page as first delivered (10368 characters delivered, 12919 once the page finishes building itself) The evidence, taken from the page as served Content present only after JavaScript runs (absent from the served HTML)
The served HTML carries 10368 characters of text; after JavaScript runs the page carries 12919. 17% of the rendered page's words are absent from the HTML the server sends. What the server sends (raw HTML text, first 280 chars) Careers - Aviva plc Skip to content Recommendation to reject "mini-tender" offers by Litani LLC We want to make you aware that a company called Litani may write, or may already have written, to you offering to buy some or all of your Aviva shares. Our warning to shareholders page…
Words present only after JavaScript runs
acceptactiveadvertisementsadvertisingallowallowedalwaysapplyaroundautomaticallybackbecausebelowblockbrowserbuttoncannotcategorycentrechoiceschooseclearclosecollectconfirmconsentcorecrimecustomisedetectdevicedifferentenableenablesenhancedexampleexperiencefilesfilterfiltersfraudfunctionfunctionalfunctionalityholdhowevericonimpactimproveincludesinterestleastmainmarketingmovenecessaryoptionalpagespersonalisationpersonalised
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR11 | warning | 17% of the words a person sees are missing from the page as first delivered, which is 0.80 of its finished size | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The measured gap between the page as served and the page after the browser has built it. What good looks like The served page and the fully built page carry the same words, with little gap between them. Why it matters Two versions of the same page exist, and which words come back depends on which version was fetched. What we found on this page 17% of the words a person sees are missing from the page as first delivered, which is 0.80 of its finished size The evidence, taken from the page as served This page as first delivered, against the page once its scripts have run
Both were taken from the same request. The first is what the site sent; the second is what a person ends up looking at.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR12 | warning | 57% of the page's text (7457 of 12919 characters) is not visible before interaction | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check How much of the page's text is hidden behind a click or an expander before anyone interacts. What good looks like The page's text is visible as it loads, not held behind a click or an expander. Why it matters Half or more of the page's text is present but never shown, so what readers see and what it contains diverge. What we found on this page 57% of the page's text (7457 of 12919 characters) is not visible before interaction The evidence, taken from the page as served How much of this page is hidden until something is clicked
Counted on the page once its scripts had run, before anything was clicked.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS04 | warning | the page's naming markup is faulty: 1 name label(s) point at nothing: the code that should hold the name is absent; 103 working control(s) sit inside a section the code marks as hidden, so they work on screen but are absent from what is read out | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Accessibility markup faults: invented roles, labels pointing at nothing, live controls marked hidden. What good looks like The page's accessibility markup is sound, with valid roles and no labels pointing at nothing. Why it matters The page's own description of its controls is wrong, so what it offers and what it declares do not match. What we found on this page the page's naming markup is faulty: 1 name label(s) point at nothing: the code that should hold the name is absent; 103 working control(s) sit inside a section the code marks as hidden, so they work on screen but are absent from what is read out The evidence, taken from the page as served The faulty markup, as the page serves it once loaded
<input type="checkbox" name="storage-access" id="ot-group-id-C0001-toggle" aria-expanded="false" ot-accordion="true" role="button" aria-controls="ot-desc-id-C0001" aria-labelledby="ot-header-id-C0001 ot-status-id-C0001"/> <input type="search" name="q" id="search-site" value="" class="m-site-search__input" placeholder="Enter a keyword"/> <button id="submit" type="submit" class="m-site-search__button"> Search </button> <a class="a-button a-button--primary a-button--full-width" href="/about-us/myaviva/">MyAviva</a> <a class="m-primary-navigation-sub-section__link a-button a-button--tertiary" href="/about-us/"> Explore About us </a> <a class="a-button a-button--tertiary" href="/about-us/our-purpose-and-priorities-overview/"> Our purpose and priorities overview </a> <a class="a-button a-button--tertiary" href="/about-us/our-purpose-and-priorities-overview/our-purpose-and-values/"> Our purpose and values </a> <a class="a-button a-button--tertiary" href="/about-us/our-purpose-and-priorities-overview/how-we-are-organised/"> How we're organised </a> <a class="a-button a-button--tertiary" href="/about-us/our-purpose-and-priorities-overview/helping-the-uk-get-ready/"> Helping the UK Get Ready </a> <a class="a-button a-button--tertiary" href="/about-us/our-purpose-and-priorities-overview/innovation/"> Innovation at Aviva </a> …and 94 more like it. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MX02 | fail | loaded-and-settled in 10.4s (raw response 213ms): rendering adds substantial work beyond the served HTML | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check On sampled pages, how long the browser work takes before the content is finally present. What good looks like The browser finishes building the page quickly, so its content settles without a long wait. Why it matters A snapshot stores what exists at the moment it is taken, so content arriving later is stored as absent. What we found on this page loaded-and-settled in 10.4s (raw response 213ms): rendering adds substantial work beyond the served HTML The evidence, taken from the page as served How long this page took to finish building itself
Timed from the request being made to the page going quiet, in a browser, before anything was clicked.
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the browser finishes building the page quickly, so its content settles without a long wait. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| DS03 | fail | an AI crawler asking for this page is refused by the security layer in front of the site, while an ordinary browser is served, so the page's content never reaches the AI and answers about it are left to memory or guesswork | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The same page loads for a browser but is refused when the request names itself as an AI service. What good looks like The page returns the same response to a named AI service as to a browser, with no edge block. Why it matters The block sits in front of the site and leaves no trace in its own logs, so the estate is closed off unnoticed. What we found on this page an AI crawler asking for this page is refused by the security layer in front of the site, while an ordinary browser is served, so the page's content never reaches the AI and answers about it are left to memory or guesswork The evidence, taken from the page as served The estate's edge tested with each AI crawler: a browser is served, the crawlers are refused
Hostwww.aviva.com · resolves to 23.215.224.114 · an Akamai edge hostname
Address trailwww.aviva.com › cert10.uk.aviva.com.ksd.edgekey.net › e5059.ksd.akamaiedge.net
Checked2026-07-31 16:33 UTC · request sent from 10.100.100.212 (our checker)
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page returns the same response to a named AI service as to a browser, with no edge block. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 5 out of a possible 5, because it is one of the checks that decide whether content can be reached and read at all, so it carries the heaviest weight in the figure for this item. Why it moves the misinformation reading This failure is a real and common route to a wrong answer for the content it affects, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT09 | fail | 1 skipped heading level(s) in document order | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Heading levels step down one at a time, rather than jumping from an H2 straight to an H5. What good looks like Heading levels step down one at a time, without jumping a level. Why it matters A skipped level breaks the trail that says which section a passage belongs to, so it is filed under the wrong one. What we found on this page 1 skipped heading level(s) in document order The evidence, taken from the page as served The page's heading outline, in document order (a jump in level is marked)
H3 Recommendation to reject "mini-tender" offers by Litani LLC H1 Diversity, equity and inclusion H2 Explore page H2 It takes Aviva H3 Transcriptย for video Inclusion and diversity at Aviva H3 Our commitments H2 Aviva Communities H2 Women in leadership H2 Developing the next generations of female leaders H2 Supporting ethnically diverse colleagues H4 Leadership and development programmes level jumped H2 UK Pay Gap Report H2 The UK Pay Gap Report H2 Diversity data gathering H2 External benchmarking H2 Progressive partnerships H2 Tracking our progress H2 Login or register H2 Site navigation H3 About us H4 Our purpose and priorities H4 Our customers and people H4 Our Board and Executives H4 2025 Annual Report H4 Get support H3 Investors H4 Strategy and performance H4 Institutional investors H4 Shareholder services H4 Corporate governance H4 Risk governance and management H4 2025 Annual Report H4 Get support H3 Newsroom H4 News and research H4 Resources H4 About Aviva H4 Get support H3 Careers H4 Careers at Aviva H4 Life at Aviva H4 Diversity and inclusion H4 Get support H3 Sustainability H4 Sustainability at Aviva H4 Sustainability news H4 Sustainability resources H4 Aviva Foundation H4 Get support H4 Get support H2 Footer H3 Useful information H4 Products in our locations H4 Use MyAviva H4 How to make a complaint H3 On this site H3 Media H3 Corporate H3 Other links H3 Social H3 Legal H3 Copyright
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: heading levels step down one at a time, without jumping a level. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT16 | warning | the page carries no structured data block stating what it is (not required; a hygiene signal) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The page carries structured data, the machine-readable summary of what it describes. What good looks like The page carries structured data summarising what it describes. Why it matters Vendors document this as optional rather than required, so its absence is a small forfeit and no more. What we found on this page the page carries no structured data block stating what it is (not required; a hygiene signal) The evidence, taken from the page as served The head of this page, as served
The page was read for a structured data block describing what the page is. <head> <title>Diversity, equity and inclusion - Aviva plc</title> <script defer="defer" type="text/javascript" src="https://rum.hlx.page/.rum/@adobe/helix-rum-js@%5E2/dist/rum-standalone.js" data-routing="env=prod,tier=publish,ams=Aviva Group"/> <link rel="preconnect" href="https://static.aviva.io/"/> <link rel="preconnect" href="https://static.aviva.io/" crossorigin="anonymous"/> <link rel="preconnect" href="https://dpm.demdex.net/"/> <link rel="preconnect" href="https://assets.adobedtm.com/"/> <link rel="preload" href="https://static.aviva.io/assets/fonts/sourcesans3-variable-roman-base.woff2" as="font" crossorigin="anonymous"/> <link rel="preload" href="https://cdn-ukwest.onetrust.com/scripttemplates/otSDKStub.js" as="script" crossorigin="anonymous"/> <link rel="preload" href="https://static.aviva.io/assets/fonts/avivacurve-regular.woff2" as="font" crossorigin="anonymous"/> <meta content="width=device-width,initial-scale=1" name="viewport"/> <meta property="templatename" content="featurepage"/> <meta property="article:published_time" content="2021-07-15T01:11:57"/> <meta property="og:description" content="We are committed to ensuring our people are a reflection of the customers โฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR13 | warning | the page does not mark out its main content, so what is unique to this page cannot be told apart from the menus and foot-of-page text repeated across the site | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page's main content is marked off from the navigation and footer around it. What good looks like A main or article region marks the primary content off from the navigation and footer around it. Why it matters Pulling the page's text returns menus and legal footers mixed with the substance, so the answer arrives buried in noise. What we found on this page the page does not mark out its main content, so what is unique to this page cannot be told apart from the menus and foot-of-page text repeated across the site The evidence, taken from the page as served The blocks this page marks out, as served
The page was read for the block that marks out its main content. <meta itemprop="name" content="Diversity, equity and inclusion"/> <meta itemprop="url" content="https://www.aviva.com/about-us/our-customers-and-people-overview/diversity-equity-and-inclโฆ <div class="l-whole-page" data-back-to-top="Back to start of main content" data-component="back-to-top-es6"> <script> <span data-module="app/init-es6" data-module-load="true"/> <script id="js-init" src="https://static.aviva.io/assets/themes-managed/v6.1.0/shared/extensions/requirejs/init.js" asynโฆ <script src="https://static.aviva.io/etc.clientlibs/settings/wcm/designs/aviva-corporate/clientlibs/resources/2-20260728โฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS01 | fail | 1 of 1 boxes in the page's forms carry no name saying what each is for, so which answer belongs in which box rests on layout alone | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Each box, dropdown and text area in a form carries a name saying what it is for. What good looks like Each field in a form carries a name saying what it is for. Why it matters Unnamed fields leave the tie between a question and its box resting on layout, which shifts as the page reflows. What we found on this page 1 of 1 boxes in the page's forms carry no name saying what each is for, so which answer belongs in which box rests on layout alone The evidence, taken from the page as served The form boxes that carry no name, as served
<input type="search" name="q" id="search-site" value="" class="m-site-search__input" placeholder="Enter a keyword"/> Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: each field in a form carries a name saying what it is for. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS08 | fail | 1 link wording(s) are used for more than one destination, so the same words point at different pages: โuk pay gap reportโ; the links are listed in the view | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Links that share exactly the same wording on one page while pointing at different destinations. What good looks like Links that share the same wording lead to the same destination. Why it matters The wording no longer settles the target, so the wrong one gets followed at the point where the choice matters. What we found on this page 1 link wording(s) are used for more than one destination, so the same words point at different pages: โuk pay gap reportโ; the links are listed in the view The evidence, taken from the page as served Links that share the same text but point to different destinations, as served
<a title="Opens UK Pay Gap report 2025 PDF" href="//static.aviva.io/content/dam/aviva-corporate/documents/about-us/aviva-pay-gap-report-2025-uk.pdf">UK Pay Gap Report</a> <a class="a-button a-button--transparent l-section__cta" href="/about-us/our-customers-and-people-overview/diversity-equity-and-inclusion/uk-pay-gap-report/"> UK Pay Gap Report </a> Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: links that share the same wording lead to the same destination. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS10 | fail | the page's first heading is not its top-level heading, so the structure starts part way down; the heading structure skips a level in 1 place(s), so the order does not follow | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check A page's headings start at the top level and step down without skipping a level. What good looks like The page's headings start at the top level and step down without skipping a level. Why it matters Content under a skipped level has no clear parent section, so structure taken from the page misplaces its text. What we found on this page the page's first heading is not its top-level heading, so the structure starts part way down; the heading structure skips a level in 1 place(s), so the order does not follow The evidence, taken from the page as served The page's heading outline, in document order (a jump in level is marked)
H3 Recommendation to reject "mini-tender" offers by Litani LLC level jumped H1 Diversity, equity and inclusion H2 Explore page H2 It takes Aviva H3 Transcriptย for video Inclusion and diversity at Aviva H3 Our commitments H2 Aviva Communities H2 Women in leadership H2 Developing the next generations of female leaders H2 Supporting ethnically diverse colleagues H4 Leadership and development programmes level jumped H2 UK Pay Gap Report H2 The UK Pay Gap Report H2 Diversity data gathering H2 External benchmarking H2 Progressive partnerships H2 Tracking our progress H2 Login or register H2 Site navigation H3 About us H4 Our purpose and priorities H4 Our customers and people H4 Our Board and Executives H4 2025 Annual Report H4 Get support H3 Investors H4 Strategy and performance H4 Institutional investors H4 Shareholder services H4 Corporate governance H4 Risk governance and management H4 2025 Annual Report H4 Get support H3 Newsroom H4 News and research H4 Resources H4 About Aviva H4 Get support H3 Careers H4 Careers at Aviva H4 Life at Aviva H4 Diversity and inclusion H4 Get support H3 Sustainability H4 Sustainability at Aviva H4 Sustainability news H4 Sustainability resources H4 Aviva Foundation H4 Get support H4 Get support H2 Footer H3 Useful information H4 Products in our locations H4 Use MyAviva H4 How to make a complaint H3 On this site H3 Media H3 Corporate H3 Other links H3 Social H3 Legal H3 Copyright
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page's headings start at the top level and step down without skipping a level. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS14 | fail | 1 video(s) on the page with no captions on the video and no written transcript on the page: nothing spoken is available as text in any form | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether each video carries captions of its own, timed text on the video itself, judged together with whether the page holds a written transcript. What good looks like Captions carried on the video. A WARNING means the video has no captions but a written transcript on the page holds the words. A FAIL means neither exists, so nothing spoken is available as text in any form; that total absence is marked here once, not spread across two findings. Why it matters Spoken content that exists only as sound is invisible to a reader, human or machine: nothing said in the video can be found, read or quoted. What we found on this page 1 video(s) on the page with no captions on the video and no written transcript on the page: nothing spoken is available as text in any form The evidence, taken from the page as served Each video on the page, as served: its code, source file and caption track
No caption track on the video and no transcript link on the page. <video id="video6373223685112" data-embed="default" class="video-js" controls=""/> Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: captions carried on the video. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS16 | warning | 1 media resource(s) are named as a technical code, not human-meaningful words, so a machine cannot tell what the resource is from its name | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The name a video, audio clip or image is served under, and whether it is human-meaningful words or a technical code. What good looks like Video, audio and image files carry names made of words that say what they are, not a technical code. Why it matters A resource named as a code or a bare number says nothing about what it is, so a machine cataloguing it has only the code to go on. What we found on this page 1 media resource(s) are named as a technical code, not human-meaningful words, so a machine cannot tell what the resource is from its name The evidence, taken from the page as served The media resources whose name is a technical code, as served
A meaningful name (words that say what it is) lets a machine identify the resource; a code or a bare number cannot. <video id="video6373223685112" data-embed="default" class="video-js" controls=""/> | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR03 | warning | 13% of the words a person sees are missing from the page as first delivered (13833 characters delivered, 16384 once the page finishes building itself) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check How much of the page's content exists only once JavaScript has run. What good looks like The page's content is present in the served HTML, so it does not depend on JavaScript to appear. Why it matters The page is fetched successfully but the answer is missing from what comes back, so the content is absent rather than wrong. What we found on this page 13% of the words a person sees are missing from the page as first delivered (13833 characters delivered, 16384 once the page finishes building itself) The evidence, taken from the page as served Content present only after JavaScript runs (absent from the served HTML)
The served HTML carries 13833 characters of text; after JavaScript runs the page carries 16384. 13% of the rendered page's words are absent from the HTML the server sends. What the server sends (raw HTML text, first 280 chars) Diversity, equity and inclusion - Aviva plc Skip to content Recommendation to reject "mini-tender" offers by Litani LLC We want to make you aware that a company called Litani may write, or may already have written, to you offering to buy some or all of your Aviva shares. Our warn…
Words present only after JavaScript runs
acceptadvertisementsadvertisingallowallowedalwaysapplyautomaticallybackbecausebelowblockbrowserbuttoncannotcategorycentrechoiceschooseclearclosecollectconfirmconsentcorecrimecustomisedeliverdetectdeviceenablesenhancedexampleexperiencefilesfilterfiltersfraudfunctionfunctionalfunctionalityholdhowevericonimpactincludesinterestleastmarketingmostmovenecessaryoptionalpagespersonalisationpersonalisedplacedpopularpreferencepreferences
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR11 | warning | 13% of the words a person sees are missing from the page as first delivered, which is 0.84 of its finished size | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The measured gap between the page as served and the page after the browser has built it. What good looks like The served page and the fully built page carry the same words, with little gap between them. Why it matters Two versions of the same page exist, and which words come back depends on which version was fetched. What we found on this page 13% of the words a person sees are missing from the page as first delivered, which is 0.84 of its finished size The evidence, taken from the page as served This page as first delivered, against the page once its scripts have run
Both were taken from the same request. The first is what the site sent; the second is what a person ends up looking at.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS04 | warning | the page's naming markup is faulty: 1 name label(s) point at nothing: the code that should hold the name is absent; 103 working control(s) sit inside a section the code marks as hidden, so they work on screen but are absent from what is read out | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Accessibility markup faults: invented roles, labels pointing at nothing, live controls marked hidden. What good looks like The page's accessibility markup is sound, with valid roles and no labels pointing at nothing. Why it matters The page's own description of its controls is wrong, so what it offers and what it declares do not match. What we found on this page the page's naming markup is faulty: 1 name label(s) point at nothing: the code that should hold the name is absent; 103 working control(s) sit inside a section the code marks as hidden, so they work on screen but are absent from what is read out The evidence, taken from the page as served The faulty markup, as the page serves it once loaded
<input type="checkbox" name="storage-access" id="ot-group-id-C0001-toggle" aria-expanded="false" ot-accordion="true" role="button" aria-controls="ot-desc-id-C0001" aria-labelledby="ot-header-id-C0001 ot-status-id-C0001"/> <input type="search" name="q" id="search-site" value="" class="m-site-search__input" placeholder="Enter a keyword"/> <button id="submit" type="submit" class="m-site-search__button"> Search </button> <a class="a-button a-button--primary a-button--full-width" href="/about-us/myaviva/">MyAviva</a> <a class="m-primary-navigation-sub-section__link a-button a-button--tertiary" href="/about-us/"> Explore About us </a> <a class="a-button a-button--tertiary" href="/about-us/our-purpose-and-priorities-overview/"> Our purpose and priorities overview </a> <a class="a-button a-button--tertiary" href="/about-us/our-purpose-and-priorities-overview/our-purpose-and-values/"> Our purpose and values </a> <a class="a-button a-button--tertiary" href="/about-us/our-purpose-and-priorities-overview/how-we-are-organised/"> How we're organised </a> <a class="a-button a-button--tertiary" href="/about-us/our-purpose-and-priorities-overview/helping-the-uk-get-ready/"> Helping the UK Get Ready </a> <a class="a-button a-button--tertiary" href="/about-us/our-purpose-and-priorities-overview/innovation/"> Innovation at Aviva </a> …and 94 more like it. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AJ08 | warning | focus order: the first 12 Tab stops do not follow document order | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether pressing Tab moves through the page in the order its content is written. What good looks like Pressing Tab moves through the page in the order its content is written. Why it matters The keyboard jumps around the page out of sequence, so a form is worked through in an order nobody intended. What we found on this page focus order: the first 12 Tab stops do not follow document order The evidence, taken from the page as served How the keyboard moves through this page
Read on the page once its scripts had run, following the keyboard from the top.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| DS03 | fail | an AI crawler asking for this page is refused by the security layer in front of the site, while an ordinary browser is served, so the page's content never reaches the AI and answers about it are left to memory or guesswork | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The same page loads for a browser but is refused when the request names itself as an AI service. What good looks like The page returns the same response to a named AI service as to a browser, with no edge block. Why it matters The block sits in front of the site and leaves no trace in its own logs, so the estate is closed off unnoticed. What we found on this page an AI crawler asking for this page is refused by the security layer in front of the site, while an ordinary browser is served, so the page's content never reaches the AI and answers about it are left to memory or guesswork The evidence, taken from the page as served The estate's edge tested with each AI crawler: a browser is served, the crawlers are refused
Hostwww.aviva.com · resolves to 23.215.224.114 · an Akamai edge hostname
Address trailwww.aviva.com › cert10.uk.aviva.com.ksd.edgekey.net › e5059.ksd.akamaiedge.net
Checked2026-07-31 16:33 UTC · request sent from 10.100.100.212 (our checker)
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page returns the same response to a named AI service as to a browser, with no edge block. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 5 out of a possible 5, because it is one of the checks that decide whether content can be reached and read at all, so it carries the heaviest weight in the figure for this item. Why it moves the misinformation reading This failure is a real and common route to a wrong answer for the content it affects, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT16 | warning | the page carries no structured data block stating what it is (not required; a hygiene signal) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The page carries structured data, the machine-readable summary of what it describes. What good looks like The page carries structured data summarising what it describes. Why it matters Vendors document this as optional rather than required, so its absence is a small forfeit and no more. What we found on this page the page carries no structured data block stating what it is (not required; a hygiene signal) The evidence, taken from the page as served The head of this page, as served
The page was read for a structured data block describing what the page is. <head> <title>About Aviva - Aviva plc</title> <script defer="defer" type="text/javascript" src="https://rum.hlx.page/.rum/@adobe/helix-rum-js@%5E2/dist/rum-standalone.js" data-routing="env=prod,tier=publish,ams=Aviva Group"/> <link rel="preconnect" href="https://static.aviva.io/"/> <link rel="preconnect" href="https://static.aviva.io/" crossorigin="anonymous"/> <link rel="preconnect" href="https://dpm.demdex.net/"/> <link rel="preconnect" href="https://assets.adobedtm.com/"/> <link rel="preload" href="https://static.aviva.io/assets/fonts/sourcesans3-variable-roman-base.woff2" as="font" crossorigin="anonymous"/> <link rel="preload" href="https://cdn-ukwest.onetrust.com/scripttemplates/otSDKStub.js" as="script" crossorigin="anonymous"/> <link rel="preload" href="https://static.aviva.io/assets/fonts/avivacurve-regular.woff2" as="font" crossorigin="anonymous"/> <meta content="width=device-width,initial-scale=1" name="viewport"/> <meta property="templatename" content="featurelitepage"/> <meta property="article:published_time" content="2025-01-28T16:18:18"/> <meta property="og:description" content="Stats, facts and more information about our businesses."/> <meta property="og:title" conteโฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR13 | warning | the page does not mark out its main content, so what is unique to this page cannot be told apart from the menus and foot-of-page text repeated across the site | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page's main content is marked off from the navigation and footer around it. What good looks like A main or article region marks the primary content off from the navigation and footer around it. Why it matters Pulling the page's text returns menus and legal footers mixed with the substance, so the answer arrives buried in noise. What we found on this page the page does not mark out its main content, so what is unique to this page cannot be told apart from the menus and foot-of-page text repeated across the site The evidence, taken from the page as served The blocks this page marks out, as served
The page was read for the block that marks out its main content. <meta itemprop="name" content="About Aviva"/> <meta itemprop="url" content="https://www.aviva.com/newsroom/news-and-research-overview/about-aviva/"/> <div class="l-whole-page" data-back-to-top="Back to start of main content" data-component="back-to-top-es6"> <script> <span data-module="app/init-es6" data-module-load="true"/> <script id="js-init" src="https://static.aviva.io/assets/themes-managed/v6.1.0/shared/extensions/requirejs/init.js" asynโฆ <script src="https://static.aviva.io/etc.clientlibs/settings/wcm/designs/aviva-corporate/clientlibs/resources/2-20260728โฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS01 | fail | 1 of 1 boxes in the page's forms carry no name saying what each is for, so which answer belongs in which box rests on layout alone | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Each box, dropdown and text area in a form carries a name saying what it is for. What good looks like Each field in a form carries a name saying what it is for. Why it matters Unnamed fields leave the tie between a question and its box resting on layout, which shifts as the page reflows. What we found on this page 1 of 1 boxes in the page's forms carry no name saying what each is for, so which answer belongs in which box rests on layout alone The evidence, taken from the page as served The form boxes that carry no name, as served
<input type="search" name="q" id="search-site" value="" class="m-site-search__input" placeholder="Enter a keyword"/> Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: each field in a form carries a name saying what it is for. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS10 | fail | the page's first heading is not its top-level heading, so the structure starts part way down | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check A page's headings start at the top level and step down without skipping a level. What good looks like The page's headings start at the top level and step down without skipping a level. Why it matters Content under a skipped level has no clear parent section, so structure taken from the page misplaces its text. What we found on this page the page's first heading is not its top-level heading, so the structure starts part way down The evidence, taken from the page as served The page's heading outline, in document order (a jump in level is marked)
H3 Recommendation to reject "mini-tender" offers by Litani LLC level jumped H1 About Aviva H2 Explore page H2 Looking after our customers H2 Aviva's compelling investment case H2 Performance H2 Login or register H2 Site navigation H3 About us H4 Our purpose and priorities H4 Our customers and people H4 Our Board and Executives H4 2025 Annual Report H4 Get support H3 Investors H4 Strategy and performance H4 Institutional investors H4 Shareholder services H4 Corporate governance H4 Risk governance and management H4 2025 Annual Report H4 Get support H3 Newsroom H4 News and research H4 Resources H4 About Aviva H4 Get support H3 Careers H4 Careers at Aviva H4 Life at Aviva H4 Diversity and inclusion H4 Get support H3 Sustainability H4 Sustainability at Aviva H4 Sustainability news H4 Sustainability resources H4 Aviva Foundation H4 Get support H4 Get support H2 Footer H3 Useful information H4 Products in our locations H4 Use MyAviva H4 How to make a complaint H3 On this site H3 Media H3 Corporate H3 Other links H3 Social H3 Legal H3 Copyright
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page's headings start at the top level and step down without skipping a level. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| DS03 | fail | an AI crawler asking for this page is refused by the security layer in front of the site, while an ordinary browser is served, so the page's content never reaches the AI and answers about it are left to memory or guesswork | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The same page loads for a browser but is refused when the request names itself as an AI service. What good looks like The page returns the same response to a named AI service as to a browser, with no edge block. Why it matters The block sits in front of the site and leaves no trace in its own logs, so the estate is closed off unnoticed. What we found on this page an AI crawler asking for this page is refused by the security layer in front of the site, while an ordinary browser is served, so the page's content never reaches the AI and answers about it are left to memory or guesswork The evidence, taken from the page as served The estate's edge tested with each AI crawler: a browser is served, the crawlers are refused
Hostwww.aviva.com · resolves to 23.215.224.114 · an Akamai edge hostname
Address trailwww.aviva.com › cert10.uk.aviva.com.ksd.edgekey.net › e5059.ksd.akamaiedge.net
Checked2026-07-31 16:33 UTC · request sent from 10.100.100.212 (our checker)
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page returns the same response to a named AI service as to a browser, with no edge block. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 5 out of a possible 5, because it is one of the checks that decide whether content can be reached and read at all, so it carries the heaviest weight in the figure for this item. Why it moves the misinformation reading This failure is a real and common route to a wrong answer for the content it affects, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT32 | warning | length 184 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The meta description's length is usable, between 50 and 170 characters. What good looks like The meta description's length is usable, long enough to say something and short enough not to be cut. Why it matters Too short says nothing and too long gets cut, so the summary field is spent without doing its job. What we found on this page length 184 The evidence, taken from the page as served The page's description, as served
<meta name="description" content="Making it click for our customers. Make the most out of life, plan for the future. Have the confidence that if things go wrong, weรขยยll be there to help put them right. It takes Aviva."/> | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT16 | warning | the page carries no structured data block stating what it is (not required; a hygiene signal) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The page carries structured data, the machine-readable summary of what it describes. What good looks like The page carries structured data summarising what it describes. Why it matters Vendors document this as optional rather than required, so its absence is a small forfeit and no more. What we found on this page the page carries no structured data block stating what it is (not required; a hygiene signal) The evidence, taken from the page as served The head of this page, as served
The page was read for a structured data block describing what the page is. <head> <title>Annual Report - Aviva plc</title> <script defer="defer" type="text/javascript" src="https://rum.hlx.page/.rum/@adobe/helix-rum-js@%5E2/dist/rum-standalone.js" data-routing="env=prod,tier=publish,ams=Aviva Group"/> <link rel="preconnect" href="https://static.aviva.io/"/> <link rel="preconnect" href="https://static.aviva.io/" crossorigin="anonymous"/> <link rel="preconnect" href="https://dpm.demdex.net/"/> <link rel="preconnect" href="https://assets.adobedtm.com/"/> <link rel="preload" href="https://static.aviva.io/assets/fonts/sourcesans3-variable-roman-base.woff2" as="font" crossorigin="anonymous"/> <link rel="preload" href="https://cdn-ukwest.onetrust.com/scripttemplates/otSDKStub.js" as="script" crossorigin="anonymous"/> <link rel="preload" href="https://static.aviva.io/assets/fonts/avivacurve-regular.woff2" as="font" crossorigin="anonymous"/> <meta content="width=device-width,initial-scale=1" name="viewport"/> <meta property="templatename" content="featurepage"/> <meta property="article:published_time" content="2026-03-05T07:00:00"/> <meta property="og:description" content="Making it click for our customers. Make the most out of life, plan for the future. Have the โฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR13 | warning | the page does not mark out its main content, so what is unique to this page cannot be told apart from the menus and foot-of-page text repeated across the site | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page's main content is marked off from the navigation and footer around it. What good looks like A main or article region marks the primary content off from the navigation and footer around it. Why it matters Pulling the page's text returns menus and legal footers mixed with the substance, so the answer arrives buried in noise. What we found on this page the page does not mark out its main content, so what is unique to this page cannot be told apart from the menus and foot-of-page text repeated across the site The evidence, taken from the page as served The blocks this page marks out, as served
The page was read for the block that marks out its main content. <meta itemprop="name" content="Annual Report"/> <meta itemprop="url" content="https://www.aviva.com/investors/strategy-and-performance-overview/annual-report/"/> <div class="l-whole-page" data-back-to-top="Back to start of main content" data-component="back-to-top-es6"> <script> <span data-module="app/init-es6" data-module-load="true"/> <script id="js-init" src="https://static.aviva.io/assets/themes-managed/v6.1.0/shared/extensions/requirejs/init.js" asynโฆ <script src="https://static.aviva.io/etc.clientlibs/settings/wcm/designs/aviva-corporate/clientlibs/resources/2-20260728โฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS01 | fail | 1 of 1 boxes in the page's forms carry no name saying what each is for, so which answer belongs in which box rests on layout alone | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Each box, dropdown and text area in a form carries a name saying what it is for. What good looks like Each field in a form carries a name saying what it is for. Why it matters Unnamed fields leave the tie between a question and its box resting on layout, which shifts as the page reflows. What we found on this page 1 of 1 boxes in the page's forms carry no name saying what each is for, so which answer belongs in which box rests on layout alone The evidence, taken from the page as served The form boxes that carry no name, as served
<input type="search" name="q" id="search-site" value="" class="m-site-search__input" placeholder="Enter a keyword"/> Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: each field in a form carries a name saying what it is for. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS10 | fail | the page's first heading is not its top-level heading, so the structure starts part way down | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check A page's headings start at the top level and step down without skipping a level. What good looks like The page's headings start at the top level and step down without skipping a level. Why it matters Content under a skipped level has no clear parent section, so structure taken from the page misplaces its text. What we found on this page the page's first heading is not its top-level heading, so the structure starts part way down The evidence, taken from the page as served The page's heading outline, in document order (a jump in level is marked)
H3 Recommendation to reject "mini-tender" offers by Litani LLC level jumped H1 Annual Report 2025 H2 Explore page H2 Amanda Blanc DBE H2 Amanda Blanc DBE, Group Chief Executive Officer รขยย full statement from our Annu H2 Watch our full year results 2025 video with Group CEO, Amanda Blanc DBE H3 Transcriptย for video Watch our full year results 2025 video with Group CEO, Ama H2 Annual Report and Accounts H2 Highlights H2 Our strategic progress: another year of delivery H3 Progress in 2025 H3 Spotlight on Workplace H3 Progress in 2025 H3 Spotlight on Direct Line H3 Progress in 2025 H3 Spotlight on AI H3 Progress in 2025 H3 Spotlight on investment in the UK H2 Our investment case H2 The UKรขยยs only diversified insurer: market-leading positions across the UK, Can H2 Accelerating capital-light growth: driving towards 75% capital-light with >20% R H2 Consistent customer-centric strategy: leading UK franchise & brand, lifetime pro H2 Track record of delivery: strong growth, sustainable returns, financial strength H2 Superior returns for shareholders: new 3-year targets and enhanced distributions H2 Key downloads H3 Aviva plc Annual Report and Accounts 2025 H3 Climate-related Financial Disclosure 2025 H3 Aviva plc Sustainability Datasheet 2025 - Read Only H3 Reporting Criteria 2025 H3 UKSEF Reporting Package 2025 H3 UKSEF iXBRL 2025 HTML H2 Reports archive H2 Login or register H2 Site navigation H3 About us H4 Our purpose and priorities H4 Our customers and people H4 Our Board and Executives H4 2025 Annual Report H4 Get support H3 Investors H4 Strategy and performance H4 Institutional investors H4 Shareholder services H4 Corporate governance H4 Risk governance and management H4 2025 Annual Report H4 Get support H3 Newsroom H4 News and research H4 Resources H4 About Aviva H4 Get support H3 Careers H4 Careers at Aviva H4 Life at Aviva H4 Diversity and inclusion H4 Get support H3 Sustainability H4 Sustainability at Aviva H4 Sustainability news H4 Sustainability resources H4 Aviva Foundation H4 Get support H4 Get support H2 Footer H3 Useful information H4 Products in our locations H4 Use MyAviva H4 How to make a complaint H3 On this site H3 Media H3 Corporate H3 Other links H3 Social H3 Legal H3 Copyright
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page's headings start at the top level and step down without skipping a level. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS14 | fail | 1 video(s) on the page with no captions on the video and no written transcript on the page: nothing spoken is available as text in any form | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether each video carries captions of its own, timed text on the video itself, judged together with whether the page holds a written transcript. What good looks like Captions carried on the video. A WARNING means the video has no captions but a written transcript on the page holds the words. A FAIL means neither exists, so nothing spoken is available as text in any form; that total absence is marked here once, not spread across two findings. Why it matters Spoken content that exists only as sound is invisible to a reader, human or machine: nothing said in the video can be found, read or quoted. What we found on this page 1 video(s) on the page with no captions on the video and no written transcript on the page: nothing spoken is available as text in any form The evidence, taken from the page as served Each video on the page, as served: its code, source file and caption track
No caption track on the video and no transcript link on the page. <video id="video6390041787112" data-embed="default" class="video-js" controls=""/> Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: captions carried on the video. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS16 | warning | 1 media resource(s) are named as a technical code, not human-meaningful words, so a machine cannot tell what the resource is from its name | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The name a video, audio clip or image is served under, and whether it is human-meaningful words or a technical code. What good looks like Video, audio and image files carry names made of words that say what they are, not a technical code. Why it matters A resource named as a code or a bare number says nothing about what it is, so a machine cataloguing it has only the code to go on. What we found on this page 1 media resource(s) are named as a technical code, not human-meaningful words, so a machine cannot tell what the resource is from its name The evidence, taken from the page as served The media resources whose name is a technical code, as served
A meaningful name (words that say what it is) lets a machine identify the resource; a code or a bare number cannot. <video id="video6390041787112" data-embed="default" class="video-js" controls=""/> | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| DS03 | fail | an AI crawler asking for this page is refused by the security layer in front of the site, while an ordinary browser is served, so the page's content never reaches the AI and answers about it are left to memory or guesswork | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The same page loads for a browser but is refused when the request names itself as an AI service. What good looks like The page returns the same response to a named AI service as to a browser, with no edge block. Why it matters The block sits in front of the site and leaves no trace in its own logs, so the estate is closed off unnoticed. What we found on this page an AI crawler asking for this page is refused by the security layer in front of the site, while an ordinary browser is served, so the page's content never reaches the AI and answers about it are left to memory or guesswork The evidence, taken from the page as served The estate's edge tested with each AI crawler: a browser is served, the crawlers are refused
Hostwww.aviva.com · resolves to 23.215.224.114 · an Akamai edge hostname
Address trailwww.aviva.com › cert10.uk.aviva.com.ksd.edgekey.net › e5059.ksd.akamaiedge.net
Checked2026-07-31 16:33 UTC · request sent from 10.100.100.212 (our checker)
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page returns the same response to a named AI service as to a browser, with no edge block. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 5 out of a possible 5, because it is one of the checks that decide whether content can be reached and read at all, so it carries the heaviest weight in the figure for this item. Why it moves the misinformation reading This failure is a real and common route to a wrong answer for the content it affects, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT06 | warning | title length 66 chars | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The title's length sits in a usable window, between 10 and 65 characters. What good looks like The title's length sits in a usable window, neither too short to say anything nor too long to be cut. Why it matters A title outside that window is liable to be rewritten elsewhere, and control of the page's name goes with it. What we found on this page title length 66 chars The evidence, taken from the page as served The page title, as served
<title>Innovation | Driving transformative change - Aviva plc - Aviva plc</title> | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT16 | warning | the page carries no structured data block stating what it is (not required; a hygiene signal) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The page carries structured data, the machine-readable summary of what it describes. What good looks like The page carries structured data summarising what it describes. Why it matters Vendors document this as optional rather than required, so its absence is a small forfeit and no more. What we found on this page the page carries no structured data block stating what it is (not required; a hygiene signal) The evidence, taken from the page as served The head of this page, as served
The page was read for a structured data block describing what the page is. <head> <title>Innovation | Driving transformative change - Aviva plc - Aviva plc</title> <script defer="defer" type="text/javascript" src="https://rum.hlx.page/.rum/@adobe/helix-rum-js@%5E2/dist/rum-standalone.js" data-routing="env=prod,tier=publish,ams=Aviva Group"/> <link rel="preconnect" href="https://static.aviva.io/"/> <link rel="preconnect" href="https://static.aviva.io/" crossorigin="anonymous"/> <link rel="preconnect" href="https://dpm.demdex.net/"/> <link rel="preconnect" href="https://assets.adobedtm.com/"/> <link rel="preload" href="https://static.aviva.io/assets/fonts/sourcesans3-variable-roman-base.woff2" as="font" crossorigin="anonymous"/> <link rel="preload" href="https://cdn-ukwest.onetrust.com/scripttemplates/otSDKStub.js" as="script" crossorigin="anonymous"/> <link rel="preload" href="https://static.aviva.io/assets/fonts/avivacurve-regular.woff2" as="font" crossorigin="anonymous"/> <meta content="width=device-width,initial-scale=1" name="viewport"/> <meta property="templatename" content="featurepage"/> <meta property="article:published_time" content="2021-07-15T00:24:06"/> <meta property="og:description" content="Our innovation team seek new opportunities, accelerโฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR13 | warning | the page does not mark out its main content, so what is unique to this page cannot be told apart from the menus and foot-of-page text repeated across the site | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page's main content is marked off from the navigation and footer around it. What good looks like A main or article region marks the primary content off from the navigation and footer around it. Why it matters Pulling the page's text returns menus and legal footers mixed with the substance, so the answer arrives buried in noise. What we found on this page the page does not mark out its main content, so what is unique to this page cannot be told apart from the menus and foot-of-page text repeated across the site The evidence, taken from the page as served The blocks this page marks out, as served
The page was read for the block that marks out its main content. <meta itemprop="name" content="Innovation | Driving transformative change - Aviva plc"/> <meta itemprop="url" content="https://www.aviva.com/about-us/our-purpose-and-priorities-overview/innovation/"/> <div class="l-whole-page" data-back-to-top="Back to start of main content" data-component="back-to-top-es6"> <script> <span data-module="app/init-es6" data-module-load="true"/> <script id="js-init" src="https://static.aviva.io/assets/themes-managed/v6.1.0/shared/extensions/requirejs/init.js" asynโฆ <script src="https://static.aviva.io/etc.clientlibs/settings/wcm/designs/aviva-corporate/clientlibs/resources/2-20260728โฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS01 | fail | 1 of 1 boxes in the page's forms carry no name saying what each is for, so which answer belongs in which box rests on layout alone | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Each box, dropdown and text area in a form carries a name saying what it is for. What good looks like Each field in a form carries a name saying what it is for. Why it matters Unnamed fields leave the tie between a question and its box resting on layout, which shifts as the page reflows. What we found on this page 1 of 1 boxes in the page's forms carry no name saying what each is for, so which answer belongs in which box rests on layout alone The evidence, taken from the page as served The form boxes that carry no name, as served
<input type="search" name="q" id="search-site" value="" class="m-site-search__input" placeholder="Enter a keyword"/> Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: each field in a form carries a name saying what it is for. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS10 | fail | the page's first heading is not its top-level heading, so the structure starts part way down | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check A page's headings start at the top level and step down without skipping a level. What good looks like The page's headings start at the top level and step down without skipping a level. Why it matters Content under a skipped level has no clear parent section, so structure taken from the page misplaces its text. What we found on this page the page's first heading is not its top-level heading, so the structure starts part way down The evidence, taken from the page as served The page's heading outline, in document order (a jump in level is marked)
H3 Recommendation to reject "mini-tender" offers by Litani LLC level jumped H1 Innovation H2 Explore page H2 Innovation at Aviva H2 Our podcasts H3 Transcriptย for video Episode 1: From Build to Buy H3 Transcriptย for video Episode 2: Pitching B2B H3 Transcriptย for video Episode 3: Being Enterprise Ready H3 Transcriptย for video Episode 4: Working Together H3 Transcriptย for video Episode 5: Partnership plus Investment The episode explore H3 Transcriptย for video Episode 6: Partnering Internationally H2 Our focus H3 AI and GenAI H3 FinTech and WealthTech H3 Embedded insurance H3 Cyber, security and digital trust H3 Future of mobility and IoT H3 ClimateTech and sustainability H3 Future of work H3 Health and wellbeing H2 Our partnerships H3 Founders Factory H3 Insurtech UK H2 Here's some examples of recent successful partnerships: H2 Venture investments H2 Portfolio companies H2 The pledges H3 The Fintech Pledge principles H3 The Invest in Women Taskforce pledge H2 Hackathon H3 Transcriptย for video Aviva Hackathon 2025 H2 Contact us H3 Partner with us H3 Investment opportunities H3 Join the team H3 Follow Aviva on LinkedIn H2 Login or register H2 Site navigation H3 About us H4 Our purpose and priorities H4 Our customers and people H4 Our Board and Executives H4 2025 Annual Report H4 Get support H3 Investors H4 Strategy and performance H4 Institutional investors H4 Shareholder services H4 Corporate governance H4 Risk governance and management H4 2025 Annual Report H4 Get support H3 Newsroom H4 News and research H4 Resources H4 About Aviva H4 Get support H3 Careers H4 Careers at Aviva H4 Life at Aviva H4 Diversity and inclusion H4 Get support H3 Sustainability H4 Sustainability at Aviva H4 Sustainability news H4 Sustainability resources H4 Aviva Foundation H4 Get support H4 Get support H2 Footer H3 Useful information H4 Products in our locations H4 Use MyAviva H4 How to make a complaint H3 On this site H3 Media H3 Corporate H3 Other links H3 Social H3 Legal H3 Copyright
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page's headings start at the top level and step down without skipping a level. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS14 | fail | 1 video(s) on the page with no captions on the video and no written transcript on the page: nothing spoken is available as text in any form | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether each video carries captions of its own, timed text on the video itself, judged together with whether the page holds a written transcript. What good looks like Captions carried on the video. A WARNING means the video has no captions but a written transcript on the page holds the words. A FAIL means neither exists, so nothing spoken is available as text in any form; that total absence is marked here once, not spread across two findings. Why it matters Spoken content that exists only as sound is invisible to a reader, human or machine: nothing said in the video can be found, read or quoted. What we found on this page 1 video(s) on the page with no captions on the video and no written transcript on the page: nothing spoken is available as text in any form The evidence, taken from the page as served Each video on the page, as served: its code, source file and caption track
No caption track on the video and no transcript link on the page. <video id="video6393621631112" data-embed="default" class="video-js" controls=""/> Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: captions carried on the video. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS16 | warning | 1 media resource(s) are named as a technical code, not human-meaningful words, so a machine cannot tell what the resource is from its name | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The name a video, audio clip or image is served under, and whether it is human-meaningful words or a technical code. What good looks like Video, audio and image files carry names made of words that say what they are, not a technical code. Why it matters A resource named as a code or a bare number says nothing about what it is, so a machine cataloguing it has only the code to go on. What we found on this page 1 media resource(s) are named as a technical code, not human-meaningful words, so a machine cannot tell what the resource is from its name The evidence, taken from the page as served The media resources whose name is a technical code, as served
A meaningful name (words that say what it is) lets a machine identify the resource; a code or a bare number cannot. <video id="video6393621631112" data-embed="default" class="video-js" controls=""/> | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| DS28 | fail | one link to sources on other sites was refused when it was checked. The page is still published, but the other site turns away requests that do not come from a person using a browser. It is listed in the view | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check For a single page, the share of its links to OTHER sites, sampled, that lead nowhere. The site's own links are assessed separately. What good looks like The page's references to other sites open for any reader. Where one refuses or has gone, the page carries the fact itself, shows the reference as plain text rather than as a link, or points to a source that answers. Why it matters The outside sources this page offers as support did not answer when they were asked for, so what the page claims is left resting on material that does not come back. In a regulated setting, where a link is carrying a figure or a required statement, that is the difference between a claim that is evidenced and one that is merely asserted. What we found on this page one link to sources on other sites was refused when it was checked. The page is still published, but the other site turns away requests that do not come from a person using a browser. It is listed in the view The evidence, taken from the page as served The external links checked on this page, with the status each returned
A link that did not open appears here in two forms. A DEAD link points at a page that has gone. A REFUSED link points at a page that is still published, but the other site turns away requests that do not come from a person using a browser, so our request was declined. Both land in the same place: the material this page offers as its support did not come back when it was asked for. The consequence is not a matter of tidiness. Where a link carries the weight of a claim, a figure, a policy or a regulatory statement, and the target does not open, the support behind that claim is missing at the moment it is needed. Three things follow, and each of them costs the organisation. The same fact gets taken from somewhere else, which hands a third party control of how the claim is worded. Or the claim is treated as unsupported and set aside. Or an answer is drawn from what remains on the page, and a partial account is presented as a complete one. A refused link is the worst of the three, because the page still reads as though the evidence sits one step away, so the gap is invisible and the answer carries false confidence. A refusal by another site is still this site's matter to resolve, because this site chose to rest a claim on it. Three practical ways close it. Carry the fact being relied on in the page's own words, so the claim stands without the visit. Keep the reference but stop making it a link, showing the address as plain text, so nothing promises a route that does not open. Or point to a source that answers any reader. Where the reference has to stay live, say beside it what a reader will meet, so no one is sent to a closed door without warning.
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page's references to other sites open for any reader. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 15 out of a possible 5, because it is one of the checks that decide whether content can be reached and read at all, so it carries the heaviest weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| DS03 | fail | an AI crawler asking for this page is refused by the security layer in front of the site, while an ordinary browser is served, so the page's content never reaches the AI and answers about it are left to memory or guesswork | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The same page loads for a browser but is refused when the request names itself as an AI service. What good looks like The page returns the same response to a named AI service as to a browser, with no edge block. Why it matters The block sits in front of the site and leaves no trace in its own logs, so the estate is closed off unnoticed. What we found on this page an AI crawler asking for this page is refused by the security layer in front of the site, while an ordinary browser is served, so the page's content never reaches the AI and answers about it are left to memory or guesswork The evidence, taken from the page as served The estate's edge tested with each AI crawler: a browser is served, the crawlers are refused
Hostwww.aviva.com · resolves to 23.215.224.114 · an Akamai edge hostname
Address trailwww.aviva.com › cert10.uk.aviva.com.ksd.edgekey.net › e5059.ksd.akamaiedge.net
Checked2026-07-31 16:33 UTC · request sent from 10.100.100.212 (our checker)
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page returns the same response to a named AI service as to a browser, with no edge block. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 5 out of a possible 5, because it is one of the checks that decide whether content can be reached and read at all, so it carries the heaviest weight in the figure for this item. Why it moves the misinformation reading This failure is a real and common route to a wrong answer for the content it affects, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT16 | warning | the page carries no structured data block stating what it is (not required; a hygiene signal) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The page carries structured data, the machine-readable summary of what it describes. What good looks like The page carries structured data summarising what it describes. Why it matters Vendors document this as optional rather than required, so its absence is a small forfeit and no more. What we found on this page the page carries no structured data block stating what it is (not required; a hygiene signal) The evidence, taken from the page as served The head of this page, as served
The page was read for a structured data block describing what the page is. <head> <title>Social media and Brand - Aviva plc</title> <script defer="defer" type="text/javascript" src="https://rum.hlx.page/.rum/@adobe/helix-rum-js@%5E2/dist/rum-standalone.js" data-routing="env=prod,tier=publish,ams=Aviva Group"/> <link rel="preconnect" href="https://static.aviva.io/"/> <link rel="preconnect" href="https://static.aviva.io/" crossorigin="anonymous"/> <link rel="preconnect" href="https://dpm.demdex.net/"/> <link rel="preconnect" href="https://assets.adobedtm.com/"/> <link rel="preload" href="https://static.aviva.io/assets/fonts/sourcesans3-variable-roman-base.woff2" as="font" crossorigin="anonymous"/> <link rel="preload" href="https://cdn-ukwest.onetrust.com/scripttemplates/otSDKStub.js" as="script" crossorigin="anonymous"/> <link rel="preload" href="https://static.aviva.io/assets/fonts/avivacurve-regular.woff2" as="font" crossorigin="anonymous"/> <meta content="width=device-width,initial-scale=1" name="viewport"/> <meta property="templatename" content="featurelitepage"/> <meta property="article:published_time" content="2022-12-07T02:59:00"/> <meta property="og:description" content="Explore our Aviva Brand images, films, podcasts and social media."/> <meta propโฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR13 | warning | the page does not mark out its main content, so what is unique to this page cannot be told apart from the menus and foot-of-page text repeated across the site | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page's main content is marked off from the navigation and footer around it. What good looks like A main or article region marks the primary content off from the navigation and footer around it. Why it matters Pulling the page's text returns menus and legal footers mixed with the substance, so the answer arrives buried in noise. What we found on this page the page does not mark out its main content, so what is unique to this page cannot be told apart from the menus and foot-of-page text repeated across the site The evidence, taken from the page as served The blocks this page marks out, as served
The page was read for the block that marks out its main content. <meta itemprop="name" content="Photography and social media"/> <meta itemprop="url" content="https://www.aviva.com/newsroom/resources-overview/photography-and-social-media/"/> <div class="l-whole-page" data-back-to-top="Back to start of main content" data-component="back-to-top-es6"> <script> <span data-module="app/init-es6" data-module-load="true"/> <script id="js-init" src="https://static.aviva.io/assets/themes-managed/v6.1.0/shared/extensions/requirejs/init.js" asynโฆ <script src="https://static.aviva.io/etc.clientlibs/settings/wcm/designs/aviva-corporate/clientlibs/resources/2-20260728โฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS01 | fail | 1 of 1 boxes in the page's forms carry no name saying what each is for, so which answer belongs in which box rests on layout alone | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Each box, dropdown and text area in a form carries a name saying what it is for. What good looks like Each field in a form carries a name saying what it is for. Why it matters Unnamed fields leave the tie between a question and its box resting on layout, which shifts as the page reflows. What we found on this page 1 of 1 boxes in the page's forms carry no name saying what each is for, so which answer belongs in which box rests on layout alone The evidence, taken from the page as served The form boxes that carry no name, as served
<input type="search" name="q" id="search-site" value="" class="m-site-search__input" placeholder="Enter a keyword"/> Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: each field in a form carries a name saying what it is for. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS10 | fail | the page's first heading is not its top-level heading, so the structure starts part way down | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check A page's headings start at the top level and step down without skipping a level. What good looks like The page's headings start at the top level and step down without skipping a level. Why it matters Content under a skipped level has no clear parent section, so structure taken from the page misplaces its text. What we found on this page the page's first heading is not its top-level heading, so the structure starts part way down The evidence, taken from the page as served The page's heading outline, in document order (a jump in level is marked)
H3 Recommendation to reject "mini-tender" offers by Litani LLC level jumped H1 Photography and social media H2 Explore page H2 Our brand H2 Social media accounts H2 Login or register H2 Site navigation H3 About us H4 Our purpose and priorities H4 Our customers and people H4 Our Board and Executives H4 2025 Annual Report H4 Get support H3 Investors H4 Strategy and performance H4 Institutional investors H4 Shareholder services H4 Corporate governance H4 Risk governance and management H4 2025 Annual Report H4 Get support H3 Newsroom H4 News and research H4 Resources H4 About Aviva H4 Get support H3 Careers H4 Careers at Aviva H4 Life at Aviva H4 Diversity and inclusion H4 Get support H3 Sustainability H4 Sustainability at Aviva H4 Sustainability news H4 Sustainability resources H4 Aviva Foundation H4 Get support H4 Get support H2 Footer H3 Useful information H4 Products in our locations H4 Use MyAviva H4 How to make a complaint H3 On this site H3 Media H3 Corporate H3 Other links H3 Social H3 Legal H3 Copyright
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page's headings start at the top level and step down without skipping a level. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT34 | fail | the page's own words are thin: 335 of its 358 words are shared navigation and footer, so it reads as 91% identical to another page, which a machine can then take as a duplicate and pass over, missing the little content that is its own; the matching page is named in the view | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether a page's own words are so few against a large shared navigation and footer that it reads as near-identical to other pages. What good looks like A page carries enough of its own words that a shared navigation and footer do not make it read as a copy of other pages. Why it matters When shared furniture is most of the text, distinct pages look like copies of each other and the little real content is easily passed over. What we found on this page the page's own words are thin: 335 of its 358 words are shared navigation and footer, so it reads as 91% identical to another page, which a machine can then take as a duplicate and pass over, missing the little content that is its own; the matching page is named in the view The evidence, taken from the page as served This page's own words, lost in shared navigation and footer
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: a page carries enough of its own words that a shared navigation and footer do not make it read as a copy of other pages. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 1 out of a possible 5, because it is one of the supporting checks, so it carries the lightest weight in the figure for this item. Why it moves the misinformation reading This failure is a real and common route to a wrong answer for the content it affects, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| DS03 | fail | an AI crawler asking for this page is refused by the security layer in front of the site, while an ordinary browser is served, so the page's content never reaches the AI and answers about it are left to memory or guesswork | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The same page loads for a browser but is refused when the request names itself as an AI service. What good looks like The page returns the same response to a named AI service as to a browser, with no edge block. Why it matters The block sits in front of the site and leaves no trace in its own logs, so the estate is closed off unnoticed. What we found on this page an AI crawler asking for this page is refused by the security layer in front of the site, while an ordinary browser is served, so the page's content never reaches the AI and answers about it are left to memory or guesswork The evidence, taken from the page as served The estate's edge tested with each AI crawler: a browser is served, the crawlers are refused
Hostwww.aviva.com · resolves to 23.215.224.114 · an Akamai edge hostname
Address trailwww.aviva.com › cert10.uk.aviva.com.ksd.edgekey.net › e5059.ksd.akamaiedge.net
Checked2026-07-31 16:33 UTC · request sent from 10.100.100.212 (our checker)
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page returns the same response to a named AI service as to a browser, with no edge block. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 5 out of a possible 5, because it is one of the checks that decide whether content can be reached and read at all, so it carries the heaviest weight in the figure for this item. Why it moves the misinformation reading This failure is a real and common route to a wrong answer for the content it affects, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT32 | warning | length 48 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The meta description's length is usable, between 50 and 170 characters. What good looks like The meta description's length is usable, long enough to say something and short enough not to be cut. Why it matters Too short says nothing and too long gets cut, so the summary field is spent without doing its job. What we found on this page length 48 The evidence, taken from the page as served The page's description, as served
<meta name="description" content="Contact information for our Sustainability team."/> | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT16 | warning | the page carries no structured data block stating what it is (not required; a hygiene signal) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The page carries structured data, the machine-readable summary of what it describes. What good looks like The page carries structured data summarising what it describes. Why it matters Vendors document this as optional rather than required, so its absence is a small forfeit and no more. What we found on this page the page carries no structured data block stating what it is (not required; a hygiene signal) The evidence, taken from the page as served The head of this page, as served
The page was read for a structured data block describing what the page is. <head> <title>Sustainability contacts - Aviva plc</title> <script defer="defer" type="text/javascript" src="https://rum.hlx.page/.rum/@adobe/helix-rum-js@%5E2/dist/rum-standalone.js" data-routing="env=prod,tier=publish,ams=Aviva Group"/> <link rel="preconnect" href="https://static.aviva.io/"/> <link rel="preconnect" href="https://static.aviva.io/" crossorigin="anonymous"/> <link rel="preconnect" href="https://dpm.demdex.net/"/> <link rel="preconnect" href="https://assets.adobedtm.com/"/> <link rel="preload" href="https://static.aviva.io/assets/fonts/sourcesans3-variable-roman-base.woff2" as="font" crossorigin="anonymous"/> <link rel="preload" href="https://cdn-ukwest.onetrust.com/scripttemplates/otSDKStub.js" as="script" crossorigin="anonymous"/> <link rel="preload" href="https://static.aviva.io/assets/fonts/avivacurve-regular.woff2" as="font" crossorigin="anonymous"/> <meta content="width=device-width,initial-scale=1" name="viewport"/> <meta property="templatename" content="featurelitepage"/> <meta property="article:published_time" content="2021-05-05T16:58:40"/> <meta property="og:description" content="Contact information for our Sustainability team."/> <meta property="og:title" โฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR13 | warning | the page does not mark out its main content, so what is unique to this page cannot be told apart from the menus and foot-of-page text repeated across the site | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page's main content is marked off from the navigation and footer around it. What good looks like A main or article region marks the primary content off from the navigation and footer around it. Why it matters Pulling the page's text returns menus and legal footers mixed with the substance, so the answer arrives buried in noise. What we found on this page the page does not mark out its main content, so what is unique to this page cannot be told apart from the menus and foot-of-page text repeated across the site The evidence, taken from the page as served The blocks this page marks out, as served
The page was read for the block that marks out its main content. <meta itemprop="name" content="Sustainability contacts"/> <meta itemprop="url" content="https://www.aviva.com/sustainability/sustainability-resources-overview/contact-us/"/> <div class="l-whole-page" data-back-to-top="Back to start of main content" data-component="back-to-top-es6"> <script> <span data-module="app/init-es6" data-module-load="true"/> <script id="js-init" src="https://static.aviva.io/assets/themes-managed/v6.1.0/shared/extensions/requirejs/init.js" asynโฆ <script src="https://static.aviva.io/etc.clientlibs/settings/wcm/designs/aviva-corporate/clientlibs/resources/2-20260728โฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS01 | fail | 1 of 1 boxes in the page's forms carry no name saying what each is for, so which answer belongs in which box rests on layout alone | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Each box, dropdown and text area in a form carries a name saying what it is for. What good looks like Each field in a form carries a name saying what it is for. Why it matters Unnamed fields leave the tie between a question and its box resting on layout, which shifts as the page reflows. What we found on this page 1 of 1 boxes in the page's forms carry no name saying what each is for, so which answer belongs in which box rests on layout alone The evidence, taken from the page as served The form boxes that carry no name, as served
<input type="search" name="q" id="search-site" value="" class="m-site-search__input" placeholder="Enter a keyword"/> Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: each field in a form carries a name saying what it is for. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS08 | fail | 1 link wording(s) are used for more than one destination, so the same words point at different pages: โsustainabilityโ; the links are listed in the view | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Links that share exactly the same wording on one page while pointing at different destinations. What good looks like Links that share the same wording lead to the same destination. Why it matters The wording no longer settles the target, so the wrong one gets followed at the point where the choice matters. What we found on this page 1 link wording(s) are used for more than one destination, so the same words point at different pages: โsustainabilityโ; the links are listed in the view The evidence, taken from the page as served Links that share the same text but point to different destinations, as served
<a class="a-breadcrumb-page" itemprop="item" href="/sustainability/">Sustainability</a> <a class="a-button a-button--tertiary" href="/ARCHIVE/social-purpose/"> Sustainability </a> Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: links that share the same wording lead to the same destination. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS10 | fail | the page's first heading is not its top-level heading, so the structure starts part way down | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check A page's headings start at the top level and step down without skipping a level. What good looks like The page's headings start at the top level and step down without skipping a level. Why it matters Content under a skipped level has no clear parent section, so structure taken from the page misplaces its text. What we found on this page the page's first heading is not its top-level heading, so the structure starts part way down The evidence, taken from the page as served The page's heading outline, in document order (a jump in level is marked)
H3 Recommendation to reject "mini-tender" offers by Litani LLC level jumped H1 Sustainability contacts H2 Explore page H2 Contact information for our Sustainability team H2 Leah Ramoutar H2 David Schofield H2 Claudine Blamey H2 Other contact details H2 General counsel H2 Media contacts H2 Investor and shareholder contacts H2 Manage your shares H2 Login or register H2 Site navigation H3 About us H4 Our purpose and priorities H4 Our customers and people H4 Our Board and Executives H4 2025 Annual Report H4 Get support H3 Investors H4 Strategy and performance H4 Institutional investors H4 Shareholder services H4 Corporate governance H4 Risk governance and management H4 2025 Annual Report H4 Get support H3 Newsroom H4 News and research H4 Resources H4 About Aviva H4 Get support H3 Careers H4 Careers at Aviva H4 Life at Aviva H4 Diversity and inclusion H4 Get support H3 Sustainability H4 Sustainability at Aviva H4 Sustainability news H4 Sustainability resources H4 Aviva Foundation H4 Get support H4 Get support H2 Footer H3 Useful information H4 Products in our locations H4 Use MyAviva H4 How to make a complaint H3 On this site H3 Media H3 Corporate H3 Other links H3 Social H3 Legal H3 Copyright
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page's headings start at the top level and step down without skipping a level. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT34 | fail | the page's own words are thin: 336 of its 358 words are shared navigation and footer, so it reads as 91% identical to another page, which a machine can then take as a duplicate and pass over, missing the little content that is its own; the matching page is named in the view | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether a page's own words are so few against a large shared navigation and footer that it reads as near-identical to other pages. What good looks like A page carries enough of its own words that a shared navigation and footer do not make it read as a copy of other pages. Why it matters When shared furniture is most of the text, distinct pages look like copies of each other and the little real content is easily passed over. What we found on this page the page's own words are thin: 336 of its 358 words are shared navigation and footer, so it reads as 91% identical to another page, which a machine can then take as a duplicate and pass over, missing the little content that is its own; the matching page is named in the view The evidence, taken from the page as served This page's own words, lost in shared navigation and footer
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: a page carries enough of its own words that a shared navigation and footer do not make it read as a copy of other pages. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 1 out of a possible 5, because it is one of the supporting checks, so it carries the lightest weight in the figure for this item. Why it moves the misinformation reading This failure is a real and common route to a wrong answer for the content it affects, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| DS03 | fail | an AI crawler asking for this page is refused by the security layer in front of the site, while an ordinary browser is served, so the page's content never reaches the AI and answers about it are left to memory or guesswork | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The same page loads for a browser but is refused when the request names itself as an AI service. What good looks like The page returns the same response to a named AI service as to a browser, with no edge block. Why it matters The block sits in front of the site and leaves no trace in its own logs, so the estate is closed off unnoticed. What we found on this page an AI crawler asking for this page is refused by the security layer in front of the site, while an ordinary browser is served, so the page's content never reaches the AI and answers about it are left to memory or guesswork The evidence, taken from the page as served The estate's edge tested with each AI crawler: a browser is served, the crawlers are refused
Hostwww.aviva.com · resolves to 23.215.224.114 · an Akamai edge hostname
Address trailwww.aviva.com › cert10.uk.aviva.com.ksd.edgekey.net › e5059.ksd.akamaiedge.net
Checked2026-07-31 16:33 UTC · request sent from 10.100.100.212 (our checker)
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page returns the same response to a named AI service as to a browser, with no edge block. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 5 out of a possible 5, because it is one of the checks that decide whether content can be reached and read at all, so it carries the heaviest weight in the figure for this item. Why it moves the misinformation reading This failure is a real and common route to a wrong answer for the content it affects, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT16 | warning | the page carries no structured data block stating what it is (not required; a hygiene signal) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The page carries structured data, the machine-readable summary of what it describes. What good looks like The page carries structured data summarising what it describes. Why it matters Vendors document this as optional rather than required, so its absence is a small forfeit and no more. What we found on this page the page carries no structured data block stating what it is (not required; a hygiene signal) The evidence, taken from the page as served The head of this page, as served
The page was read for a structured data block describing what the page is. <head> <title>Corporate contacts - Aviva plc</title> <script defer="defer" type="text/javascript" src="https://rum.hlx.page/.rum/@adobe/helix-rum-js@%5E2/dist/rum-standalone.js" data-routing="env=prod,tier=publish,ams=Aviva Group"/> <link rel="preconnect" href="https://static.aviva.io/"/> <link rel="preconnect" href="https://static.aviva.io/" crossorigin="anonymous"/> <link rel="preconnect" href="https://dpm.demdex.net/"/> <link rel="preconnect" href="https://assets.adobedtm.com/"/> <link rel="preload" href="https://static.aviva.io/assets/fonts/sourcesans3-variable-roman-base.woff2" as="font" crossorigin="anonymous"/> <link rel="preload" href="https://cdn-ukwest.onetrust.com/scripttemplates/otSDKStub.js" as="script" crossorigin="anonymous"/> <link rel="preload" href="https://static.aviva.io/assets/fonts/avivacurve-regular.woff2" as="font" crossorigin="anonymous"/> <meta content="width=device-width,initial-scale=1" name="viewport"/> <meta property="templatename" content="standardpage"/> <meta property="article:published_time" content="2026-06-23T08:00:00"/> <meta property="og:description" content="Customer and company contacts, Aviva plc registered address and social media accounts.โฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR13 | warning | the page does not mark out its main content, so what is unique to this page cannot be told apart from the menus and foot-of-page text repeated across the site | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page's main content is marked off from the navigation and footer around it. What good looks like A main or article region marks the primary content off from the navigation and footer around it. Why it matters Pulling the page's text returns menus and legal footers mixed with the substance, so the answer arrives buried in noise. What we found on this page the page does not mark out its main content, so what is unique to this page cannot be told apart from the menus and foot-of-page text repeated across the site The evidence, taken from the page as served The blocks this page marks out, as served
The page was read for the block that marks out its main content. <meta itemprop="name" content="Corporate contacts"/> <meta itemprop="url" content="https://www.aviva.com/corporate-contacts/"/> <div class="l-whole-page" data-back-to-top="Back to start of main content" data-component="back-to-top-es6"> <script> <span data-module="app/init-es6" data-module-load="true"/> <script id="js-init" src="https://static.aviva.io/assets/themes-managed/v6.1.0/shared/extensions/requirejs/init.js" asynโฆ <script src="https://static.aviva.io/etc.clientlibs/settings/wcm/designs/aviva-corporate/clientlibs/resources/2-20260728โฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS01 | fail | 1 of 1 boxes in the page's forms carry no name saying what each is for, so which answer belongs in which box rests on layout alone | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Each box, dropdown and text area in a form carries a name saying what it is for. What good looks like Each field in a form carries a name saying what it is for. Why it matters Unnamed fields leave the tie between a question and its box resting on layout, which shifts as the page reflows. What we found on this page 1 of 1 boxes in the page's forms carry no name saying what each is for, so which answer belongs in which box rests on layout alone The evidence, taken from the page as served The form boxes that carry no name, as served
<input type="search" name="q" id="search-site" value="" class="m-site-search__input" placeholder="Enter a keyword"/> Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: each field in a form carries a name saying what it is for. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS08 | fail | 1 link wording(s) are used for more than one destination, so the same words point at different pages: โcareersโ; the links are listed in the view | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Links that share exactly the same wording on one page while pointing at different destinations. What good looks like Links that share the same wording lead to the same destination. Why it matters The wording no longer settles the target, so the wrong one gets followed at the point where the choice matters. What we found on this page 1 link wording(s) are used for more than one destination, so the same words point at different pages: โcareersโ; the links are listed in the view The evidence, taken from the page as served Links that share the same text but point to different destinations, as served
<a aria-describedby="1668f858-44ad-4bff-bbe7-61c081221d40" class="m-card__link" href="/careers/careers-at-aviva-overview/job-search/">Careers</a> <a class="a-button a-button--tertiary" href="/careers/"> Careers </a> Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: links that share the same wording lead to the same destination. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS10 | fail | the page's first heading is not its top-level heading, so the structure starts part way down | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check A page's headings start at the top level and step down without skipping a level. What good looks like The page's headings start at the top level and step down without skipping a level. Why it matters Content under a skipped level has no clear parent section, so structure taken from the page misplaces its text. What we found on this page the page's first heading is not its top-level heading, so the structure starts part way down The evidence, taken from the page as served The page's heading outline, in document order (a jump in level is marked)
H3 Recommendation to reject "mini-tender" offers by Litani LLC level jumped H1 Corporate contacts H2 Explore page H2 How can customers contact us? H3 Aviva UK H3 Aviva Ireland H3 Aviva Canada H3 Aviva Investors H3 MyAviva H3 UK complaints H2 Company contacts H3 Investors and shareholders H3 Media H3 Sustainability H2 Registered address H3 Aviva plc head office H2 Social media accounts H2 More contacts H3 Careers H3 Heritage H3 Privacy policy H3 Innovation H2 Login or register H2 Site navigation H3 About us H4 Our purpose and priorities H4 Our customers and people H4 Our Board and Executives H4 2025 Annual Report H4 Get support H3 Investors H4 Strategy and performance H4 Institutional investors H4 Shareholder services H4 Corporate governance H4 Risk governance and management H4 2025 Annual Report H4 Get support H3 Newsroom H4 News and research H4 Resources H4 About Aviva H4 Get support H3 Careers H4 Careers at Aviva H4 Life at Aviva H4 Diversity and inclusion H4 Get support H3 Sustainability H4 Sustainability at Aviva H4 Sustainability news H4 Sustainability resources H4 Aviva Foundation H4 Get support H4 Get support H2 Footer H3 Useful information H4 Products in our locations H4 Use MyAviva H4 How to make a complaint H3 On this site H3 Media H3 Corporate H3 Other links H3 Social H3 Legal H3 Copyright
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page's headings start at the top level and step down without skipping a level. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT34 | fail | the page's own words are thin: 336 of its 404 words are shared navigation and footer, so it reads as 82% identical to another page, which a machine can then take as a duplicate and pass over, missing the little content that is its own; the matching page is named in the view | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether a page's own words are so few against a large shared navigation and footer that it reads as near-identical to other pages. What good looks like A page carries enough of its own words that a shared navigation and footer do not make it read as a copy of other pages. Why it matters When shared furniture is most of the text, distinct pages look like copies of each other and the little real content is easily passed over. What we found on this page the page's own words are thin: 336 of its 404 words are shared navigation and footer, so it reads as 82% identical to another page, which a machine can then take as a duplicate and pass over, missing the little content that is its own; the matching page is named in the view The evidence, taken from the page as served This page's own words, lost in shared navigation and footer
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: a page carries enough of its own words that a shared navigation and footer do not make it read as a copy of other pages. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 1 out of a possible 5, because it is one of the supporting checks, so it carries the lightest weight in the figure for this item. Why it moves the misinformation reading This failure is a real and common route to a wrong answer for the content it affects, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| DS03 | fail | an AI crawler asking for this page is refused by the security layer in front of the site, while an ordinary browser is served, so the page's content never reaches the AI and answers about it are left to memory or guesswork | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The same page loads for a browser but is refused when the request names itself as an AI service. What good looks like The page returns the same response to a named AI service as to a browser, with no edge block. Why it matters The block sits in front of the site and leaves no trace in its own logs, so the estate is closed off unnoticed. What we found on this page an AI crawler asking for this page is refused by the security layer in front of the site, while an ordinary browser is served, so the page's content never reaches the AI and answers about it are left to memory or guesswork The evidence, taken from the page as served The estate's edge tested with each AI crawler: a browser is served, the crawlers are refused
Hostwww.aviva.com · resolves to 23.215.224.114 · an Akamai edge hostname
Address trailwww.aviva.com › cert10.uk.aviva.com.ksd.edgekey.net › e5059.ksd.akamaiedge.net
Checked2026-07-31 16:33 UTC · request sent from 10.100.100.212 (our checker)
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page returns the same response to a named AI service as to a browser, with no edge block. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 5 out of a possible 5, because it is one of the checks that decide whether content can be reached and read at all, so it carries the heaviest weight in the figure for this item. Why it moves the misinformation reading This failure is a real and common route to a wrong answer for the content it affects, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT16 | warning | the page carries no structured data block stating what it is (not required; a hygiene signal) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The page carries structured data, the machine-readable summary of what it describes. What good looks like The page carries structured data summarising what it describes. Why it matters Vendors document this as optional rather than required, so its absence is a small forfeit and no more. What we found on this page the page carries no structured data block stating what it is (not required; a hygiene signal) The evidence, taken from the page as served The head of this page, as served
The page was read for a structured data block describing what the page is. <head> <title>News and research overview - Aviva plc</title> <script defer="defer" type="text/javascript" src="https://rum.hlx.page/.rum/@adobe/helix-rum-js@%5E2/dist/rum-standalone.js" data-routing="env=prod,tier=publish,ams=Aviva Group"/> <link rel="preconnect" href="https://static.aviva.io/"/> <link rel="preconnect" href="https://static.aviva.io/" crossorigin="anonymous"/> <link rel="preconnect" href="https://dpm.demdex.net/"/> <link rel="preconnect" href="https://assets.adobedtm.com/"/> <link rel="preload" href="https://static.aviva.io/assets/fonts/sourcesans3-variable-roman-base.woff2" as="font" crossorigin="anonymous"/> <link rel="preload" href="https://cdn-ukwest.onetrust.com/scripttemplates/otSDKStub.js" as="script" crossorigin="anonymous"/> <link rel="preload" href="https://static.aviva.io/assets/fonts/avivacurve-regular.woff2" as="font" crossorigin="anonymous"/> <meta content="width=device-width,initial-scale=1" name="viewport"/> <meta property="templatename" content="categorypage"/> <meta property="article:published_time" content="2026-07-09T20:19:40"/> <meta property="og:description" content="This page brings together links to help you explore Avivaรขยยs news and researcโฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR13 | warning | the page does not mark out its main content, so what is unique to this page cannot be told apart from the menus and foot-of-page text repeated across the site | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page's main content is marked off from the navigation and footer around it. What good looks like A main or article region marks the primary content off from the navigation and footer around it. Why it matters Pulling the page's text returns menus and legal footers mixed with the substance, so the answer arrives buried in noise. What we found on this page the page does not mark out its main content, so what is unique to this page cannot be told apart from the menus and foot-of-page text repeated across the site The evidence, taken from the page as served The blocks this page marks out, as served
The page was read for the block that marks out its main content. <meta itemprop="name" content="News and research overview"/> <meta itemprop="url" content="https://www.aviva.com/newsroom/news-and-research-overview/"/> <div class="l-whole-page" data-back-to-top="Back to start of main content" data-component="back-to-top-es6"> <script> <span data-module="app/init-es6" data-module-load="true"/> <script id="js-init" src="https://static.aviva.io/assets/themes-managed/v6.1.0/shared/extensions/requirejs/init.js" asynโฆ <script src="https://static.aviva.io/etc.clientlibs/settings/wcm/designs/aviva-corporate/clientlibs/resources/2-20260728โฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS01 | fail | 1 of 1 boxes in the page's forms carry no name saying what each is for, so which answer belongs in which box rests on layout alone | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Each box, dropdown and text area in a form carries a name saying what it is for. What good looks like Each field in a form carries a name saying what it is for. Why it matters Unnamed fields leave the tie between a question and its box resting on layout, which shifts as the page reflows. What we found on this page 1 of 1 boxes in the page's forms carry no name saying what each is for, so which answer belongs in which box rests on layout alone The evidence, taken from the page as served The form boxes that carry no name, as served
<input type="search" name="q" id="search-site" value="" class="m-site-search__input" placeholder="Enter a keyword"/> Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: each field in a form carries a name saying what it is for. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS10 | fail | the page's first heading is not its top-level heading, so the structure starts part way down | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check A page's headings start at the top level and step down without skipping a level. What good looks like The page's headings start at the top level and step down without skipping a level. Why it matters Content under a skipped level has no clear parent section, so structure taken from the page misplaces its text. What we found on this page the page's first heading is not its top-level heading, so the structure starts part way down The evidence, taken from the page as served The page's heading outline, in document order (a jump in level is marked)
H3 Recommendation to reject "mini-tender" offers by Litani LLC level jumped H1 News and research H2 Information for journalists and researchers H3 Features and insight H3 Media contacts H3 About Aviva H3 Latest results H2 Explore our other Newsroom pages H3 Resources H3 Search news releases H2 Login or register H2 Site navigation H3 About us H4 Our purpose and priorities H4 Our customers and people H4 Our Board and Executives H4 2025 Annual Report H4 Get support H3 Investors H4 Strategy and performance H4 Institutional investors H4 Shareholder services H4 Corporate governance H4 Risk governance and management H4 2025 Annual Report H4 Get support H3 Newsroom H4 News and research H4 Resources H4 About Aviva H4 Get support H3 Careers H4 Careers at Aviva H4 Life at Aviva H4 Diversity and inclusion H4 Get support H3 Sustainability H4 Sustainability at Aviva H4 Sustainability news H4 Sustainability resources H4 Aviva Foundation H4 Get support H4 Get support H2 Footer H3 Useful information H4 Products in our locations H4 Use MyAviva H4 How to make a complaint H3 On this site H3 Media H3 Corporate H3 Other links H3 Social H3 Legal H3 Copyright
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page's headings start at the top level and step down without skipping a level. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT34 | fail | the page's own words are thin: 336 of its 351 words are shared navigation and footer, so it reads as 96% identical to another page, which a machine can then take as a duplicate and pass over, missing the little content that is its own; the matching page is named in the view | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether a page's own words are so few against a large shared navigation and footer that it reads as near-identical to other pages. What good looks like A page carries enough of its own words that a shared navigation and footer do not make it read as a copy of other pages. Why it matters When shared furniture is most of the text, distinct pages look like copies of each other and the little real content is easily passed over. What we found on this page the page's own words are thin: 336 of its 351 words are shared navigation and footer, so it reads as 96% identical to another page, which a machine can then take as a duplicate and pass over, missing the little content that is its own; the matching page is named in the view The evidence, taken from the page as served This page's own words, lost in shared navigation and footer
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: a page carries enough of its own words that a shared navigation and footer do not make it read as a copy of other pages. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 1 out of a possible 5, because it is one of the supporting checks, so it carries the lightest weight in the figure for this item. Why it moves the misinformation reading This failure is a real and common route to a wrong answer for the content it affects, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| DS03 | fail | an AI crawler asking for this page is refused by the security layer in front of the site, while an ordinary browser is served, so the page's content never reaches the AI and answers about it are left to memory or guesswork | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The same page loads for a browser but is refused when the request names itself as an AI service. What good looks like The page returns the same response to a named AI service as to a browser, with no edge block. Why it matters The block sits in front of the site and leaves no trace in its own logs, so the estate is closed off unnoticed. What we found on this page an AI crawler asking for this page is refused by the security layer in front of the site, while an ordinary browser is served, so the page's content never reaches the AI and answers about it are left to memory or guesswork The evidence, taken from the page as served The estate's edge tested with each AI crawler: a browser is served, the crawlers are refused
Hostwww.aviva.com · resolves to 23.215.224.114 · an Akamai edge hostname
Address trailwww.aviva.com › cert10.uk.aviva.com.ksd.edgekey.net › e5059.ksd.akamaiedge.net
Checked2026-07-31 16:33 UTC · request sent from 10.100.100.212 (our checker)
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page returns the same response to a named AI service as to a browser, with no edge block. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 5 out of a possible 5, because it is one of the checks that decide whether content can be reached and read at all, so it carries the heaviest weight in the figure for this item. Why it moves the misinformation reading This failure is a real and common route to a wrong answer for the content it affects, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT09 | fail | 1 skipped heading level(s) in document order | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Heading levels step down one at a time, rather than jumping from an H2 straight to an H5. What good looks like Heading levels step down one at a time, without jumping a level. Why it matters A skipped level breaks the trail that says which section a passage belongs to, so it is filed under the wrong one. What we found on this page 1 skipped heading level(s) in document order The evidence, taken from the page as served The page's heading outline, in document order (a jump in level is marked)
H3 Recommendation to reject "mini-tender" offers by Litani LLC H1 Manage your shares H2 Explore page H2 Manage your shareholding online at the Investor Centre H6 *Currency restrictions apply to dividends paid outside of the UK and Eurozone level jumped H2 Contacting us about your shares H2 Share dealing H2 Manage your shares FAQs H2 More for shareholders H2 Shareholder updates H2 Communication H2 Shareholder meetings and archives H2 Share capital H2 Login or register H2 Site navigation H3 About us H4 Our purpose and priorities H4 Our customers and people H4 Our Board and Executives H4 2025 Annual Report H4 Get support H3 Investors H4 Strategy and performance H4 Institutional investors H4 Shareholder services H4 Corporate governance H4 Risk governance and management H4 2025 Annual Report H4 Get support H3 Newsroom H4 News and research H4 Resources H4 About Aviva H4 Get support H3 Careers H4 Careers at Aviva H4 Life at Aviva H4 Diversity and inclusion H4 Get support H3 Sustainability H4 Sustainability at Aviva H4 Sustainability news H4 Sustainability resources H4 Aviva Foundation H4 Get support H4 Get support H2 Footer H3 Useful information H4 Products in our locations H4 Use MyAviva H4 How to make a complaint H3 On this site H3 Media H3 Corporate H3 Other links H3 Social H3 Legal H3 Copyright
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: heading levels step down one at a time, without jumping a level. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT16 | warning | the page carries no structured data block stating what it is (not required; a hygiene signal) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The page carries structured data, the machine-readable summary of what it describes. What good looks like The page carries structured data summarising what it describes. Why it matters Vendors document this as optional rather than required, so its absence is a small forfeit and no more. What we found on this page the page carries no structured data block stating what it is (not required; a hygiene signal) The evidence, taken from the page as served The head of this page, as served
The page was read for a structured data block describing what the page is. <head> <title>Manage your shares - Aviva plc</title> <script defer="defer" type="text/javascript" src="https://rum.hlx.page/.rum/@adobe/helix-rum-js@%5E2/dist/rum-standalone.js" data-routing="env=prod,tier=publish,ams=Aviva Group"/> <link rel="preconnect" href="https://static.aviva.io/"/> <link rel="preconnect" href="https://static.aviva.io/" crossorigin="anonymous"/> <link rel="preconnect" href="https://dpm.demdex.net/"/> <link rel="preconnect" href="https://assets.adobedtm.com/"/> <link rel="preload" href="https://static.aviva.io/assets/fonts/sourcesans3-variable-roman-base.woff2" as="font" crossorigin="anonymous"/> <link rel="preload" href="https://cdn-ukwest.onetrust.com/scripttemplates/otSDKStub.js" as="script" crossorigin="anonymous"/> <link rel="preload" href="https://static.aviva.io/assets/fonts/avivacurve-regular.woff2" as="font" crossorigin="anonymous"/> <meta content="width=device-width,initial-scale=1" name="viewport"/> <meta property="templatename" content="featurepage"/> <meta property="article:published_time" content="2021-07-15T02:30:00"/> <meta property="og:description" content="Contacts and helpful information for managing your shares."/> <meta property="og:title"โฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR13 | warning | the page does not mark out its main content, so what is unique to this page cannot be told apart from the menus and foot-of-page text repeated across the site | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page's main content is marked off from the navigation and footer around it. What good looks like A main or article region marks the primary content off from the navigation and footer around it. Why it matters Pulling the page's text returns menus and legal footers mixed with the substance, so the answer arrives buried in noise. What we found on this page the page does not mark out its main content, so what is unique to this page cannot be told apart from the menus and foot-of-page text repeated across the site The evidence, taken from the page as served The blocks this page marks out, as served
The page was read for the block that marks out its main content. <meta itemprop="name" content="Manage your shares"/> <meta itemprop="url" content="https://www.aviva.com/investors/shareholder-services-overview/manage-your-shares/"/> <div class="l-whole-page" data-back-to-top="Back to start of main content" data-component="back-to-top-es6"> <script> <span data-module="app/init-es6" data-module-load="true"/> <script id="js-init" src="https://static.aviva.io/assets/themes-managed/v6.1.0/shared/extensions/requirejs/init.js" asynโฆ <script src="https://static.aviva.io/etc.clientlibs/settings/wcm/designs/aviva-corporate/clientlibs/resources/2-20260728โฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS01 | fail | 1 of 1 boxes in the page's forms carry no name saying what each is for, so which answer belongs in which box rests on layout alone | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Each box, dropdown and text area in a form carries a name saying what it is for. What good looks like Each field in a form carries a name saying what it is for. Why it matters Unnamed fields leave the tie between a question and its box resting on layout, which shifts as the page reflows. What we found on this page 1 of 1 boxes in the page's forms carry no name saying what each is for, so which answer belongs in which box rests on layout alone The evidence, taken from the page as served The form boxes that carry no name, as served
<input type="search" name="q" id="search-site" value="" class="m-site-search__input" placeholder="Enter a keyword"/> Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: each field in a form carries a name saying what it is for. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS08 | fail | 1 link wording(s) are used for more than one destination, so the same words point at different pages: โsee your terms and conditionsโ; the links are listed in the view | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Links that share exactly the same wording on one page while pointing at different destinations. What good looks like Links that share the same wording lead to the same destination. Why it matters The wording no longer settles the target, so the wrong one gets followed at the point where the choice matters. What we found on this page 1 link wording(s) are used for more than one destination, so the same words point at different pages: โsee your terms and conditionsโ; the links are listed in the view The evidence, taken from the page as served Links that share the same text but point to different destinations, as served
<a title="See terms and conditions" href="https://www-uk.computershare.com/Investor/#Help/ImportantInfo" style="background-color: rgb(255,255,255);">See your terms and conditions</a> <a title="opens computershare investors terms and conditions" href="https://www-us.computershare.com/Investor/TermsAndConditions" style="background-color: rgb(255,255,255);">See your terms and conditions</a> Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: links that share the same wording lead to the same destination. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS10 | fail | the page's first heading is not its top-level heading, so the structure starts part way down; the heading structure skips a level in 1 place(s), so the order does not follow | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check A page's headings start at the top level and step down without skipping a level. What good looks like The page's headings start at the top level and step down without skipping a level. Why it matters Content under a skipped level has no clear parent section, so structure taken from the page misplaces its text. What we found on this page the page's first heading is not its top-level heading, so the structure starts part way down; the heading structure skips a level in 1 place(s), so the order does not follow The evidence, taken from the page as served The page's heading outline, in document order (a jump in level is marked)
H3 Recommendation to reject "mini-tender" offers by Litani LLC level jumped H1 Manage your shares H2 Explore page H2 Manage your shareholding online at the Investor Centre H6 *Currency restrictions apply to dividends paid outside of the UK and Eurozone level jumped H2 Contacting us about your shares H2 Share dealing H2 Manage your shares FAQs H2 More for shareholders H2 Shareholder updates H2 Communication H2 Shareholder meetings and archives H2 Share capital H2 Login or register H2 Site navigation H3 About us H4 Our purpose and priorities H4 Our customers and people H4 Our Board and Executives H4 2025 Annual Report H4 Get support H3 Investors H4 Strategy and performance H4 Institutional investors H4 Shareholder services H4 Corporate governance H4 Risk governance and management H4 2025 Annual Report H4 Get support H3 Newsroom H4 News and research H4 Resources H4 About Aviva H4 Get support H3 Careers H4 Careers at Aviva H4 Life at Aviva H4 Diversity and inclusion H4 Get support H3 Sustainability H4 Sustainability at Aviva H4 Sustainability news H4 Sustainability resources H4 Aviva Foundation H4 Get support H4 Get support H2 Footer H3 Useful information H4 Products in our locations H4 Use MyAviva H4 How to make a complaint H3 On this site H3 Media H3 Corporate H3 Other links H3 Social H3 Legal H3 Copyright
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page's headings start at the top level and step down without skipping a level. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| DS03 | fail | an AI crawler asking for this page is refused by the security layer in front of the site, while an ordinary browser is served, so the page's content never reaches the AI and answers about it are left to memory or guesswork | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The same page loads for a browser but is refused when the request names itself as an AI service. What good looks like The page returns the same response to a named AI service as to a browser, with no edge block. Why it matters The block sits in front of the site and leaves no trace in its own logs, so the estate is closed off unnoticed. What we found on this page an AI crawler asking for this page is refused by the security layer in front of the site, while an ordinary browser is served, so the page's content never reaches the AI and answers about it are left to memory or guesswork The evidence, taken from the page as served The estate's edge tested with each AI crawler: a browser is served, the crawlers are refused
Hostwww.aviva.com · resolves to 23.215.224.114 · an Akamai edge hostname
Address trailwww.aviva.com › cert10.uk.aviva.com.ksd.edgekey.net › e5059.ksd.akamaiedge.net
Checked2026-07-31 16:33 UTC · request sent from 10.100.100.212 (our checker)
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page returns the same response to a named AI service as to a browser, with no edge block. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 5 out of a possible 5, because it is one of the checks that decide whether content can be reached and read at all, so it carries the heaviest weight in the figure for this item. Why it moves the misinformation reading This failure is a real and common route to a wrong answer for the content it affects, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT16 | warning | the page carries no structured data block stating what it is (not required; a hygiene signal) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The page carries structured data, the machine-readable summary of what it describes. What good looks like The page carries structured data summarising what it describes. Why it matters Vendors document this as optional rather than required, so its absence is a small forfeit and no more. What we found on this page the page carries no structured data block stating what it is (not required; a hygiene signal) The evidence, taken from the page as served The head of this page, as served
The page was read for a structured data block describing what the page is. <head> <title>Our people - Aviva plc</title> <script defer="defer" type="text/javascript" src="https://rum.hlx.page/.rum/@adobe/helix-rum-js@%5E2/dist/rum-standalone.js" data-routing="env=prod,tier=publish,ams=Aviva Group"/> <link rel="preconnect" href="https://static.aviva.io/"/> <link rel="preconnect" href="https://static.aviva.io/" crossorigin="anonymous"/> <link rel="preconnect" href="https://dpm.demdex.net/"/> <link rel="preconnect" href="https://assets.adobedtm.com/"/> <link rel="preload" href="https://static.aviva.io/assets/fonts/sourcesans3-variable-roman-base.woff2" as="font" crossorigin="anonymous"/> <link rel="preload" href="https://cdn-ukwest.onetrust.com/scripttemplates/otSDKStub.js" as="script" crossorigin="anonymous"/> <link rel="preload" href="https://static.aviva.io/assets/fonts/avivacurve-regular.woff2" as="font" crossorigin="anonymous"/> <meta content="width=device-width,initial-scale=1" name="viewport"/> <meta property="templatename" content="featurelitepage"/> <meta property="article:published_time" content="2021-07-15T03:58:26"/> <meta property="og:description" content="Our people bring our purpose to life รขยย making things better for our customers, communitieโฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR13 | warning | the page does not mark out its main content, so what is unique to this page cannot be told apart from the menus and foot-of-page text repeated across the site | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page's main content is marked off from the navigation and footer around it. What good looks like A main or article region marks the primary content off from the navigation and footer around it. Why it matters Pulling the page's text returns menus and legal footers mixed with the substance, so the answer arrives buried in noise. What we found on this page the page does not mark out its main content, so what is unique to this page cannot be told apart from the menus and foot-of-page text repeated across the site The evidence, taken from the page as served The blocks this page marks out, as served
The page was read for the block that marks out its main content. <meta itemprop="name" content="Our people"/> <meta itemprop="url" content="https://www.aviva.com/about-us/our-customers-and-people-overview/our-people/"/> <div class="l-whole-page" data-back-to-top="Back to start of main content" data-component="back-to-top-es6"> <script> <span data-module="app/init-es6" data-module-load="true"/> <script id="js-init" src="https://static.aviva.io/assets/themes-managed/v6.1.0/shared/extensions/requirejs/init.js" asynโฆ <script src="https://static.aviva.io/etc.clientlibs/settings/wcm/designs/aviva-corporate/clientlibs/resources/2-20260728โฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS01 | fail | 1 of 1 boxes in the page's forms carry no name saying what each is for, so which answer belongs in which box rests on layout alone | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Each box, dropdown and text area in a form carries a name saying what it is for. What good looks like Each field in a form carries a name saying what it is for. Why it matters Unnamed fields leave the tie between a question and its box resting on layout, which shifts as the page reflows. What we found on this page 1 of 1 boxes in the page's forms carry no name saying what each is for, so which answer belongs in which box rests on layout alone The evidence, taken from the page as served The form boxes that carry no name, as served
<input type="search" name="q" id="search-site" value="" class="m-site-search__input" placeholder="Enter a keyword"/> Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: each field in a form carries a name saying what it is for. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS10 | fail | the page's first heading is not its top-level heading, so the structure starts part way down | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check A page's headings start at the top level and step down without skipping a level. What good looks like The page's headings start at the top level and step down without skipping a level. Why it matters Content under a skipped level has no clear parent section, so structure taken from the page misplaces its text. What we found on this page the page's first heading is not its top-level heading, so the structure starts part way down The evidence, taken from the page as served The page's heading outline, in document order (a jump in level is marked)
H3 Recommendation to reject "mini-tender" offers by Litani LLC level jumped H1 Our people H2 Explore page H2 Our people are Aviva H2 Our culture and values H3 Commitment H3 Community H3 Confidence H3 Care H2 Developing careers H2 Great Place to Work H2 Doing the right thing for our people H2 Aviva is for everyone H3 Transcriptย for video This is me H2 Health and wellbeing H3 Being a Living Wage employer H3 Equal paid parental leave H2 Meet our people H2 The one who hosts tea H2 The one who studies storms H2 The one who found balance H2 The one who never thought sheรขยยd work for an insurer H2 Login or register H2 Site navigation H3 About us H4 Our purpose and priorities H4 Our customers and people H4 Our Board and Executives H4 2025 Annual Report H4 Get support H3 Investors H4 Strategy and performance H4 Institutional investors H4 Shareholder services H4 Corporate governance H4 Risk governance and management H4 2025 Annual Report H4 Get support H3 Newsroom H4 News and research H4 Resources H4 About Aviva H4 Get support H3 Careers H4 Careers at Aviva H4 Life at Aviva H4 Diversity and inclusion H4 Get support H3 Sustainability H4 Sustainability at Aviva H4 Sustainability news H4 Sustainability resources H4 Aviva Foundation H4 Get support H4 Get support H2 Footer H3 Useful information H4 Products in our locations H4 Use MyAviva H4 How to make a complaint H3 On this site H3 Media H3 Corporate H3 Other links H3 Social H3 Legal H3 Copyright
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page's headings start at the top level and step down without skipping a level. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS14 | fail | 1 video(s) on the page with no captions on the video and no written transcript on the page: nothing spoken is available as text in any form | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether each video carries captions of its own, timed text on the video itself, judged together with whether the page holds a written transcript. What good looks like Captions carried on the video. A WARNING means the video has no captions but a written transcript on the page holds the words. A FAIL means neither exists, so nothing spoken is available as text in any form; that total absence is marked here once, not spread across two findings. Why it matters Spoken content that exists only as sound is invisible to a reader, human or machine: nothing said in the video can be found, read or quoted. What we found on this page 1 video(s) on the page with no captions on the video and no written transcript on the page: nothing spoken is available as text in any form The evidence, taken from the page as served Each video on the page, as served: its code, source file and caption track
No caption track on the video and no transcript link on the page. <video id="video6373223685112" data-embed="default" class="video-js" controls=""/> Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: captions carried on the video. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS16 | warning | 1 media resource(s) are named as a technical code, not human-meaningful words, so a machine cannot tell what the resource is from its name | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The name a video, audio clip or image is served under, and whether it is human-meaningful words or a technical code. What good looks like Video, audio and image files carry names made of words that say what they are, not a technical code. Why it matters A resource named as a code or a bare number says nothing about what it is, so a machine cataloguing it has only the code to go on. What we found on this page 1 media resource(s) are named as a technical code, not human-meaningful words, so a machine cannot tell what the resource is from its name The evidence, taken from the page as served The media resources whose name is a technical code, as served
A meaningful name (words that say what it is) lets a machine identify the resource; a code or a bare number cannot. <video id="video6373223685112" data-embed="default" class="video-js" controls=""/> | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| DS03 | fail | an AI crawler asking for this page is refused by the security layer in front of the site, while an ordinary browser is served, so the page's content never reaches the AI and answers about it are left to memory or guesswork | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The same page loads for a browser but is refused when the request names itself as an AI service. What good looks like The page returns the same response to a named AI service as to a browser, with no edge block. Why it matters The block sits in front of the site and leaves no trace in its own logs, so the estate is closed off unnoticed. What we found on this page an AI crawler asking for this page is refused by the security layer in front of the site, while an ordinary browser is served, so the page's content never reaches the AI and answers about it are left to memory or guesswork The evidence, taken from the page as served The estate's edge tested with each AI crawler: a browser is served, the crawlers are refused
Hostwww.aviva.com · resolves to 23.215.224.114 · an Akamai edge hostname
Address trailwww.aviva.com › cert10.uk.aviva.com.ksd.edgekey.net › e5059.ksd.akamaiedge.net
Checked2026-07-31 16:33 UTC · request sent from 10.100.100.212 (our checker)
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page returns the same response to a named AI service as to a browser, with no edge block. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 5 out of a possible 5, because it is one of the checks that decide whether content can be reached and read at all, so it carries the heaviest weight in the figure for this item. Why it moves the misinformation reading This failure is a real and common route to a wrong answer for the content it affects, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT09 | fail | 1 skipped heading level(s) in document order | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Heading levels step down one at a time, rather than jumping from an H2 straight to an H5. What good looks like Heading levels step down one at a time, without jumping a level. Why it matters A skipped level breaks the trail that says which section a passage belongs to, so it is filed under the wrong one. What we found on this page 1 skipped heading level(s) in document order The evidence, taken from the page as served The page's heading outline, in document order (a jump in level is marked)
H3 Recommendation to reject "mini-tender" offers by Litani LLC H1 Results, presentations and reports H2 Explore page H2 Featured H2 Latest H2 Results H4 14 May 2026: Q1 2026 Trading Update รขยย for three months ending 31 March 2026 level jumped H2 Archive H2 Results H2 Presentations H2 Reports H2 Our sustainability reports and policies H2 Login or register H2 Site navigation H3 About us H4 Our purpose and priorities H4 Our customers and people H4 Our Board and Executives H4 2025 Annual Report H4 Get support H3 Investors H4 Strategy and performance H4 Institutional investors H4 Shareholder services H4 Corporate governance H4 Risk governance and management H4 2025 Annual Report H4 Get support H3 Newsroom H4 News and research H4 Resources H4 About Aviva H4 Get support H3 Careers H4 Careers at Aviva H4 Life at Aviva H4 Diversity and inclusion H4 Get support H3 Sustainability H4 Sustainability at Aviva H4 Sustainability news H4 Sustainability resources H4 Aviva Foundation H4 Get support H4 Get support H2 Footer H3 Useful information H4 Products in our locations H4 Use MyAviva H4 How to make a complaint H3 On this site H3 Media H3 Corporate H3 Other links H3 Social H3 Legal H3 Copyright
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: heading levels step down one at a time, without jumping a level. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT16 | warning | the page carries no structured data block stating what it is (not required; a hygiene signal) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The page carries structured data, the machine-readable summary of what it describes. What good looks like The page carries structured data summarising what it describes. Why it matters Vendors document this as optional rather than required, so its absence is a small forfeit and no more. What we found on this page the page carries no structured data block stating what it is (not required; a hygiene signal) The evidence, taken from the page as served The head of this page, as served
The page was read for a structured data block describing what the page is. <head> <title>Our results, presentations and reports - Aviva plc</title> <script defer="defer" type="text/javascript" src="https://rum.hlx.page/.rum/@adobe/helix-rum-js@%5E2/dist/rum-standalone.js" data-routing="env=prod,tier=publish,ams=Aviva Group"/> <link rel="preconnect" href="https://static.aviva.io/"/> <link rel="preconnect" href="https://static.aviva.io/" crossorigin="anonymous"/> <link rel="preconnect" href="https://dpm.demdex.net/"/> <link rel="preconnect" href="https://assets.adobedtm.com/"/> <link rel="preload" href="https://static.aviva.io/assets/fonts/sourcesans3-variable-roman-base.woff2" as="font" crossorigin="anonymous"/> <link rel="preload" href="https://cdn-ukwest.onetrust.com/scripttemplates/otSDKStub.js" as="script" crossorigin="anonymous"/> <link rel="preload" href="https://static.aviva.io/assets/fonts/avivacurve-regular.woff2" as="font" crossorigin="anonymous"/> <meta content="width=device-width,initial-scale=1" name="viewport"/> <meta property="templatename" content="featurepage"/> <meta property="article:published_time" content="2024-07-16T11:00:00"/> <meta property="og:description" content="View the latest or look back through our results, presentations andโฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR13 | warning | the page does not mark out its main content, so what is unique to this page cannot be told apart from the menus and foot-of-page text repeated across the site | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page's main content is marked off from the navigation and footer around it. What good looks like A main or article region marks the primary content off from the navigation and footer around it. Why it matters Pulling the page's text returns menus and legal footers mixed with the substance, so the answer arrives buried in noise. What we found on this page the page does not mark out its main content, so what is unique to this page cannot be told apart from the menus and foot-of-page text repeated across the site The evidence, taken from the page as served The blocks this page marks out, as served
The page was read for the block that marks out its main content. <meta itemprop="name" content="Results, presentations and reports"/> <meta itemprop="url" content="https://www.aviva.com/investors/strategy-and-performance-overview/results-presentations-reโฆ <div class="l-whole-page" data-back-to-top="Back to start of main content" data-component="back-to-top-es6"> <script> <span data-module="app/init-es6" data-module-load="true"/> <script id="js-init" src="https://static.aviva.io/assets/themes-managed/v6.1.0/shared/extensions/requirejs/init.js" asynโฆ <script src="https://static.aviva.io/etc.clientlibs/settings/wcm/designs/aviva-corporate/clientlibs/resources/2-20260728โฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS01 | fail | 1 of 1 boxes in the page's forms carry no name saying what each is for, so which answer belongs in which box rests on layout alone | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Each box, dropdown and text area in a form carries a name saying what it is for. What good looks like Each field in a form carries a name saying what it is for. Why it matters Unnamed fields leave the tie between a question and its box resting on layout, which shifts as the page reflows. What we found on this page 1 of 1 boxes in the page's forms carry no name saying what each is for, so which answer belongs in which box rests on layout alone The evidence, taken from the page as served The form boxes that carry no name, as served
<input type="search" name="q" id="search-site" value="" class="m-site-search__input" placeholder="Enter a keyword"/> Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: each field in a form carries a name saying what it is for. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS08 | fail | 1 link wording(s) are used for more than one destination, so the same words point at different pages: โread more ""โ; the links are listed in the view | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Links that share exactly the same wording on one page while pointing at different destinations. What good looks like Links that share the same wording lead to the same destination. Why it matters The wording no longer settles the target, so the wrong one gets followed at the point where the choice matters. What we found on this page 1 link wording(s) are used for more than one destination, so the same words point at different pages: โread more ""โ; the links are listed in the view The evidence, taken from the page as served Links that share the same text but point to different destinations, as served
<a class="a-button a-button--tertiary " href="/investors/strategy-and-performance-overview/results-presentations-reports/results-archive/"> Read more <span class="u-hidden--visually">""</span> </a> <a class="a-button a-button--tertiary " href="/investors/strategy-and-performance-overview/results-presentations-reports/presentations-archive/"> Read more <span class="u-hidden--visually">""</span> </a> <a class="a-button a-button--tertiary " href="/investors/strategy-and-performance-overview/results-presentations-reports/reports-archive/"> Read more <span class="u-hidden--visually">""</span> </a> Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: links that share the same wording lead to the same destination. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS10 | fail | the page's first heading is not its top-level heading, so the structure starts part way down; the heading structure skips a level in 1 place(s), so the order does not follow | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check A page's headings start at the top level and step down without skipping a level. What good looks like The page's headings start at the top level and step down without skipping a level. Why it matters Content under a skipped level has no clear parent section, so structure taken from the page misplaces its text. What we found on this page the page's first heading is not its top-level heading, so the structure starts part way down; the heading structure skips a level in 1 place(s), so the order does not follow The evidence, taken from the page as served The page's heading outline, in document order (a jump in level is marked)
H3 Recommendation to reject "mini-tender" offers by Litani LLC level jumped H1 Results, presentations and reports H2 Explore page H2 Featured H2 Latest H2 Results H4 14 May 2026: Q1 2026 Trading Update รขยย for three months ending 31 March 2026 level jumped H2 Archive H2 Results H2 Presentations H2 Reports H2 Our sustainability reports and policies H2 Login or register H2 Site navigation H3 About us H4 Our purpose and priorities H4 Our customers and people H4 Our Board and Executives H4 2025 Annual Report H4 Get support H3 Investors H4 Strategy and performance H4 Institutional investors H4 Shareholder services H4 Corporate governance H4 Risk governance and management H4 2025 Annual Report H4 Get support H3 Newsroom H4 News and research H4 Resources H4 About Aviva H4 Get support H3 Careers H4 Careers at Aviva H4 Life at Aviva H4 Diversity and inclusion H4 Get support H3 Sustainability H4 Sustainability at Aviva H4 Sustainability news H4 Sustainability resources H4 Aviva Foundation H4 Get support H4 Get support H2 Footer H3 Useful information H4 Products in our locations H4 Use MyAviva H4 How to make a complaint H3 On this site H3 Media H3 Corporate H3 Other links H3 Social H3 Legal H3 Copyright
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page's headings start at the top level and step down without skipping a level. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT34 | fail | the page's own words are thin: 336 of its 350 words are shared navigation and footer, so it reads as 94% identical to another page, which a machine can then take as a duplicate and pass over, missing the little content that is its own; the matching page is named in the view | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether a page's own words are so few against a large shared navigation and footer that it reads as near-identical to other pages. What good looks like A page carries enough of its own words that a shared navigation and footer do not make it read as a copy of other pages. Why it matters When shared furniture is most of the text, distinct pages look like copies of each other and the little real content is easily passed over. What we found on this page the page's own words are thin: 336 of its 350 words are shared navigation and footer, so it reads as 94% identical to another page, which a machine can then take as a duplicate and pass over, missing the little content that is its own; the matching page is named in the view The evidence, taken from the page as served This page's own words, lost in shared navigation and footer
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: a page carries enough of its own words that a shared navigation and footer do not make it read as a copy of other pages. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 1 out of a possible 5, because it is one of the supporting checks, so it carries the lightest weight in the figure for this item. Why it moves the misinformation reading This failure is a real and common route to a wrong answer for the content it affects, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| DS03 | fail | an AI crawler asking for this page is refused by the security layer in front of the site, while an ordinary browser is served, so the page's content never reaches the AI and answers about it are left to memory or guesswork | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The same page loads for a browser but is refused when the request names itself as an AI service. What good looks like The page returns the same response to a named AI service as to a browser, with no edge block. Why it matters The block sits in front of the site and leaves no trace in its own logs, so the estate is closed off unnoticed. What we found on this page an AI crawler asking for this page is refused by the security layer in front of the site, while an ordinary browser is served, so the page's content never reaches the AI and answers about it are left to memory or guesswork The evidence, taken from the page as served The estate's edge tested with each AI crawler: a browser is served, the crawlers are refused
Hostwww.aviva.com · resolves to 23.215.224.114 · an Akamai edge hostname
Address trailwww.aviva.com › cert10.uk.aviva.com.ksd.edgekey.net › e5059.ksd.akamaiedge.net
Checked2026-07-31 16:33 UTC · request sent from 10.100.100.212 (our checker)
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page returns the same response to a named AI service as to a browser, with no edge block. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 5 out of a possible 5, because it is one of the checks that decide whether content can be reached and read at all, so it carries the heaviest weight in the figure for this item. Why it moves the misinformation reading This failure is a real and common route to a wrong answer for the content it affects, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT16 | warning | the page carries no structured data block stating what it is (not required; a hygiene signal) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The page carries structured data, the machine-readable summary of what it describes. What good looks like The page carries structured data summarising what it describes. Why it matters Vendors document this as optional rather than required, so its absence is a small forfeit and no more. What we found on this page the page carries no structured data block stating what it is (not required; a hygiene signal) The evidence, taken from the page as served The head of this page, as served
The page was read for a structured data block describing what the page is. <head> <title>Sustainability resources and reporting hub - Aviva plc</title> <script defer="defer" type="text/javascript" src="https://rum.hlx.page/.rum/@adobe/helix-rum-js@%5E2/dist/rum-standalone.js" data-routing="env=prod,tier=publish,ams=Aviva Group"/> <link rel="preconnect" href="https://static.aviva.io/"/> <link rel="preconnect" href="https://static.aviva.io/" crossorigin="anonymous"/> <link rel="preconnect" href="https://dpm.demdex.net/"/> <link rel="preconnect" href="https://assets.adobedtm.com/"/> <link rel="preload" href="https://static.aviva.io/assets/fonts/sourcesans3-variable-roman-base.woff2" as="font" crossorigin="anonymous"/> <link rel="preload" href="https://cdn-ukwest.onetrust.com/scripttemplates/otSDKStub.js" as="script" crossorigin="anonymous"/> <link rel="preload" href="https://static.aviva.io/assets/fonts/avivacurve-regular.woff2" as="font" crossorigin="anonymous"/> <meta content="width=device-width,initial-scale=1" name="viewport"/> <meta property="templatename" content="featurepage"/> <meta property="article:published_time" content="2021-05-05T16:58:34"/> <meta property="og:description" content="Read and download our latest reports, policies, and resources tโฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR13 | warning | the page does not mark out its main content, so what is unique to this page cannot be told apart from the menus and foot-of-page text repeated across the site | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page's main content is marked off from the navigation and footer around it. What good looks like A main or article region marks the primary content off from the navigation and footer around it. Why it matters Pulling the page's text returns menus and legal footers mixed with the substance, so the answer arrives buried in noise. What we found on this page the page does not mark out its main content, so what is unique to this page cannot be told apart from the menus and foot-of-page text repeated across the site The evidence, taken from the page as served The blocks this page marks out, as served
The page was read for the block that marks out its main content. <meta itemprop="name" content="Sustainability resources and reporting hub"/> <meta itemprop="url" content="https://www.aviva.com/sustainability/sustainability-resources-overview/resources-and-reporโฆ <div class="l-whole-page" data-back-to-top="Back to start of main content" data-component="back-to-top-es6"> <script> <span data-module="app/init-es6" data-module-load="true"/> <script id="js-init" src="https://static.aviva.io/assets/themes-managed/v6.1.0/shared/extensions/requirejs/init.js" asynโฆ <script src="https://static.aviva.io/etc.clientlibs/settings/wcm/designs/aviva-corporate/clientlibs/resources/2-20260728โฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS01 | fail | 1 of 1 boxes in the page's forms carry no name saying what each is for, so which answer belongs in which box rests on layout alone | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Each box, dropdown and text area in a form carries a name saying what it is for. What good looks like Each field in a form carries a name saying what it is for. Why it matters Unnamed fields leave the tie between a question and its box resting on layout, which shifts as the page reflows. What we found on this page 1 of 1 boxes in the page's forms carry no name saying what each is for, so which answer belongs in which box rests on layout alone The evidence, taken from the page as served The form boxes that carry no name, as served
<input type="search" name="q" id="search-site" value="" class="m-site-search__input" placeholder="Enter a keyword"/> Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: each field in a form carries a name saying what it is for. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS08 | fail | 1 link wording(s) are used for more than one destination, so the same words point at different pages: โsustainabilityโ; the links are listed in the view | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Links that share exactly the same wording on one page while pointing at different destinations. What good looks like Links that share the same wording lead to the same destination. Why it matters The wording no longer settles the target, so the wrong one gets followed at the point where the choice matters. What we found on this page 1 link wording(s) are used for more than one destination, so the same words point at different pages: โsustainabilityโ; the links are listed in the view The evidence, taken from the page as served Links that share the same text but point to different destinations, as served
<a class="a-breadcrumb-page" itemprop="item" href="/sustainability/">Sustainability</a> <a class="a-button a-button--tertiary" href="/ARCHIVE/social-purpose/"> Sustainability </a> Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: links that share the same wording lead to the same destination. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS10 | fail | the page's first heading is not its top-level heading, so the structure starts part way down | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check A page's headings start at the top level and step down without skipping a level. What good looks like The page's headings start at the top level and step down without skipping a level. Why it matters Content under a skipped level has no clear parent section, so structure taken from the page misplaces its text. What we found on this page the page's first heading is not its top-level heading, so the structure starts part way down The evidence, taken from the page as served The page's heading outline, in document order (a jump in level is marked)
H3 Recommendation to reject "mini-tender" offers by Litani LLC level jumped H1 Sustainability resources and reporting hub H2 Explore page H2 Our sustainability reports H2 Our partnership impact reports H2 Our thought leadership reports H2 Sustainability policies H3 Sustainability Business Standard H3 Aviva Biodiversity Policy H3 Human Rights Policy H3 Modern Slavery Act Statement H3 Aviva Investment and Underwriting Baseline Exclusions Policy H3 Aviva IWR Sustainable Investing Policy H2 Other policies and reports H3 The AvivaรขยยฏBusiness Ethics Code 2025 H3 Aviva working with Governments policy H3 Customer Experience Business Standard H3 Aviva Data Privacy Statement H3 UK Customer Data Charter H3 Procurement and Outsourcing Business Standard H3 Aviva Sustainable Procurement Statement H3 Prevention of Bribery and Corruption Statement H3 Aviva Group Gifts and Entertainment Procedures รขยย July 2020 H3 Speak Up Charter H3 Health, safety and security H3 Other reports H2 Governance H3 Customer Conduct and Reputation Committee ToRs H3 Aviva Third Party Business Code of Behaviour H3 Global Voting Policy H3 Tax Strategy H2 Responses H2 Archive H2 Login or register H2 Site navigation H3 About us H4 Our purpose and priorities H4 Our customers and people H4 Our Board and Executives H4 2025 Annual Report H4 Get support H3 Investors H4 Strategy and performance H4 Institutional investors H4 Shareholder services H4 Corporate governance H4 Risk governance and management H4 2025 Annual Report H4 Get support H3 Newsroom H4 News and research H4 Resources H4 About Aviva H4 Get support H3 Careers H4 Careers at Aviva H4 Life at Aviva H4 Diversity and inclusion H4 Get support H3 Sustainability H4 Sustainability at Aviva H4 Sustainability news H4 Sustainability resources H4 Aviva Foundation H4 Get support H4 Get support H2 Footer H3 Useful information H4 Products in our locations H4 Use MyAviva H4 How to make a complaint H3 On this site H3 Media H3 Corporate H3 Other links H3 Social H3 Legal H3 Copyright
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page's headings start at the top level and step down without skipping a level. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| DS03 | fail | an AI crawler asking for this page is refused by the security layer in front of the site, while an ordinary browser is served, so the page's content never reaches the AI and answers about it are left to memory or guesswork | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The same page loads for a browser but is refused when the request names itself as an AI service. What good looks like The page returns the same response to a named AI service as to a browser, with no edge block. Why it matters The block sits in front of the site and leaves no trace in its own logs, so the estate is closed off unnoticed. What we found on this page an AI crawler asking for this page is refused by the security layer in front of the site, while an ordinary browser is served, so the page's content never reaches the AI and answers about it are left to memory or guesswork The evidence, taken from the page as served The estate's edge tested with each AI crawler: a browser is served, the crawlers are refused
Hostwww.aviva.com · resolves to 23.215.224.114 · an Akamai edge hostname
Address trailwww.aviva.com › cert10.uk.aviva.com.ksd.edgekey.net › e5059.ksd.akamaiedge.net
Checked2026-07-31 16:33 UTC · request sent from 10.100.100.212 (our checker)
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page returns the same response to a named AI service as to a browser, with no edge block. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 5 out of a possible 5, because it is one of the checks that decide whether content can be reached and read at all, so it carries the heaviest weight in the figure for this item. Why it moves the misinformation reading This failure is a real and common route to a wrong answer for the content it affects, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT32 | warning | length 44 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The meta description's length is usable, between 50 and 170 characters. What good looks like The meta description's length is usable, long enough to say something and short enough not to be cut. Why it matters Too short says nothing and too long gets cut, so the summary field is spent without doing its job. What we found on this page length 44 The evidence, taken from the page as served The page's description, as served
<meta name="description" content="Explore what sustainability at Aviva means. "/> | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT16 | warning | the page carries no structured data block stating what it is (not required; a hygiene signal) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The page carries structured data, the machine-readable summary of what it describes. What good looks like The page carries structured data summarising what it describes. Why it matters Vendors document this as optional rather than required, so its absence is a small forfeit and no more. What we found on this page the page carries no structured data block stating what it is (not required; a hygiene signal) The evidence, taken from the page as served The head of this page, as served
The page was read for a structured data block describing what the page is. <head> <title>Sustainability - Aviva plc</title> <script defer="defer" type="text/javascript" src="https://rum.hlx.page/.rum/@adobe/helix-rum-js@%5E2/dist/rum-standalone.js" data-routing="env=prod,tier=publish,ams=Aviva Group"/> <link rel="preconnect" href="https://static.aviva.io/"/> <link rel="preconnect" href="https://static.aviva.io/" crossorigin="anonymous"/> <link rel="preconnect" href="https://dpm.demdex.net/"/> <link rel="preconnect" href="https://assets.adobedtm.com/"/> <link rel="preload" href="https://static.aviva.io/assets/fonts/sourcesans3-variable-roman-base.woff2" as="font" crossorigin="anonymous"/> <link rel="preload" href="https://cdn-ukwest.onetrust.com/scripttemplates/otSDKStub.js" as="script" crossorigin="anonymous"/> <link rel="preload" href="https://static.aviva.io/assets/fonts/avivacurve-regular.woff2" as="font" crossorigin="anonymous"/> <meta content="width=device-width,initial-scale=1" name="viewport"/> <meta property="templatename" content="categorypage"/> <meta property="article:published_time" content="2017-10-19T09:24:07"/> <meta property="og:description" content="Explore what sustainability at Aviva means. "/> <meta property="og:title" content="Sustainโฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR13 | warning | the page does not mark out its main content, so what is unique to this page cannot be told apart from the menus and foot-of-page text repeated across the site | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page's main content is marked off from the navigation and footer around it. What good looks like A main or article region marks the primary content off from the navigation and footer around it. Why it matters Pulling the page's text returns menus and legal footers mixed with the substance, so the answer arrives buried in noise. What we found on this page the page does not mark out its main content, so what is unique to this page cannot be told apart from the menus and foot-of-page text repeated across the site The evidence, taken from the page as served The blocks this page marks out, as served
The page was read for the block that marks out its main content. <meta itemprop="name" content="Sustainability"/> <meta itemprop="url" content="https://www.aviva.com/sustainability/"/> <div class="l-whole-page" data-back-to-top="Back to start of main content" data-component="back-to-top-es6"> <script> <span data-module="app/init-es6" data-module-load="true"/> <script id="js-init" src="https://static.aviva.io/assets/themes-managed/v6.1.0/shared/extensions/requirejs/init.js" asynโฆ <script src="https://static.aviva.io/etc.clientlibs/settings/wcm/designs/aviva-corporate/clientlibs/resources/2-20260728โฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS01 | fail | 1 of 1 boxes in the page's forms carry no name saying what each is for, so which answer belongs in which box rests on layout alone | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Each box, dropdown and text area in a form carries a name saying what it is for. What good looks like Each field in a form carries a name saying what it is for. Why it matters Unnamed fields leave the tie between a question and its box resting on layout, which shifts as the page reflows. What we found on this page 1 of 1 boxes in the page's forms carry no name saying what each is for, so which answer belongs in which box rests on layout alone The evidence, taken from the page as served The form boxes that carry no name, as served
<input type="search" name="q" id="search-site" value="" class="m-site-search__input" placeholder="Enter a keyword"/> Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: each field in a form carries a name saying what it is for. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS08 | fail | 1 link wording(s) are used for more than one destination, so the same words point at different pages: โsustainabilityโ; the links are listed in the view | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Links that share exactly the same wording on one page while pointing at different destinations. What good looks like Links that share the same wording lead to the same destination. Why it matters The wording no longer settles the target, so the wrong one gets followed at the point where the choice matters. What we found on this page 1 link wording(s) are used for more than one destination, so the same words point at different pages: โsustainabilityโ; the links are listed in the view The evidence, taken from the page as served Links that share the same text but point to different destinations, as served
<a class="a-breadcrumb-page" itemprop="item" href="/sustainability/" tabindex="-1" aria-current="page">Sustainability</a> <a class="a-button a-button--tertiary" href="/ARCHIVE/social-purpose/"> Sustainability </a> Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: links that share the same wording lead to the same destination. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS10 | fail | the page's first heading is not its top-level heading, so the structure starts part way down | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check A page's headings start at the top level and step down without skipping a level. What good looks like The page's headings start at the top level and step down without skipping a level. Why it matters Content under a skipped level has no clear parent section, so structure taken from the page misplaces its text. What we found on this page the page's first heading is not its top-level heading, so the structure starts part way down The evidence, taken from the page as served The page's heading outline, in document order (a jump in level is marked)
H3 Recommendation to reject "mini-tender" offers by Litani LLC level jumped H1 Sustainability H2 Taking climate action H2 Taking social action H2 Acting as a sustainable business H3 Our sustainability ambition H3 Taking action with our partners H3 Our transition plan H3 Sustainability resources and reporting hub H2 Changing our world for the better takes action H3 Transcriptย for video Avivaรขยยs Sustainability Ambition H2 Our sustainability news H2 We're making a difference H2 Discover more H3 About us H3 Newsroom H3 Investors H2 Login or register H2 Site navigation H3 About us H4 Our purpose and priorities H4 Our customers and people H4 Our Board and Executives H4 2025 Annual Report H4 Get support H3 Investors H4 Strategy and performance H4 Institutional investors H4 Shareholder services H4 Corporate governance H4 Risk governance and management H4 2025 Annual Report H4 Get support H3 Newsroom H4 News and research H4 Resources H4 About Aviva H4 Get support H3 Careers H4 Careers at Aviva H4 Life at Aviva H4 Diversity and inclusion H4 Get support H3 Sustainability H4 Sustainability at Aviva H4 Sustainability news H4 Sustainability resources H4 Aviva Foundation H4 Get support H4 Get support H2 Footer H3 Useful information H4 Products in our locations H4 Use MyAviva H4 How to make a complaint H3 On this site H3 Media H3 Corporate H3 Other links H3 Social H3 Legal H3 Copyright
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page's headings start at the top level and step down without skipping a level. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS14 | fail | 1 video(s) on the page with no captions on the video and no written transcript on the page: nothing spoken is available as text in any form | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether each video carries captions of its own, timed text on the video itself, judged together with whether the page holds a written transcript. What good looks like Captions carried on the video. A WARNING means the video has no captions but a written transcript on the page holds the words. A FAIL means neither exists, so nothing spoken is available as text in any form; that total absence is marked here once, not spread across two findings. Why it matters Spoken content that exists only as sound is invisible to a reader, human or machine: nothing said in the video can be found, read or quoted. What we found on this page 1 video(s) on the page with no captions on the video and no written transcript on the page: nothing spoken is available as text in any form The evidence, taken from the page as served Each video on the page, as served: its code, source file and caption track
No caption track on the video and no transcript link on the page. <video id="video6390315810112" data-embed="default" class="video-js" controls=""/> Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: captions carried on the video. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS16 | warning | 1 media resource(s) are named as a technical code, not human-meaningful words, so a machine cannot tell what the resource is from its name | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The name a video, audio clip or image is served under, and whether it is human-meaningful words or a technical code. What good looks like Video, audio and image files carry names made of words that say what they are, not a technical code. Why it matters A resource named as a code or a bare number says nothing about what it is, so a machine cataloguing it has only the code to go on. What we found on this page 1 media resource(s) are named as a technical code, not human-meaningful words, so a machine cannot tell what the resource is from its name The evidence, taken from the page as served The media resources whose name is a technical code, as served
A meaningful name (words that say what it is) lets a machine identify the resource; a code or a bare number cannot. <video id="video6390315810112" data-embed="default" class="video-js" controls=""/> | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| DS03 | fail | an AI crawler asking for this page is refused by the security layer in front of the site, while an ordinary browser is served, so the page's content never reaches the AI and answers about it are left to memory or guesswork | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The same page loads for a browser but is refused when the request names itself as an AI service. What good looks like The page returns the same response to a named AI service as to a browser, with no edge block. Why it matters The block sits in front of the site and leaves no trace in its own logs, so the estate is closed off unnoticed. What we found on this page an AI crawler asking for this page is refused by the security layer in front of the site, while an ordinary browser is served, so the page's content never reaches the AI and answers about it are left to memory or guesswork The evidence, taken from the page as served The estate's edge tested with each AI crawler: a browser is served, the crawlers are refused
Hostwww.aviva.com · resolves to 23.215.224.114 · an Akamai edge hostname
Address trailwww.aviva.com › cert10.uk.aviva.com.ksd.edgekey.net › e5059.ksd.akamaiedge.net
Checked2026-07-31 16:33 UTC · request sent from 10.100.100.212 (our checker)
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page returns the same response to a named AI service as to a browser, with no edge block. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 5 out of a possible 5, because it is one of the checks that decide whether content can be reached and read at all, so it carries the heaviest weight in the figure for this item. Why it moves the misinformation reading This failure is a real and common route to a wrong answer for the content it affects, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT16 | warning | the page carries no structured data block stating what it is (not required; a hygiene signal) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The page carries structured data, the machine-readable summary of what it describes. What good looks like The page carries structured data summarising what it describes. Why it matters Vendors document this as optional rather than required, so its absence is a small forfeit and no more. What we found on this page the page carries no structured data block stating what it is (not required; a hygiene signal) The evidence, taken from the page as served The head of this page, as served
The page was read for a structured data block describing what the page is. <head> <title>Our strategy - Aviva plc</title> <script defer="defer" type="text/javascript" src="https://rum.hlx.page/.rum/@adobe/helix-rum-js@%5E2/dist/rum-standalone.js" data-routing="env=prod,tier=publish,ams=Aviva Group"/> <link rel="preconnect" href="https://static.aviva.io/"/> <link rel="preconnect" href="https://static.aviva.io/" crossorigin="anonymous"/> <link rel="preconnect" href="https://dpm.demdex.net/"/> <link rel="preconnect" href="https://assets.adobedtm.com/"/> <link rel="preload" href="https://static.aviva.io/assets/fonts/sourcesans3-variable-roman-base.woff2" as="font" crossorigin="anonymous"/> <link rel="preload" href="https://cdn-ukwest.onetrust.com/scripttemplates/otSDKStub.js" as="script" crossorigin="anonymous"/> <link rel="preload" href="https://static.aviva.io/assets/fonts/avivacurve-regular.woff2" as="font" crossorigin="anonymous"/> <meta content="width=device-width,initial-scale=1" name="viewport"/> <meta property="templatename" content="featurelitepage"/> <meta property="article:published_time" content="2025-02-27T09:00:00"/> <meta property="og:description" content="Consistent strategy with strong performance momentum."/> <meta property="og:title" contenโฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR13 | warning | the page does not mark out its main content, so what is unique to this page cannot be told apart from the menus and foot-of-page text repeated across the site | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page's main content is marked off from the navigation and footer around it. What good looks like A main or article region marks the primary content off from the navigation and footer around it. Why it matters Pulling the page's text returns menus and legal footers mixed with the substance, so the answer arrives buried in noise. What we found on this page the page does not mark out its main content, so what is unique to this page cannot be told apart from the menus and foot-of-page text repeated across the site The evidence, taken from the page as served The blocks this page marks out, as served
The page was read for the block that marks out its main content. <meta itemprop="name" content="Investment case and strategy"/> <meta itemprop="url" content="https://www.aviva.com/investors/strategy-and-performance-overview/investment-case-and-straโฆ <div class="l-whole-page" data-back-to-top="Back to start of main content" data-component="back-to-top-es6"> <script> <span data-module="app/init-es6" data-module-load="true"/> <script id="js-init" src="https://static.aviva.io/assets/themes-managed/v6.1.0/shared/extensions/requirejs/init.js" asynโฆ <script src="https://static.aviva.io/etc.clientlibs/settings/wcm/designs/aviva-corporate/clientlibs/resources/2-20260728โฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS01 | fail | 1 of 1 boxes in the page's forms carry no name saying what each is for, so which answer belongs in which box rests on layout alone | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Each box, dropdown and text area in a form carries a name saying what it is for. What good looks like Each field in a form carries a name saying what it is for. Why it matters Unnamed fields leave the tie between a question and its box resting on layout, which shifts as the page reflows. What we found on this page 1 of 1 boxes in the page's forms carry no name saying what each is for, so which answer belongs in which box rests on layout alone The evidence, taken from the page as served The form boxes that carry no name, as served
<input type="search" name="q" id="search-site" value="" class="m-site-search__input" placeholder="Enter a keyword"/> Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: each field in a form carries a name saying what it is for. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS10 | fail | the page's first heading is not its top-level heading, so the structure starts part way down | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check A page's headings start at the top level and step down without skipping a level. What good looks like The page's headings start at the top level and step down without skipping a level. Why it matters Content under a skipped level has no clear parent section, so structure taken from the page misplaces its text. What we found on this page the page's first heading is not its top-level heading, so the structure starts part way down The evidence, taken from the page as served The page's heading outline, in document order (a jump in level is marked)
H3 Recommendation to reject "mini-tender" offers by Litani LLC level jumped H1 Investment case and strategy H2 Explore page H2 Consistent strategy with strong performance momentum H2 Our compelling investment case H2 We have four clear strategic priorities H3 Growth H3 Customer H3 Efficiency H3 Sustainability H2 Group targets H3 Operating earnings per share H3 IFRS return on equity H3 Cash remittances H2 Watch our full year results 2025 video with Group CEO, Amanda Blanc DBE H3 Transcriptย for video Watch our full year results 2025 video with Group CEO, Ama H2 More for investors H3 How weรขยยre organised H3 Annual Report H3 Newsroom H2 Business model H2 Login or register H2 Site navigation H3 About us H4 Our purpose and priorities H4 Our customers and people H4 Our Board and Executives H4 2025 Annual Report H4 Get support H3 Investors H4 Strategy and performance H4 Institutional investors H4 Shareholder services H4 Corporate governance H4 Risk governance and management H4 2025 Annual Report H4 Get support H3 Newsroom H4 News and research H4 Resources H4 About Aviva H4 Get support H3 Careers H4 Careers at Aviva H4 Life at Aviva H4 Diversity and inclusion H4 Get support H3 Sustainability H4 Sustainability at Aviva H4 Sustainability news H4 Sustainability resources H4 Aviva Foundation H4 Get support H4 Get support H2 Footer H3 Useful information H4 Products in our locations H4 Use MyAviva H4 How to make a complaint H3 On this site H3 Media H3 Corporate H3 Other links H3 Social H3 Legal H3 Copyright
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page's headings start at the top level and step down without skipping a level. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS14 | fail | 1 video(s) on the page with no captions on the video and no written transcript on the page: nothing spoken is available as text in any form | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether each video carries captions of its own, timed text on the video itself, judged together with whether the page holds a written transcript. What good looks like Captions carried on the video. A WARNING means the video has no captions but a written transcript on the page holds the words. A FAIL means neither exists, so nothing spoken is available as text in any form; that total absence is marked here once, not spread across two findings. Why it matters Spoken content that exists only as sound is invisible to a reader, human or machine: nothing said in the video can be found, read or quoted. What we found on this page 1 video(s) on the page with no captions on the video and no written transcript on the page: nothing spoken is available as text in any form The evidence, taken from the page as served Each video on the page, as served: its code, source file and caption track
No caption track on the video and no transcript link on the page. <video id="video6390041787112" data-embed="default" class="video-js" controls=""/> Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: captions carried on the video. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS16 | warning | 1 media resource(s) are named as a technical code, not human-meaningful words, so a machine cannot tell what the resource is from its name | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The name a video, audio clip or image is served under, and whether it is human-meaningful words or a technical code. What good looks like Video, audio and image files carry names made of words that say what they are, not a technical code. Why it matters A resource named as a code or a bare number says nothing about what it is, so a machine cataloguing it has only the code to go on. What we found on this page 1 media resource(s) are named as a technical code, not human-meaningful words, so a machine cannot tell what the resource is from its name The evidence, taken from the page as served The media resources whose name is a technical code, as served
A meaningful name (words that say what it is) lets a machine identify the resource; a code or a bare number cannot. <video id="video6390041787112" data-embed="default" class="video-js" controls=""/> | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| DS03 | fail | an AI crawler asking for this page is refused by the security layer in front of the site, while an ordinary browser is served, so the page's content never reaches the AI and answers about it are left to memory or guesswork | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The same page loads for a browser but is refused when the request names itself as an AI service. What good looks like The page returns the same response to a named AI service as to a browser, with no edge block. Why it matters The block sits in front of the site and leaves no trace in its own logs, so the estate is closed off unnoticed. What we found on this page an AI crawler asking for this page is refused by the security layer in front of the site, while an ordinary browser is served, so the page's content never reaches the AI and answers about it are left to memory or guesswork The evidence, taken from the page as served The estate's edge tested with each AI crawler: a browser is served, the crawlers are refused
Hostwww.aviva.com · resolves to 23.215.224.114 · an Akamai edge hostname
Address trailwww.aviva.com › cert10.uk.aviva.com.ksd.edgekey.net › e5059.ksd.akamaiedge.net
Checked2026-07-31 16:33 UTC · request sent from 10.100.100.212 (our checker)
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page returns the same response to a named AI service as to a browser, with no edge block. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 5 out of a possible 5, because it is one of the checks that decide whether content can be reached and read at all, so it carries the heaviest weight in the figure for this item. Why it moves the misinformation reading This failure is a real and common route to a wrong answer for the content it affects, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT32 | warning | length 229 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The meta description's length is usable, between 50 and 170 characters. What good looks like The meta description's length is usable, long enough to say something and short enough not to be cut. Why it matters Too short says nothing and too long gets cut, so the summary field is spent without doing its job. What we found on this page length 229 The evidence, taken from the page as served The page's description, as served
<meta name="description" content="Everything youรขยยre about to read, hear and see will uncover just a little bit of what really matters to us at Aviva. This collection of features shows how weรขยยre living up to our purpose: with you today, for a better tomorrow. "/> | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT16 | warning | the page carries no structured data block stating what it is (not required; a hygiene signal) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The page carries structured data, the machine-readable summary of what it describes. What good looks like The page carries structured data summarising what it describes. Why it matters Vendors document this as optional rather than required, so its absence is a small forfeit and no more. What we found on this page the page carries no structured data block stating what it is (not required; a hygiene signal) The evidence, taken from the page as served The head of this page, as served
The page was read for a structured data block describing what the page is. <head> <title>Features and insight - Aviva plc</title> <script defer="defer" type="text/javascript" src="https://rum.hlx.page/.rum/@adobe/helix-rum-js@%5E2/dist/rum-standalone.js" data-routing="env=prod,tier=publish,ams=Aviva Group"/> <link rel="preconnect" href="https://static.aviva.io/"/> <link rel="preconnect" href="https://static.aviva.io/" crossorigin="anonymous"/> <link rel="preconnect" href="https://dpm.demdex.net/"/> <link rel="preconnect" href="https://assets.adobedtm.com/"/> <link rel="preload" href="https://static.aviva.io/assets/fonts/sourcesans3-variable-roman-base.woff2" as="font" crossorigin="anonymous"/> <link rel="preload" href="https://cdn-ukwest.onetrust.com/scripttemplates/otSDKStub.js" as="script" crossorigin="anonymous"/> <link rel="preload" href="https://static.aviva.io/assets/fonts/avivacurve-regular.woff2" as="font" crossorigin="anonymous"/> <meta content="width=device-width,initial-scale=1" name="viewport"/> <meta property="templatename" content="featurepage"/> <meta property="article:published_time" content="2021-08-19T13:25:29"/> <meta property="og:description" content="Everything youรขยยre about to read, hear and see will uncover just a little bit of whaโฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR13 | warning | the page does not mark out its main content, so what is unique to this page cannot be told apart from the menus and foot-of-page text repeated across the site | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page's main content is marked off from the navigation and footer around it. What good looks like A main or article region marks the primary content off from the navigation and footer around it. Why it matters Pulling the page's text returns menus and legal footers mixed with the substance, so the answer arrives buried in noise. What we found on this page the page does not mark out its main content, so what is unique to this page cannot be told apart from the menus and foot-of-page text repeated across the site The evidence, taken from the page as served The blocks this page marks out, as served
The page was read for the block that marks out its main content. <meta itemprop="name" content="Features and insight"/> <meta itemprop="url" content="https://www.aviva.com/newsroom/news-and-research-overview/features-and-insight/"/> <div class="l-whole-page" data-back-to-top="Back to start of main content" data-component="back-to-top-es6"> <script> <span data-module="app/init-es6" data-module-load="true"/> <script id="js-init" src="https://static.aviva.io/assets/themes-managed/v6.1.0/shared/extensions/requirejs/init.js" asynโฆ <script src="https://static.aviva.io/etc.clientlibs/settings/wcm/designs/aviva-corporate/clientlibs/resources/2-20260728โฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS01 | fail | 1 of 1 boxes in the page's forms carry no name saying what each is for, so which answer belongs in which box rests on layout alone | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Each box, dropdown and text area in a form carries a name saying what it is for. What good looks like Each field in a form carries a name saying what it is for. Why it matters Unnamed fields leave the tie between a question and its box resting on layout, which shifts as the page reflows. What we found on this page 1 of 1 boxes in the page's forms carry no name saying what each is for, so which answer belongs in which box rests on layout alone The evidence, taken from the page as served The form boxes that carry no name, as served
<input type="search" name="q" id="search-site" value="" class="m-site-search__input" placeholder="Enter a keyword"/> Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: each field in a form carries a name saying what it is for. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS10 | fail | the page's first heading is not its top-level heading, so the structure starts part way down | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check A page's headings start at the top level and step down without skipping a level. What good looks like The page's headings start at the top level and step down without skipping a level. Why it matters Content under a skipped level has no clear parent section, so structure taken from the page misplaces its text. What we found on this page the page's first heading is not its top-level heading, so the structure starts part way down The evidence, taken from the page as served The page's heading outline, in document order (a jump in level is marked)
H3 Recommendation to reject "mini-tender" offers by Litani LLC level jumped H1 Features H2 Spotlight features H2 What would you really like to save up for? H2 The one who found balance H2 All features H2 Home-makers: how investing in housing helps Britain get ready for growth H2 Getting ready for work H2 The one who stands behind the promise H2 The one who rebuilt her life H2 The one who gives an extra scoop H2 The one who hosts tea H2 The รยฃ300m Cambridge investment H2 The one who studies storms H2 The one who found balance H2 The one who came back stronger H2 A city worth investing in H2 The one who never thought sheรขยยd work for an insurer H2 Login or register H2 Site navigation H3 About us H4 Our purpose and priorities H4 Our customers and people H4 Our Board and Executives H4 2025 Annual Report H4 Get support H3 Investors H4 Strategy and performance H4 Institutional investors H4 Shareholder services H4 Corporate governance H4 Risk governance and management H4 2025 Annual Report H4 Get support H3 Newsroom H4 News and research H4 Resources H4 About Aviva H4 Get support H3 Careers H4 Careers at Aviva H4 Life at Aviva H4 Diversity and inclusion H4 Get support H3 Sustainability H4 Sustainability at Aviva H4 Sustainability news H4 Sustainability resources H4 Aviva Foundation H4 Get support H4 Get support H2 Footer H3 Useful information H4 Products in our locations H4 Use MyAviva H4 How to make a complaint H3 On this site H3 Media H3 Corporate H3 Other links H3 Social H3 Legal H3 Copyright
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page's headings start at the top level and step down without skipping a level. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| DS03 | fail | an AI crawler asking for this page is refused by the security layer in front of the site, while an ordinary browser is served, so the page's content never reaches the AI and answers about it are left to memory or guesswork | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The same page loads for a browser but is refused when the request names itself as an AI service. What good looks like The page returns the same response to a named AI service as to a browser, with no edge block. Why it matters The block sits in front of the site and leaves no trace in its own logs, so the estate is closed off unnoticed. What we found on this page an AI crawler asking for this page is refused by the security layer in front of the site, while an ordinary browser is served, so the page's content never reaches the AI and answers about it are left to memory or guesswork The evidence, taken from the page as served The estate's edge tested with each AI crawler: a browser is served, the crawlers are refused
Hostwww.aviva.com · resolves to 23.215.224.114 · an Akamai edge hostname
Address trailwww.aviva.com › cert10.uk.aviva.com.ksd.edgekey.net › e5059.ksd.akamaiedge.net
Checked2026-07-31 16:33 UTC · request sent from 10.100.100.212 (our checker)
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page returns the same response to a named AI service as to a browser, with no edge block. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 5 out of a possible 5, because it is one of the checks that decide whether content can be reached and read at all, so it carries the heaviest weight in the figure for this item. Why it moves the misinformation reading This failure is a real and common route to a wrong answer for the content it affects, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT32 | warning | length 37 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The meta description's length is usable, between 50 and 170 characters. What good looks like The meta description's length is usable, long enough to say something and short enough not to be cut. Why it matters Too short says nothing and too long gets cut, so the summary field is spent without doing its job. What we found on this page length 37 The evidence, taken from the page as served The page's description, as served
<meta name="description" content="Information on shareholder dividends."/> | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT16 | warning | the page carries no structured data block stating what it is (not required; a hygiene signal) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The page carries structured data, the machine-readable summary of what it describes. What good looks like The page carries structured data summarising what it describes. Why it matters Vendors document this as optional rather than required, so its absence is a small forfeit and no more. What we found on this page the page carries no structured data block stating what it is (not required; a hygiene signal) The evidence, taken from the page as served The head of this page, as served
The page was read for a structured data block describing what the page is. <head> <title>Dividends - Aviva plc</title> <script defer="defer" type="text/javascript" src="https://rum.hlx.page/.rum/@adobe/helix-rum-js@%5E2/dist/rum-standalone.js" data-routing="env=prod,tier=publish,ams=Aviva Group"/> <link rel="preconnect" href="https://static.aviva.io/"/> <link rel="preconnect" href="https://static.aviva.io/" crossorigin="anonymous"/> <link rel="preconnect" href="https://dpm.demdex.net/"/> <link rel="preconnect" href="https://assets.adobedtm.com/"/> <link rel="preload" href="https://static.aviva.io/assets/fonts/sourcesans3-variable-roman-base.woff2" as="font" crossorigin="anonymous"/> <link rel="preload" href="https://cdn-ukwest.onetrust.com/scripttemplates/otSDKStub.js" as="script" crossorigin="anonymous"/> <link rel="preload" href="https://static.aviva.io/assets/fonts/avivacurve-regular.woff2" as="font" crossorigin="anonymous"/> <meta content="width=device-width,initial-scale=1" name="viewport"/> <meta property="templatename" content="featurepage"/> <meta property="article:published_time" content="2021-07-15T02:30:00"/> <meta property="og:description" content="Information on shareholder dividends."/> <meta property="og:title" content="Information on shareโฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR13 | warning | the page does not mark out its main content, so what is unique to this page cannot be told apart from the menus and foot-of-page text repeated across the site | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page's main content is marked off from the navigation and footer around it. What good looks like A main or article region marks the primary content off from the navigation and footer around it. Why it matters Pulling the page's text returns menus and legal footers mixed with the substance, so the answer arrives buried in noise. What we found on this page the page does not mark out its main content, so what is unique to this page cannot be told apart from the menus and foot-of-page text repeated across the site The evidence, taken from the page as served The blocks this page marks out, as served
The page was read for the block that marks out its main content. <meta itemprop="name" content="Dividends"/> <meta itemprop="url" content="https://www.aviva.com/investors/shareholder-services-overview/dividends/"/> <div class="l-whole-page" data-back-to-top="Back to start of main content" data-component="back-to-top-es6"> <script> <span data-module="app/init-es6" data-module-load="true"/> <script id="js-init" src="https://static.aviva.io/assets/themes-managed/v6.1.0/shared/extensions/requirejs/init.js" asynโฆ <script src="https://static.aviva.io/etc.clientlibs/settings/wcm/designs/aviva-corporate/clientlibs/resources/2-20260728โฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS01 | fail | 1 of 1 boxes in the page's forms carry no name saying what each is for, so which answer belongs in which box rests on layout alone | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Each box, dropdown and text area in a form carries a name saying what it is for. What good looks like Each field in a form carries a name saying what it is for. Why it matters Unnamed fields leave the tie between a question and its box resting on layout, which shifts as the page reflows. What we found on this page 1 of 1 boxes in the page's forms carry no name saying what each is for, so which answer belongs in which box rests on layout alone The evidence, taken from the page as served The form boxes that carry no name, as served
<input type="search" name="q" id="search-site" value="" class="m-site-search__input" placeholder="Enter a keyword"/> Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: each field in a form carries a name saying what it is for. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS10 | fail | the page's first heading is not its top-level heading, so the structure starts part way down | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check A page's headings start at the top level and step down without skipping a level. What good looks like The page's headings start at the top level and step down without skipping a level. Why it matters Content under a skipped level has no clear parent section, so structure taken from the page misplaces its text. What we found on this page the page's first heading is not its top-level heading, so the structure starts part way down The evidence, taken from the page as served The page's heading outline, in document order (a jump in level is marked)
H3 Recommendation to reject "mini-tender" offers by Litani LLC level jumped H1 Information on shareholder dividends H2 Explore page H2 Latest dividend H2 Payment options H2 Tell us how you want us to pay your dividends H2 Dividend policy H2 Current and historical dividend timetable H2 Ordinary/ADR shareholders H2 Direct Line Insurance Group plc historical dividend information H2 Preference shareholders H2 Dividend FAQs H2 More for shareholders H2 Manage your shares H2 Shareholder updates H2 Communication H2 Shareholder meetings and archives H2 Share capital H2 Login or register H2 Site navigation H3 About us H4 Our purpose and priorities H4 Our customers and people H4 Our Board and Executives H4 2025 Annual Report H4 Get support H3 Investors H4 Strategy and performance H4 Institutional investors H4 Shareholder services H4 Corporate governance H4 Risk governance and management H4 2025 Annual Report H4 Get support H3 Newsroom H4 News and research H4 Resources H4 About Aviva H4 Get support H3 Careers H4 Careers at Aviva H4 Life at Aviva H4 Diversity and inclusion H4 Get support H3 Sustainability H4 Sustainability at Aviva H4 Sustainability news H4 Sustainability resources H4 Aviva Foundation H4 Get support H4 Get support H2 Footer H3 Useful information H4 Products in our locations H4 Use MyAviva H4 How to make a complaint H3 On this site H3 Media H3 Corporate H3 Other links H3 Social H3 Legal H3 Copyright
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page's headings start at the top level and step down without skipping a level. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS12 | fail | 3 of 3 data tables lack header cells: values are extracted without column meaning | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Data tables mark their header cells, so each number stays tied to its column. What good looks like Data tables mark their header cells, so each value stays tied to its column. Why it matters Without headers a figure is extracted as a bare number, so it gets quoted against the wrong heading. What we found on this page 3 of 3 data tables lack header cells: values are extracted without column meaning The evidence, taken from the page as served The data tables with no header cells, as served
<table width="100%" border="0" cellspacing="0" cellpadding="1"> <tbody> <tr> <td><strong>Type</strong></td> <td><strong>Ex-dividend date</strong></td> <td><strong>Record date</strong></td> <td><strong>Payment date</strong></td> <td><strong>ADR Payment date</strong></td> <td><strong>Dividend pence per share</strong></tdโฆ <table width="100%" border="0" cellspacing="0" cellpadding="1"> <tbody> <tr> <td><strong>Dividend</strong><br/></td> <td><strong>Amount</strong><br/></td> <td><strong>Payment date</strong><br/></td> </tr> <tr> <td>2024 Interim Dividend</td> <td>2.0p</td> <td>11 October 2024</td> </tr> <tr> <td>2023 Final Dividend</td> โฆ <table width="100%" border="0" cellspacing="0" cellpadding="1"> <tbody> <tr> <td><strong>Holding</strong></td> <td><strong>Ex-dividend date</strong></td> <td><strong>Record date</strong></td> <td><strong>Payment date</strong></td> </tr> <tr> <td>8 รข ย%</td> <td>06 Mar 25</td> <td>07 Mar 25</td> <td>31 Mar 25</td> </tr>โฆ Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: data tables mark their header cells, so each value stays tied to its column. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it does not move the misinformation reading This failure makes content harder to reach or to read, but it is not a direct route to a wrong answer, so it is held out of the misinformation reading rather than counted twice. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| DS03 | fail | an AI crawler asking for this page is refused by the security layer in front of the site, while an ordinary browser is served, so the page's content never reaches the AI and answers about it are left to memory or guesswork | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The same page loads for a browser but is refused when the request names itself as an AI service. What good looks like The page returns the same response to a named AI service as to a browser, with no edge block. Why it matters The block sits in front of the site and leaves no trace in its own logs, so the estate is closed off unnoticed. What we found on this page an AI crawler asking for this page is refused by the security layer in front of the site, while an ordinary browser is served, so the page's content never reaches the AI and answers about it are left to memory or guesswork The evidence, taken from the page as served The estate's edge tested with each AI crawler: a browser is served, the crawlers are refused
Hostwww.aviva.com · resolves to 23.215.224.114 · an Akamai edge hostname
Address trailwww.aviva.com › cert10.uk.aviva.com.ksd.edgekey.net › e5059.ksd.akamaiedge.net
Checked2026-07-31 16:33 UTC · request sent from 10.100.100.212 (our checker)
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page returns the same response to a named AI service as to a browser, with no edge block. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 5 out of a possible 5, because it is one of the checks that decide whether content can be reached and read at all, so it carries the heaviest weight in the figure for this item. Why it moves the misinformation reading This failure is a real and common route to a wrong answer for the content it affects, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT16 | warning | the page carries no structured data block stating what it is (not required; a hygiene signal) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The page carries structured data, the machine-readable summary of what it describes. What good looks like The page carries structured data summarising what it describes. Why it matters Vendors document this as optional rather than required, so its absence is a small forfeit and no more. What we found on this page the page carries no structured data block stating what it is (not required; a hygiene signal) The evidence, taken from the page as served The head of this page, as served
The page was read for a structured data block describing what the page is. <head> <title>Job search - Aviva plc</title> <script defer="defer" type="text/javascript" src="https://rum.hlx.page/.rum/@adobe/helix-rum-js@%5E2/dist/rum-standalone.js" data-routing="env=prod,tier=publish,ams=Aviva Group"/> <link rel="preconnect" href="https://static.aviva.io/"/> <link rel="preconnect" href="https://static.aviva.io/" crossorigin="anonymous"/> <link rel="preconnect" href="https://dpm.demdex.net/"/> <link rel="preconnect" href="https://assets.adobedtm.com/"/> <link rel="preload" href="https://static.aviva.io/assets/fonts/sourcesans3-variable-roman-base.woff2" as="font" crossorigin="anonymous"/> <link rel="preload" href="https://cdn-ukwest.onetrust.com/scripttemplates/otSDKStub.js" as="script" crossorigin="anonymous"/> <link rel="preload" href="https://static.aviva.io/assets/fonts/avivacurve-regular.woff2" as="font" crossorigin="anonymous"/> <meta content="width=device-width,initial-scale=1" name="viewport"/> <meta property="templatename" content="featurepage"/> <meta property="article:published_time" content="2021-07-15T01:14:33"/> <meta property="og:description" content="We empower each other to shine in our careers. We provide the training, development and opportuโฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR13 | warning | the page does not mark out its main content, so what is unique to this page cannot be told apart from the menus and foot-of-page text repeated across the site | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page's main content is marked off from the navigation and footer around it. What good looks like A main or article region marks the primary content off from the navigation and footer around it. Why it matters Pulling the page's text returns menus and legal footers mixed with the substance, so the answer arrives buried in noise. What we found on this page the page does not mark out its main content, so what is unique to this page cannot be told apart from the menus and foot-of-page text repeated across the site The evidence, taken from the page as served The blocks this page marks out, as served
The page was read for the block that marks out its main content. <meta itemprop="name" content="Job search"/> <meta itemprop="url" content="https://www.aviva.com/careers/careers-at-aviva-overview/job-search/"/> <div class="l-whole-page" data-back-to-top="Back to start of main content" data-component="back-to-top-es6"> <script> <span data-module="app/init-es6" data-module-load="true"/> <script id="js-init" src="https://static.aviva.io/assets/themes-managed/v6.1.0/shared/extensions/requirejs/init.js" asynโฆ <script src="https://static.aviva.io/etc.clientlibs/settings/wcm/designs/aviva-corporate/clientlibs/resources/2-20260728โฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS01 | fail | 1 of 1 boxes in the page's forms carry no name saying what each is for, so which answer belongs in which box rests on layout alone | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Each box, dropdown and text area in a form carries a name saying what it is for. What good looks like Each field in a form carries a name saying what it is for. Why it matters Unnamed fields leave the tie between a question and its box resting on layout, which shifts as the page reflows. What we found on this page 1 of 1 boxes in the page's forms carry no name saying what each is for, so which answer belongs in which box rests on layout alone The evidence, taken from the page as served The form boxes that carry no name, as served
<input type="search" name="q" id="search-site" value="" class="m-site-search__input" placeholder="Enter a keyword"/> Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: each field in a form carries a name saying what it is for. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS10 | fail | the page's first heading is not its top-level heading, so the structure starts part way down | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check A page's headings start at the top level and step down without skipping a level. What good looks like The page's headings start at the top level and step down without skipping a level. Why it matters Content under a skipped level has no clear parent section, so structure taken from the page misplaces its text. What we found on this page the page's first heading is not its top-level heading, so the structure starts part way down The evidence, taken from the page as served The page's heading outline, in document order (a jump in level is marked)
H3 Recommendation to reject "mini-tender" offers by Litani LLC level jumped H1 Job search H2 Explore page H2 Careers around the world H2 Job opportunities H2 Graduates, apprentices and interns H2 Aviva graduate programme H2 Aviva apprentice programme H2 Aviva Investors internship H2 Build a career with purpose H2 How to spot scams H2 Login or register H2 Site navigation H3 About us H4 Our purpose and priorities H4 Our customers and people H4 Our Board and Executives H4 2025 Annual Report H4 Get support H3 Investors H4 Strategy and performance H4 Institutional investors H4 Shareholder services H4 Corporate governance H4 Risk governance and management H4 2025 Annual Report H4 Get support H3 Newsroom H4 News and research H4 Resources H4 About Aviva H4 Get support H3 Careers H4 Careers at Aviva H4 Life at Aviva H4 Diversity and inclusion H4 Get support H3 Sustainability H4 Sustainability at Aviva H4 Sustainability news H4 Sustainability resources H4 Aviva Foundation H4 Get support H4 Get support H2 Footer H3 Useful information H4 Products in our locations H4 Use MyAviva H4 How to make a complaint H3 On this site H3 Media H3 Corporate H3 Other links H3 Social H3 Legal H3 Copyright
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page's headings start at the top level and step down without skipping a level. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| DS03 | fail | an AI crawler asking for this page is refused by the security layer in front of the site, while an ordinary browser is served, so the page's content never reaches the AI and answers about it are left to memory or guesswork | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The same page loads for a browser but is refused when the request names itself as an AI service. What good looks like The page returns the same response to a named AI service as to a browser, with no edge block. Why it matters The block sits in front of the site and leaves no trace in its own logs, so the estate is closed off unnoticed. What we found on this page an AI crawler asking for this page is refused by the security layer in front of the site, while an ordinary browser is served, so the page's content never reaches the AI and answers about it are left to memory or guesswork The evidence, taken from the page as served The estate's edge tested with each AI crawler: a browser is served, the crawlers are refused
Hostwww.aviva.com · resolves to 23.215.224.114 · an Akamai edge hostname
Address trailwww.aviva.com › cert10.uk.aviva.com.ksd.edgekey.net › e5059.ksd.akamaiedge.net
Checked2026-07-31 16:33 UTC · request sent from 10.100.100.212 (our checker)
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page returns the same response to a named AI service as to a browser, with no edge block. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 5 out of a possible 5, because it is one of the checks that decide whether content can be reached and read at all, so it carries the heaviest weight in the figure for this item. Why it moves the misinformation reading This failure is a real and common route to a wrong answer for the content it affects, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT16 | warning | the page carries no structured data block stating what it is (not required; a hygiene signal) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The page carries structured data, the machine-readable summary of what it describes. What good looks like The page carries structured data summarising what it describes. Why it matters Vendors document this as optional rather than required, so its absence is a small forfeit and no more. What we found on this page the page carries no structured data block stating what it is (not required; a hygiene signal) The evidence, taken from the page as served The head of this page, as served
The page was read for a structured data block describing what the page is. <head> <title>Our purpose and priorities overview - Aviva plc</title> <script defer="defer" type="text/javascript" src="https://rum.hlx.page/.rum/@adobe/helix-rum-js@%5E2/dist/rum-standalone.js" data-routing="env=prod,tier=publish,ams=Aviva Group"/> <link rel="preconnect" href="https://static.aviva.io/"/> <link rel="preconnect" href="https://static.aviva.io/" crossorigin="anonymous"/> <link rel="preconnect" href="https://dpm.demdex.net/"/> <link rel="preconnect" href="https://assets.adobedtm.com/"/> <link rel="preload" href="https://static.aviva.io/assets/fonts/sourcesans3-variable-roman-base.woff2" as="font" crossorigin="anonymous"/> <link rel="preload" href="https://cdn-ukwest.onetrust.com/scripttemplates/otSDKStub.js" as="script" crossorigin="anonymous"/> <link rel="preload" href="https://static.aviva.io/assets/fonts/avivacurve-regular.woff2" as="font" crossorigin="anonymous"/> <meta content="width=device-width,initial-scale=1" name="viewport"/> <meta property="templatename" content="categorypage"/> <meta property="article:published_time" content="2026-07-10T03:29:14"/> <meta property="og:description" content="This page brings together links to help you explore Avivaรขยยs purposeโฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR13 | warning | the page does not mark out its main content, so what is unique to this page cannot be told apart from the menus and foot-of-page text repeated across the site | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page's main content is marked off from the navigation and footer around it. What good looks like A main or article region marks the primary content off from the navigation and footer around it. Why it matters Pulling the page's text returns menus and legal footers mixed with the substance, so the answer arrives buried in noise. What we found on this page the page does not mark out its main content, so what is unique to this page cannot be told apart from the menus and foot-of-page text repeated across the site The evidence, taken from the page as served The blocks this page marks out, as served
The page was read for the block that marks out its main content. <meta itemprop="name" content="Our purpose and priorities overview"/> <meta itemprop="url" content="https://www.aviva.com/about-us/our-purpose-and-priorities-overview/"/> <div class="l-whole-page" data-back-to-top="Back to start of main content" data-component="back-to-top-es6"> <script> <span data-module="app/init-es6" data-module-load="true"/> <script id="js-init" src="https://static.aviva.io/assets/themes-managed/v6.1.0/shared/extensions/requirejs/init.js" asynโฆ <script src="https://static.aviva.io/etc.clientlibs/settings/wcm/designs/aviva-corporate/clientlibs/resources/2-20260728โฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS01 | fail | 1 of 1 boxes in the page's forms carry no name saying what each is for, so which answer belongs in which box rests on layout alone | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Each box, dropdown and text area in a form carries a name saying what it is for. What good looks like Each field in a form carries a name saying what it is for. Why it matters Unnamed fields leave the tie between a question and its box resting on layout, which shifts as the page reflows. What we found on this page 1 of 1 boxes in the page's forms carry no name saying what each is for, so which answer belongs in which box rests on layout alone The evidence, taken from the page as served The form boxes that carry no name, as served
<input type="search" name="q" id="search-site" value="" class="m-site-search__input" placeholder="Enter a keyword"/> Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: each field in a form carries a name saying what it is for. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS10 | fail | the page's first heading is not its top-level heading, so the structure starts part way down | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check A page's headings start at the top level and step down without skipping a level. What good looks like The page's headings start at the top level and step down without skipping a level. Why it matters Content under a skipped level has no clear parent section, so structure taken from the page misplaces its text. What we found on this page the page's first heading is not its top-level heading, so the structure starts part way down The evidence, taken from the page as served The page's heading outline, in document order (a jump in level is marked)
H3 Recommendation to reject "mini-tender" offers by Litani LLC level jumped H1 Our purpose and priorities H2 Purpose, values and how we're organised H3 Our purpose and values H3 How we're organised H2 Helping the UK Get Ready H3 Helping the UK Get Ready H3 Where we invest in the UK H2 Innovation at Aviva H3 Innovation at Aviva H3 Onboarding process for start-ups H2 More purpose and priorities pages H3 Public Affairs at Aviva H3 Aviva Capital Partners H3 Aviva venues H2 Explore our other About us pages H3 Our customers and people H3 Our Board and Executives H2 Login or register H2 Site navigation H3 About us H4 Our purpose and priorities H4 Our customers and people H4 Our Board and Executives H4 2025 Annual Report H4 Get support H3 Investors H4 Strategy and performance H4 Institutional investors H4 Shareholder services H4 Corporate governance H4 Risk governance and management H4 2025 Annual Report H4 Get support H3 Newsroom H4 News and research H4 Resources H4 About Aviva H4 Get support H3 Careers H4 Careers at Aviva H4 Life at Aviva H4 Diversity and inclusion H4 Get support H3 Sustainability H4 Sustainability at Aviva H4 Sustainability news H4 Sustainability resources H4 Aviva Foundation H4 Get support H4 Get support H2 Footer H3 Useful information H4 Products in our locations H4 Use MyAviva H4 How to make a complaint H3 On this site H3 Media H3 Corporate H3 Other links H3 Social H3 Legal H3 Copyright
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page's headings start at the top level and step down without skipping a level. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| DS03 | fail | an AI crawler asking for this page is refused by the security layer in front of the site, while an ordinary browser is served, so the page's content never reaches the AI and answers about it are left to memory or guesswork | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The same page loads for a browser but is refused when the request names itself as an AI service. What good looks like The page returns the same response to a named AI service as to a browser, with no edge block. Why it matters The block sits in front of the site and leaves no trace in its own logs, so the estate is closed off unnoticed. What we found on this page an AI crawler asking for this page is refused by the security layer in front of the site, while an ordinary browser is served, so the page's content never reaches the AI and answers about it are left to memory or guesswork The evidence, taken from the page as served The estate's edge tested with each AI crawler: a browser is served, the crawlers are refused
Hostwww.aviva.com · resolves to 23.215.224.114 · an Akamai edge hostname
Address trailwww.aviva.com › cert10.uk.aviva.com.ksd.edgekey.net › e5059.ksd.akamaiedge.net
Checked2026-07-31 16:33 UTC · request sent from 10.100.100.212 (our checker)
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page returns the same response to a named AI service as to a browser, with no edge block. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 5 out of a possible 5, because it is one of the checks that decide whether content can be reached and read at all, so it carries the heaviest weight in the figure for this item. Why it moves the misinformation reading This failure is a real and common route to a wrong answer for the content it affects, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT16 | warning | the page carries no structured data block stating what it is (not required; a hygiene signal) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The page carries structured data, the machine-readable summary of what it describes. What good looks like The page carries structured data summarising what it describes. Why it matters Vendors document this as optional rather than required, so its absence is a small forfeit and no more. What we found on this page the page carries no structured data block stating what it is (not required; a hygiene signal) The evidence, taken from the page as served The head of this page, as served
The page was read for a structured data block describing what the page is. <head> <title>Shareholder services overview - Aviva plc</title> <script defer="defer" type="text/javascript" src="https://rum.hlx.page/.rum/@adobe/helix-rum-js@%5E2/dist/rum-standalone.js" data-routing="env=prod,tier=publish,ams=Aviva Group"/> <link rel="preconnect" href="https://static.aviva.io/"/> <link rel="preconnect" href="https://static.aviva.io/" crossorigin="anonymous"/> <link rel="preconnect" href="https://dpm.demdex.net/"/> <link rel="preconnect" href="https://assets.adobedtm.com/"/> <link rel="preload" href="https://static.aviva.io/assets/fonts/sourcesans3-variable-roman-base.woff2" as="font" crossorigin="anonymous"/> <link rel="preload" href="https://cdn-ukwest.onetrust.com/scripttemplates/otSDKStub.js" as="script" crossorigin="anonymous"/> <link rel="preload" href="https://static.aviva.io/assets/fonts/avivacurve-regular.woff2" as="font" crossorigin="anonymous"/> <meta content="width=device-width,initial-scale=1" name="viewport"/> <meta property="templatename" content="categorypage"/> <meta property="article:published_time" content="2026-07-10T04:52:48"/> <meta property="og:description" content="This page brings together links for Avivaรขยยs shareholders."/> <meta properโฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR13 | warning | the page does not mark out its main content, so what is unique to this page cannot be told apart from the menus and foot-of-page text repeated across the site | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page's main content is marked off from the navigation and footer around it. What good looks like A main or article region marks the primary content off from the navigation and footer around it. Why it matters Pulling the page's text returns menus and legal footers mixed with the substance, so the answer arrives buried in noise. What we found on this page the page does not mark out its main content, so what is unique to this page cannot be told apart from the menus and foot-of-page text repeated across the site The evidence, taken from the page as served The blocks this page marks out, as served
The page was read for the block that marks out its main content. <meta itemprop="name" content="Shareholder services overview"/> <meta itemprop="url" content="https://www.aviva.com/investors/shareholder-services-overview/"/> <div class="l-whole-page" data-back-to-top="Back to start of main content" data-component="back-to-top-es6"> <script> <span data-module="app/init-es6" data-module-load="true"/> <script id="js-init" src="https://static.aviva.io/assets/themes-managed/v6.1.0/shared/extensions/requirejs/init.js" asynโฆ <script src="https://static.aviva.io/etc.clientlibs/settings/wcm/designs/aviva-corporate/clientlibs/resources/2-20260728โฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS01 | fail | 1 of 1 boxes in the page's forms carry no name saying what each is for, so which answer belongs in which box rests on layout alone | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Each box, dropdown and text area in a form carries a name saying what it is for. What good looks like Each field in a form carries a name saying what it is for. Why it matters Unnamed fields leave the tie between a question and its box resting on layout, which shifts as the page reflows. What we found on this page 1 of 1 boxes in the page's forms carry no name saying what each is for, so which answer belongs in which box rests on layout alone The evidence, taken from the page as served The form boxes that carry no name, as served
<input type="search" name="q" id="search-site" value="" class="m-site-search__input" placeholder="Enter a keyword"/> Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: each field in a form carries a name saying what it is for. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS10 | fail | the page's first heading is not its top-level heading, so the structure starts part way down | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check A page's headings start at the top level and step down without skipping a level. What good looks like The page's headings start at the top level and step down without skipping a level. Why it matters Content under a skipped level has no clear parent section, so structure taken from the page misplaces its text. What we found on this page the page's first heading is not its top-level heading, so the structure starts part way down The evidence, taken from the page as served The page's heading outline, in document order (a jump in level is marked)
H3 Recommendation to reject "mini-tender" offers by Litani LLC level jumped H1 Shareholder services H2 Welcome from George Culmer, your Chair H3 Transcriptย for video Welcome to Shareholder services H2 Dividends H3 Dividends H3 Dividends FAQs H2 Manage your shares H3 Manage your shares H3 Manage your shares FAQs H2 Useful information for shareholders H3 Shareholder updates H3 Shareholder meetings H3 Warning to shareholders H3 Share capital H3 Communication H3 Shareholder contacts H3 Shareholder privacy policy H2 Explore our other Investor pages H3 Strategy and performance H3 Institutional investors H3 Corporate governance H3 Risk governance and management H2 Login or register H2 Site navigation H3 About us H4 Our purpose and priorities H4 Our customers and people H4 Our Board and Executives H4 2025 Annual Report H4 Get support H3 Investors H4 Strategy and performance H4 Institutional investors H4 Shareholder services H4 Corporate governance H4 Risk governance and management H4 2025 Annual Report H4 Get support H3 Newsroom H4 News and research H4 Resources H4 About Aviva H4 Get support H3 Careers H4 Careers at Aviva H4 Life at Aviva H4 Diversity and inclusion H4 Get support H3 Sustainability H4 Sustainability at Aviva H4 Sustainability news H4 Sustainability resources H4 Aviva Foundation H4 Get support H4 Get support H2 Footer H3 Useful information H4 Products in our locations H4 Use MyAviva H4 How to make a complaint H3 On this site H3 Media H3 Corporate H3 Other links H3 Social H3 Legal H3 Copyright
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page's headings start at the top level and step down without skipping a level. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS14 | fail | 1 video(s) on the page with no captions on the video and no written transcript on the page: nothing spoken is available as text in any form | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether each video carries captions of its own, timed text on the video itself, judged together with whether the page holds a written transcript. What good looks like Captions carried on the video. A WARNING means the video has no captions but a written transcript on the page holds the words. A FAIL means neither exists, so nothing spoken is available as text in any form; that total absence is marked here once, not spread across two findings. Why it matters Spoken content that exists only as sound is invisible to a reader, human or machine: nothing said in the video can be found, read or quoted. What we found on this page 1 video(s) on the page with no captions on the video and no written transcript on the page: nothing spoken is available as text in any form The evidence, taken from the page as served Each video on the page, as served: its code, source file and caption track
No caption track on the video and no transcript link on the page. <video id="video6317654882112" data-embed="default" class="video-js" controls=""/> Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: captions carried on the video. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS16 | warning | 1 media resource(s) are named as a technical code, not human-meaningful words, so a machine cannot tell what the resource is from its name | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The name a video, audio clip or image is served under, and whether it is human-meaningful words or a technical code. What good looks like Video, audio and image files carry names made of words that say what they are, not a technical code. Why it matters A resource named as a code or a bare number says nothing about what it is, so a machine cataloguing it has only the code to go on. What we found on this page 1 media resource(s) are named as a technical code, not human-meaningful words, so a machine cannot tell what the resource is from its name The evidence, taken from the page as served The media resources whose name is a technical code, as served
A meaningful name (words that say what it is) lets a machine identify the resource; a code or a bare number cannot. <video id="video6317654882112" data-embed="default" class="video-js" controls=""/> | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| DS03 | fail | an AI crawler asking for this page is refused by the security layer in front of the site, while an ordinary browser is served, so the page's content never reaches the AI and answers about it are left to memory or guesswork | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The same page loads for a browser but is refused when the request names itself as an AI service. What good looks like The page returns the same response to a named AI service as to a browser, with no edge block. Why it matters The block sits in front of the site and leaves no trace in its own logs, so the estate is closed off unnoticed. What we found on this page an AI crawler asking for this page is refused by the security layer in front of the site, while an ordinary browser is served, so the page's content never reaches the AI and answers about it are left to memory or guesswork The evidence, taken from the page as served The estate's edge tested with each AI crawler: a browser is served, the crawlers are refused
Hostwww.aviva.com · resolves to 23.215.224.114 · an Akamai edge hostname
Address trailwww.aviva.com › cert10.uk.aviva.com.ksd.edgekey.net › e5059.ksd.akamaiedge.net
Checked2026-07-31 16:33 UTC · request sent from 10.100.100.212 (our checker)
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page returns the same response to a named AI service as to a browser, with no edge block. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 5 out of a possible 5, because it is one of the checks that decide whether content can be reached and read at all, so it carries the heaviest weight in the figure for this item. Why it moves the misinformation reading This failure is a real and common route to a wrong answer for the content it affects, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT16 | warning | the page carries no structured data block stating what it is (not required; a hygiene signal) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The page carries structured data, the machine-readable summary of what it describes. What good looks like The page carries structured data summarising what it describes. Why it matters Vendors document this as optional rather than required, so its absence is a small forfeit and no more. What we found on this page the page carries no structured data block stating what it is (not required; a hygiene signal) The evidence, taken from the page as served The head of this page, as served
The page was read for a structured data block describing what the page is. <head> <title>Sustainability news - Aviva plc</title> <script defer="defer" type="text/javascript" src="https://rum.hlx.page/.rum/@adobe/helix-rum-js@%5E2/dist/rum-standalone.js" data-routing="env=prod,tier=publish,ams=Aviva Group"/> <link rel="preconnect" href="https://static.aviva.io/"/> <link rel="preconnect" href="https://static.aviva.io/" crossorigin="anonymous"/> <link rel="preconnect" href="https://dpm.demdex.net/"/> <link rel="preconnect" href="https://assets.adobedtm.com/"/> <link rel="preload" href="https://static.aviva.io/assets/fonts/sourcesans3-variable-roman-base.woff2" as="font" crossorigin="anonymous"/> <link rel="preload" href="https://cdn-ukwest.onetrust.com/scripttemplates/otSDKStub.js" as="script" crossorigin="anonymous"/> <link rel="preload" href="https://static.aviva.io/assets/fonts/avivacurve-regular.woff2" as="font" crossorigin="anonymous"/> <meta content="width=device-width,initial-scale=1" name="viewport"/> <meta property="templatename" content="featurepage"/> <meta property="article:published_time" content="2025-01-10T10:31:57"/> <meta property="og:description" content="We're continually releasing news about our sustainability ambition in action.รขยย"/> <mโฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR13 | warning | the page does not mark out its main content, so what is unique to this page cannot be told apart from the menus and foot-of-page text repeated across the site | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page's main content is marked off from the navigation and footer around it. What good looks like A main or article region marks the primary content off from the navigation and footer around it. Why it matters Pulling the page's text returns menus and legal footers mixed with the substance, so the answer arrives buried in noise. What we found on this page the page does not mark out its main content, so what is unique to this page cannot be told apart from the menus and foot-of-page text repeated across the site The evidence, taken from the page as served The blocks this page marks out, as served
The page was read for the block that marks out its main content. <meta itemprop="name" content="Sustainability news"/> <meta itemprop="url" content="https://www.aviva.com/sustainability/sustainability-news-overview/sustainability-news/"/> <div class="l-whole-page" data-back-to-top="Back to start of main content" data-component="back-to-top-es6"> <script> <span data-module="app/init-es6" data-module-load="true"/> <script id="js-init" src="https://static.aviva.io/assets/themes-managed/v6.1.0/shared/extensions/requirejs/init.js" asynโฆ <script src="https://static.aviva.io/etc.clientlibs/settings/wcm/designs/aviva-corporate/clientlibs/resources/2-20260728โฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS01 | fail | 1 of 1 boxes in the page's forms carry no name saying what each is for, so which answer belongs in which box rests on layout alone | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Each box, dropdown and text area in a form carries a name saying what it is for. What good looks like Each field in a form carries a name saying what it is for. Why it matters Unnamed fields leave the tie between a question and its box resting on layout, which shifts as the page reflows. What we found on this page 1 of 1 boxes in the page's forms carry no name saying what each is for, so which answer belongs in which box rests on layout alone The evidence, taken from the page as served The form boxes that carry no name, as served
<input type="search" name="q" id="search-site" value="" class="m-site-search__input" placeholder="Enter a keyword"/> Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: each field in a form carries a name saying what it is for. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS08 | fail | 6 link wording(s) are used for more than one destination, so the same words point at different pages: โgo to aviva investors website ""โ, โgo to bitc website ""โ, โgo to packaged living website ""โ and 3 more; the links are listed in the view | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Links that share exactly the same wording on one page while pointing at different destinations. What good looks like Links that share the same wording lead to the same destination. Why it matters The wording no longer settles the target, so the wrong one gets followed at the point where the choice matters. What we found on this page 6 link wording(s) are used for more than one destination, so the same words point at different pages: โgo to aviva investors website ""โ, โgo to bitc website ""โ, โgo to packaged living website ""โ and 3 more; the links are listed in the view The evidence, taken from the page as served Links that share the same text but point to different destinations, as served
<a class="a-breadcrumb-page" itemprop="item" href="/sustainability/">Sustainability</a> <a class="a-button a-button--tertiary " href="https://www.avivainvestors.com/en-gb/about/company-news/2026/05/aviva-investors-green-loan-for-central-london-student-accommodation/"> Go to Aviva Investors website <span class="u-hidden--visually">""</span> </a> <a class="a-button a-button--tertiary " href="https://www.avivainvestors.com/en-gb/about/company-news/2026/03/aviva-investors-reaches-practical-completion-of-old-granada-studios/"> Go to Aviva Investors website <span class="u-hidden--visually">""</span> </a> <a class="a-button a-button--tertiary " href="https://www.avivainvestors.com/en-gb/about/company-news/2026/04/aviva-investors-invests-in-colombian-afforestation-project/"> Go to Aviva Investors website <span class="u-hidden--visually">""</span> </a> <a class="a-button a-button--tertiary " href="/newsroom/news-and-research-overview/news-releases/2026/03/aviva-and-the-national-housing-bank-to-invest-100m-to-build-thousands-of-high-quality-family-homes/"> Read more <span class="u-hidden--visually">""</span> </a> <a class="a-button a-button--tertiary " href="https://www.avivainvestors.com/en-gb/about/company-news/2026/03/aviva-investors-reaches-practical-completion-of-old-granada-studios/"> Go to Aviva Investors website <span class="u-hidden--visually">""</span> </a> <a class="a-button a-button--tertiary " href="/newsroom/news-and-research-overview/news-releases/2026/02/planning-approval-secured-for-london-cancer-hub/"> Read more <span class="u-hidden--visually">""</span> </a> <a class="a-button a-button--tertiary " href="https://www.avivainvestors.com/en-gb/about/company-news/2025/11/aviva-investors-launches-social-value-label-for-development-projects/"> Go to Aviva Investors website <span class="u-hidden--visually">""</span> </a> <a class="a-button a-button--tertiary " href="https://www.avivainvestors.com/en-gb/about/company-news/2025/10/aviva-investors-provides-green-loan-for-central-london-office/"> Go to Aviva Investors website <span class="u-hidden--visually">""</span> </a> <a class="a-button a-button--tertiary " href="https://www.avivainvestors.com/en-gb/about/company-news/2025/09/aviva-investors-invests-in-european-battery-energy-storage/"> Go to Aviva Investors website <span class="u-hidden--visually">""</span> </a> Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: links that share the same wording lead to the same destination. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS10 | fail | the page's first heading is not its top-level heading, so the structure starts part way down | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check A page's headings start at the top level and step down without skipping a level. What good looks like The page's headings start at the top level and step down without skipping a level. Why it matters Content under a skipped level has no clear parent section, so structure taken from the page misplaces its text. What we found on this page the page's first heading is not its top-level heading, so the structure starts part way down The evidence, taken from the page as served The page's heading outline, in document order (a jump in level is marked)
H3 Recommendation to reject "mini-tender" offers by Litani LLC level jumped H1 Sustainability news H2 Explore page H2 Sustainability news H2 The Aviva Foundation and Mencap launch financial confidence programme... H2 Aviva and Age UK announce launch of industry-first mid-retirement MOT... H2 Tesco insurance introduces free parent life cover in partnership with Aviva H2 Social prescribing: low awareness but high public appetite H2 Aviva paid nearly รยฃ2 billion in protection claims in 2025 H2 Aviva launches new financial wellbeing tool for pension savers H2 Aviva launches London Cancer Hub Fund... H2 New partnership formed to develop site of Southamptonรขยยs former Toys R Us H2 Aviva shows support for UK charities and communities H2 Award-winning rainforest garden from Chelsea Flower Show takes root at Bristol Z H2 UKรขยยs iconic landmarks at risk from climate change by 2050, according to new re H2 SMEs optimistic for future growth, but need support with workloads H2 Sustainability news related to our investments H3 Aviva Investors provides green loan towards central London student accommodation H3 Aviva Investors reaches practical completion of Old Granada Studios in Mancheste H3 Aviva Investors partners with Climate Impact Partners to invest in Colombian aff H3 Aviva and the National Housing Bank to invest รยฃ100m to build thousands of high- H3 Aviva Investors reaches practical completion of Old Granada Studios in Mancheste H3 Planning approval secured for London Cancer Hub... H3 Aviva Investors launches innovative Social Value Label for real estate developme H3 Aviva Investors provides green loan for redevelopment of Central London office s H3 Aviva Investors makes investment of up to รขยยฌ150 million in European Battery Ene H3 Aviva Investors provides financing towards Haweswater Aqueduct Resilience Progra H3 Barnet Council approves landmark rental housing scheme at Bunns Lane, Mill Hill H3 รยฃ350m landmark deal to turbo charge growth in Norwich H3 Aviva and Moda secure deal with Homes England, NatWest and WMCA for major รยฃ200m H3 Aviva Investors funds 133 new single-family homes in Bedfordshire in partnership H3 Aviva Investors provides financing towards two new campus developments for Cardi H3 Aviva Investors makes tenth UK single-family housing investment H3 Aviva Investors dual VC investments with Oxford Science Enterprises & Alloyed H3 Aviva Investors makes รยฃ15 million venture & growth capital investment with Camb H3 Aviva Investors completes รขยยฌ40 million investment into European renewables deve H3 Aviva Investors tops-up investment in Innovo Renewables development platform H3 Aviva Investors launches Carbon Removal Fund H3 Aviva Investors acquires 99-bed purpose-built student accommodation asset in Gla H3 Aviva Investors provides forward funding for new student village complex at Staf H3 Aviva Investors & Packaged Living bring Octopus Energyรขยยs รขยยZero Billsรขยย tari H3 Aviva Investors provides รยฃ65 million in debt financing to UK electric fleet spe H2 Sustainability news from our partners H3 Aviva Foundation Impact Reportร H3 Aviva and WWF partnership success (2021-2025) H3 Cornwall to benefit from The Wildlife Trustsรขยย temperate rainforest restoration H3 Aviva strengthens commitment to gender-balanced leadership H3 Highland estate as big as Glasgow to be revitalised in partnership between commu H3 Business leaders join forces in Norwich to learn about food insecurity and child H3 New reserve in the heart of the Dales will return rainforests to Yorkshire H3 WWF and Aviva unveil new saltmarsh research: a blueprint for climate resilience H3 Manx Wildlife Trust to restore largest area of rainforest to date H3 Bristol Zoo Project to become home to RHS Chelsea Flower Showรขยยs magical rainfo H3 Telling the story of The Wildlife Trusts and Aviva British Rainforest Garden H3 The Wildlife Trusts and Aviva to create British Rainforest Garden for RHS Chelse H3 Aviva is now one of Nattergalรขยยs key institutional investors, with Aviva's Grou H3 Cumbria Wildlife Trust asks public to help buy Skiddaw Forest and create England H3 Packaged Living & Aviva Investors to fund 101 single-family housing development H3 Pembrokeshire announced as new location for Atlantic rainforest restoration H3 Packaged Living and Aviva Investors to fund delivery of 121 new homes in Ebbsfle H3 Packaged Living and Aviva Investors acquire two single family housing developmen H3 Packaged Living and Aviva strike รยฃ60m single-family housing deal H3 Packaged Living and Aviva Investors push accelerator on single-family housing H3 Aviva partners with BITC to provide much-needed support for communities across t H3 Devon to benefit from The Wildlife Trustsรขยย Atlantic rainforest recovery progra H3 First locations for The Wildlife Trustsรขยย Atlantic rainforest recovery programm H2 Our features H2 Home-makers: how investing in housing helps Britain get ready for growth H2 Getting ready for work H2 Nature isnรขยยt always a walk in the park H2 "You can't teach someone to budget their way out of poverty." H2 Finding a way forward through difficult times H2 Bringing rainforests back to the UK H2 Login or register H2 Site navigation H3 About us H4 Our purpose and priorities H4 Our customers and people H4 Our Board and Executives H4 2025 Annual Report H4 Get support H3 Investors H4 Strategy and performance H4 Institutional investors H4 Shareholder services H4 Corporate governance H4 Risk governance and management H4 2025 Annual Report H4 Get support H3 Newsroom H4 News and research H4 Resources H4 About Aviva H4 Get support H3 Careers H4 Careers at Aviva H4 Life at Aviva H4 Diversity and inclusion H4 Get support H3 Sustainability H4 Sustainability at Aviva H4 Sustainability news H4 Sustainability resources H4 Aviva Foundation H4 Get support H4 Get support H2 Footer H3 Useful information H4 Products in our locations H4 Use MyAviva H4 How to make a complaint H3 On this site H3 Media H3 Corporate H3 Other links H3 Social H3 Legal H3 Copyright
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page's headings start at the top level and step down without skipping a level. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| DS03 | fail | an AI crawler asking for this page is refused by the security layer in front of the site, while an ordinary browser is served, so the page's content never reaches the AI and answers about it are left to memory or guesswork | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The same page loads for a browser but is refused when the request names itself as an AI service. What good looks like The page returns the same response to a named AI service as to a browser, with no edge block. Why it matters The block sits in front of the site and leaves no trace in its own logs, so the estate is closed off unnoticed. What we found on this page an AI crawler asking for this page is refused by the security layer in front of the site, while an ordinary browser is served, so the page's content never reaches the AI and answers about it are left to memory or guesswork The evidence, taken from the page as served The estate's edge tested with each AI crawler: a browser is served, the crawlers are refused
Hostwww.aviva.com · resolves to 23.215.224.114 · an Akamai edge hostname
Address trailwww.aviva.com › cert10.uk.aviva.com.ksd.edgekey.net › e5059.ksd.akamaiedge.net
Checked2026-07-31 16:33 UTC · request sent from 10.100.100.212 (our checker)
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page returns the same response to a named AI service as to a browser, with no edge block. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 5 out of a possible 5, because it is one of the checks that decide whether content can be reached and read at all, so it carries the heaviest weight in the figure for this item. Why it moves the misinformation reading This failure is a real and common route to a wrong answer for the content it affects, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT16 | warning | the page carries no structured data block stating what it is (not required; a hygiene signal) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The page carries structured data, the machine-readable summary of what it describes. What good looks like The page carries structured data summarising what it describes. Why it matters Vendors document this as optional rather than required, so its absence is a small forfeit and no more. What we found on this page the page carries no structured data block stating what it is (not required; a hygiene signal) The evidence, taken from the page as served The head of this page, as served
The page was read for a structured data block describing what the page is. <head> <title>Our purpose and values - Aviva plc</title> <script defer="defer" type="text/javascript" src="https://rum.hlx.page/.rum/@adobe/helix-rum-js@%5E2/dist/rum-standalone.js" data-routing="env=prod,tier=publish,ams=Aviva Group"/> <link rel="preconnect" href="https://static.aviva.io/"/> <link rel="preconnect" href="https://static.aviva.io/" crossorigin="anonymous"/> <link rel="preconnect" href="https://dpm.demdex.net/"/> <link rel="preconnect" href="https://assets.adobedtm.com/"/> <link rel="preload" href="https://static.aviva.io/assets/fonts/sourcesans3-variable-roman-base.woff2" as="font" crossorigin="anonymous"/> <link rel="preload" href="https://cdn-ukwest.onetrust.com/scripttemplates/otSDKStub.js" as="script" crossorigin="anonymous"/> <link rel="preload" href="https://static.aviva.io/assets/fonts/avivacurve-regular.woff2" as="font" crossorigin="anonymous"/> <meta content="width=device-width,initial-scale=1" name="viewport"/> <meta property="templatename" content="featurepage"/> <meta property="article:published_time" content="2026-06-12T10:30:00"/> <meta property="og:description" content="Discover Avivaรขยยs purpose - with you today, for a better tomorrow - and values: Caโฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR13 | warning | the page does not mark out its main content, so what is unique to this page cannot be told apart from the menus and foot-of-page text repeated across the site | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page's main content is marked off from the navigation and footer around it. What good looks like A main or article region marks the primary content off from the navigation and footer around it. Why it matters Pulling the page's text returns menus and legal footers mixed with the substance, so the answer arrives buried in noise. What we found on this page the page does not mark out its main content, so what is unique to this page cannot be told apart from the menus and foot-of-page text repeated across the site The evidence, taken from the page as served The blocks this page marks out, as served
The page was read for the block that marks out its main content. <meta itemprop="name" content="Our purpose and values"/> <meta itemprop="url" content="https://www.aviva.com/about-us/our-purpose-and-priorities-overview/our-purpose-and-values/โฆ <div class="l-whole-page" data-back-to-top="Back to start of main content" data-component="back-to-top-es6"> <script> <span data-module="app/init-es6" data-module-load="true"/> <script id="js-init" src="https://static.aviva.io/assets/themes-managed/v6.1.0/shared/extensions/requirejs/init.js" asynโฆ <script src="https://static.aviva.io/etc.clientlibs/settings/wcm/designs/aviva-corporate/clientlibs/resources/2-20260728โฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS01 | fail | 1 of 1 boxes in the page's forms carry no name saying what each is for, so which answer belongs in which box rests on layout alone | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Each box, dropdown and text area in a form carries a name saying what it is for. What good looks like Each field in a form carries a name saying what it is for. Why it matters Unnamed fields leave the tie between a question and its box resting on layout, which shifts as the page reflows. What we found on this page 1 of 1 boxes in the page's forms carry no name saying what each is for, so which answer belongs in which box rests on layout alone The evidence, taken from the page as served The form boxes that carry no name, as served
<input type="search" name="q" id="search-site" value="" class="m-site-search__input" placeholder="Enter a keyword"/> Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: each field in a form carries a name saying what it is for. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS10 | fail | the page's first heading is not its top-level heading, so the structure starts part way down | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check A page's headings start at the top level and step down without skipping a level. What good looks like The page's headings start at the top level and step down without skipping a level. Why it matters Content under a skipped level has no clear parent section, so structure taken from the page misplaces its text. What we found on this page the page's first heading is not its top-level heading, so the structure starts part way down The evidence, taken from the page as served The page's heading outline, in document order (a jump in level is marked)
H3 Recommendation to reject "mini-tender" offers by Litani LLC level jumped H1 Our purpose and values H2 Explore page H2 What's Aviva's purpose? H2 For the moments you plan for and the ones you don't H3 Transcriptย for video For Every Story H2 How does our purpose come to life for customers? H3 Jakob's story H3 Poppy's story H3 Daniel's story H2 What are our values? H3 Transcriptย for video Aviva Values H2 How do we live our values? H3 Care H3 Commitment H3 Community H3 Confidence H2 You might also be interested in... H3 Investment case and strategy H3 Aviva's sustainability ambition H2 Login or register H2 Site navigation H3 About us H4 Our purpose and priorities H4 Our customers and people H4 Our Board and Executives H4 2025 Annual Report H4 Get support H3 Investors H4 Strategy and performance H4 Institutional investors H4 Shareholder services H4 Corporate governance H4 Risk governance and management H4 2025 Annual Report H4 Get support H3 Newsroom H4 News and research H4 Resources H4 About Aviva H4 Get support H3 Careers H4 Careers at Aviva H4 Life at Aviva H4 Diversity and inclusion H4 Get support H3 Sustainability H4 Sustainability at Aviva H4 Sustainability news H4 Sustainability resources H4 Aviva Foundation H4 Get support H4 Get support H2 Footer H3 Useful information H4 Products in our locations H4 Use MyAviva H4 How to make a complaint H3 On this site H3 Media H3 Corporate H3 Other links H3 Social H3 Legal H3 Copyright
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page's headings start at the top level and step down without skipping a level. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS14 | fail | 2 video(s) on the page with no captions on the video and no written transcript on the page: nothing spoken is available as text in any form | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether each video carries captions of its own, timed text on the video itself, judged together with whether the page holds a written transcript. What good looks like Captions carried on the video. A WARNING means the video has no captions but a written transcript on the page holds the words. A FAIL means neither exists, so nothing spoken is available as text in any form; that total absence is marked here once, not spread across two findings. Why it matters Spoken content that exists only as sound is invisible to a reader, human or machine: nothing said in the video can be found, read or quoted. What we found on this page 2 video(s) on the page with no captions on the video and no written transcript on the page: nothing spoken is available as text in any form The evidence, taken from the page as served Each video on the page, as served: its code, source file and caption track
No caption track on the video and no transcript link on the page. <video id="video6388755589112" data-embed="default" class="video-js" controls=""/> <video id="video6307530586112" data-embed="default" class="video-js" controls=""/> Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: captions carried on the video. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS16 | warning | 2 media resource(s) are named as a technical code, not human-meaningful words, so a machine cannot tell what the resource is from its name | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The name a video, audio clip or image is served under, and whether it is human-meaningful words or a technical code. What good looks like Video, audio and image files carry names made of words that say what they are, not a technical code. Why it matters A resource named as a code or a bare number says nothing about what it is, so a machine cataloguing it has only the code to go on. What we found on this page 2 media resource(s) are named as a technical code, not human-meaningful words, so a machine cannot tell what the resource is from its name The evidence, taken from the page as served The media resources whose name is a technical code, as served
A meaningful name (words that say what it is) lets a machine identify the resource; a code or a bare number cannot. <video id="video6388755589112" data-embed="default" class="video-js" controls=""/> <video id="video6307530586112" data-embed="default" class="video-js" controls=""/> | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| DS03 | fail | an AI crawler asking for this page is refused by the security layer in front of the site, while an ordinary browser is served, so the page's content never reaches the AI and answers about it are left to memory or guesswork | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The same page loads for a browser but is refused when the request names itself as an AI service. What good looks like The page returns the same response to a named AI service as to a browser, with no edge block. Why it matters The block sits in front of the site and leaves no trace in its own logs, so the estate is closed off unnoticed. What we found on this page an AI crawler asking for this page is refused by the security layer in front of the site, while an ordinary browser is served, so the page's content never reaches the AI and answers about it are left to memory or guesswork The evidence, taken from the page as served The estate's edge tested with each AI crawler: a browser is served, the crawlers are refused
Hostwww.aviva.com · resolves to 23.215.224.114 · an Akamai edge hostname
Address trailwww.aviva.com › cert10.uk.aviva.com.ksd.edgekey.net › e5059.ksd.akamaiedge.net
Checked2026-07-31 16:33 UTC · request sent from 10.100.100.212 (our checker)
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page returns the same response to a named AI service as to a browser, with no edge block. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 5 out of a possible 5, because it is one of the checks that decide whether content can be reached and read at all, so it carries the heaviest weight in the figure for this item. Why it moves the misinformation reading This failure is a real and common route to a wrong answer for the content it affects, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT16 | warning | the page carries no structured data block stating what it is (not required; a hygiene signal) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The page carries structured data, the machine-readable summary of what it describes. What good looks like The page carries structured data summarising what it describes. Why it matters Vendors document this as optional rather than required, so its absence is a small forfeit and no more. What we found on this page the page carries no structured data block stating what it is (not required; a hygiene signal) The evidence, taken from the page as served The head of this page, as served
The page was read for a structured data block describing what the page is. <head> <title>Our Board - Aviva plc</title> <script defer="defer" type="text/javascript" src="https://rum.hlx.page/.rum/@adobe/helix-rum-js@%5E2/dist/rum-standalone.js" data-routing="env=prod,tier=publish,ams=Aviva Group"/> <link rel="preconnect" href="https://static.aviva.io/"/> <link rel="preconnect" href="https://static.aviva.io/" crossorigin="anonymous"/> <link rel="preconnect" href="https://dpm.demdex.net/"/> <link rel="preconnect" href="https://assets.adobedtm.com/"/> <link rel="preload" href="https://static.aviva.io/assets/fonts/sourcesans3-variable-roman-base.woff2" as="font" crossorigin="anonymous"/> <link rel="preload" href="https://cdn-ukwest.onetrust.com/scripttemplates/otSDKStub.js" as="script" crossorigin="anonymous"/> <link rel="preload" href="https://static.aviva.io/assets/fonts/avivacurve-regular.woff2" as="font" crossorigin="anonymous"/> <meta content="width=device-width,initial-scale=1" name="viewport"/> <meta property="templatename" content="featurelitepage"/> <meta property="article:published_time" content="2021-07-15T03:51:55"/> <meta property="og:description" content="Our Board is accountable for our long-term success. Itรขยยs made up of the Chair, and our exeโฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR13 | warning | the page does not mark out its main content, so what is unique to this page cannot be told apart from the menus and foot-of-page text repeated across the site | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page's main content is marked off from the navigation and footer around it. What good looks like A main or article region marks the primary content off from the navigation and footer around it. Why it matters Pulling the page's text returns menus and legal footers mixed with the substance, so the answer arrives buried in noise. What we found on this page the page does not mark out its main content, so what is unique to this page cannot be told apart from the menus and foot-of-page text repeated across the site The evidence, taken from the page as served The blocks this page marks out, as served
The page was read for the block that marks out its main content. <meta itemprop="name" content="Our Board"/> <meta itemprop="url" content="https://www.aviva.com/about-us/our-board-and-executives-overview/our-board/"/> <div class="l-whole-page" data-back-to-top="Back to start of main content" data-component="back-to-top-es6"> <script> <span data-module="app/init-es6" data-module-load="true"/> <script id="js-init" src="https://static.aviva.io/assets/themes-managed/v6.1.0/shared/extensions/requirejs/init.js" asynโฆ <script src="https://static.aviva.io/etc.clientlibs/settings/wcm/designs/aviva-corporate/clientlibs/resources/2-20260728โฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS01 | fail | 1 of 1 boxes in the page's forms carry no name saying what each is for, so which answer belongs in which box rests on layout alone | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Each box, dropdown and text area in a form carries a name saying what it is for. What good looks like Each field in a form carries a name saying what it is for. Why it matters Unnamed fields leave the tie between a question and its box resting on layout, which shifts as the page reflows. What we found on this page 1 of 1 boxes in the page's forms carry no name saying what each is for, so which answer belongs in which box rests on layout alone The evidence, taken from the page as served The form boxes that carry no name, as served
<input type="search" name="q" id="search-site" value="" class="m-site-search__input" placeholder="Enter a keyword"/> Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: each field in a form carries a name saying what it is for. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS10 | fail | the page's first heading is not its top-level heading, so the structure starts part way down | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check A page's headings start at the top level and step down without skipping a level. What good looks like The page's headings start at the top level and step down without skipping a level. Why it matters Content under a skipped level has no clear parent section, so structure taken from the page misplaces its text. What we found on this page the page's first heading is not its top-level heading, so the structure starts part way down The evidence, taken from the page as served The page's heading outline, in document order (a jump in level is marked)
H3 Recommendation to reject "mini-tender" offers by Litani LLC level jumped H1 Our Board H2 Explore page H2 Meet our Board H2 George Culmer H2 Dame Amanda Blanc H2 Charlotte Jones H2 Cheryl Agius H2 Andrea Blance H2 Ian Clark H2 Patrick Flynn H2 Shonaid Jemmett-Page H2 Mohit Joshi H2 Pippa Lambert H2 Jim McConville H2 Michael Mire H2 T.Neil Morrison H2 Susan Adams H2 Board information H2 Roles H2 Login or register H2 Site navigation H3 About us H4 Our purpose and priorities H4 Our customers and people H4 Our Board and Executives H4 2025 Annual Report H4 Get support H3 Investors H4 Strategy and performance H4 Institutional investors H4 Shareholder services H4 Corporate governance H4 Risk governance and management H4 2025 Annual Report H4 Get support H3 Newsroom H4 News and research H4 Resources H4 About Aviva H4 Get support H3 Careers H4 Careers at Aviva H4 Life at Aviva H4 Diversity and inclusion H4 Get support H3 Sustainability H4 Sustainability at Aviva H4 Sustainability news H4 Sustainability resources H4 Aviva Foundation H4 Get support H4 Get support H2 Footer H3 Useful information H4 Products in our locations H4 Use MyAviva H4 How to make a complaint H3 On this site H3 Media H3 Corporate H3 Other links H3 Social H3 Legal H3 Copyright
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page's headings start at the top level and step down without skipping a level. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT34 | fail | the page's own words are thin: 336 of its 400 words are shared navigation and footer, so it reads as 82% identical to another page, which a machine can then take as a duplicate and pass over, missing the little content that is its own; the matching page is named in the view | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether a page's own words are so few against a large shared navigation and footer that it reads as near-identical to other pages. What good looks like A page carries enough of its own words that a shared navigation and footer do not make it read as a copy of other pages. Why it matters When shared furniture is most of the text, distinct pages look like copies of each other and the little real content is easily passed over. What we found on this page the page's own words are thin: 336 of its 400 words are shared navigation and footer, so it reads as 82% identical to another page, which a machine can then take as a duplicate and pass over, missing the little content that is its own; the matching page is named in the view The evidence, taken from the page as served This page's own words, lost in shared navigation and footer
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: a page carries enough of its own words that a shared navigation and footer do not make it read as a copy of other pages. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 1 out of a possible 5, because it is one of the supporting checks, so it carries the lightest weight in the figure for this item. Why it moves the misinformation reading This failure is a real and common route to a wrong answer for the content it affects, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| DS03 | fail | an AI crawler asking for this page is refused by the security layer in front of the site, while an ordinary browser is served, so the page's content never reaches the AI and answers about it are left to memory or guesswork | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The same page loads for a browser but is refused when the request names itself as an AI service. What good looks like The page returns the same response to a named AI service as to a browser, with no edge block. Why it matters The block sits in front of the site and leaves no trace in its own logs, so the estate is closed off unnoticed. What we found on this page an AI crawler asking for this page is refused by the security layer in front of the site, while an ordinary browser is served, so the page's content never reaches the AI and answers about it are left to memory or guesswork The evidence, taken from the page as served The estate's edge tested with each AI crawler: a browser is served, the crawlers are refused
Hostwww.aviva.com · resolves to 23.215.224.114 · an Akamai edge hostname
Address trailwww.aviva.com › cert10.uk.aviva.com.ksd.edgekey.net › e5059.ksd.akamaiedge.net
Checked2026-07-31 16:33 UTC · request sent from 10.100.100.212 (our checker)
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page returns the same response to a named AI service as to a browser, with no edge block. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 5 out of a possible 5, because it is one of the checks that decide whether content can be reached and read at all, so it carries the heaviest weight in the figure for this item. Why it moves the misinformation reading This failure is a real and common route to a wrong answer for the content it affects, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT16 | warning | the page carries no structured data block stating what it is (not required; a hygiene signal) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The page carries structured data, the machine-readable summary of what it describes. What good looks like The page carries structured data summarising what it describes. Why it matters Vendors document this as optional rather than required, so its absence is a small forfeit and no more. What we found on this page the page carries no structured data block stating what it is (not required; a hygiene signal) The evidence, taken from the page as served The head of this page, as served
The page was read for a structured data block describing what the page is. <head> <title>Helping the UK Get Ready - Aviva plc</title> <script defer="defer" type="text/javascript" src="https://rum.hlx.page/.rum/@adobe/helix-rum-js@%5E2/dist/rum-standalone.js" data-routing="env=prod,tier=publish,ams=Aviva Group"/> <link rel="preconnect" href="https://static.aviva.io/"/> <link rel="preconnect" href="https://static.aviva.io/" crossorigin="anonymous"/> <link rel="preconnect" href="https://dpm.demdex.net/"/> <link rel="preconnect" href="https://assets.adobedtm.com/"/> <link rel="preload" href="https://static.aviva.io/assets/fonts/sourcesans3-variable-roman-base.woff2" as="font" crossorigin="anonymous"/> <link rel="preload" href="https://cdn-ukwest.onetrust.com/scripttemplates/otSDKStub.js" as="script" crossorigin="anonymous"/> <link rel="preload" href="https://static.aviva.io/assets/fonts/avivacurve-regular.woff2" as="font" crossorigin="anonymous"/> <meta content="width=device-width,initial-scale=1" name="viewport"/> <meta property="templatename" content="featurepage"/> <meta property="article:published_time" content="2026-06-08T09:32:52"/> <meta property="og:description" content="Aviva helps to strengthen communities, support people getting into work, restore โฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR13 | warning | the page does not mark out its main content, so what is unique to this page cannot be told apart from the menus and foot-of-page text repeated across the site | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page's main content is marked off from the navigation and footer around it. What good looks like A main or article region marks the primary content off from the navigation and footer around it. Why it matters Pulling the page's text returns menus and legal footers mixed with the substance, so the answer arrives buried in noise. What we found on this page the page does not mark out its main content, so what is unique to this page cannot be told apart from the menus and foot-of-page text repeated across the site The evidence, taken from the page as served The blocks this page marks out, as served
The page was read for the block that marks out its main content. <meta itemprop="name" content="Helping the UK Get Ready "/> <meta itemprop="url" content="https://www.aviva.com/about-us/our-purpose-and-priorities-overview/helping-the-uk-get-readโฆ <div class="l-whole-page" data-back-to-top="Back to start of main content" data-component="back-to-top-es6"> <script> <span data-module="app/init-es6" data-module-load="true"/> <script id="js-init" src="https://static.aviva.io/assets/themes-managed/v6.1.0/shared/extensions/requirejs/init.js" asynโฆ <script src="https://static.aviva.io/etc.clientlibs/settings/wcm/designs/aviva-corporate/clientlibs/resources/2-20260728โฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS01 | fail | 1 of 1 boxes in the page's forms carry no name saying what each is for, so which answer belongs in which box rests on layout alone | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Each box, dropdown and text area in a form carries a name saying what it is for. What good looks like Each field in a form carries a name saying what it is for. Why it matters Unnamed fields leave the tie between a question and its box resting on layout, which shifts as the page reflows. What we found on this page 1 of 1 boxes in the page's forms carry no name saying what each is for, so which answer belongs in which box rests on layout alone The evidence, taken from the page as served The form boxes that carry no name, as served
<input type="search" name="q" id="search-site" value="" class="m-site-search__input" placeholder="Enter a keyword"/> Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: each field in a form carries a name saying what it is for. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS10 | fail | the page's first heading is not its top-level heading, so the structure starts part way down | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check A page's headings start at the top level and step down without skipping a level. What good looks like The page's headings start at the top level and step down without skipping a level. Why it matters Content under a skipped level has no clear parent section, so structure taken from the page misplaces its text. What we found on this page the page's first heading is not its top-level heading, so the structure starts part way down The evidence, taken from the page as served The page's heading outline, in document order (a jump in level is marked)
H3 Recommendation to reject "mini-tender" offers by Litani LLC level jumped H1 Helping the UK Get Ready H2 Explore page H2 Ready for Tomorrow: Financial Confidence H2 Ready for Tomorrow: Financial Confidence H3 Transcript for video Ready for Tomorrow: Financial Confidence H3 The one who found balance H3 Building confidence, choice and control H2 How are we backing the UK? H3 Manchester รขยย building the future, today H3 Cambridge รขยย innovation and skills H3 London รขยย modern workplaces and future growth H3 London รขยย worldรขยยleading cancer research and innovation H2 How are we supporting people into work? H3 Transcriptย for video Building skills for the future H2 How are we protecting nature and climate? H3 Bringing rainforests back to the UK H3 Building Future Communities H2 Where are we investing in the UK? H3 Building a stronger, more resilient country H2 FAQs about 'Helping the UK Get Ready' H2 Login or register H2 Site navigation H3 About us H4 Our purpose and priorities H4 Our customers and people H4 Our Board and Executives H4 2025 Annual Report H4 Get support H3 Investors H4 Strategy and performance H4 Institutional investors H4 Shareholder services H4 Corporate governance H4 Risk governance and management H4 2025 Annual Report H4 Get support H3 Newsroom H4 News and research H4 Resources H4 About Aviva H4 Get support H3 Careers H4 Careers at Aviva H4 Life at Aviva H4 Diversity and inclusion H4 Get support H3 Sustainability H4 Sustainability at Aviva H4 Sustainability news H4 Sustainability resources H4 Aviva Foundation H4 Get support H4 Get support H2 Footer H3 Useful information H4 Products in our locations H4 Use MyAviva H4 How to make a complaint H3 On this site H3 Media H3 Corporate H3 Other links H3 Social H3 Legal H3 Copyright
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page's headings start at the top level and step down without skipping a level. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS14 | fail | 1 video(s) on the page with no captions on the video and no written transcript on the page: nothing spoken is available as text in any form | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether each video carries captions of its own, timed text on the video itself, judged together with whether the page holds a written transcript. What good looks like Captions carried on the video. A WARNING means the video has no captions but a written transcript on the page holds the words. A FAIL means neither exists, so nothing spoken is available as text in any form; that total absence is marked here once, not spread across two findings. Why it matters Spoken content that exists only as sound is invisible to a reader, human or machine: nothing said in the video can be found, read or quoted. What we found on this page 1 video(s) on the page with no captions on the video and no written transcript on the page: nothing spoken is available as text in any form The evidence, taken from the page as served Each video on the page, as served: its code, source file and caption track
No caption track on the video and no transcript link on the page. <video id="video6396859722112" data-embed="default" class="video-js" controls=""/> Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: captions carried on the video. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS16 | warning | 1 media resource(s) are named as a technical code, not human-meaningful words, so a machine cannot tell what the resource is from its name | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The name a video, audio clip or image is served under, and whether it is human-meaningful words or a technical code. What good looks like Video, audio and image files carry names made of words that say what they are, not a technical code. Why it matters A resource named as a code or a bare number says nothing about what it is, so a machine cataloguing it has only the code to go on. What we found on this page 1 media resource(s) are named as a technical code, not human-meaningful words, so a machine cannot tell what the resource is from its name The evidence, taken from the page as served The media resources whose name is a technical code, as served
A meaningful name (words that say what it is) lets a machine identify the resource; a code or a bare number cannot. <video id="video6396859722112" data-embed="default" class="video-js" controls=""/> | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| DS28 | fail | one link to sources on other sites was refused when it was checked. The page is still published, but the other site turns away requests that do not come from a person using a browser. It is listed in the view | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check For a single page, the share of its links to OTHER sites, sampled, that lead nowhere. The site's own links are assessed separately. What good looks like The page's references to other sites open for any reader. Where one refuses or has gone, the page carries the fact itself, shows the reference as plain text rather than as a link, or points to a source that answers. Why it matters The outside sources this page offers as support did not answer when they were asked for, so what the page claims is left resting on material that does not come back. In a regulated setting, where a link is carrying a figure or a required statement, that is the difference between a claim that is evidenced and one that is merely asserted. What we found on this page one link to sources on other sites was refused when it was checked. The page is still published, but the other site turns away requests that do not come from a person using a browser. It is listed in the view The evidence, taken from the page as served The external links checked on this page, with the status each returned
A link that did not open appears here in two forms. A DEAD link points at a page that has gone. A REFUSED link points at a page that is still published, but the other site turns away requests that do not come from a person using a browser, so our request was declined. Both land in the same place: the material this page offers as its support did not come back when it was asked for. The consequence is not a matter of tidiness. Where a link carries the weight of a claim, a figure, a policy or a regulatory statement, and the target does not open, the support behind that claim is missing at the moment it is needed. Three things follow, and each of them costs the organisation. The same fact gets taken from somewhere else, which hands a third party control of how the claim is worded. Or the claim is treated as unsupported and set aside. Or an answer is drawn from what remains on the page, and a partial account is presented as a complete one. A refused link is the worst of the three, because the page still reads as though the evidence sits one step away, so the gap is invisible and the answer carries false confidence. A refusal by another site is still this site's matter to resolve, because this site chose to rest a claim on it. Three practical ways close it. Carry the fact being relied on in the page's own words, so the claim stands without the visit. Keep the reference but stop making it a link, showing the address as plain text, so nothing promises a route that does not open. Or point to a source that answers any reader. Where the reference has to stay live, say beside it what a reader will meet, so no one is sent to a closed door without warning.
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page's references to other sites open for any reader. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 15 out of a possible 5, because it is one of the checks that decide whether content can be reached and read at all, so it carries the heaviest weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| DS03 | fail | an AI crawler asking for this page is refused by the security layer in front of the site, while an ordinary browser is served, so the page's content never reaches the AI and answers about it are left to memory or guesswork | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The same page loads for a browser but is refused when the request names itself as an AI service. What good looks like The page returns the same response to a named AI service as to a browser, with no edge block. Why it matters The block sits in front of the site and leaves no trace in its own logs, so the estate is closed off unnoticed. What we found on this page an AI crawler asking for this page is refused by the security layer in front of the site, while an ordinary browser is served, so the page's content never reaches the AI and answers about it are left to memory or guesswork The evidence, taken from the page as served The estate's edge tested with each AI crawler: a browser is served, the crawlers are refused
Hostwww.aviva.com · resolves to 23.215.224.114 · an Akamai edge hostname
Address trailwww.aviva.com › cert10.uk.aviva.com.ksd.edgekey.net › e5059.ksd.akamaiedge.net
Checked2026-07-31 16:33 UTC · request sent from 10.100.100.212 (our checker)
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page returns the same response to a named AI service as to a browser, with no edge block. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 5 out of a possible 5, because it is one of the checks that decide whether content can be reached and read at all, so it carries the heaviest weight in the figure for this item. Why it moves the misinformation reading This failure is a real and common route to a wrong answer for the content it affects, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT31 | warning | the page carries no description of itself in its head | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The page provides a meta description, the short summary offered alongside its title. What good looks like The page provides a meta description. Why it matters Absent, the page gives up its one documented summary field, though Google rewrites these freely anyway. What we found on this page the page carries no description of itself in its head The evidence, taken from the page as served The head of this page, as served
The head of the page was read for a description tag. <head> <title>Aviva venues - Aviva plc</title> <script defer="defer" type="text/javascript" src="https://rum.hlx.page/.rum/@adobe/helix-rum-js@%5E2/dist/rum-standalone.js" data-routing="env=prod,tier=publish,ams=Aviva Group"/> <link rel="preconnect" href="https://static.aviva.io/"/> <link rel="preconnect" href="https://static.aviva.io/" crossorigin="anonymous"/> <link rel="preconnect" href="https://dpm.demdex.net/"/> <link rel="preconnect" href="https://assets.adobedtm.com/"/> <link rel="preload" href="https://static.aviva.io/assets/fonts/sourcesans3-variable-roman-base.woff2" as="font" crossorigin="anonymous"/> <link rel="preload" href="https://cdn-ukwest.onetrust.com/scripttemplates/otSDKStub.js" as="script" crossorigin="anonymous"/> <link rel="preload" href="https://static.aviva.io/assets/fonts/avivacurve-regular.woff2" as="font" crossorigin="anonymous"/> <meta content="width=device-width,initial-scale=1" name="viewport"/> <meta property="templatename" content="featurepage"/> <meta property="article:published_time" content="2024-05-31T11:13:15"/> <meta property="og:title" content="Aviva venues"/> <meta property="og:url" content="https://www.aviva.com/about-us/our-purpose-and-priโฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT16 | warning | the page carries no structured data block stating what it is (not required; a hygiene signal) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The page carries structured data, the machine-readable summary of what it describes. What good looks like The page carries structured data summarising what it describes. Why it matters Vendors document this as optional rather than required, so its absence is a small forfeit and no more. What we found on this page the page carries no structured data block stating what it is (not required; a hygiene signal) The evidence, taken from the page as served The head of this page, as served
The page was read for a structured data block describing what the page is. <head> <title>Aviva venues - Aviva plc</title> <script defer="defer" type="text/javascript" src="https://rum.hlx.page/.rum/@adobe/helix-rum-js@%5E2/dist/rum-standalone.js" data-routing="env=prod,tier=publish,ams=Aviva Group"/> <link rel="preconnect" href="https://static.aviva.io/"/> <link rel="preconnect" href="https://static.aviva.io/" crossorigin="anonymous"/> <link rel="preconnect" href="https://dpm.demdex.net/"/> <link rel="preconnect" href="https://assets.adobedtm.com/"/> <link rel="preload" href="https://static.aviva.io/assets/fonts/sourcesans3-variable-roman-base.woff2" as="font" crossorigin="anonymous"/> <link rel="preload" href="https://cdn-ukwest.onetrust.com/scripttemplates/otSDKStub.js" as="script" crossorigin="anonymous"/> <link rel="preload" href="https://static.aviva.io/assets/fonts/avivacurve-regular.woff2" as="font" crossorigin="anonymous"/> <meta content="width=device-width,initial-scale=1" name="viewport"/> <meta property="templatename" content="featurepage"/> <meta property="article:published_time" content="2024-05-31T11:13:15"/> <meta property="og:title" content="Aviva venues"/> <meta property="og:url" content="https://www.aviva.com/about-us/our-purpose-and-priโฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR13 | warning | the page does not mark out its main content, so what is unique to this page cannot be told apart from the menus and foot-of-page text repeated across the site | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page's main content is marked off from the navigation and footer around it. What good looks like A main or article region marks the primary content off from the navigation and footer around it. Why it matters Pulling the page's text returns menus and legal footers mixed with the substance, so the answer arrives buried in noise. What we found on this page the page does not mark out its main content, so what is unique to this page cannot be told apart from the menus and foot-of-page text repeated across the site The evidence, taken from the page as served The blocks this page marks out, as served
The page was read for the block that marks out its main content. <meta itemprop="name" content="Aviva venues"/> <meta itemprop="url" content="https://www.aviva.com/about-us/our-purpose-and-priorities-overview/aviva-venues/"/> <div class="l-whole-page" data-back-to-top="Back to start of main content" data-component="back-to-top-es6"> <script> <span data-module="app/init-es6" data-module-load="true"/> <script id="js-init" src="https://static.aviva.io/assets/themes-managed/v6.1.0/shared/extensions/requirejs/init.js" asynโฆ <script src="https://static.aviva.io/etc.clientlibs/settings/wcm/designs/aviva-corporate/clientlibs/resources/2-20260728โฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS01 | fail | 1 of 1 boxes in the page's forms carry no name saying what each is for, so which answer belongs in which box rests on layout alone | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Each box, dropdown and text area in a form carries a name saying what it is for. What good looks like Each field in a form carries a name saying what it is for. Why it matters Unnamed fields leave the tie between a question and its box resting on layout, which shifts as the page reflows. What we found on this page 1 of 1 boxes in the page's forms carry no name saying what each is for, so which answer belongs in which box rests on layout alone The evidence, taken from the page as served The form boxes that carry no name, as served
<input type="search" name="q" id="search-site" value="" class="m-site-search__input" placeholder="Enter a keyword"/> Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: each field in a form carries a name saying what it is for. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS10 | fail | the page's first heading is not its top-level heading, so the structure starts part way down | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check A page's headings start at the top level and step down without skipping a level. What good looks like The page's headings start at the top level and step down without skipping a level. Why it matters Content under a skipped level has no clear parent section, so structure taken from the page misplaces its text. What we found on this page the page's first heading is not its top-level heading, so the structure starts part way down The evidence, taken from the page as served The page's heading outline, in document order (a jump in level is marked)
H3 Recommendation to reject "mini-tender" offers by Litani LLC level jumped H1 Aviva venues H2 Explore page H3 Aviva Arena H3 Aviva Studios H3 Aviva Stadium H2 Aviva Arena H2 Dame Amanda Blanc H2 Welcome to Aviva Arena H3 Transcript for video Welcome to Aviva Arena H2 Aviva Arena Stop Motion: Bringing the venue to Life H3 Transcript for video Aviva Arena Stop Motion: Bringing the venue to Life H2 Aviva Studios H3 Transcriptย for video Welcome to Aviva Studios H2 Aviva Studios: community and sustainability H2 Factory Academy H2 Aviva รยฃ10 Tickets H2 Official Sustainability Partner H2 Aviva Stadium H2 Irish Rugby Football Union H2 Football Association of Ireland H2 Aviva Stadium initiatives H2 Best Seat in the House H2 Aviva Mini Rugby H2 In Her Boots H2 Login or register H2 Site navigation H3 About us H4 Our purpose and priorities H4 Our customers and people H4 Our Board and Executives H4 2025 Annual Report H4 Get support H3 Investors H4 Strategy and performance H4 Institutional investors H4 Shareholder services H4 Corporate governance H4 Risk governance and management H4 2025 Annual Report H4 Get support H3 Newsroom H4 News and research H4 Resources H4 About Aviva H4 Get support H3 Careers H4 Careers at Aviva H4 Life at Aviva H4 Diversity and inclusion H4 Get support H3 Sustainability H4 Sustainability at Aviva H4 Sustainability news H4 Sustainability resources H4 Aviva Foundation H4 Get support H4 Get support H2 Footer H3 Useful information H4 Products in our locations H4 Use MyAviva H4 How to make a complaint H3 On this site H3 Media H3 Corporate H3 Other links H3 Social H3 Legal H3 Copyright
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page's headings start at the top level and step down without skipping a level. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS14 | fail | 1 video(s) on the page with no captions on the video and no written transcript on the page: nothing spoken is available as text in any form | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether each video carries captions of its own, timed text on the video itself, judged together with whether the page holds a written transcript. What good looks like Captions carried on the video. A WARNING means the video has no captions but a written transcript on the page holds the words. A FAIL means neither exists, so nothing spoken is available as text in any form; that total absence is marked here once, not spread across two findings. Why it matters Spoken content that exists only as sound is invisible to a reader, human or machine: nothing said in the video can be found, read or quoted. What we found on this page 1 video(s) on the page with no captions on the video and no written transcript on the page: nothing spoken is available as text in any form The evidence, taken from the page as served Each video on the page, as served: its code, source file and caption track
No caption track on the video and no transcript link on the page. <video id="video6339520026112" data-embed="default" class="video-js" controls=""/> Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: captions carried on the video. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS16 | warning | 1 media resource(s) are named as a technical code, not human-meaningful words, so a machine cannot tell what the resource is from its name | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The name a video, audio clip or image is served under, and whether it is human-meaningful words or a technical code. What good looks like Video, audio and image files carry names made of words that say what they are, not a technical code. Why it matters A resource named as a code or a bare number says nothing about what it is, so a machine cataloguing it has only the code to go on. What we found on this page 1 media resource(s) are named as a technical code, not human-meaningful words, so a machine cannot tell what the resource is from its name The evidence, taken from the page as served The media resources whose name is a technical code, as served
A meaningful name (words that say what it is) lets a machine identify the resource; a code or a bare number cannot. <video id="video6339520026112" data-embed="default" class="video-js" controls=""/> | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| DS03 | fail | an AI crawler asking for this page is refused by the security layer in front of the site, while an ordinary browser is served, so the page's content never reaches the AI and answers about it are left to memory or guesswork | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The same page loads for a browser but is refused when the request names itself as an AI service. What good looks like The page returns the same response to a named AI service as to a browser, with no edge block. Why it matters The block sits in front of the site and leaves no trace in its own logs, so the estate is closed off unnoticed. What we found on this page an AI crawler asking for this page is refused by the security layer in front of the site, while an ordinary browser is served, so the page's content never reaches the AI and answers about it are left to memory or guesswork The evidence, taken from the page as served The estate's edge tested with each AI crawler: a browser is served, the crawlers are refused
Hostwww.aviva.com · resolves to 23.215.224.114 · an Akamai edge hostname
Address trailwww.aviva.com › cert10.uk.aviva.com.ksd.edgekey.net › e5059.ksd.akamaiedge.net
Checked2026-07-31 16:33 UTC · request sent from 10.100.100.212 (our checker)
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page returns the same response to a named AI service as to a browser, with no edge block. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 5 out of a possible 5, because it is one of the checks that decide whether content can be reached and read at all, so it carries the heaviest weight in the figure for this item. Why it moves the misinformation reading This failure is a real and common route to a wrong answer for the content it affects, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT16 | warning | the page carries no structured data block stating what it is (not required; a hygiene signal) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The page carries structured data, the machine-readable summary of what it describes. What good looks like The page carries structured data summarising what it describes. Why it matters Vendors document this as optional rather than required, so its absence is a small forfeit and no more. What we found on this page the page carries no structured data block stating what it is (not required; a hygiene signal) The evidence, taken from the page as served The head of this page, as served
The page was read for a structured data block describing what the page is. <head> <title>Our customers and people overview - Aviva plc</title> <script defer="defer" type="text/javascript" src="https://rum.hlx.page/.rum/@adobe/helix-rum-js@%5E2/dist/rum-standalone.js" data-routing="env=prod,tier=publish,ams=Aviva Group"/> <link rel="preconnect" href="https://static.aviva.io/"/> <link rel="preconnect" href="https://static.aviva.io/" crossorigin="anonymous"/> <link rel="preconnect" href="https://dpm.demdex.net/"/> <link rel="preconnect" href="https://assets.adobedtm.com/"/> <link rel="preload" href="https://static.aviva.io/assets/fonts/sourcesans3-variable-roman-base.woff2" as="font" crossorigin="anonymous"/> <link rel="preload" href="https://cdn-ukwest.onetrust.com/scripttemplates/otSDKStub.js" as="script" crossorigin="anonymous"/> <link rel="preload" href="https://static.aviva.io/assets/fonts/avivacurve-regular.woff2" as="font" crossorigin="anonymous"/> <meta content="width=device-width,initial-scale=1" name="viewport"/> <meta property="templatename" content="categorypage"/> <meta property="article:published_time" content="2026-07-10T03:29:14"/> <meta property="og:description" content="This page brings together links to help you explore Aviva's customers aโฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR13 | warning | the page does not mark out its main content, so what is unique to this page cannot be told apart from the menus and foot-of-page text repeated across the site | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page's main content is marked off from the navigation and footer around it. What good looks like A main or article region marks the primary content off from the navigation and footer around it. Why it matters Pulling the page's text returns menus and legal footers mixed with the substance, so the answer arrives buried in noise. What we found on this page the page does not mark out its main content, so what is unique to this page cannot be told apart from the menus and foot-of-page text repeated across the site The evidence, taken from the page as served The blocks this page marks out, as served
The page was read for the block that marks out its main content. <meta itemprop="name" content="Our customers and people overview"/> <meta itemprop="url" content="https://www.aviva.com/about-us/our-customers-and-people-overview/"/> <div class="l-whole-page" data-back-to-top="Back to start of main content" data-component="back-to-top-es6"> <script> <span data-module="app/init-es6" data-module-load="true"/> <script id="js-init" src="https://static.aviva.io/assets/themes-managed/v6.1.0/shared/extensions/requirejs/init.js" asynโฆ <script src="https://static.aviva.io/etc.clientlibs/settings/wcm/designs/aviva-corporate/clientlibs/resources/2-20260728โฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS01 | fail | 1 of 1 boxes in the page's forms carry no name saying what each is for, so which answer belongs in which box rests on layout alone | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Each box, dropdown and text area in a form carries a name saying what it is for. What good looks like Each field in a form carries a name saying what it is for. Why it matters Unnamed fields leave the tie between a question and its box resting on layout, which shifts as the page reflows. What we found on this page 1 of 1 boxes in the page's forms carry no name saying what each is for, so which answer belongs in which box rests on layout alone The evidence, taken from the page as served The form boxes that carry no name, as served
<input type="search" name="q" id="search-site" value="" class="m-site-search__input" placeholder="Enter a keyword"/> Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: each field in a form carries a name saying what it is for. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS10 | fail | the page's first heading is not its top-level heading, so the structure starts part way down | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check A page's headings start at the top level and step down without skipping a level. What good looks like The page's headings start at the top level and step down without skipping a level. Why it matters Content under a skipped level has no clear parent section, so structure taken from the page misplaces its text. What we found on this page the page's first heading is not its top-level heading, so the structure starts part way down The evidence, taken from the page as served The page's heading outline, in document order (a jump in level is marked)
H3 Recommendation to reject "mini-tender" offers by Litani LLC level jumped H1 Our customers and people H2 Diversity, equity and inclusion H3 Diversity, equity and inclusion H3 Aviva Communities H3 Women in Finance Charter H3 UK Pay Gap Report H2 Our customers H3 Our customers H3 Doing the right thing, even when itรขยยs hard H3 New beginnings can happen at any age H3 Helping customers with lifeรขยยs big moves H3 Bringing comfort in a time of loss H3 Turning calls into connections H2 Our people H3 Our people H2 Our heritage H3 Our heritage H3 Timeline H3 Legacy companies H3 About the Archive H3 Remembrance H3 Amicable Contributors H3 Direct Line Archive H2 Our locations H3 Our locations H2 Explore our other About us pages H3 Our purpose and priorities H3 Our Board and Executives H2 Login or register H2 Site navigation H3 About us H4 Our purpose and priorities H4 Our customers and people H4 Our Board and Executives H4 2025 Annual Report H4 Get support H3 Investors H4 Strategy and performance H4 Institutional investors H4 Shareholder services H4 Corporate governance H4 Risk governance and management H4 2025 Annual Report H4 Get support H3 Newsroom H4 News and research H4 Resources H4 About Aviva H4 Get support H3 Careers H4 Careers at Aviva H4 Life at Aviva H4 Diversity and inclusion H4 Get support H3 Sustainability H4 Sustainability at Aviva H4 Sustainability news H4 Sustainability resources H4 Aviva Foundation H4 Get support H4 Get support H2 Footer H3 Useful information H4 Products in our locations H4 Use MyAviva H4 How to make a complaint H3 On this site H3 Media H3 Corporate H3 Other links H3 Social H3 Legal H3 Copyright
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page's headings start at the top level and step down without skipping a level. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| DS03 | fail | an AI crawler asking for this page is refused by the security layer in front of the site, while an ordinary browser is served, so the page's content never reaches the AI and answers about it are left to memory or guesswork | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The same page loads for a browser but is refused when the request names itself as an AI service. What good looks like The page returns the same response to a named AI service as to a browser, with no edge block. Why it matters The block sits in front of the site and leaves no trace in its own logs, so the estate is closed off unnoticed. What we found on this page an AI crawler asking for this page is refused by the security layer in front of the site, while an ordinary browser is served, so the page's content never reaches the AI and answers about it are left to memory or guesswork The evidence, taken from the page as served The estate's edge tested with each AI crawler: a browser is served, the crawlers are refused
Hostwww.aviva.com · resolves to 23.215.224.114 · an Akamai edge hostname
Address trailwww.aviva.com › cert10.uk.aviva.com.ksd.edgekey.net › e5059.ksd.akamaiedge.net
Checked2026-07-31 16:33 UTC · request sent from 10.100.100.212 (our checker)
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page returns the same response to a named AI service as to a browser, with no edge block. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 5 out of a possible 5, because it is one of the checks that decide whether content can be reached and read at all, so it carries the heaviest weight in the figure for this item. Why it moves the misinformation reading This failure is a real and common route to a wrong answer for the content it affects, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT16 | warning | the page carries no structured data block stating what it is (not required; a hygiene signal) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The page carries structured data, the machine-readable summary of what it describes. What good looks like The page carries structured data summarising what it describes. Why it matters Vendors document this as optional rather than required, so its absence is a small forfeit and no more. What we found on this page the page carries no structured data block stating what it is (not required; a hygiene signal) The evidence, taken from the page as served The head of this page, as served
The page was read for a structured data block describing what the page is. <head> <title>Group Executive Committee - Aviva plc</title> <script defer="defer" type="text/javascript" src="https://rum.hlx.page/.rum/@adobe/helix-rum-js@%5E2/dist/rum-standalone.js" data-routing="env=prod,tier=publish,ams=Aviva Group"/> <link rel="preconnect" href="https://static.aviva.io/"/> <link rel="preconnect" href="https://static.aviva.io/" crossorigin="anonymous"/> <link rel="preconnect" href="https://dpm.demdex.net/"/> <link rel="preconnect" href="https://assets.adobedtm.com/"/> <link rel="preload" href="https://static.aviva.io/assets/fonts/sourcesans3-variable-roman-base.woff2" as="font" crossorigin="anonymous"/> <link rel="preload" href="https://cdn-ukwest.onetrust.com/scripttemplates/otSDKStub.js" as="script" crossorigin="anonymous"/> <link rel="preload" href="https://static.aviva.io/assets/fonts/avivacurve-regular.woff2" as="font" crossorigin="anonymous"/> <meta content="width=device-width,initial-scale=1" name="viewport"/> <meta property="templatename" content="featurelitepage"/> <meta property="article:published_time" content="2021-07-15T04:01:09"/> <meta property="og:description" content="The Group Executive Committee is made up of our business CEOs and senior exeโฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR13 | warning | the page does not mark out its main content, so what is unique to this page cannot be told apart from the menus and foot-of-page text repeated across the site | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page's main content is marked off from the navigation and footer around it. What good looks like A main or article region marks the primary content off from the navigation and footer around it. Why it matters Pulling the page's text returns menus and legal footers mixed with the substance, so the answer arrives buried in noise. What we found on this page the page does not mark out its main content, so what is unique to this page cannot be told apart from the menus and foot-of-page text repeated across the site The evidence, taken from the page as served The blocks this page marks out, as served
The page was read for the block that marks out its main content. <meta itemprop="name" content="Group Executive Committee"/> <meta itemprop="url" content="https://www.aviva.com/about-us/our-board-and-executives-overview/our-group-executive-commiโฆ <div class="l-whole-page" data-back-to-top="Back to start of main content" data-component="back-to-top-es6"> <script> <span data-module="app/init-es6" data-module-load="true"/> <script id="js-init" src="https://static.aviva.io/assets/themes-managed/v6.1.0/shared/extensions/requirejs/init.js" asynโฆ <script src="https://static.aviva.io/etc.clientlibs/settings/wcm/designs/aviva-corporate/clientlibs/resources/2-20260728โฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS01 | fail | 1 of 1 boxes in the page's forms carry no name saying what each is for, so which answer belongs in which box rests on layout alone | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Each box, dropdown and text area in a form carries a name saying what it is for. What good looks like Each field in a form carries a name saying what it is for. Why it matters Unnamed fields leave the tie between a question and its box resting on layout, which shifts as the page reflows. What we found on this page 1 of 1 boxes in the page's forms carry no name saying what each is for, so which answer belongs in which box rests on layout alone The evidence, taken from the page as served The form boxes that carry no name, as served
<input type="search" name="q" id="search-site" value="" class="m-site-search__input" placeholder="Enter a keyword"/> Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: each field in a form carries a name saying what it is for. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS10 | fail | the page's first heading is not its top-level heading, so the structure starts part way down | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check A page's headings start at the top level and step down without skipping a level. What good looks like The page's headings start at the top level and step down without skipping a level. Why it matters Content under a skipped level has no clear parent section, so structure taken from the page misplaces its text. What we found on this page the page's first heading is not its top-level heading, so the structure starts part way down The evidence, taken from the page as served The page's heading outline, in document order (a jump in level is marked)
H3 Recommendation to reject "mini-tender" offers by Litani LLC level jumped H1 Our Group Executive Committee H2 Explore page H2 Meet our Group Executive Committee H2 Dame Amanda Blanc H2 Charlotte Jones H2 Doug Brown H2 Chris Cochrane H2 Nav Dhillon H2 Stephen Doherty H2 Craig Fazzini-Jones H2 Danielle Harmer H2 James Hillman H2 Martin OรขยยMalley H2 Jason Storah H2 Cheryl Toner H2 Mark Versey H2 Group Executive Committee information H2 Login or register H2 Site navigation H3 About us H4 Our purpose and priorities H4 Our customers and people H4 Our Board and Executives H4 2025 Annual Report H4 Get support H3 Investors H4 Strategy and performance H4 Institutional investors H4 Shareholder services H4 Corporate governance H4 Risk governance and management H4 2025 Annual Report H4 Get support H3 Newsroom H4 News and research H4 Resources H4 About Aviva H4 Get support H3 Careers H4 Careers at Aviva H4 Life at Aviva H4 Diversity and inclusion H4 Get support H3 Sustainability H4 Sustainability at Aviva H4 Sustainability news H4 Sustainability resources H4 Aviva Foundation H4 Get support H4 Get support H2 Footer H3 Useful information H4 Products in our locations H4 Use MyAviva H4 How to make a complaint H3 On this site H3 Media H3 Corporate H3 Other links H3 Social H3 Legal H3 Copyright
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page's headings start at the top level and step down without skipping a level. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT34 | fail | the page's own words are thin: 336 of its 403 words are shared navigation and footer, so it reads as 81% identical to another page, which a machine can then take as a duplicate and pass over, missing the little content that is its own; the matching page is named in the view | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether a page's own words are so few against a large shared navigation and footer that it reads as near-identical to other pages. What good looks like A page carries enough of its own words that a shared navigation and footer do not make it read as a copy of other pages. Why it matters When shared furniture is most of the text, distinct pages look like copies of each other and the little real content is easily passed over. What we found on this page the page's own words are thin: 336 of its 403 words are shared navigation and footer, so it reads as 81% identical to another page, which a machine can then take as a duplicate and pass over, missing the little content that is its own; the matching page is named in the view The evidence, taken from the page as served This page's own words, lost in shared navigation and footer
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: a page carries enough of its own words that a shared navigation and footer do not make it read as a copy of other pages. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 1 out of a possible 5, because it is one of the supporting checks, so it carries the lightest weight in the figure for this item. Why it moves the misinformation reading This failure is a real and common route to a wrong answer for the content it affects, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| DS03 | fail | an AI crawler asking for this page is refused by the security layer in front of the site, while an ordinary browser is served, so the page's content never reaches the AI and answers about it are left to memory or guesswork | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The same page loads for a browser but is refused when the request names itself as an AI service. What good looks like The page returns the same response to a named AI service as to a browser, with no edge block. Why it matters The block sits in front of the site and leaves no trace in its own logs, so the estate is closed off unnoticed. What we found on this page an AI crawler asking for this page is refused by the security layer in front of the site, while an ordinary browser is served, so the page's content never reaches the AI and answers about it are left to memory or guesswork The evidence, taken from the page as served The estate's edge tested with each AI crawler: a browser is served, the crawlers are refused
Hostwww.aviva.com · resolves to 23.215.224.114 · an Akamai edge hostname
Address trailwww.aviva.com › cert10.uk.aviva.com.ksd.edgekey.net › e5059.ksd.akamaiedge.net
Checked2026-07-31 16:33 UTC · request sent from 10.100.100.212 (our checker)
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page returns the same response to a named AI service as to a browser, with no edge block. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 5 out of a possible 5, because it is one of the checks that decide whether content can be reached and read at all, so it carries the heaviest weight in the figure for this item. Why it moves the misinformation reading This failure is a real and common route to a wrong answer for the content it affects, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT16 | warning | the page carries no structured data block stating what it is (not required; a hygiene signal) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The page carries structured data, the machine-readable summary of what it describes. What good looks like The page carries structured data summarising what it describes. Why it matters Vendors document this as optional rather than required, so its absence is a small forfeit and no more. What we found on this page the page carries no structured data block stating what it is (not required; a hygiene signal) The evidence, taken from the page as served The head of this page, as served
The page was read for a structured data block describing what the page is. <head> <title>Strategy and performance overview - Aviva plc</title> <script defer="defer" type="text/javascript" src="https://rum.hlx.page/.rum/@adobe/helix-rum-js@%5E2/dist/rum-standalone.js" data-routing="env=prod,tier=publish,ams=Aviva Group"/> <link rel="preconnect" href="https://static.aviva.io/"/> <link rel="preconnect" href="https://static.aviva.io/" crossorigin="anonymous"/> <link rel="preconnect" href="https://dpm.demdex.net/"/> <link rel="preconnect" href="https://assets.adobedtm.com/"/> <link rel="preload" href="https://static.aviva.io/assets/fonts/sourcesans3-variable-roman-base.woff2" as="font" crossorigin="anonymous"/> <link rel="preload" href="https://cdn-ukwest.onetrust.com/scripttemplates/otSDKStub.js" as="script" crossorigin="anonymous"/> <link rel="preload" href="https://static.aviva.io/assets/fonts/avivacurve-regular.woff2" as="font" crossorigin="anonymous"/> <meta content="width=device-width,initial-scale=1" name="viewport"/> <meta property="templatename" content="categorypage"/> <meta property="article:published_time" content="2026-07-10T04:52:38"/> <meta property="og:description" content="This page brings together links to help you explore Avivaรขยยs strategy โฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR13 | warning | the page does not mark out its main content, so what is unique to this page cannot be told apart from the menus and foot-of-page text repeated across the site | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page's main content is marked off from the navigation and footer around it. What good looks like A main or article region marks the primary content off from the navigation and footer around it. Why it matters Pulling the page's text returns menus and legal footers mixed with the substance, so the answer arrives buried in noise. What we found on this page the page does not mark out its main content, so what is unique to this page cannot be told apart from the menus and foot-of-page text repeated across the site The evidence, taken from the page as served The blocks this page marks out, as served
The page was read for the block that marks out its main content. <meta itemprop="name" content="Strategy and performance overview"/> <meta itemprop="url" content="https://www.aviva.com/investors/strategy-and-performance-overview/"/> <div class="l-whole-page" data-back-to-top="Back to start of main content" data-component="back-to-top-es6"> <script> <span data-module="app/init-es6" data-module-load="true"/> <script id="js-init" src="https://static.aviva.io/assets/themes-managed/v6.1.0/shared/extensions/requirejs/init.js" asynโฆ <script src="https://static.aviva.io/etc.clientlibs/settings/wcm/designs/aviva-corporate/clientlibs/resources/2-20260728โฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS01 | fail | 1 of 1 boxes in the page's forms carry no name saying what each is for, so which answer belongs in which box rests on layout alone | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Each box, dropdown and text area in a form carries a name saying what it is for. What good looks like Each field in a form carries a name saying what it is for. Why it matters Unnamed fields leave the tie between a question and its box resting on layout, which shifts as the page reflows. What we found on this page 1 of 1 boxes in the page's forms carry no name saying what each is for, so which answer belongs in which box rests on layout alone The evidence, taken from the page as served The form boxes that carry no name, as served
<input type="search" name="q" id="search-site" value="" class="m-site-search__input" placeholder="Enter a keyword"/> Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: each field in a form carries a name saying what it is for. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS10 | fail | the page's first heading is not its top-level heading, so the structure starts part way down | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check A page's headings start at the top level and step down without skipping a level. What good looks like The page's headings start at the top level and step down without skipping a level. Why it matters Content under a skipped level has no clear parent section, so structure taken from the page misplaces its text. What we found on this page the page's first heading is not its top-level heading, so the structure starts part way down The evidence, taken from the page as served The page's heading outline, in document order (a jump in level is marked)
H3 Recommendation to reject "mini-tender" offers by Litani LLC level jumped H1 Strategy and performance H2 Investment case, strategy and Annual Report H3 Investment case and strategy H3 2025 Annual Report H2 Results, presentations and reports H3 Results, presentations and reports H3 In focus presentations H3 Archive of past results H3 Archive of past presentations H3 Archive of past reports H2 Announcements and financial calendar H3 Regulatory announcements H3 Financial calendar H3 Acquisition of Direct Line Insurance Group plc H2 Explore our other Investor pages H3 Institutional investors H3 Shareholder services H3 Corporate governance H3 Risk governance and management H2 Login or register H2 Site navigation H3 About us H4 Our purpose and priorities H4 Our customers and people H4 Our Board and Executives H4 2025 Annual Report H4 Get support H3 Investors H4 Strategy and performance H4 Institutional investors H4 Shareholder services H4 Corporate governance H4 Risk governance and management H4 2025 Annual Report H4 Get support H3 Newsroom H4 News and research H4 Resources H4 About Aviva H4 Get support H3 Careers H4 Careers at Aviva H4 Life at Aviva H4 Diversity and inclusion H4 Get support H3 Sustainability H4 Sustainability at Aviva H4 Sustainability news H4 Sustainability resources H4 Aviva Foundation H4 Get support H4 Get support H2 Footer H3 Useful information H4 Products in our locations H4 Use MyAviva H4 How to make a complaint H3 On this site H3 Media H3 Corporate H3 Other links H3 Social H3 Legal H3 Copyright
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page's headings start at the top level and step down without skipping a level. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT34 | fail | the page's own words are thin: 336 of its 359 words are shared navigation and footer, so it reads as 93% identical to another page, which a machine can then take as a duplicate and pass over, missing the little content that is its own; the matching page is named in the view | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether a page's own words are so few against a large shared navigation and footer that it reads as near-identical to other pages. What good looks like A page carries enough of its own words that a shared navigation and footer do not make it read as a copy of other pages. Why it matters When shared furniture is most of the text, distinct pages look like copies of each other and the little real content is easily passed over. What we found on this page the page's own words are thin: 336 of its 359 words are shared navigation and footer, so it reads as 93% identical to another page, which a machine can then take as a duplicate and pass over, missing the little content that is its own; the matching page is named in the view The evidence, taken from the page as served This page's own words, lost in shared navigation and footer
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: a page carries enough of its own words that a shared navigation and footer do not make it read as a copy of other pages. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 1 out of a possible 5, because it is one of the supporting checks, so it carries the lightest weight in the figure for this item. Why it moves the misinformation reading This failure is a real and common route to a wrong answer for the content it affects, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| DS03 | fail | an AI crawler asking for this page is refused by the security layer in front of the site, while an ordinary browser is served, so the page's content never reaches the AI and answers about it are left to memory or guesswork | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The same page loads for a browser but is refused when the request names itself as an AI service. What good looks like The page returns the same response to a named AI service as to a browser, with no edge block. Why it matters The block sits in front of the site and leaves no trace in its own logs, so the estate is closed off unnoticed. What we found on this page an AI crawler asking for this page is refused by the security layer in front of the site, while an ordinary browser is served, so the page's content never reaches the AI and answers about it are left to memory or guesswork The evidence, taken from the page as served The estate's edge tested with each AI crawler: a browser is served, the crawlers are refused
Hostwww.aviva.com · resolves to 23.215.224.114 · an Akamai edge hostname
Address trailwww.aviva.com › cert10.uk.aviva.com.ksd.edgekey.net › e5059.ksd.akamaiedge.net
Checked2026-07-31 16:33 UTC · request sent from 10.100.100.212 (our checker)
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page returns the same response to a named AI service as to a browser, with no edge block. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 5 out of a possible 5, because it is one of the checks that decide whether content can be reached and read at all, so it carries the heaviest weight in the figure for this item. Why it moves the misinformation reading This failure is a real and common route to a wrong answer for the content it affects, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT16 | warning | the page carries no structured data block stating what it is (not required; a hygiene signal) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The page carries structured data, the machine-readable summary of what it describes. What good looks like The page carries structured data summarising what it describes. Why it matters Vendors document this as optional rather than required, so its absence is a small forfeit and no more. What we found on this page the page carries no structured data block stating what it is (not required; a hygiene signal) The evidence, taken from the page as served The head of this page, as served
The page was read for a structured data block describing what the page is. <head> <title>Institutional investors overview - Aviva plc</title> <script defer="defer" type="text/javascript" src="https://rum.hlx.page/.rum/@adobe/helix-rum-js@%5E2/dist/rum-standalone.js" data-routing="env=prod,tier=publish,ams=Aviva Group"/> <link rel="preconnect" href="https://static.aviva.io/"/> <link rel="preconnect" href="https://static.aviva.io/" crossorigin="anonymous"/> <link rel="preconnect" href="https://dpm.demdex.net/"/> <link rel="preconnect" href="https://assets.adobedtm.com/"/> <link rel="preload" href="https://static.aviva.io/assets/fonts/sourcesans3-variable-roman-base.woff2" as="font" crossorigin="anonymous"/> <link rel="preload" href="https://cdn-ukwest.onetrust.com/scripttemplates/otSDKStub.js" as="script" crossorigin="anonymous"/> <link rel="preload" href="https://static.aviva.io/assets/fonts/avivacurve-regular.woff2" as="font" crossorigin="anonymous"/> <meta content="width=device-width,initial-scale=1" name="viewport"/> <meta property="templatename" content="categorypage"/> <meta property="article:published_time" content="2026-07-10T04:52:48"/> <meta property="og:description" content="This page brings together links for Aviva's institutional investors."/> โฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR13 | warning | the page does not mark out its main content, so what is unique to this page cannot be told apart from the menus and foot-of-page text repeated across the site | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page's main content is marked off from the navigation and footer around it. What good looks like A main or article region marks the primary content off from the navigation and footer around it. Why it matters Pulling the page's text returns menus and legal footers mixed with the substance, so the answer arrives buried in noise. What we found on this page the page does not mark out its main content, so what is unique to this page cannot be told apart from the menus and foot-of-page text repeated across the site The evidence, taken from the page as served The blocks this page marks out, as served
The page was read for the block that marks out its main content. <meta itemprop="name" content="Institutional investors overview"/> <meta itemprop="url" content="https://www.aviva.com/investors/institutional-investors-overview/"/> <div class="l-whole-page" data-back-to-top="Back to start of main content" data-component="back-to-top-es6"> <script> <span data-module="app/init-es6" data-module-load="true"/> <script id="js-init" src="https://static.aviva.io/assets/themes-managed/v6.1.0/shared/extensions/requirejs/init.js" asynโฆ <script src="https://static.aviva.io/etc.clientlibs/settings/wcm/designs/aviva-corporate/clientlibs/resources/2-20260728โฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS01 | fail | 1 of 1 boxes in the page's forms carry no name saying what each is for, so which answer belongs in which box rests on layout alone | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Each box, dropdown and text area in a form carries a name saying what it is for. What good looks like Each field in a form carries a name saying what it is for. Why it matters Unnamed fields leave the tie between a question and its box resting on layout, which shifts as the page reflows. What we found on this page 1 of 1 boxes in the page's forms carry no name saying what each is for, so which answer belongs in which box rests on layout alone The evidence, taken from the page as served The form boxes that carry no name, as served
<input type="search" name="q" id="search-site" value="" class="m-site-search__input" placeholder="Enter a keyword"/> Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: each field in a form carries a name saying what it is for. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS10 | fail | the page's first heading is not its top-level heading, so the structure starts part way down | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check A page's headings start at the top level and step down without skipping a level. What good looks like The page's headings start at the top level and step down without skipping a level. Why it matters Content under a skipped level has no clear parent section, so structure taken from the page misplaces its text. What we found on this page the page's first heading is not its top-level heading, so the structure starts part way down The evidence, taken from the page as served The page's heading outline, in document order (a jump in level is marked)
H3 Recommendation to reject "mini-tender" offers by Litani LLC level jumped H1 Institutional investors H2 Information for institutional investors H3 Credit ratings and debt H3 Shareholder profile H3 Equity analysts H3 IR contacts H2 Explore our other Investor pages H3 Strategy and performance H3 Shareholder services H3 Corporate governance H3 Risk governance and management H2 Login or register H2 Site navigation H3 About us H4 Our purpose and priorities H4 Our customers and people H4 Our Board and Executives H4 2025 Annual Report H4 Get support H3 Investors H4 Strategy and performance H4 Institutional investors H4 Shareholder services H4 Corporate governance H4 Risk governance and management H4 2025 Annual Report H4 Get support H3 Newsroom H4 News and research H4 Resources H4 About Aviva H4 Get support H3 Careers H4 Careers at Aviva H4 Life at Aviva H4 Diversity and inclusion H4 Get support H3 Sustainability H4 Sustainability at Aviva H4 Sustainability news H4 Sustainability resources H4 Aviva Foundation H4 Get support H4 Get support H2 Footer H3 Useful information H4 Products in our locations H4 Use MyAviva H4 How to make a complaint H3 On this site H3 Media H3 Corporate H3 Other links H3 Social H3 Legal H3 Copyright
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page's headings start at the top level and step down without skipping a level. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT34 | fail | the page's own words are thin: 336 of its 346 words are shared navigation and footer, so it reads as 96% identical to another page, which a machine can then take as a duplicate and pass over, missing the little content that is its own; the matching page is named in the view | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether a page's own words are so few against a large shared navigation and footer that it reads as near-identical to other pages. What good looks like A page carries enough of its own words that a shared navigation and footer do not make it read as a copy of other pages. Why it matters When shared furniture is most of the text, distinct pages look like copies of each other and the little real content is easily passed over. What we found on this page the page's own words are thin: 336 of its 346 words are shared navigation and footer, so it reads as 96% identical to another page, which a machine can then take as a duplicate and pass over, missing the little content that is its own; the matching page is named in the view The evidence, taken from the page as served This page's own words, lost in shared navigation and footer
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: a page carries enough of its own words that a shared navigation and footer do not make it read as a copy of other pages. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 1 out of a possible 5, because it is one of the supporting checks, so it carries the lightest weight in the figure for this item. Why it moves the misinformation reading This failure is a real and common route to a wrong answer for the content it affects, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
The first documents discovered on the estate, scored separately from pages.
| Document information | |
|---|---|
| Title | Aviva plc Q1 2026 Trading Update announcement |
| Author | Aviva plc |
| PDF version, pages, size | 1.4 ยท 9 pages ยท 123 KB |
| Found on | https://www.aviva.com |
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| DS29 | fail | 14 of 15 AI crawlers asking for this document are refused by the security layer in front of the document host, while an ordinary browser is served, so the document is closed to nearly all AI systems and their answers about it are left to memory or guesswork. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The documents load for a browser but are refused when the request names itself as an AI service, tested on the host that actually serves them (often separate from the pages). What good looks like The document host returns the same response to a named AI service as to a browser, with no edge block. Why it matters The document is refused to AI crawlers at the edge, so its contents never reach the systems that answer about it, and what they state about it is left to guesswork. What we found on this page 14 of 15 AI crawlers asking for this document are refused by the security layer in front of the document host, while an ordinary browser is served, so the document is closed to nearly all AI systems and their answers about it are left to memory or guesswork. The evidence, taken from the page as served Each crawler's own request to this document, and the status it received
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the document host returns the same response to a named AI service as to a browser, with no edge block. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 5 out of a possible 5, because it is one of the checks that decide whether content can be reached and read at all, so it carries the heaviest weight in the figure for this item. Why it moves the misinformation reading This failure is a real and common route to a wrong answer for the content it affects, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| PD13 | warning | the document carries no underlying tags marking its headings, figures and reading order, so nothing in the file records how it is meant to be read | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the document carries the underlying tags that mark up its headings, figures and reading order. What good looks like The document carries an internal structure map, so it is tagged for reading order. Why it matters Without those tags the file records only where things sit on the page, which is why its headings and tables come apart when the text is read out. What we found on this page the document carries no underlying tags marking its headings, figures and reading order, so nothing in the file records how it is meant to be read The evidence, taken from the page as served This document's properties, as recorded in the file
The file was read for the underlying tags that mark up its headings, figures and reading order.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| PD12 | fail | 4 place(s) where separate table cells ran together when the text was read out, so a number can be read against the wrong row or column, a misread figure in the accounts | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether numbers in tables stay attached to their row and column once the text is pulled out. What good looks like Numbers in tables stay attached to their row and column once the text is pulled out. Why it matters A figure that comes loose from its heading is read against the wrong row or the wrong column, so the number an AI system quotes is not the number the document gives. What we found on this page 4 place(s) where separate table cells ran together when the text was read out, so a number can be read against the wrong row or column, a misread figure in the accounts The evidence, taken from the page as served The text as it reads out, at the places where a value and its label ran together
News Release 14 May 2026 Aviva plc Q1 2026 Trading Update Benefits of diversified model evident with strong growth in capital-light businesses Combined operating ratio improving and on course for 2026 guidance Firmly on track to meet Group targets General Insurance premiums1 ยฃ3.4bn +19%2 Q125: ยฃ2.9bn Group undiscounted COR 94.1% 2.5pp improvement Q125: 96.6% Wealth net flows ยฃ3.3bn +49% Q125: ยฃ2.3bn Wealth AUM ยฃ233bn +18% Q125: ยฃ197bn Solvency II cover ratio3 171% (9)pp FY25: 1 Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: numbers in tables stay attached to their row and column once the text is pulled out. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure is a real and common route to a wrong answer for the content it affects, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| PD25 | alert | the same content is not published as an ordinary web page, only as this PDF, which is a harder format to read reliably. This is an alert, not a fault in the document. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the same content is also published as an ordinary web page, not only as a download. What good looks like The same content is also published as an ordinary web page, not only as a download. Why it matters Without a page version the content exists only in document form, where its structure is far more fragile. What we found on this page the same content is not published as an ordinary web page, only as this PDF, which is a harder format to read reliably. This is an alert, not a fault in the document. The evidence, taken from the page as served Where an ordinary web page of this content was looked for
Each address below was asked for. A companion page is also matched by a title matching the document's own.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Document information | |
|---|---|
| Title | Aviva plc Results Announcement 2025 |
| Author | Aviva plc |
| PDF version, pages, size | 1.4 ยท 15 pages ยท 637 KB |
| Found on | https://www.aviva.com |
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| DS29 | fail | 14 of 15 AI crawlers asking for this document are refused by the security layer in front of the document host, while an ordinary browser is served, so the document is closed to nearly all AI systems and their answers about it are left to memory or guesswork. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The documents load for a browser but are refused when the request names itself as an AI service, tested on the host that actually serves them (often separate from the pages). What good looks like The document host returns the same response to a named AI service as to a browser, with no edge block. Why it matters The document is refused to AI crawlers at the edge, so its contents never reach the systems that answer about it, and what they state about it is left to guesswork. What we found on this page 14 of 15 AI crawlers asking for this document are refused by the security layer in front of the document host, while an ordinary browser is served, so the document is closed to nearly all AI systems and their answers about it are left to memory or guesswork. The evidence, taken from the page as served Each crawler's own request to this document, and the status it received
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the document host returns the same response to a named AI service as to a browser, with no edge block. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 5 out of a possible 5, because it is one of the checks that decide whether content can be reached and read at all, so it carries the heaviest weight in the figure for this item. Why it moves the misinformation reading This failure is a real and common route to a wrong answer for the content it affects, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| PD13 | warning | the document carries no underlying tags marking its headings, figures and reading order, so nothing in the file records how it is meant to be read | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the document carries the underlying tags that mark up its headings, figures and reading order. What good looks like The document carries an internal structure map, so it is tagged for reading order. Why it matters Without those tags the file records only where things sit on the page, which is why its headings and tables come apart when the text is read out. What we found on this page the document carries no underlying tags marking its headings, figures and reading order, so nothing in the file records how it is meant to be read The evidence, taken from the page as served This document's properties, as recorded in the file
The file was read for the underlying tags that mark up its headings, figures and reading order.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| PD11 | fail | no headings come through in the first page's text, so it reads as one undivided block with nothing to mark where its sections begin | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether headings on the document's first page are still recognisable once the text is pulled out. What good looks like Headings on the first page stay recognisable once the text is pulled out. Why it matters With no headings to divide it the document reads as one undivided block, so a passage loses the section it sat in. What we found on this page no headings come through in the first page's text, so it reads as one undivided block with nothing to mark where its sections begin The evidence, taken from the page as served The first page's text as it reads out, with no headings to be found
It takes Aviva Aviva plc Results Announcement 2025 Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: headings on the first page stay recognisable once the text is pulled out. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it does not move the misinformation reading This failure makes content harder to reach or to read, but it is not a direct route to a wrong answer, so it is held out of the misinformation reading rather than counted twice. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| PD12 | fail | the document has table-like content, but its column boundaries are lost when the text is read out (11 place(s) where separate cells ran together), so the numbers no longer line up with their row and column labels | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether numbers in tables stay attached to their row and column once the text is pulled out. What good looks like Numbers in tables stay attached to their row and column once the text is pulled out. Why it matters A figure that comes loose from its heading is read against the wrong row or the wrong column, so the number an AI system quotes is not the number the document gives. What we found on this page the document has table-like content, but its column boundaries are lost when the text is read out (11 place(s) where separate cells ran together), so the numbers no longer line up with their row and column labels The evidence, taken from the page as served The text as it reads out, at the places where a value and its label ran together
It takes Aviva Aviva plc Results Announcement 2025 News Release 5 March 2026 Aviva plc 2025 Results Announcement Excellent performance with operating profits up 25% โ extending multi-year track-record of delivery Group targets delivered one year early Confident in our trajectory and built for long-term success Operating profit1 Operating earnings per share1 IFRS return on equity1 Cash remittances Total dividend per share ยฃ2,203m +25% 2024: ยฃ1,767m 56.0p +17% 2024: 48.0p 17.5% +1.8pp 202 Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: numbers in tables stay attached to their row and column once the text is pulled out. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure is a real and common route to a wrong answer for the content it affects, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| PD14 | warning | the document has images but carries no text descriptions for them, so any figures that live only inside a chart or diagram are absent from the text | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether charts and images in the document carry a written description of what they show. What good looks like Charts and images in the document carry a written description of what they show. Why it matters Data living only inside a chart picture is absent from the document's text, so the figures behind it go unstated. What we found on this page the document has images but carries no text descriptions for them, so any figures that live only inside a chart or diagram are absent from the text The evidence, taken from the page as served Which pages carry images with no text description
Images with no text description appear on page(s): 1 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| PD25 | alert | the same content is not published as an ordinary web page, only as this PDF, which is a harder format to read reliably. This is an alert, not a fault in the document. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the same content is also published as an ordinary web page, not only as a download. What good looks like The same content is also published as an ordinary web page, not only as a download. Why it matters Without a page version the content exists only in document form, where its structure is far more fragile. What we found on this page the same content is not published as an ordinary web page, only as this PDF, which is a harder format to read reliably. This is an alert, not a fault in the document. The evidence, taken from the page as served Where an ordinary web page of this content was looked for
Each address below was asked for. A companion page is also matched by a title matching the document's own.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Document information | |
|---|---|
| Title | Aviva plc Annual Report and Accounts 2025 |
| Author | Aviva plc |
| PDF version, pages, size | 1.6 ยท 340 pages ยท 18469 KB |
| Found on | https://www.aviva.com |
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| DS29 | fail | 14 of 15 AI crawlers asking for this document are refused by the security layer in front of the document host, while an ordinary browser is served, so the document is closed to nearly all AI systems and their answers about it are left to memory or guesswork. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The documents load for a browser but are refused when the request names itself as an AI service, tested on the host that actually serves them (often separate from the pages). What good looks like The document host returns the same response to a named AI service as to a browser, with no edge block. Why it matters The document is refused to AI crawlers at the edge, so its contents never reach the systems that answer about it, and what they state about it is left to guesswork. What we found on this page 14 of 15 AI crawlers asking for this document are refused by the security layer in front of the document host, while an ordinary browser is served, so the document is closed to nearly all AI systems and their answers about it are left to memory or guesswork. The evidence, taken from the page as served Each crawler's own request to this document, and the status it received
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the document host returns the same response to a named AI service as to a browser, with no edge block. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 5 out of a possible 5, because it is one of the checks that decide whether content can be reached and read at all, so it carries the heaviest weight in the figure for this item. Why it moves the misinformation reading This failure is a real and common route to a wrong answer for the content it affects, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| PD19 | warning | the document is large (18469 KB); very large files risk being only partly read, so later sections may be missed | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The size of the file, and whether it passes the point where large documents risk partial processing. What good looks like The file sits within the size where documents process in full. Why it matters A very large file is at risk of being handled only in part, leaving later material out of what comes back. What we found on this page the document is large (18469 KB); very large files risk being only partly read, so later sections may be missed The evidence, taken from the page as served How large this document is
Measured from the file as the site served it.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| PD20 | warning | the document is 340 pages long; later sections of very long documents risk being only partly read | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The number of pages, and whether the document is long enough for its later sections to be at risk. What good looks like The document is short enough that its later pages process in full. Why it matters In a very long document the later chapters risk being left out, so what gets quoted comes only from the front. What we found on this page the document is 340 pages long; later sections of very long documents risk being only partly read The evidence, taken from the page as served How long this document is
Counted from the file as the site served it.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| PD11 | fail | no headings come through in the first page's text, so it reads as one undivided block with nothing to mark where its sections begin | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether headings on the document's first page are still recognisable once the text is pulled out. What good looks like Headings on the first page stay recognisable once the text is pulled out. Why it matters With no headings to divide it the document reads as one undivided block, so a passage loses the section it sat in. What we found on this page no headings come through in the first page's text, so it reads as one undivided block with nothing to mark where its sections begin The evidence, taken from the page as served The first page's text as it reads out, with no headings to be found
It takes A viva Aviva plc Annual Report and Accounts 2025 Aviva plc Annual Report and Accounts 2025 It takes Aviva Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: headings on the first page stay recognisable once the text is pulled out. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it does not move the misinformation reading This failure makes content harder to reach or to read, but it is not a direct route to a wrong answer, so it is held out of the misinformation reading rather than counted twice. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| PD12 | fail | 3 place(s) where separate table cells ran together when the text was read out, so a number can be read against the wrong row or column, a misread figure in the accounts | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether numbers in tables stay attached to their row and column once the text is pulled out. What good looks like Numbers in tables stay attached to their row and column once the text is pulled out. Why it matters A figure that comes loose from its heading is read against the wrong row or the wrong column, so the number an AI system quotes is not the number the document gives. What we found on this page 3 place(s) where separate table cells ran together when the text was read out, so a number can be read against the wrong row or column, a misread figure in the accounts The evidence, taken from the page as served The text as it reads out, at the places where a value and its label ran together
It takes A viva Aviva plc Annual Report and Accounts 2025 Aviva plc Annual Report and Accounts 2025 It takes Aviva Make the most out of life, plan for the future. Have the confidence that if things go wrong, weโll be there to help put them right. It takes Aviva. The Strategic report, Governance report, IFRS Financial Statements and Other information altogether comprise the Aviva plc Annual Report and Accounts 2025. The Strategic report contains information about Aviva, how we run our bu Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: numbers in tables stay attached to their row and column once the text is pulled out. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure is a real and common route to a wrong answer for the content it affects, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| PD14 | fail | 5 of 5 image(s) carry no text description of what they show, so figures that live only inside a chart or diagram are absent from the text and go unstated | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether charts and images in the document carry a written description of what they show. What good looks like Charts and images in the document carry a written description of what they show. Why it matters Data living only inside a chart picture is absent from the document's text, so the figures behind it go unstated. What we found on this page 5 of 5 image(s) carry no text description of what they show, so figures that live only inside a chart or diagram are absent from the text and go unstated The evidence, taken from the page as served Which pages carry images with no text description
Images with no text description appear on page(s): 1, 2, 3, 4, 5, 6, 7, 8 ; 5 image(s) with no description Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: charts and images in the document carry a written description of what they show. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure is a real and common route to a wrong answer for the content it affects, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| PD30 | warning | the document has 10 interactive form field(s); whatever is typed into them is not part of the page text, so those answers are not read out unless the form is saved as flat text | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the document contains fillable form fields whose typed-in answers sit outside the page text. What good looks like Any fillable fields use the standard AcroForm format rather than the older XFA one. Why it matters Answers typed into form fields sit outside the page's own text, so a completed form reads as though it were blank. What we found on this page the document has 10 interactive form field(s); whatever is typed into them is not part of the page text, so those answers are not read out unless the form is saved as flat text The evidence, taken from the page as served The interactive form fields whose typed-in answers are not part of the page text
X, Instagram, youtube, linkedin, Home, Button6, Button7, Button8, Strategic report, Button9 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| PD25 | alert | the same content is not published as an ordinary web page, only as this PDF, which is a harder format to read reliably. This is an alert, not a fault in the document. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the same content is also published as an ordinary web page, not only as a download. What good looks like The same content is also published as an ordinary web page, not only as a download. Why it matters Without a page version the content exists only in document form, where its structure is far more fragile. What we found on this page the same content is not published as an ordinary web page, only as this PDF, which is a harder format to read reliably. This is an alert, not a fault in the document. The evidence, taken from the page as served Where an ordinary web page of this content was looked for
Each address below was asked for. A companion page is also matched by a title matching the document's own.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Document information | |
|---|---|
| Title | Aviva plc Business model 2025 |
| Author | Aviva plc |
| PDF version, pages, size | 1.6 ยท 2 pages ยท 382 KB |
| Found on | https://www.aviva.com |
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| DS29 | fail | 14 of 15 AI crawlers asking for this document are refused by the security layer in front of the document host, while an ordinary browser is served, so the document is closed to nearly all AI systems and their answers about it are left to memory or guesswork. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The documents load for a browser but are refused when the request names itself as an AI service, tested on the host that actually serves them (often separate from the pages). What good looks like The document host returns the same response to a named AI service as to a browser, with no edge block. Why it matters The document is refused to AI crawlers at the edge, so its contents never reach the systems that answer about it, and what they state about it is left to guesswork. What we found on this page 14 of 15 AI crawlers asking for this document are refused by the security layer in front of the document host, while an ordinary browser is served, so the document is closed to nearly all AI systems and their answers about it are left to memory or guesswork. The evidence, taken from the page as served Each crawler's own request to this document, and the status it received
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the document host returns the same response to a named AI service as to a browser, with no edge block. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 5 out of a possible 5, because it is one of the checks that decide whether content can be reached and read at all, so it carries the heaviest weight in the figure for this item. Why it moves the misinformation reading This failure is a real and common route to a wrong answer for the content it affects, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| PD14 | warning | the document has images but none carry a text description of what they show, so any figures that live only inside a chart or diagram are absent from the text | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether charts and images in the document carry a written description of what they show. What good looks like Charts and images in the document carry a written description of what they show. Why it matters Data living only inside a chart picture is absent from the document's text, so the figures behind it go unstated. What we found on this page the document has images but none carry a text description of what they show, so any figures that live only inside a chart or diagram are absent from the text The evidence, taken from the page as served Which pages carry images with no text description
Images with no text description appear on page(s): 1, 2 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| PD30 | warning | the document has 1 interactive form field(s); whatever is typed into them is not part of the page text, so those answers are not read out unless the form is saved as flat text | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the document contains fillable form fields whose typed-in answers sit outside the page text. What good looks like Any fillable fields use the standard AcroForm format rather than the older XFA one. Why it matters Answers typed into form fields sit outside the page's own text, so a completed form reads as though it were blank. What we found on this page the document has 1 interactive form field(s); whatever is typed into them is not part of the page text, so those answers are not read out unless the form is saved as flat text The evidence, taken from the page as served The interactive form fields whose typed-in answers are not part of the page text
Home | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| PD32 | warning | the document does not state which language it is written in, so its language has to be guessed rather than read from the file | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the document declares which language it is written in, recorded in the file itself. What good looks like The document declares which language it is written in. Why it matters With no stated language the document offers no cue to which market or jurisdiction its wording belongs. What we found on this page the document does not state which language it is written in, so its language has to be guessed rather than read from the file The evidence, taken from the page as served This document's properties, as recorded in the file
The file's own properties were read for a stated language.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| PD25 | alert | the same content is not published as an ordinary web page, only as this PDF, which is a harder format to read reliably. This is an alert, not a fault in the document. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the same content is also published as an ordinary web page, not only as a download. What good looks like The same content is also published as an ordinary web page, not only as a download. Why it matters Without a page version the content exists only in document form, where its structure is far more fragile. What we found on this page the same content is not published as an ordinary web page, only as this PDF, which is a harder format to read reliably. This is an alert, not a fault in the document. The evidence, taken from the page as served Where an ordinary web page of this content was looked for
Each address below was asked for. A companion page is also matched by a title matching the document's own.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Document information | |
|---|---|
| Title | Transition Plan |
| Author | Aviva plc |
| PDF version, pages, size | 1.6 ยท 68 pages ยท 10490 KB |
| Found on | https://www.aviva.com |
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| DS29 | fail | 14 of 15 AI crawlers asking for this document are refused by the security layer in front of the document host, while an ordinary browser is served, so the document is closed to nearly all AI systems and their answers about it are left to memory or guesswork. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The documents load for a browser but are refused when the request names itself as an AI service, tested on the host that actually serves them (often separate from the pages). What good looks like The document host returns the same response to a named AI service as to a browser, with no edge block. Why it matters The document is refused to AI crawlers at the edge, so its contents never reach the systems that answer about it, and what they state about it is left to guesswork. What we found on this page 14 of 15 AI crawlers asking for this document are refused by the security layer in front of the document host, while an ordinary browser is served, so the document is closed to nearly all AI systems and their answers about it are left to memory or guesswork. The evidence, taken from the page as served Each crawler's own request to this document, and the status it received
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the document host returns the same response to a named AI service as to a browser, with no edge block. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 5 out of a possible 5, because it is one of the checks that decide whether content can be reached and read at all, so it carries the heaviest weight in the figure for this item. Why it moves the misinformation reading This failure is a real and common route to a wrong answer for the content it affects, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| PD26 | warning | the document is over a year old (last dated 2025-02): review whether it remains current | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check How old the document is, measured from the most recent date recorded inside the file. What good looks like The document's most recent internal date is recent rather than long past. Why it matters A document years past its last update still reads as a current statement, because nothing on it says otherwise. What we found on this page the document is over a year old (last dated 2025-02): review whether it remains current The evidence, taken from the page as served This document's properties, as recorded in the file
The date shown is the date the file records for itself.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| PD19 | warning | the document is large (10490 KB); very large files risk being only partly read, so later sections may be missed | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The size of the file, and whether it passes the point where large documents risk partial processing. What good looks like The file sits within the size where documents process in full. Why it matters A very large file is at risk of being handled only in part, leaving later material out of what comes back. What we found on this page the document is large (10490 KB); very large files risk being only partly read, so later sections may be missed The evidence, taken from the page as served How large this document is
Measured from the file as the site served it.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| PD13 | warning | the document carries no underlying tags marking its headings, figures and reading order, so nothing in the file records how it is meant to be read | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the document carries the underlying tags that mark up its headings, figures and reading order. What good looks like The document carries an internal structure map, so it is tagged for reading order. Why it matters Without those tags the file records only where things sit on the page, which is why its headings and tables come apart when the text is read out. What we found on this page the document carries no underlying tags marking its headings, figures and reading order, so nothing in the file records how it is meant to be read The evidence, taken from the page as served This document's properties, as recorded in the file
The file was read for the underlying tags that mark up its headings, figures and reading order.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| PD11 | fail | no headings come through in the first page's text, so it reads as one undivided block with nothing to mark where its sections begin | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether headings on the document's first page are still recognisable once the text is pulled out. What good looks like Headings on the first page stay recognisable once the text is pulled out. Why it matters With no headings to divide it the document reads as one undivided block, so a passage loses the section it sat in. What we found on this page no headings come through in the first page's text, so it reads as one undivided block with nothing to mark where its sections begin The evidence, taken from the page as served The first page's text as it reads out, with no headings to be found
Transition Plan Aviva plc February 2025 Aurora โ Avivaโs wind turbine Perth, Scotland Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: headings on the first page stay recognisable once the text is pulled out. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it does not move the misinformation reading This failure makes content harder to reach or to read, but it is not a direct route to a wrong answer, so it is held out of the misinformation reading rather than counted twice. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| PD14 | warning | the document has images but carries no text descriptions for them, so any figures that live only inside a chart or diagram are absent from the text | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether charts and images in the document carry a written description of what they show. What good looks like Charts and images in the document carry a written description of what they show. Why it matters Data living only inside a chart picture is absent from the document's text, so the figures behind it go unstated. What we found on this page the document has images but carries no text descriptions for them, so any figures that live only inside a chart or diagram are absent from the text The evidence, taken from the page as served Which pages carry images with no text description
Images with no text description appear on page(s): 1, 2, 3, 4, 5, 6 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| PD30 | warning | the document has 6 interactive form field(s); whatever is typed into them is not part of the page text, so those answers are not read out unless the form is saved as flat text | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the document contains fillable form fields whose typed-in answers sit outside the page text. What good looks like Any fillable fields use the standard AcroForm format rather than the older XFA one. Why it matters Answers typed into form fields sit outside the page's own text, so a completed form reads as though it were blank. What we found on this page the document has 6 interactive form field(s); whatever is typed into them is not part of the page text, so those answers are not read out unless the form is saved as flat text The evidence, taken from the page as served The interactive form fields whose typed-in answers are not part of the page text
Button1, Twitter, Instagram, youtube, linkedin, Button2 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| PD32 | warning | the document does not state which language it is written in, so its language has to be guessed rather than read from the file | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the document declares which language it is written in, recorded in the file itself. What good looks like The document declares which language it is written in. Why it matters With no stated language the document offers no cue to which market or jurisdiction its wording belongs. What we found on this page the document does not state which language it is written in, so its language has to be guessed rather than read from the file The evidence, taken from the page as served This document's properties, as recorded in the file
The file's own properties were read for a stated language.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| PD25 | alert | the same content is not published as an ordinary web page, only as this PDF, which is a harder format to read reliably. This is an alert, not a fault in the document. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the same content is also published as an ordinary web page, not only as a download. What good looks like The same content is also published as an ordinary web page, not only as a download. Why it matters Without a page version the content exists only in document form, where its structure is far more fragile. What we found on this page the same content is not published as an ordinary web page, only as this PDF, which is a harder format to read reliably. This is an alert, not a fault in the document. The evidence, taken from the page as served Where an ordinary web page of this content was looked for
Each address below was asked for. A companion page is also matched by a title matching the document's own.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
This report is Stage 1, Foundations: each automated test the engine can run without human input, so there is a usable result at the first stage. Governance (owner-confirmed truth) and Visibility (how AI agents find the estate) are later stages and are shown greyed above.
What was assessed. 37 pages were assessed, selected from 120 reviewed using the site's own signals of importance (its navigation, homepage links, most-linked pages, sitemap, and any llms.txt file), and the first 5 PDF documents found were assessed separately. The industry in the header is classified from the site's own content. The traffic classification comes from a recognised top-sites list or a connected traffic provider; it reads NA when the domain is not connected to a traffic source.
Header identity signals. The regulated sector and listed company values are inferred from the same crawled content, and shown here so the header can stay to the answer alone. Regulated sector reads “Yes”: insurance sector; no explicit regulator statement in the sampled pages. Listed company reads “Yes (public)”: traded on london stock exchange (av.).
AI readiness is the weighted share of checks that passed, reported separately for pages and for PDF documents because each is reached and corrected differently. Grade A checks decide whether content can be reached and read at all; grade B whether it is understood correctly; grade C support reliability. A measured score is scaled into a ceiling when an access gate binds it (for example the site blocking AI crawlers at its edge): content that cannot be reached is not partially ready. Scores never read exactly 25, 50, 75 or 100, because those are buckets, not measurements.
Likelihood of misinformation is a band, given as a worst case (the highest any single item or estate-wide finding reaches) and a typical position across the pages or documents. Only checks whose failure is a direct route to a wrong answer carry a band; the rest affect readiness only.
| Band | Range | Meaning |
|---|---|---|
| Likely zero | 0-5% | No failing misinformation-bearing checks. |
| Very little | 6-25% | Unlikely to cause wrong information. |
| Likely | 26-50% | Could contribute to wrong information in some cases. |
| Very likely | 51-75% | A real and common route to wrong information. |
| Extremely likely | 76-100% | A frequent and direct cause of wrong information. |
Of the register's 187 checks, 114 ran automatically in this Foundations stage. 64 are governance questions for the next stage. The remainder need organisation-supplied data or an external service; each check that did not run is listed in the exports.
About us
We have been doing this for 25 years. For the last two years, we have been training AI to understand and map AI Readiness (fundamentals, governance, visibility), against our unique dataset of more than 3.7 trillion data points.
Who’s talking about us