AI Readiness Assessment
https://www.newcastle.gov.uk
Assessed2026-09-17
Reference0917/NEW/53
IndustryGovernment and public sector
Regulated · ListedNone found · No
Scale207 / 2,831
Registered identity from official sources
Registered nameNEWCASTLE-UPON-TYNE CORP
Country of incorporationUnited Kingdom
Company number03582739
Legal entity identifier213800NYIUFGF6FDJG51
Listing
Primary listingLondon Stock Exchange
ISINGB0006355217
Security3.5% Irredeemable Stock
FCA Official List (Debt and debt-like securities, LSE) · GLEIF (legal identity, matched on registered name) · retrieved 2026-09-17 16:37 UTC
Foundations assessed now ยท the automated tests
Your Digital Doorway
PeopleAI systems
Credibility ยท E-E-A-T
65.2%
AI readiness ยท Pages
28.8%
AI readiness ยท PDFs
39.1%
Misinformation ยท Pages
Extremely likely
Misinformation ยท PDFs
Extremely likely
0%25%50%75%100%
Governancestage 2 ยท not assessed yet...more
43 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.
Visibilitystage 3 ยท not assessed yet...more
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.
Key findings ยท AI readiness
How much of your content is reachable and readable, rather than blocked, buried or missing. Higher is better.
AI readiness is very low.AI systems get nothing at the door of the site, so most of the content cannot be reached at all, however well the pages themselves are built.
What is holding it back
- Where a page carries exact facts, an address, opening hours, a price, a date, leaving them only in prose means they are worked out rather than read, and that is where a wrong branch or an old price comes from.37 pages
- Without headers a figure is extracted as a bare number, so it gets quoted against the wrong heading.5 pages
- A page that is slow to answer is left behind: the reader gives up and takes its answer from someone else's material, so your own words play no part in it.16 pages
- A document stores its text as shapes; unless the font says which character each shape is, a reader can see the words but cannot know what they say. Text that cannot be named cannot be quoted, searched or read aloud correctly.3 documents
- With no headings to divide it the document reads as one undivided block, so a passage loses the section it sat in.4 documents
Key findings ยท Misinformation
Where your content could lead an AI system to state something incorrect. Only direct routes to a wrong answer count here.
Misinformation is extremely likely.The pages read as extremely likely and the documents as extremely likely to cause it.
What could cause it
- Duplicates collapse to a single surviving version, and which one survives is not the publisher's choice.pages
- The page gives two different answers about which of its addresses is the official one. A contradiction like that gets ignored, so outside systems decide for themselves which copy of the page to use.pages
- A site under load or in maintenance often answers as though nothing were wrong, returning a short notice in place of the page. Anything reading it, a person or an AI system, receives that notice as the organisation's page and takes it as what the organisation has to say. Where this happens across the site, an assessment of it describes the notice rather than the estate, and any figure drawn from it has to be read in that light.pages
- Some images in the document have no text description, so whatever they show is missing from the document's text. A chart is the classic loss: the picture holds the figures and the text never states them.documents
- Repeated pages can carry an old version beside the new one, so superseded wording sits inside the same file.documents
- When a source is only typed out as text, there is no link behind it to follow, so the reference cannot be opened or checked.documents
▸What makes up these figures door, site, pages and documents · click to view
The front doorClosed to OpenAI, Anthropic, Perplexity, Meta and Mistral, who answer people's questions. Closed to 9 services that gather material for future answers: OpenAI, Anthropic, Google, Common Crawl and 5 others.
The site as a whole10.6%Blocking at the front door, Repeated pages hold the whole estate back.
Your pages28.8%What your pages say comes back usable, but unevenly: your best reaches 32.7%, your weakest 9.7%.
Your documents39.1%What your documents say comes back readable, ready to be quoted.
▸Digital doorway measured at the front door · click to view
Anyone asking for this site, a person on a phone or an AI system building an answer, is let in, turned away, or left with no answer, in milliseconds, by machinery most organisations never see. An AI system that gets nothing here reads nothing at all: to that system the organisation simply does not answer.
People
2 out of 4 served
AI systems
14 out of 22 sent to another site
The proof behind this picture
29 live agents were first set up and readied for this assessment. 26 were sent to this door: 4 people and 22 AI systems, in the order shown on the chart; the other 3 stood ready as backup, to be called in depending on how the door answered. Of those sent, 24 made one timed call each, in their own name, asking for the same page. The 2 desktop browsers made a full visit, exactly as a person at a computer would. Nothing here is simulated: these are real calls to the live site, recorded as they happened, and each line below carries the moment it happened. Alongside them, two further readings were taken at the door: the site's security certificate, and its published rules for crawlers.
Called from54.171.52.206
The door, atwww.newcastle.gov.uk · 194.61.173.205
Started2026-09-17 16:33:36 UTC
Finished2026-09-17 16:33:46 UTC
| Visitor | When | What happened | Answer | Took | Sent | Received | Answered from |
|---|---|---|---|---|---|---|---|
| People | |||||||
| iPhone user | 16:33:38.288 | ✗ sent to another site | 307 | 90 ms | 254 B | 795 B | 194.61.173.205 |
| Android user | 16:33:38.288 | ✗ sent to another site | 307 | 93 ms | 236 B | 795 B | 194.61.173.205 |
| Safari on a Mac | 16:33:42.859 | ✓ served | 200 | 1396 ms | n/a | n/a | n/a |
| Chrome on a PC | 16:33:44.519 | ✓ served | 200 | 1284 ms | n/a | n/a | n/a |
| AI systems | |||||||
| GPTBot · OpenAI | 16:33:37.681 | ✗ sent to another site | 307 | 104 ms | 221 B | 795 B | 194.61.173.205 |
| OAI-SearchBot · OpenAI | 16:33:37.681 | ✓ served | 200 | 214 ms | 326 B | 97.2 KB | 194.61.173.205 |
| ChatGPT-User · OpenAI | 16:33:37.681 | ✗ sent to another site | 307 | 109 ms | 224 B | 795 B | 194.61.173.205 |
| ClaudeBot · Anthropic | 16:33:37.681 | ✗ sent to another site | 307 | 105 ms | 184 B | 795 B | 194.61.173.205 |
| Claude-SearchBot · Anthropic | 16:33:37.681 | ✓ served | 200 | 212 ms | 264 B | 97.2 KB | 194.61.173.205 |
| Claude-User · Anthropic | 16:33:37.681 | ✗ sent to another site | 307 | 101 ms | 226 B | 795 B | 194.61.173.205 |
| Googlebot (Gemini) | 16:33:37.783 | ✓ served | 200 | 220 ms | 288 B | 97.2 KB | 194.61.173.205 |
| GoogleOther | 16:33:37.785 | ✗ sent to another site | 307 | 94 ms | 225 B | 795 B | 194.61.173.205 |
| Bingbot (Copilot) · Microsoft | 16:33:37.787 | ✓ served | 200 | 203 ms | 287 B | 97.2 KB | 194.61.173.205 |
| PerplexityBot | 16:33:37.790 | ✓ served | 200 | 206 ms | 266 B | 97.2 KB | 194.61.173.205 |
| Perplexity-User | 16:33:37.879 | ✗ sent to another site | 307 | 93 ms | 242 B | 795 B | 194.61.173.205 |
| CCBot · Common Crawl | 16:33:37.893 | ✗ sent to another site | 307 | 90 ms | 159 B | 795 B | 194.61.173.205 |
| Bytespider · ByteDance | 16:33:37.895 | ✗ sent to another site | 307 | 89 ms | 267 B | 795 B | 194.61.173.205 |
| Amazonbot | 16:33:37.973 | ✗ sent to another site | 307 | 89 ms | 227 B | 795 B | 194.61.173.205 |
| GrokBot · xAI | 16:33:37.984 | ✗ sent to another site | 307 | 93 ms | 171 B | 795 B | 194.61.173.205 |
| Meta-ExternalAgent | 16:33:37.985 | ✗ sent to another site | 307 | 91 ms | 208 B | 795 B | 194.61.173.205 |
| Meta-WebIndexer | 16:33:37.990 | ✓ served | 200 | 208 ms | 238 B | 97.2 KB | 194.61.173.205 |
| Meta-ExternalFetcher | 16:33:37.998 | ✗ sent to another site | 307 | 87 ms | 210 B | 795 B | 194.61.173.205 |
| Applebot | 16:33:38.004 | ✓ served | 200 | 201 ms | 314 B | 97.2 KB | 194.61.173.205 |
| MistralAI-Training | 16:33:38.062 | ✗ sent to another site | 307 | 92 ms | 238 B | 795 B | 194.61.173.205 |
| MistralAI-Index | 16:33:38.077 | ✓ served | 200 | 209 ms | 263 B | 97.2 KB | 194.61.173.205 |
| MistralAI-User | 16:33:38.078 | ✗ sent to another site | 307 | 90 ms | 234 B | 795 B | 194.61.173.205 |
The desktop browsers are run in full rather than as a single call, so one figure for the information moved does not apply to them; their outcome and timing are shown.
What this shows
2 of the 4 people were served. 8 of the 22 AI systems were served and 14 were sent to another site. The visitors fall into two groups, and each is judged on its own. 8 of the 13 services that answer people's questions were let in; OpenAI, Anthropic, Perplexity, Meta and Mistral were sent to another site. 0 of the 9 services that gather material for future answers were let in; OpenAI, Anthropic, Google, Common Crawl, ByteDance and 4 others were sent to another site. Where a service arrived carrying a question, it typed the organisation's own name, โNewcastle upon Tyneโ, into the search box in the site's page header. The sizes tell the same story: a caller who is served receives the page in full, about 97.2 KB here, while a caller who is turned away receives a short refusal in its place, about 795 B, and nothing more. There is a pattern in who is refused: the door turns away the crawlers that gather pages for AI systems to learn from, while serving the ones that fetch a page when a person asks a question at that moment. That reads as a chosen policy rather than an accident. A door of this kind decides call by call. This record is what happened at this door, at this time, from this address; it can answer differently at another time, which is why the time and the address are part of the record.
How this stands up
These calls can be repeated on request while you watch. A separate checking tool, kept apart from the assessment engine so the two cannot share a mistake, knocks on the same door several times over and records whether the answers hold still; each of its checks is saved with the date, the time and the calling address.
▸E-E-A-T credibility in Google’s four terms · 65.2% · click to view
Four questions a reader asks before believing what a site says: can it be relied on, is the organisation recognised, is it clear who wrote it, and does it show first-hand knowledge. Each is measured from the checks that carry it, and the four combine into one score.
| Pillar | What it measures | Score | Weight | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Trust | Can what this site says be relied on? | 69.7% | 35% | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
How this pillar was measured
17 checks carry this pillar. They produced 148 results across the pages and documents assessed: 63 passed, 80 were flagged, 5 failed. The score is the weighted share that passed, with a flagged result counting as half.
What is holding this pillar down
failHow old the document is, measured from the most recent date recorded inside the file.3 of 5What 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. Where it was found, and what was found there
failWhether the document records when it was created or last changed, alongside the software that made it.2 of 5What good looks like The document records when it was created or last changed. Why it matters With no dates on the file there is no way to tell a document written last month from one written a decade ago. Where it was found, and what was found there
failWhether the site's own pages link to its legal and policy pages, such as the privacy policy and the terms, or whether those pages are published with no link leading to them.across the siteWhat good looks like A link somewhere on the site leads to each legal and policy page, so anyone reading the site can reach them. Why it matters Your privacy policy and terms may never be read, even though they are published. A page no other page links to is never found by readers that follow links, so answers about your policies are built without the words you actually published. Where it was found, and what was found there
warningThe copyright line at the foot of the page, and the year it states.37 of 37What good looks like The copyright line states the current year. Why it matters An old copyright year reads as a site nobody is looking after, and it dates the page for anything that relies on dates. Content can be treated as years older than it really is. Where it was found, and what was found there
…and 25 more like these. The full record is in the exports. warningThe page carries a date, ideally written into the markup rather than sitting only in the text.34 of 37What good looks like The page carries a date, ideally written into the markup rather than sitting only in the text. Why it matters An undated page gives nothing to weigh its age against, so old and new material are treated alike. Where it was found, and what was found there
…and 22 more like these. The full record is in the exports. warningPercentages and money figures in the page's words, and whether a source is named or linked in the same passage.6 of 12What good looks like A published figure names its source in the same passage. Why it matters A figure with no source cannot be checked by a reader or by anything quoting it. It travels on the organisation's name alone, and it is repeated that way. Where it was found, and what was found there
warningClaims repeated across pages in wordings that nearly match but differ in their words.across the siteWhat good looks like A claim repeated across pages is repeated in the same words. Why it matters Several wordings of one claim each carry part of its standing, and a correction made to one leaves the rest in place. Where it was found, and what was found there
warningClaims of being largest, leading, best or first in the page's words, and whether a figure or a source sits in the same passage.1 of 37What good looks like A claim of standing carries the figure or the source that supports it. Why it matters A claim of standing with no figure beside it is a statement about the organisation made by the organisation. Taken out and repeated, it carries the weight of a measured fact while resting on nothing. Where it was found, and what was found there
What passed
9 of the 17 checks in this pillar passed on each item assessed
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Authoritativeness | Is this plainly the organisation it says it is? | 40.0% | 30% | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
How this pillar was measured
6 checks carry this pillar. They produced 157 results across the pages and documents assessed: 41 passed, 83 were flagged, 33 failed. The score is the weighted share that passed, with a flagged result counting as half.
What is holding this pillar down
failWhether the page states what it is, and the exact facts it carries, in a form a machine can take as given rather than work out from the wording.37 of 37What good looks like The page states what it is in machine-readable form, and where it carries exact facts it states those too. A page of exact facts stating none of them is a fail; a narrative page without a block is a warning. Why it matters Where a page carries exact facts, an address, opening hours, a price, a date, leaving them only in prose means they are worked out rather than read, and that is where a wrong branch or an old price comes from. Where it was found, and what was found there
…and 25 more like these. The full record is in the exports. failWhether the document carries a title in its own properties, not just a name on the link to it.3 of 5What good looks like The document carries a title in its own properties. Why it matters Without a title the document is identified by its file name and by whatever the links to it happen to say. Where it was found, and what was found there
failThe file's name, read together with the title in the file's own properties: whether its words, dates and period markers say what the document is.3 of 5What good looks like A name whose words and dates identify the document, such as FY_2025_Announcement.pdf, passes. A WARNING means the name only half-identifies it: a single hinting word, period markers without a subject (FY25_Q3.pdf), or a weak name that the file's own title completes. A FAIL means a code or generic name, such as IMG_1234.pdf, with no title in the properties either, so nothing anywhere says what the document is. Why it matters The document has no usable name anywhere, neither in its file name nor in its own properties. Nobody, human or AI, can tell what it is without opening it, so it gets quoted blind or passed over. Where it was found, and what was found there
warningThe short title, description and image the page offers to services that show a preview of it, and whether they match the page.37 of 37What good looks like The page offers a summary for preview, and the summary is true to the page. Why it matters This summary travels further than the page does. It is what appears when the address is shared, and several services read it in preference to the page itself because it is short and already written for the purpose. Where it is absent, those services compose their own from whatever they find first, which is often navigation. Where it is present but out of step, the organisation is described to a wide audience by a sentence it wrote once and forgot. Where it was found, and what was found there
…and 25 more like these. The full record is in the exports. warningThe trail showing the path from the front page to this one, and whether the machine-readable version of that trail says the same.36 of 36What good looks like The page shows its place in the site, and says the same thing to a machine. Why it matters A page read on its own gives no sense of what it belongs to. The trail supplies it: one product within a range, one policy within a set. A reader deciding whether a page answers a question uses that to judge whether it has the right one, and how to describe it when it quotes it. Where the shown trail and the machine-readable one disagree, the page is placed in two positions at once and neither can be relied on. Where it was found, and what was found there
…and 24 more like these. The full record is in the exports. What passed
1 of the 6 checks in this pillar passed on each item assessed
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Expertise | Is it clear who stands behind the words? | 70.0% | 20% | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
How this pillar was measured
2 checks carry this pillar. They produced 10 results across the pages and documents assessed: 7 passed, 3 failed. The score is the weighted share that passed, with a flagged result counting as half.
What is holding this pillar down
failWhether the author field names a person or an organisation, rather than a placeholder or a tool name.3 of 5What good looks like The author field names a person or an organisation, not a placeholder or a tool name. Why it matters With no named author the document carries no accountable source, so nothing shows who stands behind it. Where it was found, and what was found there
What passed
1 of the 2 checks in this pillar passed on each item assessed
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Experience | Does the content show first-hand knowledge? | 98.7% | 15% | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
How this pillar was measured
2 checks carry this pillar. They produced 42 results across the pages and documents assessed: 41 passed, 1 were flagged. The score is the weighted share that passed, with a flagged result counting as half.
What is holding this pillar down
warningClaims of being largest, leading, best or first in the page's words, and whether a figure or a source sits in the same passage.1 of 37What good looks like A claim of standing carries the figure or the source that supports it. Why it matters A claim of standing with no figure beside it is a statement about the organisation made by the organisation. Taken out and repeated, it carries the weight of a measured fact while resting on nothing. Where it was found, and what was found there
What passed
1 of the 2 checks in this pillar passed on each item assessed
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Whether the estate can be reached and read at all: access rules, links, redirects, sitemap, transport.
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Fails · 4 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| DS03 | fail | 14 of 14 AI services do not receive the site's pages: 14 sent to another site, while an ordinary visitor is let in, so none of the content is open to them however well the pages are built. The door decides call by call: this check's own requests saw 1 of 22 not served and the front-door capture 14 of 14, and the verdict stands on the worse of the two. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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 AI systems are being turned away before they reach the site, and because the barrier sits outside the organisation's own systems, nobody inside can see it happening. Those systems carry on answering questions about the organisation, from other people's material rather than its own, so the conversation about it goes on without it and nobody has decided that. What we found on this page 14 of 14 AI services do not receive the site's pages: 14 sent to another site, while an ordinary visitor is let in, so none of the content is open to them however well the pages are built. The door decides call by call: this check's own requests saw 1 of 22 not served and the front-door capture 14 of 14, and the verdict stands on the worse of the two. The evidence, taken from the page as served Each crawler's own request to the entry page, and the status it received
Hostwww.newcastle.gov.uk · resolves to 194.61.173.205
Address trailwww.newcastle.gov.uk
Checked2026-09-17 16:33 UTC · request sent from 54.171.52.206 (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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MX12 | fail | 2 pair(s) of pages carry near-identical text: at least 90% of their own running text is the same | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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 2 pair(s) of pages carry near-identical text: at least 90% of their own running text is the same The evidence, taken from the page as served Each page pair whose own running text is near-identical (at least 90% the same passages)
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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| IN18 | fail | 6 legal or policy pages are published but no page we read links to them, so a reader following the site's links never reaches them; they are listed in the view | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the site's own pages link to its legal and policy pages, such as the privacy policy and the terms, or whether those pages are published with no link leading to them. What good looks like A link somewhere on the site leads to each legal and policy page, so anyone reading the site can reach them. Why it matters Your privacy policy and terms may never be read, even though they are published. A page no other page links to is never found by readers that follow links, so answers about your policies are built without the words you actually published. What we found on this page 6 legal or policy pages are published but no page we read links to them, so a reader following the site's links never reaches them; they are listed in the view The evidence, taken from the page as served The legal and policy pages no page links to
Each is published in the site's sitemap, but no page we read links to it. 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 link somewhere on the site leads to each legal and policy page, so anyone reading the site can reach them. 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 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT44 | fail | 25 of the 34 pages assessed share a short summary with another page, across 1 wording. Pages carrying the same summary are offered to a reader as the same page, so it has no way to tell which one answers the question in front of it. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The short summary offered alongside each page's title, and whether more than one page offers the same one. What good looks like Each page describes itself in its own words. Why it matters Where several pages carry the same summary, they are offered to a reader as though they were the same page. It has no way to tell which one answers the question in front of it, so it takes one, and the organisation has no say in which. The pages themselves may be quite different, but nothing in what they offer says so. What we found on this page 25 of the 34 pages assessed share a short summary with another page, across 1 wording. Pages carrying the same summary are offered to a reader as the same page, so it has no way to tell which one answers the question in front of it. The evidence, taken from the page as served The pages that share a summary, grouped by the summary they share
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 describes itself in its own words. 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 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Warnings · 4 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT45 | warning | 2 of the 35 pages assessed share a main heading with another page, across 1 wording. The main heading is a page's own statement of what it is about, so two pages making the same claim read as one page published twice and one of them is passed over. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The main heading on each page, and whether more than one page claims the same subject. What good looks like Each page states its own subject. Why it matters The main heading is the page's own statement of what it is about, and it is the first thing a reader uses to decide whether the page is worth reading further. Two pages making the same claim read as one page published twice. One of them is passed over, and the organisation does not choose which, so the page it would have wanted quoted may be the one dropped. What we found on this page 2 of the 35 pages assessed share a main heading with another page, across 1 wording. The main heading is a page's own statement of what it is about, so two pages making the same claim read as one page published twice and one of them is passed over. The evidence, taken from the page as served The pages that share a main heading, grouped by the heading they share
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| DS20 | warning | the main navigation differs from one page to the next: the pages assessed carry 5 different sets of navigation links between them. Which pages a reader can reach then depends on where they started. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The links in the site's main navigation, compared between one section of the site and another. What good looks like The main navigation holds the same links across the site. Why it matters Where the navigation changes, the route to a page depends on where the reader started, and pages reachable from one part of the site cannot be reached from another. What we found on this page the main navigation differs from one page to the next: the pages assessed carry 5 different sets of navigation links between them. Which pages a reader can reach then depends on where they started. The evidence, taken from the page as served The navigation each page carries
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| IN12 | warning | One claim appears across the pages assessed in more than one wording, with most of the words shared and the rest changed. Several versions of one claim each carry part of its standing, and a correction made to one leaves the rest in place. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Claims repeated across pages in wordings that nearly match but differ in their words. What good looks like A claim repeated across pages is repeated in the same words. Why it matters Several wordings of one claim each carry part of its standing, and a correction made to one leaves the rest in place. What we found on this page One claim appears across the pages assessed in more than one wording, with most of the words shared and the rest changed. Several versions of one claim each carry part of its standing, and a correction made to one leaves the rest in place. The evidence, taken from the page as served The wordings found, and the pages carrying each
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT07 | warning | 2 page title(s) are used on more than one page: โContact us | Newcastle City Councilโ, โCost of living support | Newcastle City Councilโ; 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 Several different pages carry exactly the same name, so a system choosing which to show or quote cannot tell them apart. The wrong one is picked as easily as the right one. What we found on this page 2 page title(s) are used on more than one page: โContact us | Newcastle City Councilโ, โCost of living support | Newcastle City Councilโ; 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
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Passing checks are omitted here; the full record is in the exports.
▸Pages considered 37 pages · click to view
The highest-priority pages, chosen from the site's own signals of importance.
▸https://www.newcastle.gov.uk/ 32.7% Very likely 14 out of 84
The page https://www.newcastle.gov.uk/
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Fails · 3 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 AI systems are being turned away before they reach the site, and because the barrier sits outside the organisation's own systems, nobody inside can see it happening. Those systems carry on answering questions about the organisation, from other people's material rather than its own, so the conversation about it goes on without it and nobody has decided that. 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.newcastle.gov.uk · resolves to 194.61.173.205
Address trailwww.newcastle.gov.uk
Checked2026-09-17 16:33 UTC · request sent from 54.171.52.206 (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 | fail | this page carries prices or figures and dates, and states none of it in a form a machine can take as given, so those facts have to be worked out from the wording around them | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page states what it is, and the exact facts it carries, in a form a machine can take as given rather than work out from the wording. What good looks like The page states what it is in machine-readable form, and where it carries exact facts it states those too. A page of exact facts stating none of them is a fail; a narrative page without a block is a warning. Why it matters Where a page carries exact facts, an address, opening hours, a price, a date, leaving them only in prose means they are worked out rather than read, and that is where a wrong branch or an old price comes from. What we found on this page this page carries prices or figures and dates, and states none of it in a form a machine can take as given, so those facts have to be worked out from the wording around them The evidence, taken from the page as served The head of this page, as served
The page was read for a short block of machine-readable detail saying what it is. The page's own words carry prices or figures and dates, which is why this weighs as it does. <head> <meta charset="utf-8"/> <link rel="canonical" href="https://new.newcastle.gov.uk/"/> <link rel="shortlink" href="https://new.newcastle.gov.uk/"/> <meta name="Generator" content="Drupal 10 (LocalGov Drupal | https://localgovdrupal.org)"/> <meta name="MobileOptimized" content="width"/> <meta name="HandheldFriendly" content="true"/> <meta name="viewport" content="width=device-width, initial-scale=1.0"/> <link rel="icon" href="/sites/default/files/ncc-favicon_0.ico" type="image/vnd.microsoft.icon"/> <script src="/sites/default/files/google_tag/ncc_default/google_tag.script.js?tlij1z" defer="defer"/> <title>Home | Newcastle City Council</title> <link rel="stylesheet" media="all" href="/modules/contrib/localgov_paragraphs/modules/localgov_subsites_paragraphs/css/localgov-subsites-paragraphs.css?tlij1z"/> <link rel="stylesheet" media="all" href="/core/themes/stable9/css/system/components/align.module.css?tlij1z"/> <link rel="stylesheet" media="all" href="/core/themes/stable9/css/system/components/fieldgroup.module.css?tlij1z"/> <link rel="stylesheet" media="all" href="/core/themes/stable9/css/system/components/container-inline.module.css?tlij1z"/> <link rel="stylesheet" media="all"โฆ 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 states what it is in machine-readable form, and where it carries exact facts it states those too. 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: โtheme debug theme hook: 'field' file name suggestions: โช๏ธโ; 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 Identical links on one page lead to different places, so which one gets followed is a coin toss. A reader or system lands on the wrong page while believing it chose correctly. 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: โtheme debug theme hook: 'field' file name suggestions:
โช๏ธโ; 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="ncc_front_page_tile_link" href="https://new.newcastle.gov.uk/adult-social-care"> <!-- THEME DEBUG --> <!-- THEME HOOK: 'field' --> <!-- FILE NAME SUGGESTIONS: โช๏ธ field--paragraph--localgov-image--front-page-tile.html.twig โช๏ธ field--paragraph--localgov-image.html.twig โช๏ธ field--paragraph--front-page-tile.html.โฆ <a class="ncc_front_page_tile_link" href="/births-deaths-marriages-and-ceremonies"> <!-- THEME DEBUG --> <!-- THEME HOOK: 'field' --> <!-- FILE NAME SUGGESTIONS: โช๏ธ field--paragraph--localgov-image--front-page-tile.html.twig โช๏ธ field--paragraph--localgov-image.html.twig โช๏ธ field--paragraph--front-page-tile.html.twig โช๏ธโฆ <a class="ncc_front_page_tile_link" href="https://new.newcastle.gov.uk/children-and-families"> <!-- THEME DEBUG --> <!-- THEME HOOK: 'field' --> <!-- FILE NAME SUGGESTIONS: โช๏ธ field--paragraph--localgov-image--front-page-tile.html.twig โช๏ธ field--paragraph--localgov-image.html.twig โช๏ธ field--paragraph--front-page-tile.hโฆ <a class="ncc_front_page_tile_link" href="https://new.newcastle.gov.uk/council-tax"> <!-- THEME DEBUG --> <!-- THEME HOOK: 'field' --> <!-- FILE NAME SUGGESTIONS: โช๏ธ field--paragraph--localgov-image--front-page-tile.html.twig โช๏ธ field--paragraph--localgov-image.html.twig โช๏ธ field--paragraph--front-page-tile.html.twig โชโฆ <a class="ncc_front_page_tile_link" href="/jobs-careers-and-skills"> <!-- THEME DEBUG --> <!-- THEME HOOK: 'field' --> <!-- FILE NAME SUGGESTIONS: โช๏ธ field--paragraph--localgov-image--front-page-tile.html.twig โช๏ธ field--paragraph--localgov-image.html.twig โช๏ธ field--paragraph--front-page-tile.html.twig โช๏ธ field--localgoโฆ <a class="ncc_front_page_tile_link" href="/parking"> <!-- THEME DEBUG --> <!-- THEME HOOK: 'field' --> <!-- FILE NAME SUGGESTIONS: โช๏ธ field--paragraph--localgov-image--front-page-tile.html.twig โช๏ธ field--paragraph--localgov-image.html.twig โช๏ธ field--paragraph--front-page-tile.html.twig โช๏ธ field--localgov-image.html.twiโฆ <a class="ncc_front_page_tile_link" href="/travel"> <!-- THEME DEBUG --> <!-- THEME HOOK: 'field' --> <!-- FILE NAME SUGGESTIONS: โช๏ธ field--paragraph--localgov-image--front-page-tile.html.twig โช๏ธ field--paragraph--localgov-image.html.twig โช๏ธ field--paragraph--front-page-tile.html.twig โช๏ธ field--localgov-image.html.twigโฆ <a class="ncc_front_page_tile_link" href="/benefits-and-money-advice"> <!-- THEME DEBUG --> <!-- THEME HOOK: 'field' --> <!-- FILE NAME SUGGESTIONS: โช๏ธ field--paragraph--localgov-image--front-page-tile.html.twig โช๏ธ field--paragraph--localgov-image.html.twig โช๏ธ field--paragraph--front-page-tile.html.twig โช๏ธ field--localโฆ <a class="ncc_front_page_tile_link" href="/budget-policies-performance-and-data"> <!-- THEME DEBUG --> <!-- THEME HOOK: 'field' --> <!-- FILE NAME SUGGESTIONS: โช๏ธ field--paragraph--localgov-image--front-page-tile.html.twig โช๏ธ field--paragraph--localgov-image.html.twig โช๏ธ field--paragraph--front-page-tile.html.twig โช๏ธ fโฆ <a class="ncc_front_page_tile_link" href="/communities"> <!-- THEME DEBUG --> <!-- THEME HOOK: 'field' --> <!-- FILE NAME SUGGESTIONS: โช๏ธ field--paragraph--localgov-image--front-page-tile.html.twig โช๏ธ field--paragraph--localgov-image.html.twig โช๏ธ field--paragraph--front-page-tile.html.twig โช๏ธ field--localgov-image.htmlโฆ …and 2 more like it. 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Warnings · 11 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 The page provides no summary of itself, so the short description shown beside its name is written by whoever lists it. The organisation gives up its own say in how the page is introduced. 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> <meta charset="utf-8"/> <link rel="canonical" href="https://new.newcastle.gov.uk/"/> <link rel="shortlink" href="https://new.newcastle.gov.uk/"/> <meta name="Generator" content="Drupal 10 (LocalGov Drupal | https://localgovdrupal.org)"/> <meta name="MobileOptimized" content="width"/> <meta name="HandheldFriendly" content="true"/> <meta name="viewport" content="width=device-width, initial-scale=1.0"/> <link rel="icon" href="/sites/default/files/ncc-favicon_0.ico" type="image/vnd.microsoft.icon"/> <script src="/sites/default/files/google_tag/ncc_default/google_tag.script.js?tlij1z" defer="defer"/> <title>Home | Newcastle City Council</title> <link rel="stylesheet" media="all" href="/modules/contrib/localgov_paragraphs/modules/localgov_subsites_paragraphs/css/localgov-subsites-paragraphs.css?tlij1z"/> <link rel="stylesheet" media="all" href="/core/themes/stable9/css/system/components/align.module.css?tlij1z"/> <link rel="stylesheet" media="all" href="/core/themes/stable9/css/system/components/fieldgroup.module.css?tlij1z"/> <link rel="stylesheet" media="all" href="/core/themes/stable9/css/system/components/container-inline.module.css?tlij1z"/> <link rel="stylesheet" media="all"โฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT11 | warning | 2 H1s (informational; not an error per Google) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check More than one main heading on the page, recorded for information rather than marked as a fault. What good looks like The page carries one main heading rather than several. Why it matters Two main headings make a page state its subject twice, which can blur which one defines it. On its own this rarely changes what gets quoted, so it is noted for the record rather than marked as a fault. What we found on this page 2 H1s (informational; not an error per Google) The evidence, taken from the page as served The multiple H1 headings, as served
<h1> <!-- THEME DEBUG --> <!-- THEME HOOK: 'field' --> <!-- FILE NAME SUGGESTIONS: โช๏ธ field--node--title--localgov-subsites-overview.html.twig โ field--node--title.html.twig โช๏ธ field--node--localgov-subsites-overview.html.twig โช๏ธ field--title.html.twig โช๏ธ field--string.html.twig โช๏ธ field.html.twig --> <!-- BEGIN OUTPUTโฆ <h1> <!-- THEME DEBUG --> <!-- THEME HOOK: 'field' --> <!-- FILE NAME SUGGESTIONS: โช๏ธ field--paragraph--localgov-title--localgov-banner-primary.html.twig โช๏ธ field--paragraph--localgov-title.html.twig โช๏ธ field--paragraph--localgov-banner-primary.html.twig โช๏ธ field--localgov-title.html.twig โช๏ธ field--string.html.twig โ fโฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT40 | warning | the page offers no short summary for the services that show a preview of it, so each one composes its own from whatever it finds first on the page | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The short title, description and image the page offers to services that show a preview of it, and whether they match the page. What good looks like The page offers a summary for preview, and the summary is true to the page. Why it matters This summary travels further than the page does. It is what appears when the address is shared, and several services read it in preference to the page itself because it is short and already written for the purpose. Where it is absent, those services compose their own from whatever they find first, which is often navigation. Where it is present but out of step, the organisation is described to a wide audience by a sentence it wrote once and forgot. What we found on this page the page offers no short summary for the services that show a preview of it, so each one composes its own from whatever it finds first on the page The evidence, taken from the page as served The summary this page offers for preview
Read from the page as served.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT43 | warning | 3 faults in this page's construction, none of which changes the structure anything reading it sees | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page's underlying construction holds together, or contains faults that change how it is read. What good looks like The page is built soundly enough that anything reading it sees the structure its author intended. Why it matters Anything reading the page has to take it apart before it can judge anything on it. Faults in construction can move where a section appears to end, place a heading inside a paragraph, or lose part of the page altogether. When that happens, what is read is not quite the page that was published, and neither is the answer built from it. The damage is invisible on screen, because a browser repairs quietly what a plain reader does not. What we found on this page 3 faults in this page's construction, none of which changes the structure anything reading it sees The evidence, taken from the page as served Faults in the page's construction
Found while taking the page apart exactly as a reader would.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT04 | warning | the page shows the year 2026 in its text, but nothing on the page states it as the date of the content | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The page carries a date, ideally written into the markup rather than sitting only in the text. What good looks like The page carries a date, ideally written into the markup rather than sitting only in the text. Why it matters An undated page gives nothing to weigh its age against, so old and new material are treated alike. What we found on this page the page shows the year 2026 in its text, but nothing on the page states it as the date of the content The evidence, taken from the page as served The head of this page, as served
The head of the page was read for a tag stating the date of the content. The year shown above was found in the page's own text. <head> <meta charset="utf-8"/> <link rel="canonical" href="https://new.newcastle.gov.uk/"/> <link rel="shortlink" href="https://new.newcastle.gov.uk/"/> <meta name="Generator" content="Drupal 10 (LocalGov Drupal | https://localgovdrupal.org)"/> <meta name="MobileOptimized" content="width"/> <meta name="HandheldFriendly" content="true"/> <meta name="viewport" content="width=device-width, initial-scale=1.0"/> <link rel="icon" href="/sites/default/files/ncc-favicon_0.ico" type="image/vnd.microsoft.icon"/> <script src="/sites/default/files/google_tag/ncc_default/google_tag.script.js?tlij1z" defer="defer"/> <title>Home | Newcastle City Council</title> <link rel="stylesheet" media="all" href="/modules/contrib/localgov_paragraphs/modules/localgov_subsites_paragraphs/css/localgov-subsites-paragraphs.css?tlij1z"/> <link rel="stylesheet" media="all" href="/core/themes/stable9/css/system/components/align.module.css?tlij1z"/> <link rel="stylesheet" media="all" href="/core/themes/stable9/css/system/components/fieldgroup.module.css?tlij1z"/> <link rel="stylesheet" media="all" href="/core/themes/stable9/css/system/components/container-inline.module.css?tlij1z"/> <link rel="stylesheet" media="all"โฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT35 | warning | the copyright line at the foot of this page carries no year, so there is nothing on the page as served to date it by | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The copyright line at the foot of the page, and the year it states. What good looks like The copyright line states the current year. Why it matters An old copyright year reads as a site nobody is looking after, and it dates the page for anything that relies on dates. Content can be treated as years older than it really is. What we found on this page the copyright line at the foot of this page carries no year, so there is nothing on the page as served to date it by The evidence, taken from the page as served The copyright line on this page, as served
This is the copyright line as the page serves it. It was read for a year, and carries none. ch and comment on planning applications Footer Accessibility Privacy Terms and conditions ยฉNewcastle City Council {"path":{"baseUrl":"\/","pathPrefix":"","currentPath":"node\/2323","currentPathIsAdmin":false,"isFront":true,"currentLanguage": | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AJ07 | warning | 2 required field(s) have no tie in the page's code between the field and its error message, so which field an error belongs to rests on layout alone | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether required form fields are linked in the markup to the error messages about them. What good looks like Each required field is tied in the markup to the message that describes its error. Why it matters An error message sits on the page with nothing tying it to the field it concerns, so the correction has no anchor. What we found on this page 2 required field(s) have no tie in the page's code between the field and its error message, so which field an error belongs to rests on layout alone The evidence, taken from the page as served The required fields with no error association, as served
<input data-drupal-selector="edit-s" placeholder="Search" type="text" id="edit-s--3" name="s" value="" size="30" maxlength="128" class="form-text required" required="required" aria-required="true"/> <input data-drupal-selector="edit-s" placeholder="Search" type="text" id="edit-s--4" name="s" value="" size="30" maxlength="128" class="form-text required" required="required" aria-required="true"/> | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS13 | warning | 1 of 1 iframes untitled | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Each embedded panel on the page carries a title saying what it contains. What good looks like Each embedded panel carries a title saying what it contains. Why it matters Content brought into the page from elsewhere, a map, a form, a video player, carries no name saying what it is. Anything reading the page sees a hole where that content sits. What we found on this page 1 of 1 iframes untitled The evidence, taken from the page as served The iframes with no title attribute, as served
<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-W7BB9DGL" height="0" width="0" style="display:none;visibility:hidden"/> | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR03 | warning | 23% of the words a person sees are missing from the page as first delivered (2359 characters delivered, 3160 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 looks complete to a person, but its content is built by scripts that many AI systems never run, so they receive it near-empty. The organisation's material is missing from their answers. What we found on this page 23% of the words a person sees are missing from the page as first delivered (2359 characters delivered, 3160 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 2359 characters of text; after JavaScript runs the page carries 3160. 23% of the rendered page's words are absent from the HTML the server sends. What the server sends (raw HTML text, first 280 chars) Home | Newcastle City Council Skip to main content Home Services Menu Main navigation News Pay My portal Listen and translate Search Services menu Adult social care Benefits and money advice Births, deaths, marriages and ceremonies Budget, policies, performance and data Business …
Words present only after JavaScript runs
acceptaccessadvertisinganalyticalanalyticsareasbrowsercampaignscannotchangingcollectingcomputercookiescoredisabledenableessentialexperiencefunctionfunctionalityimproveinformationinsightsintomarketingnecessaryonlyopensotherspreferencesproperlyprovidingrelevancyreportingsecuresomestoresuchsuggestedthesetoolusageuseduseswebsitewhilewindowwithout
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR11 | warning | 23% of the words a person sees are missing from the page as first delivered: the page arrives carrying 75% of the text it ends up showing | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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 23% of the words a person sees are missing from the page as first delivered: the page arrives carrying 75% of the text it ends up showing 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.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
▸https://newcastle.gov.uk/local-government/access-information-and-data/open-data/privacy-notice 10.9% Extremely likely 11 out of 84
The page https://newcastle.gov.uk/local-government/access-information-and-data/open-data/privacy-notice
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Fails · 3 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 AI systems are being turned away before they reach the site, and because the barrier sits outside the organisation's own systems, nobody inside can see it happening. Those systems carry on answering questions about the organisation, from other people's material rather than its own, so the conversation about it goes on without it and nobody has decided that. 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.newcastle.gov.uk · resolves to 194.61.173.205
Address trailwww.newcastle.gov.uk
Checked2026-09-17 16:33 UTC · request sent from 54.171.52.206 (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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| DS18 | fail | the site's own list of its pages offers this page at one address and the page then names a different one as its preferred address, so a reader following the list arrives somewhere the page disowns | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Pages that name more than one preferred address, with the declarations disagreeing. What good looks like A page's preferred-address declarations agree with one another. Why it matters The page gives two different answers about which of its addresses is the official one. A contradiction like that gets ignored, so outside systems decide for themselves which copy of the page to use. What we found on this page the site's own list of its pages offers this page at one address and the page then names a different one as its preferred address, so a reader following the list arrives somewhere the page disowns The evidence, taken from the page as served The address this page is listed at, and the address it prefers
Read from the site's own list of its pages and from the page itself.
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's preferred-address declarations agree with one another. 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT16 | fail | this page carries a telephone number, and states none of it in a form a machine can take as given, so those facts have to be worked out from the wording around them | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page states what it is, and the exact facts it carries, in a form a machine can take as given rather than work out from the wording. What good looks like The page states what it is in machine-readable form, and where it carries exact facts it states those too. A page of exact facts stating none of them is a fail; a narrative page without a block is a warning. Why it matters Where a page carries exact facts, an address, opening hours, a price, a date, leaving them only in prose means they are worked out rather than read, and that is where a wrong branch or an old price comes from. What we found on this page this page carries a telephone number, and states none of it in a form a machine can take as given, so those facts have to be worked out from the wording around them The evidence, taken from the page as served The head of this page, as served
The page was read for a short block of machine-readable detail saying what it is. The page's own words carry a telephone number, which is why this weighs as it does. <head> <meta charset="utf-8"/> <meta name="description" content="This Privacy Notice explains how we use information about you and how we protect your privacy."/> <link rel="canonical" href="https://new.newcastle.gov.uk/budget-policies-performance-data/policies/privacy-policies/privacy-notice"/> <meta name="Generator" content="Drupal 10 (LocalGov Drupal | https://localgovdrupal.org)"/> <meta name="MobileOptimized" content="width"/> <meta name="HandheldFriendly" content="true"/> <meta name="viewport" content="width=device-width, initial-scale=1.0"/> <link rel="icon" href="/sites/default/files/ncc-favicon_0.ico" type="image/vnd.microsoft.icon"/> <script src="/sites/default/files/google_tag/ncc_default/google_tag.script.js?tlij1z" defer="defer"/> <title>Privacy Notice | Newcastle City Council</title> <link rel="stylesheet" media="all" href="/core/themes/stable9/css/system/components/align.module.css?tlij1z"/> <link rel="stylesheet" media="all" href="/core/themes/stable9/css/system/components/fieldgroup.module.css?tlij1z"/> <link rel="stylesheet" media="all" href="/core/themes/stable9/css/system/components/container-inline.module.css?tlij1z"/> <link rel="stylesheet" media="all" href="/โฆ 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 states what it is in machine-readable form, and where it carries exact facts it states those too. 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Warnings · 8 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT40 | warning | the page offers no short summary for the services that show a preview of it, so each one composes its own from whatever it finds first on the page | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The short title, description and image the page offers to services that show a preview of it, and whether they match the page. What good looks like The page offers a summary for preview, and the summary is true to the page. Why it matters This summary travels further than the page does. It is what appears when the address is shared, and several services read it in preference to the page itself because it is short and already written for the purpose. Where it is absent, those services compose their own from whatever they find first, which is often navigation. Where it is present but out of step, the organisation is described to a wide audience by a sentence it wrote once and forgot. What we found on this page the page offers no short summary for the services that show a preview of it, so each one composes its own from whatever it finds first on the page The evidence, taken from the page as served The summary this page offers for preview
Read from the page as served.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT41 | warning | the page shows where it sits in the site but does not state it in a form a machine can take as given | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The trail showing the path from the front page to this one, and whether the machine-readable version of that trail says the same. What good looks like The page shows its place in the site, and says the same thing to a machine. Why it matters A page read on its own gives no sense of what it belongs to. The trail supplies it: one product within a range, one policy within a set. A reader deciding whether a page answers a question uses that to judge whether it has the right one, and how to describe it when it quotes it. Where the shown trail and the machine-readable one disagree, the page is placed in two positions at once and neither can be relied on. What we found on this page the page shows where it sits in the site but does not state it in a form a machine can take as given The evidence, taken from the page as served The path this page gives to itself
Read from the page as served: the trail shown to a reader, and the trail stated in a form a machine can take as given.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT04 | warning | the page carries no date, so there is nothing on it saying how current its content is | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The page carries a date, ideally written into the markup rather than sitting only in the text. What good looks like The page carries a date, ideally written into the markup rather than sitting only in the text. Why it matters An undated page gives nothing to weigh its age against, so old and new material are treated alike. What we found on this page the page carries no date, so there is nothing on it saying how current its content is The evidence, taken from the page as served The head of this page, as served
The head of the page and the page's own text were read for a date. <head> <meta charset="utf-8"/> <meta name="description" content="This Privacy Notice explains how we use information about you and how we protect your privacy."/> <link rel="canonical" href="https://new.newcastle.gov.uk/budget-policies-performance-data/policies/privacy-policies/privacy-notice"/> <meta name="Generator" content="Drupal 10 (LocalGov Drupal | https://localgovdrupal.org)"/> <meta name="MobileOptimized" content="width"/> <meta name="HandheldFriendly" content="true"/> <meta name="viewport" content="width=device-width, initial-scale=1.0"/> <link rel="icon" href="/sites/default/files/ncc-favicon_0.ico" type="image/vnd.microsoft.icon"/> <script src="/sites/default/files/google_tag/ncc_default/google_tag.script.js?tlij1z" defer="defer"/> <title>Privacy Notice | Newcastle City Council</title> <link rel="stylesheet" media="all" href="/core/themes/stable9/css/system/components/align.module.css?tlij1z"/> <link rel="stylesheet" media="all" href="/core/themes/stable9/css/system/components/fieldgroup.module.css?tlij1z"/> <link rel="stylesheet" media="all" href="/core/themes/stable9/css/system/components/container-inline.module.css?tlij1z"/> <link rel="stylesheet" media="all" href="/โฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT35 | warning | the copyright line at the foot of this page carries no year, so there is nothing on the page as served to date it by | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The copyright line at the foot of the page, and the year it states. What good looks like The copyright line states the current year. Why it matters An old copyright year reads as a site nobody is looking after, and it dates the page for anything that relies on dates. Content can be treated as years older than it really is. What we found on this page the copyright line at the foot of this page carries no year, so there is nothing on the page as served to date it by The evidence, taken from the page as served The copyright line on this page, as served
This is the copyright line as the page serves it. It was read for a year, and carries none. ch and comment on planning applications Footer Accessibility Privacy Terms and conditions ยฉNewcastle City Council {"path":{"baseUrl":"\/","pathPrefix":"","currentPath":"node\/2065","currentPathIsAdmin":false,"isFront":false,"currentLanguage" | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AJ07 | warning | 1 required field(s) have no tie in the page's code between the field and its error message, so which field an error belongs to rests on layout alone | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether required form fields are linked in the markup to the error messages about them. What good looks like Each required field is tied in the markup to the message that describes its error. Why it matters An error message sits on the page with nothing tying it to the field it concerns, so the correction has no anchor. What we found on this page 1 required field(s) have no tie in the page's code between the field and its error message, so which field an error belongs to rests on layout alone The evidence, taken from the page as served The required fields with no error association, as served
<input data-drupal-selector="edit-s" placeholder="Search" type="text" id="edit-s--2" name="s" value="" size="30" maxlength="128" class="form-text required" required="required" aria-required="true"/> | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MX10 | warning | 2 links to a file on this page do not say what the file is and how big it is before it is opened. A reader deciding whether to open a file has nothing to judge it by, and on a slow or metered connection an unnamed file is a risk rather than an offer. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Links that open a file, and whether the wording states the format and the size. What good looks like A link to a file states its format and its size. Why it matters A reader deciding whether to open a file has nothing to judge it by, and on a slow or metered connection an unnamed file is a risk rather than an offer. What we found on this page 2 links to a file on this page do not say what the file is and how big it is before it is opened. A reader deciding whether to open a file has nothing to judge it by, and on a slow or metered connection an unnamed file is a risk rather than an offer. The evidence, taken from the page as served The links to a file, and what each one states
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS13 | warning | 1 of 1 iframes untitled | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Each embedded panel on the page carries a title saying what it contains. What good looks like Each embedded panel carries a title saying what it contains. Why it matters Content brought into the page from elsewhere, a map, a form, a video player, carries no name saying what it is. Anything reading the page sees a hole where that content sits. What we found on this page 1 of 1 iframes untitled The evidence, taken from the page as served The iframes with no title attribute, as served
<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-W7BB9DGL" height="0" width="0" style="display:none;visibility:hidden"/> | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
▸https://www.newcastle.gov.uk/services/communities-and-neighbourhoods/asylum-and-immigration 32.1% Very likely 12 out of 84
The page https://www.newcastle.gov.uk/services/communities-and-neighbourhoods/asylum-and-immigration
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Fails · 6 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 AI systems are being turned away before they reach the site, and because the barrier sits outside the organisation's own systems, nobody inside can see it happening. Those systems carry on answering questions about the organisation, from other people's material rather than its own, so the conversation about it goes on without it and nobody has decided that. 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.newcastle.gov.uk · resolves to 194.61.173.205
Address trailwww.newcastle.gov.uk
Checked2026-09-17 16:33 UTC · request sent from 54.171.52.206 (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 heading 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)
H2 Main navigation H2 Title H4 Have your say level jumped H1 Asylum and Immigration H2 Asylum and Immigration H2 Asylum and Migration H3 The roles of national and local government H3 Support for Asylum Seekers H3 Support after a decision on your asylum claim H3 Support for Refugees H2 Related Pages H3 Most popular pages H3 We're on social media
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 | fail | this page carries an address and a telephone number, and states none of it in a form a machine can take as given, so those facts have to be worked out from the wording around them | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page states what it is, and the exact facts it carries, in a form a machine can take as given rather than work out from the wording. What good looks like The page states what it is in machine-readable form, and where it carries exact facts it states those too. A page of exact facts stating none of them is a fail; a narrative page without a block is a warning. Why it matters Where a page carries exact facts, an address, opening hours, a price, a date, leaving them only in prose means they are worked out rather than read, and that is where a wrong branch or an old price comes from. What we found on this page this page carries an address and a telephone number, and states none of it in a form a machine can take as given, so those facts have to be worked out from the wording around them The evidence, taken from the page as served The head of this page, as served
The page was read for a short block of machine-readable detail saying what it is. The page's own words carry an address and a telephone number, which is why this weighs as it does. <head> <meta charset="utf-8"/> <style>/* @see https://github.com/aFarkas/lazysizes#broken-image-symbol */.js img.b-lazy:not([src]) { visibility: hidden; }/* @see https://github.com/aFarkas/lazysizes#automatically-setting-the-sizes-attribute */.js img.lazyloaded[data-sizes=auto] { display: block; width: 100%; }</style> <meta name="description" content="The website of Newcastle City Council"/> <meta name="geo.placename" content="Newcastle upon Tyne"/> <link rel="canonical" href="https://www.newcastle.gov.uk/services/communities-and-neighbourhoods/asylum-and-immigration"/> <link rel="icon" href="favicon.ico"/> <link rel="icon" sizes="16x16" href="/favicon-16x16.png"/> <link rel="icon" sizes="32x32" href="/favicon-32x32.png"/> <link rel="icon" sizes="96x96" href="/favicon-96x96.png"/> <link rel="icon" sizes="192x192" href="/android-chrome-192x192.png"/> <link rel="apple-touch-icon" href="/apple-touch-icon-60x60.png"/> <link rel="apple-touch-icon" sizes="72x72" href="/android-chrome-72x72.png"/> <link rel="apple-touch-icon" sizes="76x76" href="/apple-touch-icon-76x76.png"/> <link rel="apple-touch-icon" sizes="114x114" href="/apple-touch-icon-114x114.png"/> <link rel="apple-touch-icon" sโฆ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 states what it is in machine-readable form, and where it carries exact facts it states those too. 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT43 | fail | 1 fault in this page's construction change the structure anything reading it sees, so what is read is not quite the page that was published | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page's underlying construction holds together, or contains faults that change how it is read. What good looks like The page is built soundly enough that anything reading it sees the structure its author intended. Why it matters Anything reading the page has to take it apart before it can judge anything on it. Faults in construction can move where a section appears to end, place a heading inside a paragraph, or lose part of the page altogether. When that happens, what is read is not quite the page that was published, and neither is the answer built from it. The damage is invisible on screen, because a browser repairs quietly what a plain reader does not. What we found on this page 1 fault in this page's construction change the structure anything reading it sees, so what is read is not quite the page that was published The evidence, taken from the page as served Faults in the page's construction that change how it reads
Found while taking the page apart exactly as a reader would.
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 is built soundly enough that anything reading it sees the structure its author intended. 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: โcity of sanctuaryโ; 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 Identical links on one page lead to different places, so which one gets followed is a coin toss. A reader or system lands on the wrong page while believing it chose correctly. 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: โcity of sanctuaryโ; 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://newcastle.cityofsanctuary.org/">City of Sanctuary</a> <a href="/services/communities-and-neighbourhoods/asylum-and-immigration/city-sanctuary" hreflang="en">City of Sanctuary</a> <a href="/services/communities-and-neighbourhoods/asylum-and-immigration/city-sanctuary" class="nav-link" data-drupal-link-system-path="node/8014">City of Sanctuary</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 The page's headings begin at its top level, rather than starting part way down. What good looks like The page's headings begin with its top-level heading. Levels skipped further down are weighed under heading hierarchy, and a page with no top-level heading at all under the missing main heading, so each fault is marked once. Why it matters The page's structure starts part way down, below a top level that never opens it. Sections then sit under nothing, and anything filing content by structure starts in the wrong place. 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 (the starting level is marked)
H2 Main navigation level jumped H2 Title H4 Have your say H1 Asylum and Immigration H2 Asylum and Immigration H2 Asylum and Migration H3 The roles of national and local government H3 Support for Asylum Seekers H3 Support after a decision on your asylum claim H3 Support for Refugees H2 Related Pages H3 Most popular pages H3 We're on social media
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 begin with its top-level heading. 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Warnings · 6 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT32 | warning | the page's meta description, the short summary it offers about itself, runs to 37 characters, too short to say what the page is about; a usable summary runs from 50 to 170 characters | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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 the page's meta description, the short summary it offers about itself, runs to 37 characters, too short to say what the page is about; a usable summary runs from 50 to 170 characters The evidence, taken from the page as served The page's description, as served
<meta name="description" content="The website of Newcastle City Council"/> | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT40 | warning | the page offers no short summary for the services that show a preview of it, so each one composes its own from whatever it finds first on the page | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The short title, description and image the page offers to services that show a preview of it, and whether they match the page. What good looks like The page offers a summary for preview, and the summary is true to the page. Why it matters This summary travels further than the page does. It is what appears when the address is shared, and several services read it in preference to the page itself because it is short and already written for the purpose. Where it is absent, those services compose their own from whatever they find first, which is often navigation. Where it is present but out of step, the organisation is described to a wide audience by a sentence it wrote once and forgot. What we found on this page the page offers no short summary for the services that show a preview of it, so each one composes its own from whatever it finds first on the page The evidence, taken from the page as served The summary this page offers for preview
Read from the page as served.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT41 | warning | the page does not show where it sits in the site, so anything reading it on its own has nothing to say what it belongs to | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The trail showing the path from the front page to this one, and whether the machine-readable version of that trail says the same. What good looks like The page shows its place in the site, and says the same thing to a machine. Why it matters A page read on its own gives no sense of what it belongs to. The trail supplies it: one product within a range, one policy within a set. A reader deciding whether a page answers a question uses that to judge whether it has the right one, and how to describe it when it quotes it. Where the shown trail and the machine-readable one disagree, the page is placed in two positions at once and neither can be relied on. What we found on this page the page does not show where it sits in the site, so anything reading it on its own has nothing to say what it belongs to The evidence, taken from the page as served The path this page gives to itself
Read from the page as served: the trail shown to a reader, and the trail stated in a form a machine can take as given.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT04 | warning | the page carries no date, so there is nothing on it saying how current its content is | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The page carries a date, ideally written into the markup rather than sitting only in the text. What good looks like The page carries a date, ideally written into the markup rather than sitting only in the text. Why it matters An undated page gives nothing to weigh its age against, so old and new material are treated alike. What we found on this page the page carries no date, so there is nothing on it saying how current its content is The evidence, taken from the page as served The head of this page, as served
The head of the page and the page's own text were read for a date. <head> <meta charset="utf-8"/> <style>/* @see https://github.com/aFarkas/lazysizes#broken-image-symbol */.js img.b-lazy:not([src]) { visibility: hidden; }/* @see https://github.com/aFarkas/lazysizes#automatically-setting-the-sizes-attribute */.js img.lazyloaded[data-sizes=auto] { display: block; width: 100%; }</style> <meta name="description" content="The website of Newcastle City Council"/> <meta name="geo.placename" content="Newcastle upon Tyne"/> <link rel="canonical" href="https://www.newcastle.gov.uk/services/communities-and-neighbourhoods/asylum-and-immigration"/> <link rel="icon" href="favicon.ico"/> <link rel="icon" sizes="16x16" href="/favicon-16x16.png"/> <link rel="icon" sizes="32x32" href="/favicon-32x32.png"/> <link rel="icon" sizes="96x96" href="/favicon-96x96.png"/> <link rel="icon" sizes="192x192" href="/android-chrome-192x192.png"/> <link rel="apple-touch-icon" href="/apple-touch-icon-60x60.png"/> <link rel="apple-touch-icon" sizes="72x72" href="/android-chrome-72x72.png"/> <link rel="apple-touch-icon" sizes="76x76" href="/apple-touch-icon-76x76.png"/> <link rel="apple-touch-icon" sizes="114x114" href="/apple-touch-icon-114x114.png"/> <link rel="apple-touch-icon" sโฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT35 | warning | the copyright line at the foot of this page carries no year, so there is nothing on the page as served to date it by | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The copyright line at the foot of the page, and the year it states. What good looks like The copyright line states the current year. Why it matters An old copyright year reads as a site nobody is looking after, and it dates the page for anything that relies on dates. Content can be treated as years older than it really is. What we found on this page the copyright line at the foot of this page carries no year, so there is nothing on the page as served to date it by The evidence, taken from the page as served The copyright line on this page, as served
This is the copyright line as the page serves it. It was read for a year, and carries none. stagram Find out how we use social media Press Office and News ReciteMe and Accessibility ยฉNewcastle City Council Privacy Notice Terms and conditions Contact Us Covid-19 support Listen and translate {"path":{"baseUrl":"\/","pathPrefix":"","c | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
▸https://www.newcastle.gov.uk/netzero 32.7% Very likely 15 out of 84
The page https://www.newcastle.gov.uk/netzero
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Fails · 2 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 AI systems are being turned away before they reach the site, and because the barrier sits outside the organisation's own systems, nobody inside can see it happening. Those systems carry on answering questions about the organisation, from other people's material rather than its own, so the conversation about it goes on without it and nobody has decided that. 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.newcastle.gov.uk · resolves to 194.61.173.205
Address trailwww.newcastle.gov.uk
Checked2026-09-17 16:33 UTC · request sent from 54.171.52.206 (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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| DS14 | fail | 2 redirect hops on the way to the page that answers | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check How many redirect hops a page takes before arriving, and whether it lands on an untidy address. What good looks like A page arrives in few redirect hops and lands on a tidy address. Why it matters Addresses here pass through several forwarding steps before a page appears, and some readers give up part way. The address that ends up quoted is one of the intermediate ones, not the proper one. What we found on this page 2 redirect hops on the way to the page that answers The evidence, taken from the page as served The steps this address took before it arrived
Followed from the address asked for to the page that finally answered.
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 arrives in few redirect hops and lands on a tidy address. 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Warnings · 13 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 The page provides no summary of itself, so the short description shown beside its name is written by whoever lists it. The organisation gives up its own say in how the page is introduced. 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> <meta charset="utf-8"/> <link rel="canonical" href="https://new.newcastle.gov.uk/climate-change-and-net-zero"/> <meta name="Generator" content="Drupal 10 (LocalGov Drupal | https://localgovdrupal.org)"/> <meta name="MobileOptimized" content="width"/> <meta name="HandheldFriendly" content="true"/> <meta name="viewport" content="width=device-width, initial-scale=1.0"/> <link rel="icon" href="/sites/default/files/ncc-favicon_0.ico" type="image/vnd.microsoft.icon"/> <script src="/sites/default/files/google_tag/ncc_default/google_tag.script.js?tlij1z" defer="defer"/> <title>Climate change and net zero | Newcastle City Council</title> <link rel="stylesheet" media="all" href="/modules/contrib/localgov_paragraphs/modules/localgov_subsites_paragraphs/css/localgov-subsites-paragraphs.css?tlij1z"/> <link rel="stylesheet" media="all" href="/modules/contrib/localgov_subsites/css/one-column-flexible.css?tlij1z"/> <link rel="stylesheet" media="all" href="/core/themes/stable9/css/system/components/align.module.css?tlij1z"/> <link rel="stylesheet" media="all" href="/core/themes/stable9/css/system/components/fieldgroup.module.css?tlij1z"/> <link rel="stylesheet" media="all" href="/core/themesโฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT16 | warning | the page states nothing about itself in a form a machine can take as given, so who you are and what the page is about are worked out from its wording | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page states what it is, and the exact facts it carries, in a form a machine can take as given rather than work out from the wording. What good looks like The page states what it is in machine-readable form, and where it carries exact facts it states those too. A page of exact facts stating none of them is a fail; a narrative page without a block is a warning. Why it matters Where a page carries exact facts, an address, opening hours, a price, a date, leaving them only in prose means they are worked out rather than read, and that is where a wrong branch or an old price comes from. What we found on this page the page states nothing about itself in a form a machine can take as given, so who you are and what the page is about are worked out from its wording The evidence, taken from the page as served The head of this page, as served
The page was read for a short block of machine-readable detail saying what it is. The page's own words carry no exact facts of that kind. <head> <meta charset="utf-8"/> <link rel="canonical" href="https://new.newcastle.gov.uk/climate-change-and-net-zero"/> <meta name="Generator" content="Drupal 10 (LocalGov Drupal | https://localgovdrupal.org)"/> <meta name="MobileOptimized" content="width"/> <meta name="HandheldFriendly" content="true"/> <meta name="viewport" content="width=device-width, initial-scale=1.0"/> <link rel="icon" href="/sites/default/files/ncc-favicon_0.ico" type="image/vnd.microsoft.icon"/> <script src="/sites/default/files/google_tag/ncc_default/google_tag.script.js?tlij1z" defer="defer"/> <title>Climate change and net zero | Newcastle City Council</title> <link rel="stylesheet" media="all" href="/modules/contrib/localgov_paragraphs/modules/localgov_subsites_paragraphs/css/localgov-subsites-paragraphs.css?tlij1z"/> <link rel="stylesheet" media="all" href="/modules/contrib/localgov_subsites/css/one-column-flexible.css?tlij1z"/> <link rel="stylesheet" media="all" href="/core/themes/stable9/css/system/components/align.module.css?tlij1z"/> <link rel="stylesheet" media="all" href="/core/themes/stable9/css/system/components/fieldgroup.module.css?tlij1z"/> <link rel="stylesheet" media="all" href="/core/themesโฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT40 | warning | the page offers no short summary for the services that show a preview of it, so each one composes its own from whatever it finds first on the page | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The short title, description and image the page offers to services that show a preview of it, and whether they match the page. What good looks like The page offers a summary for preview, and the summary is true to the page. Why it matters This summary travels further than the page does. It is what appears when the address is shared, and several services read it in preference to the page itself because it is short and already written for the purpose. Where it is absent, those services compose their own from whatever they find first, which is often navigation. Where it is present but out of step, the organisation is described to a wide audience by a sentence it wrote once and forgot. What we found on this page the page offers no short summary for the services that show a preview of it, so each one composes its own from whatever it finds first on the page The evidence, taken from the page as served The summary this page offers for preview
Read from the page as served.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT41 | warning | the page shows where it sits in the site but does not state it in a form a machine can take as given | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The trail showing the path from the front page to this one, and whether the machine-readable version of that trail says the same. What good looks like The page shows its place in the site, and says the same thing to a machine. Why it matters A page read on its own gives no sense of what it belongs to. The trail supplies it: one product within a range, one policy within a set. A reader deciding whether a page answers a question uses that to judge whether it has the right one, and how to describe it when it quotes it. Where the shown trail and the machine-readable one disagree, the page is placed in two positions at once and neither can be relied on. What we found on this page the page shows where it sits in the site but does not state it in a form a machine can take as given The evidence, taken from the page as served The path this page gives to itself
Read from the page as served: the trail shown to a reader, and the trail stated in a form a machine can take as given.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT43 | warning | 1 fault in this page's construction, none of which changes the structure anything reading it sees | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page's underlying construction holds together, or contains faults that change how it is read. What good looks like The page is built soundly enough that anything reading it sees the structure its author intended. Why it matters Anything reading the page has to take it apart before it can judge anything on it. Faults in construction can move where a section appears to end, place a heading inside a paragraph, or lose part of the page altogether. When that happens, what is read is not quite the page that was published, and neither is the answer built from it. The damage is invisible on screen, because a browser repairs quietly what a plain reader does not. What we found on this page 1 fault in this page's construction, none of which changes the structure anything reading it sees The evidence, taken from the page as served Faults in the page's construction
Found while taking the page apart exactly as a reader would.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT04 | warning | the page shows the year 2026 in its text, but nothing on the page states it as the date of the content | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The page carries a date, ideally written into the markup rather than sitting only in the text. What good looks like The page carries a date, ideally written into the markup rather than sitting only in the text. Why it matters An undated page gives nothing to weigh its age against, so old and new material are treated alike. What we found on this page the page shows the year 2026 in its text, but nothing on the page states it as the date of the content The evidence, taken from the page as served The head of this page, as served
The head of the page was read for a tag stating the date of the content. The year shown above was found in the page's own text. <head> <meta charset="utf-8"/> <link rel="canonical" href="https://new.newcastle.gov.uk/climate-change-and-net-zero"/> <meta name="Generator" content="Drupal 10 (LocalGov Drupal | https://localgovdrupal.org)"/> <meta name="MobileOptimized" content="width"/> <meta name="HandheldFriendly" content="true"/> <meta name="viewport" content="width=device-width, initial-scale=1.0"/> <link rel="icon" href="/sites/default/files/ncc-favicon_0.ico" type="image/vnd.microsoft.icon"/> <script src="/sites/default/files/google_tag/ncc_default/google_tag.script.js?tlij1z" defer="defer"/> <title>Climate change and net zero | Newcastle City Council</title> <link rel="stylesheet" media="all" href="/modules/contrib/localgov_paragraphs/modules/localgov_subsites_paragraphs/css/localgov-subsites-paragraphs.css?tlij1z"/> <link rel="stylesheet" media="all" href="/modules/contrib/localgov_subsites/css/one-column-flexible.css?tlij1z"/> <link rel="stylesheet" media="all" href="/core/themes/stable9/css/system/components/align.module.css?tlij1z"/> <link rel="stylesheet" media="all" href="/core/themes/stable9/css/system/components/fieldgroup.module.css?tlij1z"/> <link rel="stylesheet" media="all" href="/core/themesโฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT35 | warning | the copyright line at the foot of this page carries no year, so there is nothing on the page as served to date it by | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The copyright line at the foot of the page, and the year it states. What good looks like The copyright line states the current year. Why it matters An old copyright year reads as a site nobody is looking after, and it dates the page for anything that relies on dates. Content can be treated as years older than it really is. What we found on this page the copyright line at the foot of this page carries no year, so there is nothing on the page as served to date it by The evidence, taken from the page as served The copyright line on this page, as served
This is the copyright line as the page serves it. It was read for a year, and carries none. ch and comment on planning applications Footer Accessibility Privacy Terms and conditions ยฉNewcastle City Council {"path":{"baseUrl":"\/","pathPrefix":"","currentPath":"node\/1374","currentPathIsAdmin":false,"isFront":false,"currentLanguage" | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AJ07 | warning | 1 required field(s) have no tie in the page's code between the field and its error message, so which field an error belongs to rests on layout alone | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether required form fields are linked in the markup to the error messages about them. What good looks like Each required field is tied in the markup to the message that describes its error. Why it matters An error message sits on the page with nothing tying it to the field it concerns, so the correction has no anchor. What we found on this page 1 required field(s) have no tie in the page's code between the field and its error message, so which field an error belongs to rests on layout alone The evidence, taken from the page as served The required fields with no error association, as served
<input data-drupal-selector="edit-s" placeholder="Search" type="text" id="edit-s--2" name="s" value="" size="30" maxlength="128" class="form-text required" required="required" aria-required="true"/> | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS09 | warning | link wording that does not say where it leads: โhereโ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Link wording that names no destination, phrases such as click here, read more and details, and one such wording repeated across many links. What good looks like Link wording names its destination, rather than saying click here or read more. Why it matters The destination is stated nowhere on the link itself, so the choice rests entirely on the text around it. Where one wording such as click here covers many links, they read as one link repeated and nothing in their names tells them apart. What we found on this page link wording that does not say where it leads: โhereโ The evidence, taken from the page as served The links whose text names no destination, as served
<a href="/news/2026/young-climate-leaders-unite-newcastle-sustainability-event" data-entity-type="node" data-entity-uuid="7d467224-17c5-4f4c-897c-db01ca801126" data-entity-substitution="canonical" title="Young climate leaders unite at Newcastle sustainability event.">here</a> | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS13 | warning | 1 of 1 iframes untitled | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Each embedded panel on the page carries a title saying what it contains. What good looks like Each embedded panel carries a title saying what it contains. Why it matters Content brought into the page from elsewhere, a map, a form, a video player, carries no name saying what it is. Anything reading the page sees a hole where that content sits. What we found on this page 1 of 1 iframes untitled The evidence, taken from the page as served The iframes with no title attribute, as served
<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-W7BB9DGL" height="0" width="0" style="display:none;visibility:hidden"/> | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR03 | warning | 14% of the words a person sees are missing from the page as first delivered (4385 characters delivered, 5186 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 looks complete to a person, but its content is built by scripts that many AI systems never run, so they receive it near-empty. The organisation's material is missing from their answers. What we found on this page 14% of the words a person sees are missing from the page as first delivered (4385 characters delivered, 5186 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 4385 characters of text; after JavaScript runs the page carries 5186. 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) Climate change and net zero | Newcastle City Council Skip to main content Climate change and net zero Services Menu Main navigation News Pay My portal Listen and translate Search Services menu Adult social care Benefits and money advice Births, deaths, marriages and ceremonies Bu…
Words present only after JavaScript runs
acceptaccessadvertisinganalyticalanalyticsbeingbrowsercampaignscannotchangingcollectingcomputercookiescoredisabledenableessentialexperiencefunctionfunctionalityimproveinsightsmarketingnecessaryonlyopensotherspreferencesproperlyprovidingrelevancyreportingsecuresomestoresuchsuggestedthesetoolusageuseduseswebsitewhilewindowwithout
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR11 | warning | 14% of the words a person sees are missing from the page as first delivered: the page arrives carrying 85% of the text it ends up showing | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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: the page arrives carrying 85% of the text it ends up showing 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.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
▸https://www.newcastle.gov.uk/costofliving 31.0% Very likely 15 out of 84
The page https://www.newcastle.gov.uk/costofliving
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Fails · 6 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 AI systems are being turned away before they reach the site, and because the barrier sits outside the organisation's own systems, nobody inside can see it happening. Those systems carry on answering questions about the organisation, from other people's material rather than its own, so the conversation about it goes on without it and nobody has decided that. 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.newcastle.gov.uk · resolves to 194.61.173.205
Address trailwww.newcastle.gov.uk
Checked2026-09-17 16:33 UTC · request sent from 54.171.52.206 (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 heading 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)
H2 Main navigation H4 Debt and money advice level jumped H4 Energy advice H4 Council tax discounts and exemptions H4 Check what benefits you can receive H4 Housing support H4 Help with school and learning costs H4 Free childcare H4 Wellbeing Hubs H4 Managing on a low income H4 Emergency funds and support H4 Help with food (foodbanks and cheap food) H4 Children and Families Newcastle H4 Mental health support H4 Household Support Fund H3 Most popular pages H3 We're on social media
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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT10 | fail | the page carries no main heading, so nothing on it states what the page is about | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The page carries a main heading (the H1), its own statement of what the page is about. What good looks like The page carries a single main heading stating what it is about. Why it matters The page never states its own subject, so anything reading it has to guess what it is about. Guessed subjects are how content gets filed, and quoted, under the wrong topic. What we found on this page the page carries no main heading, so nothing on it states what the page is about The evidence, taken from the page as served The headings on this page, as served
The page was read for a top-level heading. These are the headings it does carry. <h2 class="sr-only" id="block-nccb5-main-navigation-menu">Main navigation</h2> <h4 class="climate-ch-link">Debt and money advice</h4> <h4 class="climate-ch-link">Energy advice</h4> <h4 class="climate-ch-link">Council tax discounts and exemptions</h4> <h4 class="climate-ch-link">Check what benefits you can receive</h4> <h4 class="climate-ch-link">Housing support</h4> <h4 class="climate-ch-link">Help with school and learning costs</h4> <h4 class="climate-ch-link">Free childcare</h4> <h4 class="climate-ch-link">Wellbeing Hubs</h4> <h4 class="climate-ch-link">Managing on a low income</h4> …and 7 more like it. 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 carries a single main heading stating what it is about. 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 | fail | this page carries dates, and states none of it in a form a machine can take as given, so those facts have to be worked out from the wording around them | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page states what it is, and the exact facts it carries, in a form a machine can take as given rather than work out from the wording. What good looks like The page states what it is in machine-readable form, and where it carries exact facts it states those too. A page of exact facts stating none of them is a fail; a narrative page without a block is a warning. Why it matters Where a page carries exact facts, an address, opening hours, a price, a date, leaving them only in prose means they are worked out rather than read, and that is where a wrong branch or an old price comes from. What we found on this page this page carries dates, and states none of it in a form a machine can take as given, so those facts have to be worked out from the wording around them The evidence, taken from the page as served The head of this page, as served
The page was read for a short block of machine-readable detail saying what it is. The page's own words carry dates, which is why this weighs as it does. <head> <meta charset="utf-8"/> <style>/* @see https://github.com/aFarkas/lazysizes#broken-image-symbol */.js img.b-lazy:not([src]) { visibility: hidden; }/* @see https://github.com/aFarkas/lazysizes#automatically-setting-the-sizes-attribute */.js img.lazyloaded[data-sizes=auto] { display: block; width: 100%; }</style> <meta name="description" content="The website of Newcastle City Council"/> <meta name="geo.placename" content="Newcastle upon Tyne"/> <link rel="canonical" href="https://www.newcastle.gov.uk/cost-living-support"/> <link rel="icon" href="favicon.ico"/> <link rel="icon" sizes="16x16" href="/favicon-16x16.png"/> <link rel="icon" sizes="32x32" href="/favicon-32x32.png"/> <link rel="icon" sizes="96x96" href="/favicon-96x96.png"/> <link rel="icon" sizes="192x192" href="/android-chrome-192x192.png"/> <link rel="apple-touch-icon" href="/apple-touch-icon-60x60.png"/> <link rel="apple-touch-icon" sizes="72x72" href="/android-chrome-72x72.png"/> <link rel="apple-touch-icon" sizes="76x76" href="/apple-touch-icon-76x76.png"/> <link rel="apple-touch-icon" sizes="114x114" href="/apple-touch-icon-114x114.png"/> <link rel="apple-touch-icon" sizes="120x120" href="/apple-touch-icon-120xโฆ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 states what it is in machine-readable form, and where it carries exact facts it states those too. 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT43 | fail | 1 fault in this page's construction change the structure anything reading it sees, so what is read is not quite the page that was published | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page's underlying construction holds together, or contains faults that change how it is read. What good looks like The page is built soundly enough that anything reading it sees the structure its author intended. Why it matters Anything reading the page has to take it apart before it can judge anything on it. Faults in construction can move where a section appears to end, place a heading inside a paragraph, or lose part of the page altogether. When that happens, what is read is not quite the page that was published, and neither is the answer built from it. The damage is invisible on screen, because a browser repairs quietly what a plain reader does not. What we found on this page 1 fault in this page's construction change the structure anything reading it sees, so what is read is not quite the page that was published The evidence, taken from the page as served Faults in the page's construction that change how it reads
Found while taking the page apart exactly as a reader would.
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 is built soundly enough that anything reading it sees the structure its author intended. 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: โtheme debug theme hook: 'field' file name suggestions: โช๏ธโ; 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 Identical links on one page lead to different places, so which one gets followed is a coin toss. A reader or system lands on the wrong page while believing it chose correctly. 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: โtheme debug theme hook: 'field' file name suggestions:
โช๏ธโ; 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="/services/welfare-and-benefits/debt-and-money-advice" class="field-group-link"> <!-- THEME DEBUG --> <!-- THEME HOOK: 'field' --> <!-- FILE NAME SUGGESTIONS: โช๏ธ field--expert--paragraph--field-cc-link-title--climate-change-link--default.html.twig โช๏ธ field--expert--paragraph--field-cc-link-title--climate-changeโฆ <a href="/services/environment-and-waste/energy-advice" class="field-group-link"> <!-- THEME DEBUG --> <!-- THEME HOOK: 'field' --> <!-- FILE NAME SUGGESTIONS: โช๏ธ field--expert--paragraph--field-cc-link-title--climate-change-link--default.html.twig โช๏ธ field--expert--paragraph--field-cc-link-title--climate-change-link.hโฆ <a href="https://new.newcastle.gov.uk/council-tax/council-tax-discounts-exemptions" class="field-group-link"> <!-- THEME DEBUG --> <!-- THEME HOOK: 'field' --> <!-- FILE NAME SUGGESTIONS: โช๏ธ field--expert--paragraph--field-cc-link-title--climate-change-link--default.html.twig โช๏ธ field--expert--paragraph--field-cc-link-โฆ <a href="/services/welfare-and-benefits/check-what-benefits-you-can-receive" class="field-group-link"> <!-- THEME DEBUG --> <!-- THEME HOOK: 'field' --> <!-- FILE NAME SUGGESTIONS: โช๏ธ field--expert--paragraph--field-cc-link-title--climate-change-link--default.html.twig โช๏ธ field--expert--paragraph--field-cc-link-title--โฆ <a href="/services/housing/housing-advice-and-homelessness/what-do-if-you-need-housing-advice-or-are-homeless" class="field-group-link"> <!-- THEME DEBUG --> <!-- THEME HOOK: 'field' --> <!-- FILE NAME SUGGESTIONS: โช๏ธ field--expert--paragraph--field-cc-link-title--climate-change-link--default.html.twig โช๏ธ field--expertโฆ <a href="/services/schools-learning-and-childcare/help-school-and-learning-costs" class="field-group-link"> <!-- THEME DEBUG --> <!-- THEME HOOK: 'field' --> <!-- FILE NAME SUGGESTIONS: โช๏ธ field--expert--paragraph--field-cc-link-title--climate-change-link--default.html.twig โช๏ธ field--expert--paragraph--field-cc-link-tiโฆ <a href="/services/schools-learning-and-childcare/childcare-and-early-years/free-early-education-and" class="field-group-link"> <!-- THEME DEBUG --> <!-- THEME HOOK: 'field' --> <!-- FILE NAME SUGGESTIONS: โช๏ธ field--expert--paragraph--field-cc-link-title--climate-change-link--default.html.twig โช๏ธ field--expert--paragraโฆ <a href="/cost-living-support/wellbeing-hubs" class="field-group-link"> <!-- THEME DEBUG --> <!-- THEME HOOK: 'field' --> <!-- FILE NAME SUGGESTIONS: โช๏ธ field--expert--paragraph--field-cc-link-title--climate-change-link--default.html.twig โช๏ธ field--expert--paragraph--field-cc-link-title--climate-change-link.html.twig โชโฆ <a href="https://www.informationnow.org.uk/article/cost-of-living/" class="field-group-link"> <!-- THEME DEBUG --> <!-- THEME HOOK: 'field' --> <!-- FILE NAME SUGGESTIONS: โช๏ธ field--expert--paragraph--field-cc-link-title--climate-change-link--default.html.twig โช๏ธ field--expert--paragraph--field-cc-link-title--climate-cโฆ <a href="https://www.informationnow.org.uk/article/emergency-funds-and-support/" class="field-group-link"> <!-- THEME DEBUG --> <!-- THEME HOOK: 'field' --> <!-- FILE NAME SUGGESTIONS: โช๏ธ field--expert--paragraph--field-cc-link-title--climate-change-link--default.html.twig โช๏ธ field--expert--paragraph--field-cc-link-titโฆ …and 2 more like it. 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Warnings · 9 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT32 | warning | the page's meta description, the short summary it offers about itself, runs to 37 characters, too short to say what the page is about; a usable summary runs from 50 to 170 characters | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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 the page's meta description, the short summary it offers about itself, runs to 37 characters, too short to say what the page is about; a usable summary runs from 50 to 170 characters The evidence, taken from the page as served The page's description, as served
<meta name="description" content="The website of Newcastle City Council"/> | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT40 | warning | the page offers no short summary for the services that show a preview of it, so each one composes its own from whatever it finds first on the page | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The short title, description and image the page offers to services that show a preview of it, and whether they match the page. What good looks like The page offers a summary for preview, and the summary is true to the page. Why it matters This summary travels further than the page does. It is what appears when the address is shared, and several services read it in preference to the page itself because it is short and already written for the purpose. Where it is absent, those services compose their own from whatever they find first, which is often navigation. Where it is present but out of step, the organisation is described to a wide audience by a sentence it wrote once and forgot. What we found on this page the page offers no short summary for the services that show a preview of it, so each one composes its own from whatever it finds first on the page The evidence, taken from the page as served The summary this page offers for preview
Read from the page as served.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT41 | warning | the page does not show where it sits in the site, so anything reading it on its own has nothing to say what it belongs to | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The trail showing the path from the front page to this one, and whether the machine-readable version of that trail says the same. What good looks like The page shows its place in the site, and says the same thing to a machine. Why it matters A page read on its own gives no sense of what it belongs to. The trail supplies it: one product within a range, one policy within a set. A reader deciding whether a page answers a question uses that to judge whether it has the right one, and how to describe it when it quotes it. Where the shown trail and the machine-readable one disagree, the page is placed in two positions at once and neither can be relied on. What we found on this page the page does not show where it sits in the site, so anything reading it on its own has nothing to say what it belongs to The evidence, taken from the page as served The path this page gives to itself
Read from the page as served: the trail shown to a reader, and the trail stated in a form a machine can take as given.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT04 | warning | the page shows the year 2024 in its text, but nothing on the page states it as the date of the content | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The page carries a date, ideally written into the markup rather than sitting only in the text. What good looks like The page carries a date, ideally written into the markup rather than sitting only in the text. Why it matters An undated page gives nothing to weigh its age against, so old and new material are treated alike. What we found on this page the page shows the year 2024 in its text, but nothing on the page states it as the date of the content The evidence, taken from the page as served The head of this page, as served
The head of the page was read for a tag stating the date of the content. The year shown above was found in the page's own text. <head> <meta charset="utf-8"/> <style>/* @see https://github.com/aFarkas/lazysizes#broken-image-symbol */.js img.b-lazy:not([src]) { visibility: hidden; }/* @see https://github.com/aFarkas/lazysizes#automatically-setting-the-sizes-attribute */.js img.lazyloaded[data-sizes=auto] { display: block; width: 100%; }</style> <meta name="description" content="The website of Newcastle City Council"/> <meta name="geo.placename" content="Newcastle upon Tyne"/> <link rel="canonical" href="https://www.newcastle.gov.uk/cost-living-support"/> <link rel="icon" href="favicon.ico"/> <link rel="icon" sizes="16x16" href="/favicon-16x16.png"/> <link rel="icon" sizes="32x32" href="/favicon-32x32.png"/> <link rel="icon" sizes="96x96" href="/favicon-96x96.png"/> <link rel="icon" sizes="192x192" href="/android-chrome-192x192.png"/> <link rel="apple-touch-icon" href="/apple-touch-icon-60x60.png"/> <link rel="apple-touch-icon" sizes="72x72" href="/android-chrome-72x72.png"/> <link rel="apple-touch-icon" sizes="76x76" href="/apple-touch-icon-76x76.png"/> <link rel="apple-touch-icon" sizes="114x114" href="/apple-touch-icon-114x114.png"/> <link rel="apple-touch-icon" sizes="120x120" href="/apple-touch-icon-120xโฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT35 | warning | the copyright line at the foot of this page carries no year, so there is nothing on the page as served to date it by | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The copyright line at the foot of the page, and the year it states. What good looks like The copyright line states the current year. Why it matters An old copyright year reads as a site nobody is looking after, and it dates the page for anything that relies on dates. Content can be treated as years older than it really is. What we found on this page the copyright line at the foot of this page carries no year, so there is nothing on the page as served to date it by The evidence, taken from the page as served The copyright line on this page, as served
This is the copyright line as the page serves it. It was read for a year, and carries none. stagram Find out how we use social media Press Office and News ReciteMe and Accessibility ยฉNewcastle City Council Privacy Notice Terms and conditions Contact Us Covid-19 support Listen and translate {"path":{"baseUrl":"\/","pathPrefix":"","c | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR03 | warning | 22% of the words a person sees are missing from the page as first delivered (1833 characters delivered, 2712 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 looks complete to a person, but its content is built by scripts that many AI systems never run, so they receive it near-empty. The organisation's material is missing from their answers. What we found on this page 22% of the words a person sees are missing from the page as first delivered (1833 characters delivered, 2712 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 1833 characters of text; after JavaScript runs the page carries 2712. 22% of the rendered page's words are absent from the HTML the server sends. What the server sends (raw HTML text, first 280 chars) Cost of living support | Newcastle City Council Skip to main content Listen and translate Make a payment Jobs and careers My Portal Contact us Listen and translate Main navigation Services Business Our City Get Involved Local Government News Cost of living support โ โ โ The cost …
Words present only after JavaScript runs
acceptanalyticalchosenclosecollectingcontrolcookiecoredecliningenableessentialexperienceexternalfeedsfunctionalityhaveiconimproveinformationionsitemsnecessaryotherotherspartypreventrememberreportingsettingsshortlistsitesuchthesethirdtoolusageusesviewingwhenwhile
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR11 | warning | 22% of the words a person sees are missing from the page as first delivered: the page arrives carrying 68% of the text it ends up showing | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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 22% of the words a person sees are missing from the page as first delivered: the page arrives carrying 68% of the text it ends up showing 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.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT27 | warning | the content missing from the raw extraction is largely present inside script tags (95% of sampled missing terms): the page ships its content as script data rather than as document text | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check On the sampled pages, how much text is shipped inside scripts as data rather than as page text. What good looks like The page's text is present as page text, not shipped inside scripts as data. Why it matters Part of this page's content is packed inside its code rather than written on the page, so many reading systems never see it. What they miss is simply absent from their answers. What we found on this page the content missing from the raw extraction is largely present inside script tags (95% of sampled missing terms): the page ships its content as script data rather than as document text The evidence, taken from the page as served Where the missing words were found
The words a person sees but the delivered page did not carry were looked for inside the page's script blocks.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
▸http://www.newcastle.gov.uk/jobs 32.2% Very likely 15 out of 83
The page http://www.newcastle.gov.uk/jobs
▸http://www.newcastle.gov.uk/services/schools-learning-and-childcare/about-our-schools/school-term-dates 32.0% Very likely 15 out of 84
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Fails · 4 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 AI systems are being turned away before they reach the site, and because the barrier sits outside the organisation's own systems, nobody inside can see it happening. Those systems carry on answering questions about the organisation, from other people's material rather than its own, so the conversation about it goes on without it and nobody has decided that. 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.newcastle.gov.uk · resolves to 194.61.173.205
Address trailwww.newcastle.gov.uk
Checked2026-09-17 16:33 UTC · request sent from 54.171.52.206 (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 heading 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)
H2 Main navigation H2 Title H4 Have your say level jumped H1 School term dates H2 School term dates H2 School Year 2024 to 2025 H2 School Year 2025 to 2026 H2 School Year 2026 to 2027 H2 School Year 2027 to 2028 H2 Related Pages H3 Most popular pages H3 We're on social media
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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT43 | fail | 1 fault in this page's construction change the structure anything reading it sees, so what is read is not quite the page that was published | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page's underlying construction holds together, or contains faults that change how it is read. What good looks like The page is built soundly enough that anything reading it sees the structure its author intended. Why it matters Anything reading the page has to take it apart before it can judge anything on it. Faults in construction can move where a section appears to end, place a heading inside a paragraph, or lose part of the page altogether. When that happens, what is read is not quite the page that was published, and neither is the answer built from it. The damage is invisible on screen, because a browser repairs quietly what a plain reader does not. What we found on this page 1 fault in this page's construction change the structure anything reading it sees, so what is read is not quite the page that was published The evidence, taken from the page as served Faults in the page's construction that change how it reads
Found while taking the page apart exactly as a reader would.
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 is built soundly enough that anything reading it sees the structure its author intended. 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 The page's headings begin at its top level, rather than starting part way down. What good looks like The page's headings begin with its top-level heading. Levels skipped further down are weighed under heading hierarchy, and a page with no top-level heading at all under the missing main heading, so each fault is marked once. Why it matters The page's structure starts part way down, below a top level that never opens it. Sections then sit under nothing, and anything filing content by structure starts in the wrong place. 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 (the starting level is marked)
H2 Main navigation level jumped H2 Title H4 Have your say H1 School term dates H2 School term dates H2 School Year 2024 to 2025 H2 School Year 2025 to 2026 H2 School Year 2026 to 2027 H2 School Year 2027 to 2028 H2 Related Pages H3 Most popular pages H3 We're on social media
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 begin with its top-level heading. 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Warnings · 11 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT32 | warning | the page's meta description, the short summary it offers about itself, runs to 727 characters, longer than the 170 characters a listing shows, so the end of it is cut off | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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 the page's meta description, the short summary it offers about itself, runs to 727 characters, longer than the 170 characters a listing shows, so the end of it is cut off The evidence, taken from the page as served The page's description, as served
<meta name="description" content="Individual schools set their own school days and term dates.The dates on this page are set by the council for Local Authority maintained nursery schools and Byker Primary School. Other schools are encouraged to use the same dates but don't have to. You will find individual school term โฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT16 | warning | the page states nothing about itself in a form a machine can take as given, so who you are and what the page is about are worked out from its wording | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page states what it is, and the exact facts it carries, in a form a machine can take as given rather than work out from the wording. What good looks like The page states what it is in machine-readable form, and where it carries exact facts it states those too. A page of exact facts stating none of them is a fail; a narrative page without a block is a warning. Why it matters Where a page carries exact facts, an address, opening hours, a price, a date, leaving them only in prose means they are worked out rather than read, and that is where a wrong branch or an old price comes from. What we found on this page the page states nothing about itself in a form a machine can take as given, so who you are and what the page is about are worked out from its wording The evidence, taken from the page as served The head of this page, as served
The page was read for a short block of machine-readable detail saying what it is. The page's own words carry no exact facts of that kind. <head> <meta charset="utf-8"/> <style>/* @see https://github.com/aFarkas/lazysizes#broken-image-symbol */.js img.b-lazy:not([src]) { visibility: hidden; }/* @see https://github.com/aFarkas/lazysizes#automatically-setting-the-sizes-attribute */.js img.lazyloaded[data-sizes=auto] { display: block; width: 100%; }</style> <meta name="description" content="Individual schools set their own school days and term dates.The dates on this page are set by the council for Local Authority maintained nursery schools and Byker Primary School. Other schools are encouraged to use the same dates but don't have to. You will find individual school term dates on their own websites.The school year starts in September and is usually organised into 3 terms with a 1 week holiday halfway through the term. Term dates for Local Authority maintained schools. These dates may not apply to academies, foundation, free or voluntary aided schools. These schools are encouraged to accept the dates set by the council but they are not required to. You should contact these schools to confirm their dates."/> <meta name="keywords" content="Term dates, holidays, school holidays, end of term"/> <meta name="geo.placename" contโฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT40 | warning | the page offers no short summary for the services that show a preview of it, so each one composes its own from whatever it finds first on the page | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The short title, description and image the page offers to services that show a preview of it, and whether they match the page. What good looks like The page offers a summary for preview, and the summary is true to the page. Why it matters This summary travels further than the page does. It is what appears when the address is shared, and several services read it in preference to the page itself because it is short and already written for the purpose. Where it is absent, those services compose their own from whatever they find first, which is often navigation. Where it is present but out of step, the organisation is described to a wide audience by a sentence it wrote once and forgot. What we found on this page the page offers no short summary for the services that show a preview of it, so each one composes its own from whatever it finds first on the page The evidence, taken from the page as served The summary this page offers for preview
Read from the page as served.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT41 | warning | the page does not show where it sits in the site, so anything reading it on its own has nothing to say what it belongs to | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The trail showing the path from the front page to this one, and whether the machine-readable version of that trail says the same. What good looks like The page shows its place in the site, and says the same thing to a machine. Why it matters A page read on its own gives no sense of what it belongs to. The trail supplies it: one product within a range, one policy within a set. A reader deciding whether a page answers a question uses that to judge whether it has the right one, and how to describe it when it quotes it. Where the shown trail and the machine-readable one disagree, the page is placed in two positions at once and neither can be relied on. What we found on this page the page does not show where it sits in the site, so anything reading it on its own has nothing to say what it belongs to The evidence, taken from the page as served The path this page gives to itself
Read from the page as served: the trail shown to a reader, and the trail stated in a form a machine can take as given.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT04 | warning | the page shows the year 2027 in its text, but nothing on the page states it as the date of the content | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The page carries a date, ideally written into the markup rather than sitting only in the text. What good looks like The page carries a date, ideally written into the markup rather than sitting only in the text. Why it matters An undated page gives nothing to weigh its age against, so old and new material are treated alike. What we found on this page the page shows the year 2027 in its text, but nothing on the page states it as the date of the content The evidence, taken from the page as served The head of this page, as served
The head of the page was read for a tag stating the date of the content. The year shown above was found in the page's own text. <head> <meta charset="utf-8"/> <style>/* @see https://github.com/aFarkas/lazysizes#broken-image-symbol */.js img.b-lazy:not([src]) { visibility: hidden; }/* @see https://github.com/aFarkas/lazysizes#automatically-setting-the-sizes-attribute */.js img.lazyloaded[data-sizes=auto] { display: block; width: 100%; }</style> <meta name="description" content="Individual schools set their own school days and term dates.The dates on this page are set by the council for Local Authority maintained nursery schools and Byker Primary School. Other schools are encouraged to use the same dates but don't have to. You will find individual school term dates on their own websites.The school year starts in September and is usually organised into 3 terms with a 1 week holiday halfway through the term. Term dates for Local Authority maintained schools. These dates may not apply to academies, foundation, free or voluntary aided schools. These schools are encouraged to accept the dates set by the council but they are not required to. You should contact these schools to confirm their dates."/> <meta name="keywords" content="Term dates, holidays, school holidays, end of term"/> <meta name="geo.placename" contโฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT35 | warning | the copyright line at the foot of this page carries no year, so there is nothing on the page as served to date it by | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The copyright line at the foot of the page, and the year it states. What good looks like The copyright line states the current year. Why it matters An old copyright year reads as a site nobody is looking after, and it dates the page for anything that relies on dates. Content can be treated as years older than it really is. What we found on this page the copyright line at the foot of this page carries no year, so there is nothing on the page as served to date it by The evidence, taken from the page as served The copyright line on this page, as served
This is the copyright line as the page serves it. It was read for a year, and carries none. stagram Find out how we use social media Press Office and News ReciteMe and Accessibility ยฉNewcastle City Council Privacy Notice Terms and conditions Contact Us Covid-19 support Listen and translate {"path":{"baseUrl":"\/","pathPrefix":"","c | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MX10 | warning | 3 links to a file on this page do not say what the file is and how big it is before it is opened. A reader deciding whether to open a file has nothing to judge it by, and on a slow or metered connection an unnamed file is a risk rather than an offer. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Links that open a file, and whether the wording states the format and the size. What good looks like A link to a file states its format and its size. Why it matters A reader deciding whether to open a file has nothing to judge it by, and on a slow or metered connection an unnamed file is a risk rather than an offer. What we found on this page 3 links to a file on this page do not say what the file is and how big it is before it is opened. A reader deciding whether to open a file has nothing to judge it by, and on a slow or metered connection an unnamed file is a risk rather than an offer. The evidence, taken from the page as served The links to a file, and what each one states
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR03 | warning | 18% of the words a person sees are missing from the page as first delivered (4119 characters delivered, 4998 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 looks complete to a person, but its content is built by scripts that many AI systems never run, so they receive it near-empty. The organisation's material is missing from their answers. What we found on this page 18% of the words a person sees are missing from the page as first delivered (4119 characters delivered, 4998 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 4119 characters of text; after JavaScript runs the page carries 4998. 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) School term dates | Newcastle City Council School term dates Skip to main content Listen and translate Make a payment Jobs and careers My Portal Contact us Listen and translate Main navigation Services Business Our City Get Involved Local Government News Cost of living support โ …
Words present only after JavaScript runs
aboutacceptanalyticalchosenclosecollectingcontrolcookiecoredecliningenableessentialexperienceexternalfeedsfunctionalityhelpiconimproveionsitemsnecessaryotherspartypreventrememberreportingsettingsshortlistsitesuchthatthesethirdtoolusageusesusingviewingwhenwhile
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR11 | warning | 18% of the words a person sees are missing from the page as first delivered: the page arrives carrying 82% of the text it ends up showing | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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: the page arrives carrying 82% of the text it ends up showing 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.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT27 | warning | the content missing from the raw extraction is largely present inside script tags (92% of sampled missing terms): the page ships its content as script data rather than as document text | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check On the sampled pages, how much text is shipped inside scripts as data rather than as page text. What good looks like The page's text is present as page text, not shipped inside scripts as data. Why it matters Part of this page's content is packed inside its code rather than written on the page, so many reading systems never see it. What they miss is simply absent from their answers. What we found on this page the content missing from the raw extraction is largely present inside script tags (92% of sampled missing terms): the page ships its content as script data rather than as document text The evidence, taken from the page as served Where the missing words were found
The words a person sees but the delivered page did not carry were looked for inside the page's script blocks.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
▸http://www.newcastle.gov.uk/services/parking-and-permits/car-parks-and-street-parking 32.0% Very likely 14 out of 84
The page http://www.newcastle.gov.uk/services/parking-and-permits/car-parks-and-street-parking
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Fails · 4 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 AI systems are being turned away before they reach the site, and because the barrier sits outside the organisation's own systems, nobody inside can see it happening. Those systems carry on answering questions about the organisation, from other people's material rather than its own, so the conversation about it goes on without it and nobody has decided that. 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.newcastle.gov.uk · resolves to 194.61.173.205
Address trailwww.newcastle.gov.uk
Checked2026-09-17 16:33 UTC · request sent from 54.171.52.206 (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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| DS14 | fail | 2 redirect hops on the way to the page that answers | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check How many redirect hops a page takes before arriving, and whether it lands on an untidy address. What good looks like A page arrives in few redirect hops and lands on a tidy address. Why it matters Addresses here pass through several forwarding steps before a page appears, and some readers give up part way. The address that ends up quoted is one of the intermediate ones, not the proper one. What we found on this page 2 redirect hops on the way to the page that answers The evidence, taken from the page as served The steps this address took before it arrived
Followed from the address asked for to the page that finally answered.
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 arrives in few redirect hops and lands on a tidy address. 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 | fail | this page carries prices or figures, and states none of it in a form a machine can take as given, so those facts have to be worked out from the wording around them | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page states what it is, and the exact facts it carries, in a form a machine can take as given rather than work out from the wording. What good looks like The page states what it is in machine-readable form, and where it carries exact facts it states those too. A page of exact facts stating none of them is a fail; a narrative page without a block is a warning. Why it matters Where a page carries exact facts, an address, opening hours, a price, a date, leaving them only in prose means they are worked out rather than read, and that is where a wrong branch or an old price comes from. What we found on this page this page carries prices or figures, and states none of it in a form a machine can take as given, so those facts have to be worked out from the wording around them The evidence, taken from the page as served The head of this page, as served
The page was read for a short block of machine-readable detail saying what it is. The page's own words carry prices or figures, which is why this weighs as it does. <head> <meta charset="utf-8"/> <meta name="description" content="Discover our car parks, their locations and facilities."/> <link rel="canonical" href="https://new.newcastle.gov.uk/parking/car-parks/find"/> <meta name="Generator" content="Drupal 10 (LocalGov Drupal | https://localgovdrupal.org)"/> <meta name="MobileOptimized" content="width"/> <meta name="HandheldFriendly" content="true"/> <meta name="viewport" content="width=device-width, initial-scale=1.0"/> <link rel="icon" href="/sites/default/files/ncc-favicon_0.ico" type="image/vnd.microsoft.icon"/> <script src="/sites/default/files/google_tag/ncc_default/google_tag.script.js?tlij1z" defer="defer"/> <title>Find a car park | Newcastle City Council</title> <link rel="stylesheet" media="all" href="/core/themes/stable9/css/core/components/progress.module.css?tlij1z"/> <link rel="stylesheet" media="all" href="/core/themes/stable9/css/core/components/ajax-progress.module.css?tlij1z"/> <link rel="stylesheet" media="all" href="/core/themes/stable9/css/system/components/align.module.css?tlij1z"/> <link rel="stylesheet" media="all" href="/core/themes/stable9/css/system/components/fieldgroup.module.css?tlij1z"/> <link rel="stylesheet" mโฆ 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 states what it is in machine-readable form, and where it carries exact facts it states those too. 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: โtheme debug theme hook: 'facets_result_item' file name suggeโ, โtheme debug theme hook: 'field' file name suggestions: โช๏ธโ; 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 Identical links on one page lead to different places, so which one gets followed is a coin toss. A reader or system lands on the wrong page while believing it chose correctly. 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: โtheme debug theme hook: 'facets_result_item' file name suggeโ, โtheme debug theme hook: 'field' file name suggestions:
โช๏ธโ; 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="/parking/car-parks/find?f%5B0%5D=localgov_directories_facets%3A132" rel="nofollow" data-drupal-facet-item-id="localgov-directories-facets-132" data-drupal-facet-item-value="132" data-drupal-facet-item-count="11" data-drupal-facet-filter-value="localgov_directories_facets:132" data-drupal-facet-widget-element-cโฆ <a href="/parking/car-parks/find?f%5B0%5D=localgov_directories_facets%3A125" rel="nofollow" data-drupal-facet-item-id="localgov-directories-facets-125" data-drupal-facet-item-value="125" data-drupal-facet-item-count="22" data-drupal-facet-filter-value="localgov_directories_facets:125" data-drupal-facet-widget-element-cโฆ <a href="/parking/car-parks/find?f%5B0%5D=localgov_directories_facets%3A126" rel="nofollow" data-drupal-facet-item-id="localgov-directories-facets-126" data-drupal-facet-item-value="126" data-drupal-facet-item-count="43" data-drupal-facet-filter-value="localgov_directories_facets:126" data-drupal-facet-widget-element-cโฆ <a href="/parking/car-parks/find?f%5B0%5D=localgov_directories_facets%3A136" rel="nofollow" data-drupal-facet-item-id="localgov-directories-facets-136" data-drupal-facet-item-value="136" data-drupal-facet-item-count="8" data-drupal-facet-filter-value="localgov_directories_facets:136" data-drupal-facet-widget-element-clโฆ <a href="/parking/car-parks/find?f%5B0%5D=localgov_directories_facets%3A135" rel="nofollow" data-drupal-facet-item-id="localgov-directories-facets-135" data-drupal-facet-item-value="135" data-drupal-facet-item-count="16" data-drupal-facet-filter-value="localgov_directories_facets:135" data-drupal-facet-widget-element-cโฆ <a href="/parking/car-parks/find?f%5B0%5D=localgov_directories_facets%3A137" rel="nofollow" data-drupal-facet-item-id="localgov-directories-facets-137" data-drupal-facet-item-value="137" data-drupal-facet-item-count="9" data-drupal-facet-filter-value="localgov_directories_facets:137" data-drupal-facet-widget-element-clโฆ <a href="/parking/car-parks/find?f%5B0%5D=localgov_directories_facets%3A127" rel="nofollow" data-drupal-facet-item-id="localgov-directories-facets-127" data-drupal-facet-item-value="127" data-drupal-facet-item-count="47" data-drupal-facet-filter-value="localgov_directories_facets:127" data-drupal-facet-widget-element-cโฆ <a href="/parking/car-parks/find?f%5B0%5D=localgov_directories_facets%3A140" rel="nofollow" data-drupal-facet-item-id="localgov-directories-facets-140" data-drupal-facet-item-value="140" data-drupal-facet-item-count="1" data-drupal-facet-filter-value="localgov_directories_facets:140" data-drupal-facet-widget-element-clโฆ <a href="/parking/car-parks/find?f%5B0%5D=localgov_directories_facets%3A138" rel="nofollow" data-drupal-facet-item-id="localgov-directories-facets-138" data-drupal-facet-item-value="138" data-drupal-facet-item-count="13" data-drupal-facet-filter-value="localgov_directories_facets:138" data-drupal-facet-widget-element-cโฆ <a href="/parking/car-parks/find?f%5B0%5D=localgov_directories_facets%3A128" rel="nofollow" data-drupal-facet-item-id="localgov-directories-facets-128" data-drupal-facet-item-value="128" data-drupal-facet-item-count="18" data-drupal-facet-filter-value="localgov_directories_facets:128" data-drupal-facet-widget-element-cโฆ …and 2 more like it. 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Warnings · 10 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT40 | warning | the page offers no short summary for the services that show a preview of it, so each one composes its own from whatever it finds first on the page | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The short title, description and image the page offers to services that show a preview of it, and whether they match the page. What good looks like The page offers a summary for preview, and the summary is true to the page. Why it matters This summary travels further than the page does. It is what appears when the address is shared, and several services read it in preference to the page itself because it is short and already written for the purpose. Where it is absent, those services compose their own from whatever they find first, which is often navigation. Where it is present but out of step, the organisation is described to a wide audience by a sentence it wrote once and forgot. What we found on this page the page offers no short summary for the services that show a preview of it, so each one composes its own from whatever it finds first on the page The evidence, taken from the page as served The summary this page offers for preview
Read from the page as served.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT41 | warning | the page shows where it sits in the site but does not state it in a form a machine can take as given | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The trail showing the path from the front page to this one, and whether the machine-readable version of that trail says the same. What good looks like The page shows its place in the site, and says the same thing to a machine. Why it matters A page read on its own gives no sense of what it belongs to. The trail supplies it: one product within a range, one policy within a set. A reader deciding whether a page answers a question uses that to judge whether it has the right one, and how to describe it when it quotes it. Where the shown trail and the machine-readable one disagree, the page is placed in two positions at once and neither can be relied on. What we found on this page the page shows where it sits in the site but does not state it in a form a machine can take as given The evidence, taken from the page as served The path this page gives to itself
Read from the page as served: the trail shown to a reader, and the trail stated in a form a machine can take as given.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| DS37 | warning | 16 of the 54 links this page offers to the site's own pages carry an instruction not to follow them. That instruction is meant for links to other people's sites, and here it asks readers not to go any further into the organisation's own estate | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Links from the site to its own pages that carry an instruction not to follow them. What good looks like The site does not tell readers to ignore its own pages. Why it matters The instruction is meant for links to other people's sites, and it reaches the site's own links by accident, often across a whole navigation at once when it is set in a template. Where that happens the organisation has asked readers not to go any further into its own estate. The pages stay published, stay live for a visitor, and stay unread. What we found on this page 16 of the 54 links this page offers to the site's own pages carry an instruction not to follow them. That instruction is meant for links to other people's sites, and here it asks readers not to go any further into the organisation's own estate The evidence, taken from the page as served The site's own pages this page asks readers not to follow
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT04 | warning | the page carries no date, so there is nothing on it saying how current its content is | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The page carries a date, ideally written into the markup rather than sitting only in the text. What good looks like The page carries a date, ideally written into the markup rather than sitting only in the text. Why it matters An undated page gives nothing to weigh its age against, so old and new material are treated alike. What we found on this page the page carries no date, so there is nothing on it saying how current its content is The evidence, taken from the page as served The head of this page, as served
The head of the page and the page's own text were read for a date. <head> <meta charset="utf-8"/> <meta name="description" content="Discover our car parks, their locations and facilities."/> <link rel="canonical" href="https://new.newcastle.gov.uk/parking/car-parks/find"/> <meta name="Generator" content="Drupal 10 (LocalGov Drupal | https://localgovdrupal.org)"/> <meta name="MobileOptimized" content="width"/> <meta name="HandheldFriendly" content="true"/> <meta name="viewport" content="width=device-width, initial-scale=1.0"/> <link rel="icon" href="/sites/default/files/ncc-favicon_0.ico" type="image/vnd.microsoft.icon"/> <script src="/sites/default/files/google_tag/ncc_default/google_tag.script.js?tlij1z" defer="defer"/> <title>Find a car park | Newcastle City Council</title> <link rel="stylesheet" media="all" href="/core/themes/stable9/css/core/components/progress.module.css?tlij1z"/> <link rel="stylesheet" media="all" href="/core/themes/stable9/css/core/components/ajax-progress.module.css?tlij1z"/> <link rel="stylesheet" media="all" href="/core/themes/stable9/css/system/components/align.module.css?tlij1z"/> <link rel="stylesheet" media="all" href="/core/themes/stable9/css/system/components/fieldgroup.module.css?tlij1z"/> <link rel="stylesheet" mโฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT35 | warning | the copyright line at the foot of this page carries no year, so there is nothing on the page as served to date it by | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The copyright line at the foot of the page, and the year it states. What good looks like The copyright line states the current year. Why it matters An old copyright year reads as a site nobody is looking after, and it dates the page for anything that relies on dates. Content can be treated as years older than it really is. What we found on this page the copyright line at the foot of this page carries no year, so there is nothing on the page as served to date it by The evidence, taken from the page as served The copyright line on this page, as served
This is the copyright line as the page serves it. It was read for a year, and carries none. ch and comment on planning applications Footer Accessibility Privacy Terms and conditions ยฉNewcastle City Council {"path":{"baseUrl":"\/","pathPrefix":"","currentPath":"node\/2227","currentPathIsAdmin":false,"isFront":false,"currentLanguage" | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AJ07 | warning | 1 required field(s) have no tie in the page's code between the field and its error message, so which field an error belongs to rests on layout alone | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether required form fields are linked in the markup to the error messages about them. What good looks like Each required field is tied in the markup to the message that describes its error. Why it matters An error message sits on the page with nothing tying it to the field it concerns, so the correction has no anchor. What we found on this page 1 required field(s) have no tie in the page's code between the field and its error message, so which field an error belongs to rests on layout alone The evidence, taken from the page as served The required fields with no error association, as served
<input data-drupal-selector="edit-s" placeholder="Search" type="text" id="edit-s--2" name="s" value="" size="30" maxlength="128" class="form-text required" required="required" aria-required="true"/> | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS13 | warning | 1 of 1 iframes untitled | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Each embedded panel on the page carries a title saying what it contains. What good looks like Each embedded panel carries a title saying what it contains. Why it matters Content brought into the page from elsewhere, a map, a form, a video player, carries no name saying what it is. Anything reading the page sees a hole where that content sits. What we found on this page 1 of 1 iframes untitled The evidence, taken from the page as served The iframes with no title attribute, as served
<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-W7BB9DGL" height="0" width="0" style="display:none;visibility:hidden"/> | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR03 | warning | 24% of the words a person sees are missing from the page as first delivered (2759 characters delivered, 3834 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 looks complete to a person, but its content is built by scripts that many AI systems never run, so they receive it near-empty. The organisation's material is missing from their answers. What we found on this page 24% of the words a person sees are missing from the page as first delivered (2759 characters delivered, 3834 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 2759 characters of text; after JavaScript runs the page carries 3834. 24% of the rendered page's words are absent from the HTML the server sends. What the server sends (raw HTML text, first 280 chars) Find a car park | Newcastle City Council Skip to main content Find a car park Services Menu Main navigation News Pay My portal Listen and translate Search Services menu Adult social care Benefits and money advice Births, deaths, marriages and ceremonies Budget, policies, performa…
Words present only after JavaScript runs
acceptaccessadvertisinganalyticalanalyticsareasbeingbrowsercampaignscannotchangingcollectingcomputercontributorscookiescoredisabledenableessentialexperiencefunctionfunctionalityimproveinformationinsightsintoleafletmarketingnecessaryonlyopensopenstreetmapotherspreferencesproperlyprovidingrelevancyreportingsecuresomestoresuchsuggestedthesetoolusageuseduseswebsitewhilewindowwithout
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR11 | warning | 24% of the words a person sees are missing from the page as first delivered: the page arrives carrying 72% of the text it ends up showing | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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 24% of the words a person sees are missing from the page as first delivered: the page arrives carrying 72% of the text it ends up showing 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.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
▸http://www.newcastle.gov.uk/services/planning-building-and-development/search-view-and-comment-planning-applications 31.5% Very likely 14 out of 85
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Fails · 7 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 AI systems are being turned away before they reach the site, and because the barrier sits outside the organisation's own systems, nobody inside can see it happening. Those systems carry on answering questions about the organisation, from other people's material rather than its own, so the conversation about it goes on without it and nobody has decided that. 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.newcastle.gov.uk · resolves to 194.61.173.205
Address trailwww.newcastle.gov.uk
Checked2026-09-17 16:33 UTC · request sent from 54.171.52.206 (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 | 2 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 heading 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 2 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)
H2 Main navigation H2 Title H4 Have your say level jumped H1 Search for, view, and comment on planning applications H2 Search for, view, and comment on planning applications H3 Public Access allows you to look at details of applications, make comments, and H3 A guide to using this page H3 How do I comment on a planning application? H3 How long do I have to comment? H3 Will my comments be made public? H3 Can I view planning applications in person or comment in writing? H3 What will be considered? H3 What won't be considered? H3 What is the decision making process? H3 Will I be told about the decision? H3 What is the publicity required for applications? H3 How can I find out about high-profile major applications in the city? H3 Appeals Register H3 Customer feedback H3 Important notes H3 Further points to note H2 Related Pages H4 Need more information? level jumped H3 Most popular pages H3 We're on social media
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 | fail | this page carries prices or figures and an address, and states none of it in a form a machine can take as given, so those facts have to be worked out from the wording around them | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page states what it is, and the exact facts it carries, in a form a machine can take as given rather than work out from the wording. What good looks like The page states what it is in machine-readable form, and where it carries exact facts it states those too. A page of exact facts stating none of them is a fail; a narrative page without a block is a warning. Why it matters Where a page carries exact facts, an address, opening hours, a price, a date, leaving them only in prose means they are worked out rather than read, and that is where a wrong branch or an old price comes from. What we found on this page this page carries prices or figures and an address, and states none of it in a form a machine can take as given, so those facts have to be worked out from the wording around them The evidence, taken from the page as served The head of this page, as served
The page was read for a short block of machine-readable detail saying what it is. The page's own words carry prices or figures and an address, which is why this weighs as it does. <head> <meta charset="utf-8"/> <style>/* @see https://github.com/aFarkas/lazysizes#broken-image-symbol */.js img.b-lazy:not([src]) { visibility: hidden; }/* @see https://github.com/aFarkas/lazysizes#automatically-setting-the-sizes-attribute */.js img.lazyloaded[data-sizes=auto] { display: block; width: 100%; }</style> <meta name="description" content="Search for, view, and comment on planning applications"/> <meta name="keywords" content="planning, application, comment, public access"/> <meta name="geo.placename" content="Newcastle upon Tyne"/> <link rel="canonical" href="https://www.newcastle.gov.uk/services/planning-building-and-development/search-view-and-comment-planning-applications"/> <link rel="icon" href="favicon.ico"/> <link rel="icon" sizes="16x16" href="/favicon-16x16.png"/> <link rel="icon" sizes="32x32" href="/favicon-32x32.png"/> <link rel="icon" sizes="96x96" href="/favicon-96x96.png"/> <link rel="icon" sizes="192x192" href="/android-chrome-192x192.png"/> <link rel="apple-touch-icon" href="/apple-touch-icon-60x60.png"/> <link rel="apple-touch-icon" sizes="72x72" href="/android-chrome-72x72.png"/> <link rel="apple-touch-icon" sizes="76x76" href="/apple-touch-icon-76x7โฆ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 states what it is in machine-readable form, and where it carries exact facts it states those too. 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT43 | fail | 1 fault in this page's construction change the structure anything reading it sees, so what is read is not quite the page that was published | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page's underlying construction holds together, or contains faults that change how it is read. What good looks like The page is built soundly enough that anything reading it sees the structure its author intended. Why it matters Anything reading the page has to take it apart before it can judge anything on it. Faults in construction can move where a section appears to end, place a heading inside a paragraph, or lose part of the page altogether. When that happens, what is read is not quite the page that was published, and neither is the answer built from it. The damage is invisible on screen, because a browser repairs quietly what a plain reader does not. What we found on this page 1 fault in this page's construction change the structure anything reading it sees, so what is read is not quite the page that was published The evidence, taken from the page as served Faults in the page's construction that change how it reads
Found while taking the page apart exactly as a reader would.
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 is built soundly enough that anything reading it sees the structure its author intended. 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: โhereโ; 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 Identical links on one page lead to different places, so which one gets followed is a coin toss. A reader or system lands on the wrong page while believing it chose correctly. 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: โhereโ; 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.newcastle.gov.uk/services/planning-building-and-development/guide-planning-applications/planning-applications-guide">here</a> <a href="https://www.newcastle.gov.uk/sites/default/files/2018-12/planning_officerdelegation.pdf">here</a> <a href="/services/planning-building-and-development/guide-planning-applications/planning-applications-guide">here</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 The page's headings begin at its top level, rather than starting part way down. What good looks like The page's headings begin with its top-level heading. Levels skipped further down are weighed under heading hierarchy, and a page with no top-level heading at all under the missing main heading, so each fault is marked once. Why it matters The page's structure starts part way down, below a top level that never opens it. Sections then sit under nothing, and anything filing content by structure starts in the wrong place. 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 (the starting level is marked)
H2 Main navigation level jumped H2 Title H4 Have your say H1 Search for, view, and comment on planning applications H2 Search for, view, and comment on planning applications H3 Public Access allows you to look at details of applications, make comments, and H3 A guide to using this page H3 How do I comment on a planning application? H3 How long do I have to comment? H3 Will my comments be made public? H3 Can I view planning applications in person or comment in writing? H3 What will be considered? H3 What won't be considered? H3 What is the decision making process? H3 Will I be told about the decision? H3 What is the publicity required for applications? H3 How can I find out about high-profile major applications in the city? H3 Appeals Register H3 Customer feedback H3 Important notes H3 Further points to note H2 Related Pages H4 Need more information? H3 Most popular pages H3 We're on social media
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 begin with its top-level heading. 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| DS28 | fail | one link to sources on other sites is AI-blocked: the page opens for a person in a browser, but the site refuses callers that are not a person browsing, so an AI never receives it. 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 cites as evidence cannot be reached by an AI, whether dead, the address answering that the page is not there or blocked to automated callers, so its claims rest on material an AI cannot check. In a regulated business that is the difference between an evidenced statement and a bare assertion. What we found on this page one link to sources on other sites is AI-blocked: the page opens for a person in a browser, but the site refuses callers that are not a person browsing, so an AI never receives it. 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 fails here fails in one of two ways, and the report names them apart. A DEAD link answers, when the page is asked for in full, that the page is not there. An AI-BLOCKED link points at a page that is still published and opens for a person in a browser, but the destination refuses callers that are not a person browsing, so an AI never receives it. Opening such a link by hand proves only the human route; this assessment reflects the AI position, and from the AI position both classes land in the same place: the material this page offers as its support does not come back when it is 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. An AI-blocked 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. An AI-block on 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Warnings · 7 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT06 | warning | title length 79 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 that is too short or too long is liable to be rewritten elsewhere, and control of the page's name goes with it. What we found on this page title length 79 chars The evidence, taken from the page as served The page title, as served
<title>Search for, view, and comment on planning applications | Newcastle City Council</title> | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT40 | warning | the page offers no short summary for the services that show a preview of it, so each one composes its own from whatever it finds first on the page | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The short title, description and image the page offers to services that show a preview of it, and whether they match the page. What good looks like The page offers a summary for preview, and the summary is true to the page. Why it matters This summary travels further than the page does. It is what appears when the address is shared, and several services read it in preference to the page itself because it is short and already written for the purpose. Where it is absent, those services compose their own from whatever they find first, which is often navigation. Where it is present but out of step, the organisation is described to a wide audience by a sentence it wrote once and forgot. What we found on this page the page offers no short summary for the services that show a preview of it, so each one composes its own from whatever it finds first on the page The evidence, taken from the page as served The summary this page offers for preview
Read from the page as served.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT41 | warning | the page does not show where it sits in the site, so anything reading it on its own has nothing to say what it belongs to | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The trail showing the path from the front page to this one, and whether the machine-readable version of that trail says the same. What good looks like The page shows its place in the site, and says the same thing to a machine. Why it matters A page read on its own gives no sense of what it belongs to. The trail supplies it: one product within a range, one policy within a set. A reader deciding whether a page answers a question uses that to judge whether it has the right one, and how to describe it when it quotes it. Where the shown trail and the machine-readable one disagree, the page is placed in two positions at once and neither can be relied on. What we found on this page the page does not show where it sits in the site, so anything reading it on its own has nothing to say what it belongs to The evidence, taken from the page as served The path this page gives to itself
Read from the page as served: the trail shown to a reader, and the trail stated in a form a machine can take as given.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT04 | warning | the page shows the year 2020 in its text, but nothing on the page states it as the date of the content | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The page carries a date, ideally written into the markup rather than sitting only in the text. What good looks like The page carries a date, ideally written into the markup rather than sitting only in the text. Why it matters An undated page gives nothing to weigh its age against, so old and new material are treated alike. What we found on this page the page shows the year 2020 in its text, but nothing on the page states it as the date of the content The evidence, taken from the page as served The head of this page, as served
The head of the page was read for a tag stating the date of the content. The year shown above was found in the page's own text. <head> <meta charset="utf-8"/> <style>/* @see https://github.com/aFarkas/lazysizes#broken-image-symbol */.js img.b-lazy:not([src]) { visibility: hidden; }/* @see https://github.com/aFarkas/lazysizes#automatically-setting-the-sizes-attribute */.js img.lazyloaded[data-sizes=auto] { display: block; width: 100%; }</style> <meta name="description" content="Search for, view, and comment on planning applications"/> <meta name="keywords" content="planning, application, comment, public access"/> <meta name="geo.placename" content="Newcastle upon Tyne"/> <link rel="canonical" href="https://www.newcastle.gov.uk/services/planning-building-and-development/search-view-and-comment-planning-applications"/> <link rel="icon" href="favicon.ico"/> <link rel="icon" sizes="16x16" href="/favicon-16x16.png"/> <link rel="icon" sizes="32x32" href="/favicon-32x32.png"/> <link rel="icon" sizes="96x96" href="/favicon-96x96.png"/> <link rel="icon" sizes="192x192" href="/android-chrome-192x192.png"/> <link rel="apple-touch-icon" href="/apple-touch-icon-60x60.png"/> <link rel="apple-touch-icon" sizes="72x72" href="/android-chrome-72x72.png"/> <link rel="apple-touch-icon" sizes="76x76" href="/apple-touch-icon-76x7โฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT35 | warning | the copyright line at the foot of this page states 1988, 38 years behind the year this assessment ran, which reads as a page left unattended and is the usual sign of a template copied from elsewhere | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The copyright line at the foot of the page, and the year it states. What good looks like The copyright line states the current year. Why it matters An old copyright year reads as a site nobody is looking after, and it dates the page for anything that relies on dates. Content can be treated as years older than it really is. What we found on this page the copyright line at the foot of this page states 1988, 38 years behind the year this assessment ran, which reads as a page left unattended and is the usual sign of a template copied from elsewhere The evidence, taken from the page as served The copyright line as served, and the year it claims
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS09 | warning | link wording that does not say where it leads: โhereโ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Link wording that names no destination, phrases such as click here, read more and details, and one such wording repeated across many links. What good looks like Link wording names its destination, rather than saying click here or read more. Why it matters The destination is stated nowhere on the link itself, so the choice rests entirely on the text around it. Where one wording such as click here covers many links, they read as one link repeated and nothing in their names tells them apart. What we found on this page link wording that does not say where it leads: โhereโ The evidence, taken from the page as served The links whose text names no destination, as served
<a href="https://www.newcastle.gov.uk/services/planning-building-and-development/guide-planning-applications/planning-applications-guide">here</a> <a href="https://www.newcastle.gov.uk/sites/default/files/2018-12/planning_officerdelegation.pdf">here</a> <a href="/services/planning-building-and-development/guide-planning-applications/planning-applications-guide">here</a> | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
▸https://newcastle.gov.uk/contact-us 31.5% Very likely 16 out of 85
The page https://newcastle.gov.uk/contact-us
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Fails · 5 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 AI systems are being turned away before they reach the site, and because the barrier sits outside the organisation's own systems, nobody inside can see it happening. Those systems carry on answering questions about the organisation, from other people's material rather than its own, so the conversation about it goes on without it and nobody has decided that. 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.newcastle.gov.uk · resolves to 194.61.173.205
Address trailwww.newcastle.gov.uk
Checked2026-09-17 16:33 UTC · request sent from 54.171.52.206 (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 heading 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)
H2 Main navigation H2 Title H4 Have your say level jumped H1 Contact us H2 Contact us H2 Contact us online H3 Complaints & Compliments H2 Contact us by phone H3 24 hour telephone line H1 Relay UK H2 Contact us in writing H2 Related Pages H3 Most popular pages H3 We're on social media
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 | fail | this page carries opening hours and a telephone number, and states none of it in a form a machine can take as given, so those facts have to be worked out from the wording around them | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page states what it is, and the exact facts it carries, in a form a machine can take as given rather than work out from the wording. What good looks like The page states what it is in machine-readable form, and where it carries exact facts it states those too. A page of exact facts stating none of them is a fail; a narrative page without a block is a warning. Why it matters Where a page carries exact facts, an address, opening hours, a price, a date, leaving them only in prose means they are worked out rather than read, and that is where a wrong branch or an old price comes from. What we found on this page this page carries opening hours and a telephone number, and states none of it in a form a machine can take as given, so those facts have to be worked out from the wording around them The evidence, taken from the page as served The head of this page, as served
The page was read for a short block of machine-readable detail saying what it is. The page's own words carry opening hours and a telephone number, which is why this weighs as it does. <head> <meta charset="utf-8"/> <style>/* @see https://github.com/aFarkas/lazysizes#broken-image-symbol */.js img.b-lazy:not([src]) { visibility: hidden; }/* @see https://github.com/aFarkas/lazysizes#automatically-setting-the-sizes-attribute */.js img.lazyloaded[data-sizes=auto] { display: block; width: 100%; }</style> <meta name="description" content="The website of Newcastle City Council"/> <meta name="geo.placename" content="Newcastle upon Tyne"/> <link rel="canonical" href="https://newcastle.gov.uk/contact-us"/> <link rel="icon" href="favicon.ico"/> <link rel="icon" sizes="16x16" href="/favicon-16x16.png"/> <link rel="icon" sizes="32x32" href="/favicon-32x32.png"/> <link rel="icon" sizes="96x96" href="/favicon-96x96.png"/> <link rel="icon" sizes="192x192" href="/android-chrome-192x192.png"/> <link rel="apple-touch-icon" href="/apple-touch-icon-60x60.png"/> <link rel="apple-touch-icon" sizes="72x72" href="/android-chrome-72x72.png"/> <link rel="apple-touch-icon" sizes="76x76" href="/apple-touch-icon-76x76.png"/> <link rel="apple-touch-icon" sizes="114x114" href="/apple-touch-icon-114x114.png"/> <link rel="apple-touch-icon" sizes="120x120" href="/apple-touch-icon-120x120.png"/> <lโฆ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 states what it is in machine-readable form, and where it carries exact facts it states those too. 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT43 | fail | 1 fault in this page's construction change the structure anything reading it sees, so what is read is not quite the page that was published | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page's underlying construction holds together, or contains faults that change how it is read. What good looks like The page is built soundly enough that anything reading it sees the structure its author intended. Why it matters Anything reading the page has to take it apart before it can judge anything on it. Faults in construction can move where a section appears to end, place a heading inside a paragraph, or lose part of the page altogether. When that happens, what is read is not quite the page that was published, and neither is the answer built from it. The damage is invisible on screen, because a browser repairs quietly what a plain reader does not. What we found on this page 1 fault in this page's construction change the structure anything reading it sees, so what is read is not quite the page that was published The evidence, taken from the page as served Faults in the page's construction that change how it reads
Found while taking the page apart exactly as a reader would.
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 is built soundly enough that anything reading it sees the structure its author intended. 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 The page's headings begin at its top level, rather than starting part way down. What good looks like The page's headings begin with its top-level heading. Levels skipped further down are weighed under heading hierarchy, and a page with no top-level heading at all under the missing main heading, so each fault is marked once. Why it matters The page's structure starts part way down, below a top level that never opens it. Sections then sit under nothing, and anything filing content by structure starts in the wrong place. 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 (the starting level is marked)
H2 Main navigation level jumped H2 Title H4 Have your say H1 Contact us H2 Contact us H2 Contact us online H3 Complaints & Compliments H2 Contact us by phone H3 24 hour telephone line H1 Relay UK H2 Contact us in writing H2 Related Pages H3 Most popular pages H3 We're on social media
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 begin with its top-level heading. 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Warnings · 11 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT32 | warning | the page's meta description, the short summary it offers about itself, runs to 37 characters, too short to say what the page is about; a usable summary runs from 50 to 170 characters | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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 the page's meta description, the short summary it offers about itself, runs to 37 characters, too short to say what the page is about; a usable summary runs from 50 to 170 characters The evidence, taken from the page as served The page's description, as served
<meta name="description" content="The website of Newcastle City Council"/> | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT11 | warning | 2 H1s (informational; not an error per Google) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check More than one main heading on the page, recorded for information rather than marked as a fault. What good looks like The page carries one main heading rather than several. Why it matters Two main headings make a page state its subject twice, which can blur which one defines it. On its own this rarely changes what gets quoted, so it is noted for the record rather than marked as a fault. What we found on this page 2 H1s (informational; not an error per Google) The evidence, taken from the page as served The multiple H1 headings, as served
<h1> Contact us </h1> <h1 class="page-title" style="-webkit-text-stroke-width:0px;background-color:rgb(255, 255, 255);box-sizing:border-box;color:rgb(43, 43, 43);font-family:Lato, sans-serif;font-size:2.188em;font-style:normal;font-variant-caps:normal;font-variant-ligatures:normal;letter-spacing:normal;line-height:1.2;margin:0px 0px 0.6em;oโฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT40 | warning | the page offers no short summary for the services that show a preview of it, so each one composes its own from whatever it finds first on the page | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The short title, description and image the page offers to services that show a preview of it, and whether they match the page. What good looks like The page offers a summary for preview, and the summary is true to the page. Why it matters This summary travels further than the page does. It is what appears when the address is shared, and several services read it in preference to the page itself because it is short and already written for the purpose. Where it is absent, those services compose their own from whatever they find first, which is often navigation. Where it is present but out of step, the organisation is described to a wide audience by a sentence it wrote once and forgot. What we found on this page the page offers no short summary for the services that show a preview of it, so each one composes its own from whatever it finds first on the page The evidence, taken from the page as served The summary this page offers for preview
Read from the page as served.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT41 | warning | the page does not show where it sits in the site, so anything reading it on its own has nothing to say what it belongs to | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The trail showing the path from the front page to this one, and whether the machine-readable version of that trail says the same. What good looks like The page shows its place in the site, and says the same thing to a machine. Why it matters A page read on its own gives no sense of what it belongs to. The trail supplies it: one product within a range, one policy within a set. A reader deciding whether a page answers a question uses that to judge whether it has the right one, and how to describe it when it quotes it. Where the shown trail and the machine-readable one disagree, the page is placed in two positions at once and neither can be relied on. What we found on this page the page does not show where it sits in the site, so anything reading it on its own has nothing to say what it belongs to The evidence, taken from the page as served The path this page gives to itself
Read from the page as served: the trail shown to a reader, and the trail stated in a form a machine can take as given.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT04 | warning | the page carries no date, so there is nothing on it saying how current its content is | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The page carries a date, ideally written into the markup rather than sitting only in the text. What good looks like The page carries a date, ideally written into the markup rather than sitting only in the text. Why it matters An undated page gives nothing to weigh its age against, so old and new material are treated alike. What we found on this page the page carries no date, so there is nothing on it saying how current its content is The evidence, taken from the page as served The head of this page, as served
The head of the page and the page's own text were read for a date. <head> <meta charset="utf-8"/> <style>/* @see https://github.com/aFarkas/lazysizes#broken-image-symbol */.js img.b-lazy:not([src]) { visibility: hidden; }/* @see https://github.com/aFarkas/lazysizes#automatically-setting-the-sizes-attribute */.js img.lazyloaded[data-sizes=auto] { display: block; width: 100%; }</style> <meta name="description" content="The website of Newcastle City Council"/> <meta name="geo.placename" content="Newcastle upon Tyne"/> <link rel="canonical" href="https://newcastle.gov.uk/contact-us"/> <link rel="icon" href="favicon.ico"/> <link rel="icon" sizes="16x16" href="/favicon-16x16.png"/> <link rel="icon" sizes="32x32" href="/favicon-32x32.png"/> <link rel="icon" sizes="96x96" href="/favicon-96x96.png"/> <link rel="icon" sizes="192x192" href="/android-chrome-192x192.png"/> <link rel="apple-touch-icon" href="/apple-touch-icon-60x60.png"/> <link rel="apple-touch-icon" sizes="72x72" href="/android-chrome-72x72.png"/> <link rel="apple-touch-icon" sizes="76x76" href="/apple-touch-icon-76x76.png"/> <link rel="apple-touch-icon" sizes="114x114" href="/apple-touch-icon-114x114.png"/> <link rel="apple-touch-icon" sizes="120x120" href="/apple-touch-icon-120x120.png"/> <lโฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT35 | warning | the copyright line at the foot of this page carries no year, so there is nothing on the page as served to date it by | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The copyright line at the foot of the page, and the year it states. What good looks like The copyright line states the current year. Why it matters An old copyright year reads as a site nobody is looking after, and it dates the page for anything that relies on dates. Content can be treated as years older than it really is. What we found on this page the copyright line at the foot of this page carries no year, so there is nothing on the page as served to date it by The evidence, taken from the page as served The copyright line on this page, as served
This is the copyright line as the page serves it. It was read for a year, and carries none. stagram Find out how we use social media Press Office and News ReciteMe and Accessibility ยฉNewcastle City Council Privacy Notice Terms and conditions Contact Us Covid-19 support Listen and translate {"path":{"baseUrl":"\/","pathPrefix":"","c | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS09 | warning | link wording that does not say where it leads: โhereโ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Link wording that names no destination, phrases such as click here, read more and details, and one such wording repeated across many links. What good looks like Link wording names its destination, rather than saying click here or read more. Why it matters The destination is stated nowhere on the link itself, so the choice rests entirely on the text around it. Where one wording such as click here covers many links, they read as one link repeated and nothing in their names tells them apart. What we found on this page link wording that does not say where it leads: โhereโ The evidence, taken from the page as served The links whose text names no destination, as served
<a href="https://new.newcastle.gov.uk/complaints-compliments">here</a> | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR03 | warning | 12% of the words a person sees are missing from the page as first delivered (4577 characters delivered, 5456 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 looks complete to a person, but its content is built by scripts that many AI systems never run, so they receive it near-empty. The organisation's material is missing from their answers. What we found on this page 12% of the words a person sees are missing from the page as first delivered (4577 characters delivered, 5456 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 4577 characters of text; after JavaScript runs the page carries 5456. 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) Contact us | Newcastle City Council Skip to main content Listen and translate Make a payment Jobs and careers My Portal Contact us Listen and translate Main navigation Services Business Our City Get Involved Local Government News Cost of living support โ โ โ Title Have your say C…
Words present only after JavaScript runs
acceptanalyticalchosenclosecollectingcontrolcookiecoredecliningenableessentialexperienceexternalfeedsfunctionalityhelpiconimproveionsitemsnecessaryotherspartypreventrememberreportingsettingsshortlistsitethatthirdtoolusageusesviewing
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR11 | warning | 12% of the words a person sees are missing from the page as first delivered: the page arrives carrying 84% of the text it ends up showing | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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: the page arrives carrying 84% of the text it ends up showing 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.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT27 | warning | the content missing from the raw extraction is largely present inside script tags (94% of sampled missing terms): the page ships its content as script data rather than as document text | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check On the sampled pages, how much text is shipped inside scripts as data rather than as page text. What good looks like The page's text is present as page text, not shipped inside scripts as data. Why it matters Part of this page's content is packed inside its code rather than written on the page, so many reading systems never see it. What they miss is simply absent from their answers. What we found on this page the content missing from the raw extraction is largely present inside script tags (94% of sampled missing terms): the page ships its content as script data rather than as document text The evidence, taken from the page as served Where the missing words were found
The words a person sees but the delivered page did not carry were looked for inside the page's script blocks.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
▸https://newcastle.gov.uk/business 30.4% Very likely 11 out of 67
The page https://newcastle.gov.uk/business
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Fails · 7 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 AI systems are being turned away before they reach the site, and because the barrier sits outside the organisation's own systems, nobody inside can see it happening. Those systems carry on answering questions about the organisation, from other people's material rather than its own, so the conversation about it goes on without it and nobody has decided that. 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.newcastle.gov.uk · resolves to 194.61.173.205
Address trailwww.newcastle.gov.uk
Checked2026-09-17 16:33 UTC · request sent from 54.171.52.206 (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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MX01 | fail | the site took 383ms to start answering, past the point where an automated reader gives up and takes its answer from elsewhere | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check How quickly the page starts to answer when it is asked for. What good looks like The page starts answering within 250ms. Between 250 and 345ms is a warning; beyond 345ms is a fail, that being the point at which an automated reader gives up. Why it matters A page that is slow to answer is left behind: the reader gives up and takes its answer from someone else's material, so your own words play no part in it. What we found on this page the site took 383ms to start answering, past the point where an automated reader gives up and takes its answer from elsewhere The evidence, taken from the page as served How long this page took to start answering
Timed from the request leaving our checker to the first part of the answer coming back, on the page as served, so distance from the site plays its part. 345ms is the point beyond which an automated reader gives up.
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 starts answering within 250ms. 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 heading 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)
H2 Main navigation H1 A place to grow your business and prosper H2 Invest in Newcastle H2 Find a commercial property H3 Growing the digital sector H4 Our businesses succeed with strong leadership and great partnership within the c H3 Looking for something else? H3 Related News H6 Employment level jumped H6 (no text) H6 Finance H3 Most popular pages H3 We're on social media
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 | fail | this page carries dates, and states none of it in a form a machine can take as given, so those facts have to be worked out from the wording around them | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page states what it is, and the exact facts it carries, in a form a machine can take as given rather than work out from the wording. What good looks like The page states what it is in machine-readable form, and where it carries exact facts it states those too. A page of exact facts stating none of them is a fail; a narrative page without a block is a warning. Why it matters Where a page carries exact facts, an address, opening hours, a price, a date, leaving them only in prose means they are worked out rather than read, and that is where a wrong branch or an old price comes from. What we found on this page this page carries dates, and states none of it in a form a machine can take as given, so those facts have to be worked out from the wording around them The evidence, taken from the page as served The head of this page, as served
The page was read for a short block of machine-readable detail saying what it is. The page's own words carry dates, which is why this weighs as it does. <head> <meta charset="utf-8"/> <style>/* @see https://github.com/aFarkas/lazysizes#broken-image-symbol */.js img.b-lazy:not([src]) { visibility: hidden; }/* @see https://github.com/aFarkas/lazysizes#automatically-setting-the-sizes-attribute */.js img.lazyloaded[data-sizes=auto] { display: block; width: 100%; }</style> <meta name="description" content="The website of Newcastle City Council"/> <meta name="geo.placename" content="Newcastle upon Tyne"/> <link rel="canonical" href="https://newcastle.gov.uk/business"/> <link rel="icon" href="favicon.ico"/> <link rel="icon" sizes="16x16" href="/favicon-16x16.png"/> <link rel="icon" sizes="32x32" href="/favicon-32x32.png"/> <link rel="icon" sizes="96x96" href="/favicon-96x96.png"/> <link rel="icon" sizes="192x192" href="/android-chrome-192x192.png"/> <link rel="apple-touch-icon" href="/apple-touch-icon-60x60.png"/> <link rel="apple-touch-icon" sizes="72x72" href="/android-chrome-72x72.png"/> <link rel="apple-touch-icon" sizes="76x76" href="/apple-touch-icon-76x76.png"/> <link rel="apple-touch-icon" sizes="114x114" href="/apple-touch-icon-114x114.png"/> <link rel="apple-touch-icon" sizes="120x120" href="/apple-touch-icon-120x120.png"/> <linโฆ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 states what it is in machine-readable form, and where it carries exact facts it states those too. 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT43 | fail | 1 fault in this page's construction change the structure anything reading it sees, so what is read is not quite the page that was published | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page's underlying construction holds together, or contains faults that change how it is read. What good looks like The page is built soundly enough that anything reading it sees the structure its author intended. Why it matters Anything reading the page has to take it apart before it can judge anything on it. Faults in construction can move where a section appears to end, place a heading inside a paragraph, or lose part of the page altogether. When that happens, what is read is not quite the page that was published, and neither is the answer built from it. The damage is invisible on screen, because a browser repairs quietly what a plain reader does not. What we found on this page 1 fault in this page's construction change the structure anything reading it sees, so what is read is not quite the page that was published The evidence, taken from the page as served Faults in the page's construction that change how it reads
Found while taking the page apart exactly as a reader would.
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 is built soundly enough that anything reading it sees the structure its author intended. 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: โfind out moreโ, โtheme debug theme hook: 'image_style' begin output from 'theโ; 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 Identical links on one page lead to different places, so which one gets followed is a coin toss. A reader or system lands on the wrong page while believing it chose correctly. 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: โfind out moreโ, โtheme debug theme hook: 'image_style' begin output from 'theโ; 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="/services/business-and-commerce/business-commerce/business-support-newcastle" aria-label="Grow your business">Find out more</a> <a href="/services/business-rates/business-rates-frequently-asked-questions" aria-label="Business rates FAQ">Find out more</a> <a href="/citylife-news/employment/winners-announced-newcastles-small-business-saturday-awards" hreflang="en"> <!-- THEME DEBUG --> <!-- THEME HOOK: 'image_style' --> <!-- BEGIN OUTPUT from 'themes/contrib/bootstrap5/templates/field/image-style.html.twig' --> <!-- THEME DEBUG --> <!-- THEME HOOK: 'image' --> <!-- BEGINโฆ <a href="/citylife-news/employment/newcastles-best-small-business-peoples-choice-awards-2022" hreflang="en"> <!-- THEME DEBUG --> <!-- THEME HOOK: 'image_style' --> <!-- BEGIN OUTPUT from 'themes/contrib/bootstrap5/templates/field/image-style.html.twig' --> <!-- THEME DEBUG --> <!-- THEME HOOK: 'image' --> <!-- BEGIN Oโฆ <a href="/citylife-news/newcastle-city-council-celebrates-fair-tax-week-2022" hreflang="en"> <!-- THEME DEBUG --> <!-- THEME HOOK: 'image_style' --> <!-- BEGIN OUTPUT from 'themes/contrib/bootstrap5/templates/field/image-style.html.twig' --> <!-- THEME DEBUG --> <!-- THEME HOOK: 'image' --> <!-- BEGIN OUTPUT from 'themโฆ 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 The page's headings begin at its top level, rather than starting part way down. What good looks like The page's headings begin with its top-level heading. Levels skipped further down are weighed under heading hierarchy, and a page with no top-level heading at all under the missing main heading, so each fault is marked once. Why it matters The page's structure starts part way down, below a top level that never opens it. Sections then sit under nothing, and anything filing content by structure starts in the wrong place. 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 (the starting level is marked)
H2 Main navigation level jumped H1 A place to grow your business and prosper H2 Invest in Newcastle H2 Find a commercial property H3 Growing the digital sector H4 Our businesses succeed with strong leadership and great partnership within the c H3 Looking for something else? H3 Related News H6 Employment H6 (no text) H6 Finance H3 Most popular pages H3 We're on social media
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 begin with its top-level heading. 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Warnings · 4 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT32 | warning | the page's meta description, the short summary it offers about itself, runs to 37 characters, too short to say what the page is about; a usable summary runs from 50 to 170 characters | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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 the page's meta description, the short summary it offers about itself, runs to 37 characters, too short to say what the page is about; a usable summary runs from 50 to 170 characters The evidence, taken from the page as served The page's description, as served
<meta name="description" content="The website of Newcastle City Council"/> | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT40 | warning | the page offers no short summary for the services that show a preview of it, so each one composes its own from whatever it finds first on the page | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The short title, description and image the page offers to services that show a preview of it, and whether they match the page. What good looks like The page offers a summary for preview, and the summary is true to the page. Why it matters This summary travels further than the page does. It is what appears when the address is shared, and several services read it in preference to the page itself because it is short and already written for the purpose. Where it is absent, those services compose their own from whatever they find first, which is often navigation. Where it is present but out of step, the organisation is described to a wide audience by a sentence it wrote once and forgot. What we found on this page the page offers no short summary for the services that show a preview of it, so each one composes its own from whatever it finds first on the page The evidence, taken from the page as served The summary this page offers for preview
Read from the page as served.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT41 | warning | the page does not show where it sits in the site, so anything reading it on its own has nothing to say what it belongs to | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The trail showing the path from the front page to this one, and whether the machine-readable version of that trail says the same. What good looks like The page shows its place in the site, and says the same thing to a machine. Why it matters A page read on its own gives no sense of what it belongs to. The trail supplies it: one product within a range, one policy within a set. A reader deciding whether a page answers a question uses that to judge whether it has the right one, and how to describe it when it quotes it. Where the shown trail and the machine-readable one disagree, the page is placed in two positions at once and neither can be relied on. What we found on this page the page does not show where it sits in the site, so anything reading it on its own has nothing to say what it belongs to The evidence, taken from the page as served The path this page gives to itself
Read from the page as served: the trail shown to a reader, and the trail stated in a form a machine can take as given.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT35 | warning | the copyright line at the foot of this page carries no year, so there is nothing on the page as served to date it by | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The copyright line at the foot of the page, and the year it states. What good looks like The copyright line states the current year. Why it matters An old copyright year reads as a site nobody is looking after, and it dates the page for anything that relies on dates. Content can be treated as years older than it really is. What we found on this page the copyright line at the foot of this page carries no year, so there is nothing on the page as served to date it by The evidence, taken from the page as served The copyright line on this page, as served
This is the copyright line as the page serves it. It was read for a year, and carries none. stagram Find out how we use social media Press Office and News ReciteMe and Accessibility ยฉNewcastle City Council Privacy Notice Terms and conditions Contact Us Covid-19 support Listen and translate {"path":{"baseUrl":"\/","pathPrefix":"","c | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
▸https://newcastle.gov.uk/cost-living-support 30.4% Very likely 11 out of 67
The page https://newcastle.gov.uk/cost-living-support
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Fails · 6 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 AI systems are being turned away before they reach the site, and because the barrier sits outside the organisation's own systems, nobody inside can see it happening. Those systems carry on answering questions about the organisation, from other people's material rather than its own, so the conversation about it goes on without it and nobody has decided that. 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.newcastle.gov.uk · resolves to 194.61.173.205
Address trailwww.newcastle.gov.uk
Checked2026-09-17 16:33 UTC · request sent from 54.171.52.206 (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 heading 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)
H2 Main navigation H4 Debt and money advice level jumped H4 Energy advice H4 Council tax discounts and exemptions H4 Check what benefits you can receive H4 Housing support H4 Help with school and learning costs H4 Free childcare H4 Wellbeing Hubs H4 Managing on a low income H4 Emergency funds and support H4 Help with food (foodbanks and cheap food) H4 Children and Families Newcastle H4 Mental health support H4 Household Support Fund H3 Most popular pages H3 We're on social media
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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT10 | fail | the page carries no main heading, so nothing on it states what the page is about | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The page carries a main heading (the H1), its own statement of what the page is about. What good looks like The page carries a single main heading stating what it is about. Why it matters The page never states its own subject, so anything reading it has to guess what it is about. Guessed subjects are how content gets filed, and quoted, under the wrong topic. What we found on this page the page carries no main heading, so nothing on it states what the page is about The evidence, taken from the page as served The headings on this page, as served
The page was read for a top-level heading. These are the headings it does carry. <h2 class="sr-only" id="block-nccb5-main-navigation-menu">Main navigation</h2> <h4 class="climate-ch-link">Debt and money advice</h4> <h4 class="climate-ch-link">Energy advice</h4> <h4 class="climate-ch-link">Council tax discounts and exemptions</h4> <h4 class="climate-ch-link">Check what benefits you can receive</h4> <h4 class="climate-ch-link">Housing support</h4> <h4 class="climate-ch-link">Help with school and learning costs</h4> <h4 class="climate-ch-link">Free childcare</h4> <h4 class="climate-ch-link">Wellbeing Hubs</h4> <h4 class="climate-ch-link">Managing on a low income</h4> …and 7 more like it. 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 carries a single main heading stating what it is about. 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 | fail | this page carries dates, and states none of it in a form a machine can take as given, so those facts have to be worked out from the wording around them | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page states what it is, and the exact facts it carries, in a form a machine can take as given rather than work out from the wording. What good looks like The page states what it is in machine-readable form, and where it carries exact facts it states those too. A page of exact facts stating none of them is a fail; a narrative page without a block is a warning. Why it matters Where a page carries exact facts, an address, opening hours, a price, a date, leaving them only in prose means they are worked out rather than read, and that is where a wrong branch or an old price comes from. What we found on this page this page carries dates, and states none of it in a form a machine can take as given, so those facts have to be worked out from the wording around them The evidence, taken from the page as served The head of this page, as served
The page was read for a short block of machine-readable detail saying what it is. The page's own words carry dates, which is why this weighs as it does. <head> <meta charset="utf-8"/> <style>/* @see https://github.com/aFarkas/lazysizes#broken-image-symbol */.js img.b-lazy:not([src]) { visibility: hidden; }/* @see https://github.com/aFarkas/lazysizes#automatically-setting-the-sizes-attribute */.js img.lazyloaded[data-sizes=auto] { display: block; width: 100%; }</style> <meta name="description" content="The website of Newcastle City Council"/> <meta name="geo.placename" content="Newcastle upon Tyne"/> <link rel="canonical" href="https://newcastle.gov.uk/cost-living-support"/> <link rel="icon" href="favicon.ico"/> <link rel="icon" sizes="16x16" href="/favicon-16x16.png"/> <link rel="icon" sizes="32x32" href="/favicon-32x32.png"/> <link rel="icon" sizes="96x96" href="/favicon-96x96.png"/> <link rel="icon" sizes="192x192" href="/android-chrome-192x192.png"/> <link rel="apple-touch-icon" href="/apple-touch-icon-60x60.png"/> <link rel="apple-touch-icon" sizes="72x72" href="/android-chrome-72x72.png"/> <link rel="apple-touch-icon" sizes="76x76" href="/apple-touch-icon-76x76.png"/> <link rel="apple-touch-icon" sizes="114x114" href="/apple-touch-icon-114x114.png"/> <link rel="apple-touch-icon" sizes="120x120" href="/apple-touch-icon-120x120.โฆ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 states what it is in machine-readable form, and where it carries exact facts it states those too. 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT43 | fail | 1 fault in this page's construction change the structure anything reading it sees, so what is read is not quite the page that was published | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page's underlying construction holds together, or contains faults that change how it is read. What good looks like The page is built soundly enough that anything reading it sees the structure its author intended. Why it matters Anything reading the page has to take it apart before it can judge anything on it. Faults in construction can move where a section appears to end, place a heading inside a paragraph, or lose part of the page altogether. When that happens, what is read is not quite the page that was published, and neither is the answer built from it. The damage is invisible on screen, because a browser repairs quietly what a plain reader does not. What we found on this page 1 fault in this page's construction change the structure anything reading it sees, so what is read is not quite the page that was published The evidence, taken from the page as served Faults in the page's construction that change how it reads
Found while taking the page apart exactly as a reader would.
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 is built soundly enough that anything reading it sees the structure its author intended. 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: โtheme debug theme hook: 'field' file name suggestions: โช๏ธโ; 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 Identical links on one page lead to different places, so which one gets followed is a coin toss. A reader or system lands on the wrong page while believing it chose correctly. 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: โtheme debug theme hook: 'field' file name suggestions:
โช๏ธโ; 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="/services/welfare-and-benefits/debt-and-money-advice" class="field-group-link"> <!-- THEME DEBUG --> <!-- THEME HOOK: 'field' --> <!-- FILE NAME SUGGESTIONS: โช๏ธ field--expert--paragraph--field-cc-link-title--climate-change-link--default.html.twig โช๏ธ field--expert--paragraph--field-cc-link-title--climate-changeโฆ <a href="/services/environment-and-waste/energy-advice" class="field-group-link"> <!-- THEME DEBUG --> <!-- THEME HOOK: 'field' --> <!-- FILE NAME SUGGESTIONS: โช๏ธ field--expert--paragraph--field-cc-link-title--climate-change-link--default.html.twig โช๏ธ field--expert--paragraph--field-cc-link-title--climate-change-link.hโฆ <a href="https://new.newcastle.gov.uk/council-tax/council-tax-discounts-exemptions" class="field-group-link"> <!-- THEME DEBUG --> <!-- THEME HOOK: 'field' --> <!-- FILE NAME SUGGESTIONS: โช๏ธ field--expert--paragraph--field-cc-link-title--climate-change-link--default.html.twig โช๏ธ field--expert--paragraph--field-cc-link-โฆ <a href="/services/welfare-and-benefits/check-what-benefits-you-can-receive" class="field-group-link"> <!-- THEME DEBUG --> <!-- THEME HOOK: 'field' --> <!-- FILE NAME SUGGESTIONS: โช๏ธ field--expert--paragraph--field-cc-link-title--climate-change-link--default.html.twig โช๏ธ field--expert--paragraph--field-cc-link-title--โฆ <a href="/services/housing/housing-advice-and-homelessness/what-do-if-you-need-housing-advice-or-are-homeless" class="field-group-link"> <!-- THEME DEBUG --> <!-- THEME HOOK: 'field' --> <!-- FILE NAME SUGGESTIONS: โช๏ธ field--expert--paragraph--field-cc-link-title--climate-change-link--default.html.twig โช๏ธ field--expertโฆ <a href="/services/schools-learning-and-childcare/help-school-and-learning-costs" class="field-group-link"> <!-- THEME DEBUG --> <!-- THEME HOOK: 'field' --> <!-- FILE NAME SUGGESTIONS: โช๏ธ field--expert--paragraph--field-cc-link-title--climate-change-link--default.html.twig โช๏ธ field--expert--paragraph--field-cc-link-tiโฆ <a href="/services/schools-learning-and-childcare/childcare-and-early-years/free-early-education-and" class="field-group-link"> <!-- THEME DEBUG --> <!-- THEME HOOK: 'field' --> <!-- FILE NAME SUGGESTIONS: โช๏ธ field--expert--paragraph--field-cc-link-title--climate-change-link--default.html.twig โช๏ธ field--expert--paragraโฆ <a href="/cost-living-support/wellbeing-hubs" class="field-group-link"> <!-- THEME DEBUG --> <!-- THEME HOOK: 'field' --> <!-- FILE NAME SUGGESTIONS: โช๏ธ field--expert--paragraph--field-cc-link-title--climate-change-link--default.html.twig โช๏ธ field--expert--paragraph--field-cc-link-title--climate-change-link.html.twig โชโฆ <a href="https://www.informationnow.org.uk/article/cost-of-living/" class="field-group-link"> <!-- THEME DEBUG --> <!-- THEME HOOK: 'field' --> <!-- FILE NAME SUGGESTIONS: โช๏ธ field--expert--paragraph--field-cc-link-title--climate-change-link--default.html.twig โช๏ธ field--expert--paragraph--field-cc-link-title--climate-cโฆ <a href="https://www.informationnow.org.uk/article/emergency-funds-and-support/" class="field-group-link"> <!-- THEME DEBUG --> <!-- THEME HOOK: 'field' --> <!-- FILE NAME SUGGESTIONS: โช๏ธ field--expert--paragraph--field-cc-link-title--climate-change-link--default.html.twig โช๏ธ field--expert--paragraph--field-cc-link-titโฆ …and 2 more like it. 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Warnings · 5 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT32 | warning | the page's meta description, the short summary it offers about itself, runs to 37 characters, too short to say what the page is about; a usable summary runs from 50 to 170 characters | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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 the page's meta description, the short summary it offers about itself, runs to 37 characters, too short to say what the page is about; a usable summary runs from 50 to 170 characters The evidence, taken from the page as served The page's description, as served
<meta name="description" content="The website of Newcastle City Council"/> | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT40 | warning | the page offers no short summary for the services that show a preview of it, so each one composes its own from whatever it finds first on the page | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The short title, description and image the page offers to services that show a preview of it, and whether they match the page. What good looks like The page offers a summary for preview, and the summary is true to the page. Why it matters This summary travels further than the page does. It is what appears when the address is shared, and several services read it in preference to the page itself because it is short and already written for the purpose. Where it is absent, those services compose their own from whatever they find first, which is often navigation. Where it is present but out of step, the organisation is described to a wide audience by a sentence it wrote once and forgot. What we found on this page the page offers no short summary for the services that show a preview of it, so each one composes its own from whatever it finds first on the page The evidence, taken from the page as served The summary this page offers for preview
Read from the page as served.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT41 | warning | the page does not show where it sits in the site, so anything reading it on its own has nothing to say what it belongs to | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The trail showing the path from the front page to this one, and whether the machine-readable version of that trail says the same. What good looks like The page shows its place in the site, and says the same thing to a machine. Why it matters A page read on its own gives no sense of what it belongs to. The trail supplies it: one product within a range, one policy within a set. A reader deciding whether a page answers a question uses that to judge whether it has the right one, and how to describe it when it quotes it. Where the shown trail and the machine-readable one disagree, the page is placed in two positions at once and neither can be relied on. What we found on this page the page does not show where it sits in the site, so anything reading it on its own has nothing to say what it belongs to The evidence, taken from the page as served The path this page gives to itself
Read from the page as served: the trail shown to a reader, and the trail stated in a form a machine can take as given.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT04 | warning | the page shows the year 2024 in its text, but nothing on the page states it as the date of the content | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The page carries a date, ideally written into the markup rather than sitting only in the text. What good looks like The page carries a date, ideally written into the markup rather than sitting only in the text. Why it matters An undated page gives nothing to weigh its age against, so old and new material are treated alike. What we found on this page the page shows the year 2024 in its text, but nothing on the page states it as the date of the content The evidence, taken from the page as served The head of this page, as served
The head of the page was read for a tag stating the date of the content. The year shown above was found in the page's own text. <head> <meta charset="utf-8"/> <style>/* @see https://github.com/aFarkas/lazysizes#broken-image-symbol */.js img.b-lazy:not([src]) { visibility: hidden; }/* @see https://github.com/aFarkas/lazysizes#automatically-setting-the-sizes-attribute */.js img.lazyloaded[data-sizes=auto] { display: block; width: 100%; }</style> <meta name="description" content="The website of Newcastle City Council"/> <meta name="geo.placename" content="Newcastle upon Tyne"/> <link rel="canonical" href="https://newcastle.gov.uk/cost-living-support"/> <link rel="icon" href="favicon.ico"/> <link rel="icon" sizes="16x16" href="/favicon-16x16.png"/> <link rel="icon" sizes="32x32" href="/favicon-32x32.png"/> <link rel="icon" sizes="96x96" href="/favicon-96x96.png"/> <link rel="icon" sizes="192x192" href="/android-chrome-192x192.png"/> <link rel="apple-touch-icon" href="/apple-touch-icon-60x60.png"/> <link rel="apple-touch-icon" sizes="72x72" href="/android-chrome-72x72.png"/> <link rel="apple-touch-icon" sizes="76x76" href="/apple-touch-icon-76x76.png"/> <link rel="apple-touch-icon" sizes="114x114" href="/apple-touch-icon-114x114.png"/> <link rel="apple-touch-icon" sizes="120x120" href="/apple-touch-icon-120x120.โฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT35 | warning | the copyright line at the foot of this page carries no year, so there is nothing on the page as served to date it by | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The copyright line at the foot of the page, and the year it states. What good looks like The copyright line states the current year. Why it matters An old copyright year reads as a site nobody is looking after, and it dates the page for anything that relies on dates. Content can be treated as years older than it really is. What we found on this page the copyright line at the foot of this page carries no year, so there is nothing on the page as served to date it by The evidence, taken from the page as served The copyright line on this page, as served
This is the copyright line as the page serves it. It was read for a year, and carries none. stagram Find out how we use social media Press Office and News ReciteMe and Accessibility ยฉNewcastle City Council Privacy Notice Terms and conditions Contact Us Covid-19 support Listen and translate {"path":{"baseUrl":"\/","pathPrefix":"","c | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
▸https://newcastle.gov.uk/lets-talk 29.9% Very likely 12 out of 67
The page https://newcastle.gov.uk/lets-talk
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Fails · 7 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 AI systems are being turned away before they reach the site, and because the barrier sits outside the organisation's own systems, nobody inside can see it happening. Those systems carry on answering questions about the organisation, from other people's material rather than its own, so the conversation about it goes on without it and nobody has decided that. 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.newcastle.gov.uk · resolves to 194.61.173.205
Address trailwww.newcastle.gov.uk
Checked2026-09-17 16:33 UTC · request sent from 54.171.52.206 (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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MX01 | fail | the site took 447ms to start answering, past the point where an automated reader gives up and takes its answer from elsewhere | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check How quickly the page starts to answer when it is asked for. What good looks like The page starts answering within 250ms. Between 250 and 345ms is a warning; beyond 345ms is a fail, that being the point at which an automated reader gives up. Why it matters A page that is slow to answer is left behind: the reader gives up and takes its answer from someone else's material, so your own words play no part in it. What we found on this page the site took 447ms to start answering, past the point where an automated reader gives up and takes its answer from elsewhere The evidence, taken from the page as served How long this page took to start answering
Timed from the request leaving our checker to the first part of the answer coming back, on the page as served, so distance from the site plays its part. 345ms is the point beyond which an automated reader gives up.
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 starts answering within 250ms. 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT09 | fail | 2 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 heading 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 2 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)
H2 Main navigation H1 Working with communities H4 Consultations and community engagement level jumped H4 Volunteering H3 Doing more in your city H3 Have you got an idea on how to improve your community? H3 Newcastle Fairtrade Partnership H3 Related News H6 (no text) level jumped H6 Council H6 Council H3 Most popular pages H3 We're on social media
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 | fail | this page carries dates, and states none of it in a form a machine can take as given, so those facts have to be worked out from the wording around them | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page states what it is, and the exact facts it carries, in a form a machine can take as given rather than work out from the wording. What good looks like The page states what it is in machine-readable form, and where it carries exact facts it states those too. A page of exact facts stating none of them is a fail; a narrative page without a block is a warning. Why it matters Where a page carries exact facts, an address, opening hours, a price, a date, leaving them only in prose means they are worked out rather than read, and that is where a wrong branch or an old price comes from. What we found on this page this page carries dates, and states none of it in a form a machine can take as given, so those facts have to be worked out from the wording around them The evidence, taken from the page as served The head of this page, as served
The page was read for a short block of machine-readable detail saying what it is. The page's own words carry dates, which is why this weighs as it does. <head> <meta charset="utf-8"/> <style>/* @see https://github.com/aFarkas/lazysizes#broken-image-symbol */.js img.b-lazy:not([src]) { visibility: hidden; }/* @see https://github.com/aFarkas/lazysizes#automatically-setting-the-sizes-attribute */.js img.lazyloaded[data-sizes=auto] { display: block; width: 100%; }</style> <meta name="description" content="The website of Newcastle City Council"/> <meta name="geo.placename" content="Newcastle upon Tyne"/> <link rel="canonical" href="https://newcastle.gov.uk/lets-talk"/> <link rel="icon" href="favicon.ico"/> <link rel="icon" sizes="16x16" href="/favicon-16x16.png"/> <link rel="icon" sizes="32x32" href="/favicon-32x32.png"/> <link rel="icon" sizes="96x96" href="/favicon-96x96.png"/> <link rel="icon" sizes="192x192" href="/android-chrome-192x192.png"/> <link rel="apple-touch-icon" href="/apple-touch-icon-60x60.png"/> <link rel="apple-touch-icon" sizes="72x72" href="/android-chrome-72x72.png"/> <link rel="apple-touch-icon" sizes="76x76" href="/apple-touch-icon-76x76.png"/> <link rel="apple-touch-icon" sizes="114x114" href="/apple-touch-icon-114x114.png"/> <link rel="apple-touch-icon" sizes="120x120" href="/apple-touch-icon-120x120.png"/> <liโฆ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 states what it is in machine-readable form, and where it carries exact facts it states those too. 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT43 | fail | 1 fault in this page's construction change the structure anything reading it sees, so what is read is not quite the page that was published | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page's underlying construction holds together, or contains faults that change how it is read. What good looks like The page is built soundly enough that anything reading it sees the structure its author intended. Why it matters Anything reading the page has to take it apart before it can judge anything on it. Faults in construction can move where a section appears to end, place a heading inside a paragraph, or lose part of the page altogether. When that happens, what is read is not quite the page that was published, and neither is the answer built from it. The damage is invisible on screen, because a browser repairs quietly what a plain reader does not. What we found on this page 1 fault in this page's construction change the structure anything reading it sees, so what is read is not quite the page that was published The evidence, taken from the page as served Faults in the page's construction that change how it reads
Found while taking the page apart exactly as a reader would.
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 is built soundly enough that anything reading it sees the structure its author intended. 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 | 3 link wording(s) are used for more than one destination, so the same words point at different pages: โtheme debug theme hook: 'field' file name suggestions: โช๏ธโ, โtheme debug theme hook: 'field_group_html_element' file nameโ, โtheme debug theme hook: 'image_style' begin output from 'theโ; 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 Identical links on one page lead to different places, so which one gets followed is a coin toss. A reader or system lands on the wrong page while believing it chose correctly. What we found on this page 3 link wording(s) are used for more than one destination, so the same words point at different pages: โtheme debug theme hook: 'field' file name suggestions:
โช๏ธโ, โtheme debug theme hook: 'field_group_html_element' file nameโ, โtheme debug theme hook: 'image_style' begin output from 'theโ; 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="/get-involved/consultations" class="field-group-link"> <!-- THEME DEBUG --> <!-- THEME HOOK: 'field_group_html_element' --> <!-- FILE NAME SUGGESTIONS: โช๏ธ field-group-html-element--node--study-landing-page--group-study-r2-lhs-panel-header.html.twig โช๏ธ field-group-html-element--node--study-landing-page--div.htmโฆ <a href="/get-involved/volunteering" class="field-group-link"> <!-- THEME DEBUG --> <!-- THEME HOOK: 'field_group_html_element' --> <!-- FILE NAME SUGGESTIONS: โช๏ธ field-group-html-element--node--study-landing-page--group-study-r2-rhs-panel-header.html.twig โช๏ธ field-group-html-element--node--study-landing-page--div.htmlโฆ <a href="/get-involved/communities-team" class="field-group-link"> <!-- THEME DEBUG --> <!-- THEME HOOK: 'field' --> <!-- FILE NAME SUGGESTIONS: โช๏ธ field--paragraph--field-image--4-per-line-image-title-text-and-.html.twig โช๏ธ field--paragraph--field-image.html.twig โช๏ธ field--paragraph--4-per-line-image-title-text-and-.hโฆ <a href="/get-involved/grants-and-funding" class="field-group-link"> <!-- THEME DEBUG --> <!-- THEME HOOK: 'field' --> <!-- FILE NAME SUGGESTIONS: โช๏ธ field--paragraph--field-image--4-per-line-image-title-text-and-.html.twig โช๏ธ field--paragraph--field-image.html.twig โช๏ธ field--paragraph--4-per-line-image-title-text-and-โฆ <a href="/get-involved/assets-community-value-localism-act-2011" class="field-group-link"> <!-- THEME DEBUG --> <!-- THEME HOOK: 'field' --> <!-- FILE NAME SUGGESTIONS: โช๏ธ field--paragraph--field-image--4-per-line-image-title-text-and-.html.twig โช๏ธ field--paragraph--field-image.html.twig โช๏ธ field--paragraph--4-per-lineโฆ <a href="/our-city/newcastle-compact" class="field-group-link"> <!-- THEME DEBUG --> <!-- THEME HOOK: 'field' --> <!-- FILE NAME SUGGESTIONS: โช๏ธ field--paragraph--field-image--4-per-line-image-title-text-and-.html.twig โช๏ธ field--paragraph--field-image.html.twig โช๏ธ field--paragraph--4-per-line-image-title-text-and-.htmlโฆ <a href="/citylife-news/byker-ward-election-result" hreflang="en"> <!-- THEME DEBUG --> <!-- THEME HOOK: 'image_style' --> <!-- BEGIN OUTPUT from 'themes/contrib/bootstrap5/templates/field/image-style.html.twig' --> <!-- THEME DEBUG --> <!-- THEME HOOK: 'image' --> <!-- BEGIN OUTPUT from 'themes/contrib/bootstrap5/tempโฆ <a href="/citylife-news/council/build-forward-better-medium-term-plan-2021-22-and-2022-23" hreflang="en"> <!-- THEME DEBUG --> <!-- THEME HOOK: 'image_style' --> <!-- BEGIN OUTPUT from 'themes/contrib/bootstrap5/templates/field/image-style.html.twig' --> <!-- THEME DEBUG --> <!-- THEME HOOK: 'image' --> <!-- BEGIN OUTPโฆ <a href="/citylife-news/council/disruption-payment-system" hreflang="en"> <!-- THEME DEBUG --> <!-- THEME HOOK: 'image_style' --> <!-- BEGIN OUTPUT from 'themes/contrib/bootstrap5/templates/field/image-style.html.twig' --> <!-- THEME DEBUG --> <!-- THEME HOOK: 'image' --> <!-- BEGIN OUTPUT from 'themes/contrib/bootstraโฆ 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 The page's headings begin at its top level, rather than starting part way down. What good looks like The page's headings begin with its top-level heading. Levels skipped further down are weighed under heading hierarchy, and a page with no top-level heading at all under the missing main heading, so each fault is marked once. Why it matters The page's structure starts part way down, below a top level that never opens it. Sections then sit under nothing, and anything filing content by structure starts in the wrong place. 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 (the starting level is marked)
H2 Main navigation level jumped H1 Working with communities H4 Consultations and community engagement H4 Volunteering H3 Doing more in your city H3 Have you got an idea on how to improve your community? H3 Newcastle Fairtrade Partnership H3 Related News H6 (no text) H6 Council H6 Council H3 Most popular pages H3 We're on social media
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 begin with its top-level heading. 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Warnings · 5 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT32 | warning | the page's meta description, the short summary it offers about itself, runs to 37 characters, too short to say what the page is about; a usable summary runs from 50 to 170 characters | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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 the page's meta description, the short summary it offers about itself, runs to 37 characters, too short to say what the page is about; a usable summary runs from 50 to 170 characters The evidence, taken from the page as served The page's description, as served
<meta name="description" content="The website of Newcastle City Council"/> | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT40 | warning | the page offers no short summary for the services that show a preview of it, so each one composes its own from whatever it finds first on the page | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The short title, description and image the page offers to services that show a preview of it, and whether they match the page. What good looks like The page offers a summary for preview, and the summary is true to the page. Why it matters This summary travels further than the page does. It is what appears when the address is shared, and several services read it in preference to the page itself because it is short and already written for the purpose. Where it is absent, those services compose their own from whatever they find first, which is often navigation. Where it is present but out of step, the organisation is described to a wide audience by a sentence it wrote once and forgot. What we found on this page the page offers no short summary for the services that show a preview of it, so each one composes its own from whatever it finds first on the page The evidence, taken from the page as served The summary this page offers for preview
Read from the page as served.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT41 | warning | the page does not show where it sits in the site, so anything reading it on its own has nothing to say what it belongs to | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The trail showing the path from the front page to this one, and whether the machine-readable version of that trail says the same. What good looks like The page shows its place in the site, and says the same thing to a machine. Why it matters A page read on its own gives no sense of what it belongs to. The trail supplies it: one product within a range, one policy within a set. A reader deciding whether a page answers a question uses that to judge whether it has the right one, and how to describe it when it quotes it. Where the shown trail and the machine-readable one disagree, the page is placed in two positions at once and neither can be relied on. What we found on this page the page does not show where it sits in the site, so anything reading it on its own has nothing to say what it belongs to The evidence, taken from the page as served The path this page gives to itself
Read from the page as served: the trail shown to a reader, and the trail stated in a form a machine can take as given.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR14 | warning | the page title and the main heading name different subjects, with no word in common between them. The subject taken from the page then depends on which of the two was read, and both are shown below. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The page title and the main heading on the page, and whether the two name the same subject. What good looks like The title and the main heading name the same subject. Why it matters Where the two disagree, the subject taken from the page depends on which was read, and the page is filed and quoted under a subject it does not cover. What we found on this page the page title and the main heading name different subjects, with no word in common between them. The subject taken from the page then depends on which of the two was read, and both are shown below. The evidence, taken from the page as served The two statements this page makes about its subject
The title and the main heading were compared word by word, with ordinary connecting words set aside.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT35 | warning | the copyright line at the foot of this page carries no year, so there is nothing on the page as served to date it by | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The copyright line at the foot of the page, and the year it states. What good looks like The copyright line states the current year. Why it matters An old copyright year reads as a site nobody is looking after, and it dates the page for anything that relies on dates. Content can be treated as years older than it really is. What we found on this page the copyright line at the foot of this page carries no year, so there is nothing on the page as served to date it by The evidence, taken from the page as served The copyright line on this page, as served
This is the copyright line as the page serves it. It was read for a year, and carries none. stagram Find out how we use social media Press Office and News ReciteMe and Accessibility ยฉNewcastle City Council Privacy Notice Terms and conditions Contact Us Covid-19 support Listen and translate {"path":{"baseUrl":"\/","pathPrefix":"","c | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
▸https://newcastle.gov.uk/local-government 31.0% Very likely 11 out of 67
The page https://newcastle.gov.uk/local-government
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Fails · 6 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 AI systems are being turned away before they reach the site, and because the barrier sits outside the organisation's own systems, nobody inside can see it happening. Those systems carry on answering questions about the organisation, from other people's material rather than its own, so the conversation about it goes on without it and nobody has decided that. 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.newcastle.gov.uk · resolves to 194.61.173.205
Address trailwww.newcastle.gov.uk
Checked2026-09-17 16:33 UTC · request sent from 54.171.52.206 (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 | 2 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 heading 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 2 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)
H2 Main navigation H1 How we run the city H4 Access to information and data level jumped H4 Your elected representatives H4 Council meetings agenda and minutes H4 Equality and diversity H4 Budget, performance and spend H4 Council plan H2 Our vision for a great city H3 How we spend your council tax H3 Elections and voting H3 Your Elected Representatives H3 Looking for something else? H3 Related News H6 (no text) level jumped H6 (no text) H6 (no text) H3 Most popular pages H3 We're on social media
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 | fail | this page carries dates, and states none of it in a form a machine can take as given, so those facts have to be worked out from the wording around them | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page states what it is, and the exact facts it carries, in a form a machine can take as given rather than work out from the wording. What good looks like The page states what it is in machine-readable form, and where it carries exact facts it states those too. A page of exact facts stating none of them is a fail; a narrative page without a block is a warning. Why it matters Where a page carries exact facts, an address, opening hours, a price, a date, leaving them only in prose means they are worked out rather than read, and that is where a wrong branch or an old price comes from. What we found on this page this page carries dates, and states none of it in a form a machine can take as given, so those facts have to be worked out from the wording around them The evidence, taken from the page as served The head of this page, as served
The page was read for a short block of machine-readable detail saying what it is. The page's own words carry dates, which is why this weighs as it does. <head> <meta charset="utf-8"/> <style>/* @see https://github.com/aFarkas/lazysizes#broken-image-symbol */.js img.b-lazy:not([src]) { visibility: hidden; }/* @see https://github.com/aFarkas/lazysizes#automatically-setting-the-sizes-attribute */.js img.lazyloaded[data-sizes=auto] { display: block; width: 100%; }</style> <meta name="description" content="The website of Newcastle City Council"/> <meta name="geo.placename" content="Newcastle upon Tyne"/> <link rel="canonical" href="https://newcastle.gov.uk/local-government"/> <link rel="icon" href="favicon.ico"/> <link rel="icon" sizes="16x16" href="/favicon-16x16.png"/> <link rel="icon" sizes="32x32" href="/favicon-32x32.png"/> <link rel="icon" sizes="96x96" href="/favicon-96x96.png"/> <link rel="icon" sizes="192x192" href="/android-chrome-192x192.png"/> <link rel="apple-touch-icon" href="/apple-touch-icon-60x60.png"/> <link rel="apple-touch-icon" sizes="72x72" href="/android-chrome-72x72.png"/> <link rel="apple-touch-icon" sizes="76x76" href="/apple-touch-icon-76x76.png"/> <link rel="apple-touch-icon" sizes="114x114" href="/apple-touch-icon-114x114.png"/> <link rel="apple-touch-icon" sizes="120x120" href="/apple-touch-icon-120x120.pngโฆ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 states what it is in machine-readable form, and where it carries exact facts it states those too. 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT43 | fail | 1 fault in this page's construction change the structure anything reading it sees, so what is read is not quite the page that was published | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page's underlying construction holds together, or contains faults that change how it is read. What good looks like The page is built soundly enough that anything reading it sees the structure its author intended. Why it matters Anything reading the page has to take it apart before it can judge anything on it. Faults in construction can move where a section appears to end, place a heading inside a paragraph, or lose part of the page altogether. When that happens, what is read is not quite the page that was published, and neither is the answer built from it. The damage is invisible on screen, because a browser repairs quietly what a plain reader does not. What we found on this page 1 fault in this page's construction change the structure anything reading it sees, so what is read is not quite the page that was published The evidence, taken from the page as served Faults in the page's construction that change how it reads
Found while taking the page apart exactly as a reader would.
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 is built soundly enough that anything reading it sees the structure its author intended. 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: โfind out moreโ, โtheme debug theme hook: 'image_style' begin output from 'theโ; 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 Identical links on one page lead to different places, so which one gets followed is a coin toss. A reader or system lands on the wrong page while believing it chose correctly. 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: โfind out moreโ, โtheme debug theme hook: 'image_style' begin output from 'theโ; 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://new.newcastle.gov.uk/council-elections/elections-voting" aria-label="Find out about elections and voting">Find out more</a> <a href="/services/jobs-and-careers/working-newcastle-city-council" aria-label="find out about working for newcastle city council">Find out more</a> <a href="/citylife-news/fly-tipper-ordered-carry-out-unpaid-work-after-dumping-waste" hreflang="en"> <!-- THEME DEBUG --> <!-- THEME HOOK: 'image_style' --> <!-- BEGIN OUTPUT from 'themes/contrib/bootstrap5/templates/field/image-style.html.twig' --> <!-- THEME DEBUG --> <!-- THEME HOOK: 'image' --> <!-- BEGIN OUTPUT frโฆ <a href="/citylife-news/new-small-electrical-recycling-service-launched" hreflang="en"> <!-- THEME DEBUG --> <!-- THEME HOOK: 'image_style' --> <!-- BEGIN OUTPUT from 'themes/contrib/bootstrap5/templates/field/image-style.html.twig' --> <!-- THEME DEBUG --> <!-- THEME HOOK: 'image' --> <!-- BEGIN OUTPUT from 'themes/coโฆ <a href="/citylife-news/unlicensed-waste-carrier-fined-after-van-got-stuck-field" hreflang="en"> <!-- THEME DEBUG --> <!-- THEME HOOK: 'image_style' --> <!-- BEGIN OUTPUT from 'themes/contrib/bootstrap5/templates/field/image-style.html.twig' --> <!-- THEME DEBUG --> <!-- THEME HOOK: 'image' --> <!-- BEGIN OUTPUT from 'โฆ 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 The page's headings begin at its top level, rather than starting part way down. What good looks like The page's headings begin with its top-level heading. Levels skipped further down are weighed under heading hierarchy, and a page with no top-level heading at all under the missing main heading, so each fault is marked once. Why it matters The page's structure starts part way down, below a top level that never opens it. Sections then sit under nothing, and anything filing content by structure starts in the wrong place. 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 (the starting level is marked)
H2 Main navigation level jumped H1 How we run the city H4 Access to information and data H4 Your elected representatives H4 Council meetings agenda and minutes H4 Equality and diversity H4 Budget, performance and spend H4 Council plan H2 Our vision for a great city H3 How we spend your council tax H3 Elections and voting H3 Your Elected Representatives H3 Looking for something else? H3 Related News H6 (no text) H6 (no text) H6 (no text) H3 Most popular pages H3 We're on social media
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 begin with its top-level heading. 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Warnings · 5 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT32 | warning | the page's meta description, the short summary it offers about itself, runs to 37 characters, too short to say what the page is about; a usable summary runs from 50 to 170 characters | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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 the page's meta description, the short summary it offers about itself, runs to 37 characters, too short to say what the page is about; a usable summary runs from 50 to 170 characters The evidence, taken from the page as served The page's description, as served
<meta name="description" content="The website of Newcastle City Council"/> | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT40 | warning | the page offers no short summary for the services that show a preview of it, so each one composes its own from whatever it finds first on the page | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The short title, description and image the page offers to services that show a preview of it, and whether they match the page. What good looks like The page offers a summary for preview, and the summary is true to the page. Why it matters This summary travels further than the page does. It is what appears when the address is shared, and several services read it in preference to the page itself because it is short and already written for the purpose. Where it is absent, those services compose their own from whatever they find first, which is often navigation. Where it is present but out of step, the organisation is described to a wide audience by a sentence it wrote once and forgot. What we found on this page the page offers no short summary for the services that show a preview of it, so each one composes its own from whatever it finds first on the page The evidence, taken from the page as served The summary this page offers for preview
Read from the page as served.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT41 | warning | the page does not show where it sits in the site, so anything reading it on its own has nothing to say what it belongs to | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The trail showing the path from the front page to this one, and whether the machine-readable version of that trail says the same. What good looks like The page shows its place in the site, and says the same thing to a machine. Why it matters A page read on its own gives no sense of what it belongs to. The trail supplies it: one product within a range, one policy within a set. A reader deciding whether a page answers a question uses that to judge whether it has the right one, and how to describe it when it quotes it. Where the shown trail and the machine-readable one disagree, the page is placed in two positions at once and neither can be relied on. What we found on this page the page does not show where it sits in the site, so anything reading it on its own has nothing to say what it belongs to The evidence, taken from the page as served The path this page gives to itself
Read from the page as served: the trail shown to a reader, and the trail stated in a form a machine can take as given.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT35 | warning | the copyright line at the foot of this page carries no year, so there is nothing on the page as served to date it by | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The copyright line at the foot of the page, and the year it states. What good looks like The copyright line states the current year. Why it matters An old copyright year reads as a site nobody is looking after, and it dates the page for anything that relies on dates. Content can be treated as years older than it really is. What we found on this page the copyright line at the foot of this page carries no year, so there is nothing on the page as served to date it by The evidence, taken from the page as served The copyright line on this page, as served
This is the copyright line as the page serves it. It was read for a year, and carries none. stagram Find out how we use social media Press Office and News ReciteMe and Accessibility ยฉNewcastle City Council Privacy Notice Terms and conditions Contact Us Covid-19 support Listen and translate {"path":{"baseUrl":"\/","pathPrefix":"","c | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MX10 | warning | one link to a file on this page does not say what the file is and how big it is before it is opened. A reader deciding whether to open a file has nothing to judge it by, and on a slow or metered connection an unnamed file is a risk rather than an offer. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Links that open a file, and whether the wording states the format and the size. What good looks like A link to a file states its format and its size. Why it matters A reader deciding whether to open a file has nothing to judge it by, and on a slow or metered connection an unnamed file is a risk rather than an offer. What we found on this page one link to a file on this page does not say what the file is and how big it is before it is opened. A reader deciding whether to open a file has nothing to judge it by, and on a slow or metered connection an unnamed file is a risk rather than an offer. The evidence, taken from the page as served The links to a file, and what each one states
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
▸https://www.newcastle.gov.uk/contact-us 31.0% Very likely 12 out of 68
The page https://www.newcastle.gov.uk/contact-us
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Fails · 5 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 AI systems are being turned away before they reach the site, and because the barrier sits outside the organisation's own systems, nobody inside can see it happening. Those systems carry on answering questions about the organisation, from other people's material rather than its own, so the conversation about it goes on without it and nobody has decided that. 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.newcastle.gov.uk · resolves to 194.61.173.205
Address trailwww.newcastle.gov.uk
Checked2026-09-17 16:33 UTC · request sent from 54.171.52.206 (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 heading 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)
H2 Main navigation H2 Title H4 Have your say level jumped H1 Contact us H2 Contact us H2 Contact us online H3 Complaints & Compliments H2 Contact us by phone H3 24 hour telephone line H1 Relay UK H2 Contact us in writing H2 Related Pages H3 Most popular pages H3 We're on social media
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 | fail | this page carries opening hours and a telephone number, and states none of it in a form a machine can take as given, so those facts have to be worked out from the wording around them | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page states what it is, and the exact facts it carries, in a form a machine can take as given rather than work out from the wording. What good looks like The page states what it is in machine-readable form, and where it carries exact facts it states those too. A page of exact facts stating none of them is a fail; a narrative page without a block is a warning. Why it matters Where a page carries exact facts, an address, opening hours, a price, a date, leaving them only in prose means they are worked out rather than read, and that is where a wrong branch or an old price comes from. What we found on this page this page carries opening hours and a telephone number, and states none of it in a form a machine can take as given, so those facts have to be worked out from the wording around them The evidence, taken from the page as served The head of this page, as served
The page was read for a short block of machine-readable detail saying what it is. The page's own words carry opening hours and a telephone number, which is why this weighs as it does. <head> <meta charset="utf-8"/> <style>/* @see https://github.com/aFarkas/lazysizes#broken-image-symbol */.js img.b-lazy:not([src]) { visibility: hidden; }/* @see https://github.com/aFarkas/lazysizes#automatically-setting-the-sizes-attribute */.js img.lazyloaded[data-sizes=auto] { display: block; width: 100%; }</style> <meta name="description" content="The website of Newcastle City Council"/> <meta name="geo.placename" content="Newcastle upon Tyne"/> <link rel="canonical" href="https://www.newcastle.gov.uk/contact-us"/> <link rel="icon" href="favicon.ico"/> <link rel="icon" sizes="16x16" href="/favicon-16x16.png"/> <link rel="icon" sizes="32x32" href="/favicon-32x32.png"/> <link rel="icon" sizes="96x96" href="/favicon-96x96.png"/> <link rel="icon" sizes="192x192" href="/android-chrome-192x192.png"/> <link rel="apple-touch-icon" href="/apple-touch-icon-60x60.png"/> <link rel="apple-touch-icon" sizes="72x72" href="/android-chrome-72x72.png"/> <link rel="apple-touch-icon" sizes="76x76" href="/apple-touch-icon-76x76.png"/> <link rel="apple-touch-icon" sizes="114x114" href="/apple-touch-icon-114x114.png"/> <link rel="apple-touch-icon" sizes="120x120" href="/apple-touch-icon-120x120.png"/โฆ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 states what it is in machine-readable form, and where it carries exact facts it states those too. 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT43 | fail | 1 fault in this page's construction change the structure anything reading it sees, so what is read is not quite the page that was published | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page's underlying construction holds together, or contains faults that change how it is read. What good looks like The page is built soundly enough that anything reading it sees the structure its author intended. Why it matters Anything reading the page has to take it apart before it can judge anything on it. Faults in construction can move where a section appears to end, place a heading inside a paragraph, or lose part of the page altogether. When that happens, what is read is not quite the page that was published, and neither is the answer built from it. The damage is invisible on screen, because a browser repairs quietly what a plain reader does not. What we found on this page 1 fault in this page's construction change the structure anything reading it sees, so what is read is not quite the page that was published The evidence, taken from the page as served Faults in the page's construction that change how it reads
Found while taking the page apart exactly as a reader would.
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 is built soundly enough that anything reading it sees the structure its author intended. 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 The page's headings begin at its top level, rather than starting part way down. What good looks like The page's headings begin with its top-level heading. Levels skipped further down are weighed under heading hierarchy, and a page with no top-level heading at all under the missing main heading, so each fault is marked once. Why it matters The page's structure starts part way down, below a top level that never opens it. Sections then sit under nothing, and anything filing content by structure starts in the wrong place. 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 (the starting level is marked)
H2 Main navigation level jumped H2 Title H4 Have your say H1 Contact us H2 Contact us H2 Contact us online H3 Complaints & Compliments H2 Contact us by phone H3 24 hour telephone line H1 Relay UK H2 Contact us in writing H2 Related Pages H3 Most popular pages H3 We're on social media
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 begin with its top-level heading. 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Warnings · 7 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT32 | warning | the page's meta description, the short summary it offers about itself, runs to 37 characters, too short to say what the page is about; a usable summary runs from 50 to 170 characters | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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 the page's meta description, the short summary it offers about itself, runs to 37 characters, too short to say what the page is about; a usable summary runs from 50 to 170 characters The evidence, taken from the page as served The page's description, as served
<meta name="description" content="The website of Newcastle City Council"/> | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT11 | warning | 2 H1s (informational; not an error per Google) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check More than one main heading on the page, recorded for information rather than marked as a fault. What good looks like The page carries one main heading rather than several. Why it matters Two main headings make a page state its subject twice, which can blur which one defines it. On its own this rarely changes what gets quoted, so it is noted for the record rather than marked as a fault. What we found on this page 2 H1s (informational; not an error per Google) The evidence, taken from the page as served The multiple H1 headings, as served
<h1> Contact us </h1> <h1 class="page-title" style="-webkit-text-stroke-width:0px;background-color:rgb(255, 255, 255);box-sizing:border-box;color:rgb(43, 43, 43);font-family:Lato, sans-serif;font-size:2.188em;font-style:normal;font-variant-caps:normal;font-variant-ligatures:normal;letter-spacing:normal;line-height:1.2;margin:0px 0px 0.6em;oโฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT40 | warning | the page offers no short summary for the services that show a preview of it, so each one composes its own from whatever it finds first on the page | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The short title, description and image the page offers to services that show a preview of it, and whether they match the page. What good looks like The page offers a summary for preview, and the summary is true to the page. Why it matters This summary travels further than the page does. It is what appears when the address is shared, and several services read it in preference to the page itself because it is short and already written for the purpose. Where it is absent, those services compose their own from whatever they find first, which is often navigation. Where it is present but out of step, the organisation is described to a wide audience by a sentence it wrote once and forgot. What we found on this page the page offers no short summary for the services that show a preview of it, so each one composes its own from whatever it finds first on the page The evidence, taken from the page as served The summary this page offers for preview
Read from the page as served.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT41 | warning | the page does not show where it sits in the site, so anything reading it on its own has nothing to say what it belongs to | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The trail showing the path from the front page to this one, and whether the machine-readable version of that trail says the same. What good looks like The page shows its place in the site, and says the same thing to a machine. Why it matters A page read on its own gives no sense of what it belongs to. The trail supplies it: one product within a range, one policy within a set. A reader deciding whether a page answers a question uses that to judge whether it has the right one, and how to describe it when it quotes it. Where the shown trail and the machine-readable one disagree, the page is placed in two positions at once and neither can be relied on. What we found on this page the page does not show where it sits in the site, so anything reading it on its own has nothing to say what it belongs to The evidence, taken from the page as served The path this page gives to itself
Read from the page as served: the trail shown to a reader, and the trail stated in a form a machine can take as given.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT04 | warning | the page carries no date, so there is nothing on it saying how current its content is | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The page carries a date, ideally written into the markup rather than sitting only in the text. What good looks like The page carries a date, ideally written into the markup rather than sitting only in the text. Why it matters An undated page gives nothing to weigh its age against, so old and new material are treated alike. What we found on this page the page carries no date, so there is nothing on it saying how current its content is The evidence, taken from the page as served The head of this page, as served
The head of the page and the page's own text were read for a date. <head> <meta charset="utf-8"/> <style>/* @see https://github.com/aFarkas/lazysizes#broken-image-symbol */.js img.b-lazy:not([src]) { visibility: hidden; }/* @see https://github.com/aFarkas/lazysizes#automatically-setting-the-sizes-attribute */.js img.lazyloaded[data-sizes=auto] { display: block; width: 100%; }</style> <meta name="description" content="The website of Newcastle City Council"/> <meta name="geo.placename" content="Newcastle upon Tyne"/> <link rel="canonical" href="https://www.newcastle.gov.uk/contact-us"/> <link rel="icon" href="favicon.ico"/> <link rel="icon" sizes="16x16" href="/favicon-16x16.png"/> <link rel="icon" sizes="32x32" href="/favicon-32x32.png"/> <link rel="icon" sizes="96x96" href="/favicon-96x96.png"/> <link rel="icon" sizes="192x192" href="/android-chrome-192x192.png"/> <link rel="apple-touch-icon" href="/apple-touch-icon-60x60.png"/> <link rel="apple-touch-icon" sizes="72x72" href="/android-chrome-72x72.png"/> <link rel="apple-touch-icon" sizes="76x76" href="/apple-touch-icon-76x76.png"/> <link rel="apple-touch-icon" sizes="114x114" href="/apple-touch-icon-114x114.png"/> <link rel="apple-touch-icon" sizes="120x120" href="/apple-touch-icon-120x120.png"/โฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT35 | warning | the copyright line at the foot of this page carries no year, so there is nothing on the page as served to date it by | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The copyright line at the foot of the page, and the year it states. What good looks like The copyright line states the current year. Why it matters An old copyright year reads as a site nobody is looking after, and it dates the page for anything that relies on dates. Content can be treated as years older than it really is. What we found on this page the copyright line at the foot of this page carries no year, so there is nothing on the page as served to date it by The evidence, taken from the page as served The copyright line on this page, as served
This is the copyright line as the page serves it. It was read for a year, and carries none. stagram Find out how we use social media Press Office and News ReciteMe and Accessibility ยฉNewcastle City Council Privacy Notice Terms and conditions Contact Us Covid-19 support Listen and translate {"path":{"baseUrl":"\/","pathPrefix":"","c | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS09 | warning | link wording that does not say where it leads: โhereโ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Link wording that names no destination, phrases such as click here, read more and details, and one such wording repeated across many links. What good looks like Link wording names its destination, rather than saying click here or read more. Why it matters The destination is stated nowhere on the link itself, so the choice rests entirely on the text around it. Where one wording such as click here covers many links, they read as one link repeated and nothing in their names tells them apart. What we found on this page link wording that does not say where it leads: โhereโ The evidence, taken from the page as served The links whose text names no destination, as served
<a href="https://new.newcastle.gov.uk/complaints-compliments">here</a> | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
▸https://newcastle.gov.uk/events 10.1% Extremely likely 11 out of 67
The page https://newcastle.gov.uk/events
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Fails · 4 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 AI systems are being turned away before they reach the site, and because the barrier sits outside the organisation's own systems, nobody inside can see it happening. Those systems carry on answering questions about the organisation, from other people's material rather than its own, so the conversation about it goes on without it and nobody has decided that. 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.newcastle.gov.uk · resolves to 194.61.173.205
Address trailwww.newcastle.gov.uk
Checked2026-09-17 16:33 UTC · request sent from 54.171.52.206 (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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| DS18 | fail | the site's own list of its pages offers this page at one address and the page then names a different one as its preferred address, so a reader following the list arrives somewhere the page disowns | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Pages that name more than one preferred address, with the declarations disagreeing. What good looks like A page's preferred-address declarations agree with one another. Why it matters The page gives two different answers about which of its addresses is the official one. A contradiction like that gets ignored, so outside systems decide for themselves which copy of the page to use. What we found on this page the site's own list of its pages offers this page at one address and the page then names a different one as its preferred address, so a reader following the list arrives somewhere the page disowns The evidence, taken from the page as served The address this page is listed at, and the address it prefers
Read from the site's own list of its pages and from the page itself.
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's preferred-address declarations agree with one another. 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| DS35 | fail | the site answered as though it were serving a page, but what came back is a notice about the site itself rather than its content ("thank you for your patience"), running to 848 characters. What was measured here describes that notice, not the organisation's own page. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the address answered with the organisation's own content, or with a notice about the site itself: a queue, an overflow message or a maintenance window. What good looks like The address serves the organisation's own content. Why it matters A site under load or in maintenance often answers as though nothing were wrong, returning a short notice in place of the page. Anything reading it, a person or an AI system, receives that notice as the organisation's page and takes it as what the organisation has to say. Where this happens across the site, an assessment of it describes the notice rather than the estate, and any figure drawn from it has to be read in that light. What we found on this page the site answered as though it were serving a page, but what came back is a notice about the site itself rather than its content ("thank you for your patience"), running to 848 characters. What was measured here describes that notice, not the organisation's own page. The evidence, taken from the page as served What this address served, as served
The address answered as though it were a real page. Its text was read for the wording a site uses when it is telling visitors it cannot serve them right now. Organising events | Newcastle City Council Skip to main content Organising events Services Menu Main navigation News Pay My portal Listen and translate Search Services menu Adult social care Benefits and money advice Births, deaths, marriages and ceremonies Budget, policies, performance and data Business and commerce Children and families Communities and neighbourhoods Council and elections Council tax Environment, parks and allotments Housing Jobs, careers and skills Libraries Licences and permits Parking and bus lanes Planning and building control Public health Recycling and waste Roads, streets and travel Schools and education Topics Asylum and refugees Climate change Cost of living support Customer commitment Improvements to our website You may notice that some pages look different while we update and improve our online services. During this work you can use our services as normal. T 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 address serves the organisation's own 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS08 | fail | 1 link wording(s) are used for more than one destination, so the same words point at different pages: โtheme debug theme hook: 'field' file name suggestions: โช๏ธโ; 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 Identical links on one page lead to different places, so which one gets followed is a coin toss. A reader or system lands on the wrong page while believing it chose correctly. 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: โtheme debug theme hook: 'field' file name suggestions:
โช๏ธโ; 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="/business-and-commerce/organising-events/filming-newcastle" rel="bookmark"> <!-- THEME DEBUG --> <!-- THEME HOOK: 'field' --> <!-- FILE NAME SUGGESTIONS: โช๏ธ field--node--title--localgov-guides-overview.html.twig โ field--node--title.html.twig โช๏ธ field--node--localgov-guides-overview.html.twig โช๏ธ field--title.hโฆ <a href="/business/organising-events/drone-use" rel="bookmark"> <!-- THEME DEBUG --> <!-- THEME HOOK: 'field' --> <!-- FILE NAME SUGGESTIONS: โช๏ธ field--node--title--localgov-services-page.html.twig โ field--node--title.html.twig โช๏ธ field--node--localgov-services-page.html.twig โช๏ธ field--title.html.twig โช๏ธ field--stringโฆ <a href="/business-and-commerce/organising-events/sky-lanterns-and-balloon-releases" rel="bookmark"> <!-- THEME DEBUG --> <!-- THEME HOOK: 'field' --> <!-- FILE NAME SUGGESTIONS: โช๏ธ field--node--title--localgov-services-page.html.twig โ field--node--title.html.twig โช๏ธ field--node--localgov-services-page.html.twig โช๏ธ fiโฆ <a href="/business-and-commerce/organising-events/organising-event" rel="bookmark"> <!-- THEME DEBUG --> <!-- THEME HOOK: 'field' --> <!-- FILE NAME SUGGESTIONS: โช๏ธ field--node--title--localgov-step-by-step-overview.html.twig โ field--node--title.html.twig โช๏ธ field--node--localgov-step-by-step-overview.html.twig โช๏ธ fieโฆ 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Warnings · 7 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT16 | warning | the page states nothing about itself in a form a machine can take as given, so who you are and what the page is about are worked out from its wording | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page states what it is, and the exact facts it carries, in a form a machine can take as given rather than work out from the wording. What good looks like The page states what it is in machine-readable form, and where it carries exact facts it states those too. A page of exact facts stating none of them is a fail; a narrative page without a block is a warning. Why it matters Where a page carries exact facts, an address, opening hours, a price, a date, leaving them only in prose means they are worked out rather than read, and that is where a wrong branch or an old price comes from. What we found on this page the page states nothing about itself in a form a machine can take as given, so who you are and what the page is about are worked out from its wording The evidence, taken from the page as served The head of this page, as served
The page was read for a short block of machine-readable detail saying what it is. The page's own words carry no exact facts of that kind. <head> <meta charset="utf-8"/> <meta name="description" content="Find advice and guidance for hosting events and filming in Newcastle"/> <link rel="canonical" href="https://new.newcastle.gov.uk/business-and-commerce/organising-events"/> <meta name="Generator" content="Drupal 10 (LocalGov Drupal | https://localgovdrupal.org)"/> <meta name="MobileOptimized" content="width"/> <meta name="HandheldFriendly" content="true"/> <meta name="viewport" content="width=device-width, initial-scale=1.0"/> <link rel="icon" href="/sites/default/files/ncc-favicon_0.ico" type="image/vnd.microsoft.icon"/> <script src="/sites/default/files/google_tag/ncc_default/google_tag.script.js?tlij1z" defer="defer"/> <title>Organising events | Newcastle City Council</title> <link rel="stylesheet" media="all" href="/modules/contrib/localgov_paragraphs/modules/localgov_subsites_paragraphs/css/localgov-subsites-paragraphs.css?tlij1z"/> <link rel="stylesheet" media="all" href="/core/themes/stable9/css/system/components/align.module.css?tlij1z"/> <link rel="stylesheet" media="all" href="/core/themes/stable9/css/system/components/fieldgroup.module.css?tlij1z"/> <link rel="stylesheet" media="all" href="/core/themes/stablโฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT40 | warning | the page offers no short summary for the services that show a preview of it, so each one composes its own from whatever it finds first on the page | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The short title, description and image the page offers to services that show a preview of it, and whether they match the page. What good looks like The page offers a summary for preview, and the summary is true to the page. Why it matters This summary travels further than the page does. It is what appears when the address is shared, and several services read it in preference to the page itself because it is short and already written for the purpose. Where it is absent, those services compose their own from whatever they find first, which is often navigation. Where it is present but out of step, the organisation is described to a wide audience by a sentence it wrote once and forgot. What we found on this page the page offers no short summary for the services that show a preview of it, so each one composes its own from whatever it finds first on the page The evidence, taken from the page as served The summary this page offers for preview
Read from the page as served.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT41 | warning | the page shows where it sits in the site but does not state it in a form a machine can take as given | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The trail showing the path from the front page to this one, and whether the machine-readable version of that trail says the same. What good looks like The page shows its place in the site, and says the same thing to a machine. Why it matters A page read on its own gives no sense of what it belongs to. The trail supplies it: one product within a range, one policy within a set. A reader deciding whether a page answers a question uses that to judge whether it has the right one, and how to describe it when it quotes it. Where the shown trail and the machine-readable one disagree, the page is placed in two positions at once and neither can be relied on. What we found on this page the page shows where it sits in the site but does not state it in a form a machine can take as given The evidence, taken from the page as served The path this page gives to itself
Read from the page as served: the trail shown to a reader, and the trail stated in a form a machine can take as given.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT04 | warning | the page carries no date, so there is nothing on it saying how current its content is | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The page carries a date, ideally written into the markup rather than sitting only in the text. What good looks like The page carries a date, ideally written into the markup rather than sitting only in the text. Why it matters An undated page gives nothing to weigh its age against, so old and new material are treated alike. What we found on this page the page carries no date, so there is nothing on it saying how current its content is The evidence, taken from the page as served The head of this page, as served
The head of the page and the page's own text were read for a date. <head> <meta charset="utf-8"/> <meta name="description" content="Find advice and guidance for hosting events and filming in Newcastle"/> <link rel="canonical" href="https://new.newcastle.gov.uk/business-and-commerce/organising-events"/> <meta name="Generator" content="Drupal 10 (LocalGov Drupal | https://localgovdrupal.org)"/> <meta name="MobileOptimized" content="width"/> <meta name="HandheldFriendly" content="true"/> <meta name="viewport" content="width=device-width, initial-scale=1.0"/> <link rel="icon" href="/sites/default/files/ncc-favicon_0.ico" type="image/vnd.microsoft.icon"/> <script src="/sites/default/files/google_tag/ncc_default/google_tag.script.js?tlij1z" defer="defer"/> <title>Organising events | Newcastle City Council</title> <link rel="stylesheet" media="all" href="/modules/contrib/localgov_paragraphs/modules/localgov_subsites_paragraphs/css/localgov-subsites-paragraphs.css?tlij1z"/> <link rel="stylesheet" media="all" href="/core/themes/stable9/css/system/components/align.module.css?tlij1z"/> <link rel="stylesheet" media="all" href="/core/themes/stable9/css/system/components/fieldgroup.module.css?tlij1z"/> <link rel="stylesheet" media="all" href="/core/themes/stablโฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT35 | warning | the copyright line at the foot of this page carries no year, so there is nothing on the page as served to date it by | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The copyright line at the foot of the page, and the year it states. What good looks like The copyright line states the current year. Why it matters An old copyright year reads as a site nobody is looking after, and it dates the page for anything that relies on dates. Content can be treated as years older than it really is. What we found on this page the copyright line at the foot of this page carries no year, so there is nothing on the page as served to date it by The evidence, taken from the page as served The copyright line on this page, as served
This is the copyright line as the page serves it. It was read for a year, and carries none. ch and comment on planning applications Footer Accessibility Privacy Terms and conditions ยฉNewcastle City Council {"path":{"baseUrl":"\/","pathPrefix":"","currentPath":"node\/1329","currentPathIsAdmin":false,"isFront":false,"currentLanguage" | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AJ07 | warning | 1 required field(s) have no tie in the page's code between the field and its error message, so which field an error belongs to rests on layout alone | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether required form fields are linked in the markup to the error messages about them. What good looks like Each required field is tied in the markup to the message that describes its error. Why it matters An error message sits on the page with nothing tying it to the field it concerns, so the correction has no anchor. What we found on this page 1 required field(s) have no tie in the page's code between the field and its error message, so which field an error belongs to rests on layout alone The evidence, taken from the page as served The required fields with no error association, as served
<input data-drupal-selector="edit-s" placeholder="Search" type="text" id="edit-s--2" name="s" value="" size="30" maxlength="128" class="form-text required" required="required" aria-required="true"/> | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS13 | warning | 1 of 1 iframes untitled | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Each embedded panel on the page carries a title saying what it contains. What good looks like Each embedded panel carries a title saying what it contains. Why it matters Content brought into the page from elsewhere, a map, a form, a video player, carries no name saying what it is. Anything reading the page sees a hole where that content sits. What we found on this page 1 of 1 iframes untitled The evidence, taken from the page as served The iframes with no title attribute, as served
<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-W7BB9DGL" height="0" width="0" style="display:none;visibility:hidden"/> | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
▸https://newcastle.gov.uk/cost-living-support/household-support-fund 31.6% Very likely 10 out of 67
The page https://newcastle.gov.uk/cost-living-support/household-support-fund
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Fails · 5 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 AI systems are being turned away before they reach the site, and because the barrier sits outside the organisation's own systems, nobody inside can see it happening. Those systems carry on answering questions about the organisation, from other people's material rather than its own, so the conversation about it goes on without it and nobody has decided that. 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.newcastle.gov.uk · resolves to 194.61.173.205
Address trailwww.newcastle.gov.uk
Checked2026-09-17 16:33 UTC · request sent from 54.171.52.206 (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 heading 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)
H2 Main navigation H2 Title H4 Have your say level jumped H1 Household Support Fund H2 Household Support Fund H2 Formal Notice H2 Household Support Fund 2025 / 26 H2 Hardship payments for residents in significant financial difficulty H2 Support of localised Cost of Living and discretionary schemes H2 Other support available H3 Most popular pages H3 We're on social media
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 | fail | this page carries prices or figures and dates, and states none of it in a form a machine can take as given, so those facts have to be worked out from the wording around them | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page states what it is, and the exact facts it carries, in a form a machine can take as given rather than work out from the wording. What good looks like The page states what it is in machine-readable form, and where it carries exact facts it states those too. A page of exact facts stating none of them is a fail; a narrative page without a block is a warning. Why it matters Where a page carries exact facts, an address, opening hours, a price, a date, leaving them only in prose means they are worked out rather than read, and that is where a wrong branch or an old price comes from. What we found on this page this page carries prices or figures and dates, and states none of it in a form a machine can take as given, so those facts have to be worked out from the wording around them The evidence, taken from the page as served The head of this page, as served
The page was read for a short block of machine-readable detail saying what it is. The page's own words carry prices or figures and dates, which is why this weighs as it does. <head> <meta charset="utf-8"/> <style>/* @see https://github.com/aFarkas/lazysizes#broken-image-symbol */.js img.b-lazy:not([src]) { visibility: hidden; }/* @see https://github.com/aFarkas/lazysizes#automatically-setting-the-sizes-attribute */.js img.lazyloaded[data-sizes=auto] { display: block; width: 100%; }</style> <meta name="description" content="The website of Newcastle City Council"/> <meta name="geo.placename" content="Newcastle upon Tyne"/> <link rel="canonical" href="https://newcastle.gov.uk/cost-living-support/household-support-fund"/> <link rel="icon" href="favicon.ico"/> <link rel="icon" sizes="16x16" href="/favicon-16x16.png"/> <link rel="icon" sizes="32x32" href="/favicon-32x32.png"/> <link rel="icon" sizes="96x96" href="/favicon-96x96.png"/> <link rel="icon" sizes="192x192" href="/android-chrome-192x192.png"/> <link rel="apple-touch-icon" href="/apple-touch-icon-60x60.png"/> <link rel="apple-touch-icon" sizes="72x72" href="/android-chrome-72x72.png"/> <link rel="apple-touch-icon" sizes="76x76" href="/apple-touch-icon-76x76.png"/> <link rel="apple-touch-icon" sizes="114x114" href="/apple-touch-icon-114x114.png"/> <link rel="apple-touch-icon" sizes="120x120" href="/apโฆ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 states what it is in machine-readable form, and where it carries exact facts it states those too. 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT43 | fail | 1 fault in this page's construction change the structure anything reading it sees, so what is read is not quite the page that was published | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page's underlying construction holds together, or contains faults that change how it is read. What good looks like The page is built soundly enough that anything reading it sees the structure its author intended. Why it matters Anything reading the page has to take it apart before it can judge anything on it. Faults in construction can move where a section appears to end, place a heading inside a paragraph, or lose part of the page altogether. When that happens, what is read is not quite the page that was published, and neither is the answer built from it. The damage is invisible on screen, because a browser repairs quietly what a plain reader does not. What we found on this page 1 fault in this page's construction change the structure anything reading it sees, so what is read is not quite the page that was published The evidence, taken from the page as served Faults in the page's construction that change how it reads
Found while taking the page apart exactly as a reader would.
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 is built soundly enough that anything reading it sees the structure its author intended. 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 The page's headings begin at its top level, rather than starting part way down. What good looks like The page's headings begin with its top-level heading. Levels skipped further down are weighed under heading hierarchy, and a page with no top-level heading at all under the missing main heading, so each fault is marked once. Why it matters The page's structure starts part way down, below a top level that never opens it. Sections then sit under nothing, and anything filing content by structure starts in the wrong place. 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 (the starting level is marked)
H2 Main navigation level jumped H2 Title H4 Have your say H1 Household Support Fund H2 Household Support Fund H2 Formal Notice H2 Household Support Fund 2025 / 26 H2 Hardship payments for residents in significant financial difficulty H2 Support of localised Cost of Living and discretionary schemes H2 Other support available H3 Most popular pages H3 We're on social media
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 begin with its top-level heading. 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Warnings · 5 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT32 | warning | the page's meta description, the short summary it offers about itself, runs to 37 characters, too short to say what the page is about; a usable summary runs from 50 to 170 characters | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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 the page's meta description, the short summary it offers about itself, runs to 37 characters, too short to say what the page is about; a usable summary runs from 50 to 170 characters The evidence, taken from the page as served The page's description, as served
<meta name="description" content="The website of Newcastle City Council"/> | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT40 | warning | the page offers no short summary for the services that show a preview of it, so each one composes its own from whatever it finds first on the page | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The short title, description and image the page offers to services that show a preview of it, and whether they match the page. What good looks like The page offers a summary for preview, and the summary is true to the page. Why it matters This summary travels further than the page does. It is what appears when the address is shared, and several services read it in preference to the page itself because it is short and already written for the purpose. Where it is absent, those services compose their own from whatever they find first, which is often navigation. Where it is present but out of step, the organisation is described to a wide audience by a sentence it wrote once and forgot. What we found on this page the page offers no short summary for the services that show a preview of it, so each one composes its own from whatever it finds first on the page The evidence, taken from the page as served The summary this page offers for preview
Read from the page as served.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT41 | warning | the page does not show where it sits in the site, so anything reading it on its own has nothing to say what it belongs to | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The trail showing the path from the front page to this one, and whether the machine-readable version of that trail says the same. What good looks like The page shows its place in the site, and says the same thing to a machine. Why it matters A page read on its own gives no sense of what it belongs to. The trail supplies it: one product within a range, one policy within a set. A reader deciding whether a page answers a question uses that to judge whether it has the right one, and how to describe it when it quotes it. Where the shown trail and the machine-readable one disagree, the page is placed in two positions at once and neither can be relied on. What we found on this page the page does not show where it sits in the site, so anything reading it on its own has nothing to say what it belongs to The evidence, taken from the page as served The path this page gives to itself
Read from the page as served: the trail shown to a reader, and the trail stated in a form a machine can take as given.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT04 | warning | the page shows the year 2026 in its text, but nothing on the page states it as the date of the content | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The page carries a date, ideally written into the markup rather than sitting only in the text. What good looks like The page carries a date, ideally written into the markup rather than sitting only in the text. Why it matters An undated page gives nothing to weigh its age against, so old and new material are treated alike. What we found on this page the page shows the year 2026 in its text, but nothing on the page states it as the date of the content The evidence, taken from the page as served The head of this page, as served
The head of the page was read for a tag stating the date of the content. The year shown above was found in the page's own text. <head> <meta charset="utf-8"/> <style>/* @see https://github.com/aFarkas/lazysizes#broken-image-symbol */.js img.b-lazy:not([src]) { visibility: hidden; }/* @see https://github.com/aFarkas/lazysizes#automatically-setting-the-sizes-attribute */.js img.lazyloaded[data-sizes=auto] { display: block; width: 100%; }</style> <meta name="description" content="The website of Newcastle City Council"/> <meta name="geo.placename" content="Newcastle upon Tyne"/> <link rel="canonical" href="https://newcastle.gov.uk/cost-living-support/household-support-fund"/> <link rel="icon" href="favicon.ico"/> <link rel="icon" sizes="16x16" href="/favicon-16x16.png"/> <link rel="icon" sizes="32x32" href="/favicon-32x32.png"/> <link rel="icon" sizes="96x96" href="/favicon-96x96.png"/> <link rel="icon" sizes="192x192" href="/android-chrome-192x192.png"/> <link rel="apple-touch-icon" href="/apple-touch-icon-60x60.png"/> <link rel="apple-touch-icon" sizes="72x72" href="/android-chrome-72x72.png"/> <link rel="apple-touch-icon" sizes="76x76" href="/apple-touch-icon-76x76.png"/> <link rel="apple-touch-icon" sizes="114x114" href="/apple-touch-icon-114x114.png"/> <link rel="apple-touch-icon" sizes="120x120" href="/apโฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT35 | warning | the copyright line at the foot of this page carries no year, so there is nothing on the page as served to date it by | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The copyright line at the foot of the page, and the year it states. What good looks like The copyright line states the current year. Why it matters An old copyright year reads as a site nobody is looking after, and it dates the page for anything that relies on dates. Content can be treated as years older than it really is. What we found on this page the copyright line at the foot of this page carries no year, so there is nothing on the page as served to date it by The evidence, taken from the page as served The copyright line on this page, as served
This is the copyright line as the page serves it. It was read for a year, and carries none. stagram Find out how we use social media Press Office and News ReciteMe and Accessibility ยฉNewcastle City Council Privacy Notice Terms and conditions Contact Us Covid-19 support Listen and translate {"path":{"baseUrl":"\/","pathPrefix":"","c | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
▸https://newcastle.gov.uk/local-government/access-information-and-data/open-data/crisis-support-funding 31.0% Very likely 12 out of 67
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Fails · 5 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 AI systems are being turned away before they reach the site, and because the barrier sits outside the organisation's own systems, nobody inside can see it happening. Those systems carry on answering questions about the organisation, from other people's material rather than its own, so the conversation about it goes on without it and nobody has decided that. 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.newcastle.gov.uk · resolves to 194.61.173.205
Address trailwww.newcastle.gov.uk
Checked2026-09-17 16:33 UTC · request sent from 54.171.52.206 (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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MX01 | fail | the site took 425ms to start answering, past the point where an automated reader gives up and takes its answer from elsewhere | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check How quickly the page starts to answer when it is asked for. What good looks like The page starts answering within 250ms. Between 250 and 345ms is a warning; beyond 345ms is a fail, that being the point at which an automated reader gives up. Why it matters A page that is slow to answer is left behind: the reader gives up and takes its answer from someone else's material, so your own words play no part in it. What we found on this page the site took 425ms to start answering, past the point where an automated reader gives up and takes its answer from elsewhere The evidence, taken from the page as served How long this page took to start answering
Timed from the request leaving our checker to the first part of the answer coming back, on the page as served, so distance from the site plays its part. 345ms is the point beyond which an automated reader gives up.
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 starts answering within 250ms. 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 heading 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)
H2 Main navigation H2 Title H4 Have your say level jumped H1 Crisis support funding H2 Crisis support funding H2 The current year H2 Previous year's data H3 Most popular pages H3 We're on social media
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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT43 | fail | 1 fault in this page's construction change the structure anything reading it sees, so what is read is not quite the page that was published | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page's underlying construction holds together, or contains faults that change how it is read. What good looks like The page is built soundly enough that anything reading it sees the structure its author intended. Why it matters Anything reading the page has to take it apart before it can judge anything on it. Faults in construction can move where a section appears to end, place a heading inside a paragraph, or lose part of the page altogether. When that happens, what is read is not quite the page that was published, and neither is the answer built from it. The damage is invisible on screen, because a browser repairs quietly what a plain reader does not. What we found on this page 1 fault in this page's construction change the structure anything reading it sees, so what is read is not quite the page that was published The evidence, taken from the page as served Faults in the page's construction that change how it reads
Found while taking the page apart exactly as a reader would.
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 is built soundly enough that anything reading it sees the structure its author intended. 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 The page's headings begin at its top level, rather than starting part way down. What good looks like The page's headings begin with its top-level heading. Levels skipped further down are weighed under heading hierarchy, and a page with no top-level heading at all under the missing main heading, so each fault is marked once. Why it matters The page's structure starts part way down, below a top level that never opens it. Sections then sit under nothing, and anything filing content by structure starts in the wrong place. 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 (the starting level is marked)
H2 Main navigation level jumped H2 Title H4 Have your say H1 Crisis support funding H2 Crisis support funding H2 The current year H2 Previous year's data H3 Most popular pages H3 We're on social media
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 begin with its top-level heading. 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Warnings · 7 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT32 | warning | the page's meta description, the short summary it offers about itself, runs to 37 characters, too short to say what the page is about; a usable summary runs from 50 to 170 characters | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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 the page's meta description, the short summary it offers about itself, runs to 37 characters, too short to say what the page is about; a usable summary runs from 50 to 170 characters The evidence, taken from the page as served The page's description, as served
<meta name="description" content="The website of Newcastle City Council"/> | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT16 | warning | the page states nothing about itself in a form a machine can take as given, so who you are and what the page is about are worked out from its wording | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page states what it is, and the exact facts it carries, in a form a machine can take as given rather than work out from the wording. What good looks like The page states what it is in machine-readable form, and where it carries exact facts it states those too. A page of exact facts stating none of them is a fail; a narrative page without a block is a warning. Why it matters Where a page carries exact facts, an address, opening hours, a price, a date, leaving them only in prose means they are worked out rather than read, and that is where a wrong branch or an old price comes from. What we found on this page the page states nothing about itself in a form a machine can take as given, so who you are and what the page is about are worked out from its wording The evidence, taken from the page as served The head of this page, as served
The page was read for a short block of machine-readable detail saying what it is. The page's own words carry no exact facts of that kind. <head> <meta charset="utf-8"/> <style>/* @see https://github.com/aFarkas/lazysizes#broken-image-symbol */.js img.b-lazy:not([src]) { visibility: hidden; }/* @see https://github.com/aFarkas/lazysizes#automatically-setting-the-sizes-attribute */.js img.lazyloaded[data-sizes=auto] { display: block; width: 100%; }</style> <meta name="description" content="The website of Newcastle City Council"/> <meta name="geo.placename" content="Newcastle upon Tyne"/> <link rel="canonical" href="https://newcastle.gov.uk/local-government/access-information-and-data/open-data/crisis-support-funding"/> <link rel="icon" href="favicon.ico"/> <link rel="icon" sizes="16x16" href="/favicon-16x16.png"/> <link rel="icon" sizes="32x32" href="/favicon-32x32.png"/> <link rel="icon" sizes="96x96" href="/favicon-96x96.png"/> <link rel="icon" sizes="192x192" href="/android-chrome-192x192.png"/> <link rel="apple-touch-icon" href="/apple-touch-icon-60x60.png"/> <link rel="apple-touch-icon" sizes="72x72" href="/android-chrome-72x72.png"/> <link rel="apple-touch-icon" sizes="76x76" href="/apple-touch-icon-76x76.png"/> <link rel="apple-touch-icon" sizes="114x114" href="/apple-touch-icon-114x114.png"/> <link rel="apple-toโฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT40 | warning | the page offers no short summary for the services that show a preview of it, so each one composes its own from whatever it finds first on the page | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The short title, description and image the page offers to services that show a preview of it, and whether they match the page. What good looks like The page offers a summary for preview, and the summary is true to the page. Why it matters This summary travels further than the page does. It is what appears when the address is shared, and several services read it in preference to the page itself because it is short and already written for the purpose. Where it is absent, those services compose their own from whatever they find first, which is often navigation. Where it is present but out of step, the organisation is described to a wide audience by a sentence it wrote once and forgot. What we found on this page the page offers no short summary for the services that show a preview of it, so each one composes its own from whatever it finds first on the page The evidence, taken from the page as served The summary this page offers for preview
Read from the page as served.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT41 | warning | the page does not show where it sits in the site, so anything reading it on its own has nothing to say what it belongs to | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The trail showing the path from the front page to this one, and whether the machine-readable version of that trail says the same. What good looks like The page shows its place in the site, and says the same thing to a machine. Why it matters A page read on its own gives no sense of what it belongs to. The trail supplies it: one product within a range, one policy within a set. A reader deciding whether a page answers a question uses that to judge whether it has the right one, and how to describe it when it quotes it. Where the shown trail and the machine-readable one disagree, the page is placed in two positions at once and neither can be relied on. What we found on this page the page does not show where it sits in the site, so anything reading it on its own has nothing to say what it belongs to The evidence, taken from the page as served The path this page gives to itself
Read from the page as served: the trail shown to a reader, and the trail stated in a form a machine can take as given.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT04 | warning | the page shows the year 2023 in its text, but nothing on the page states it as the date of the content | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The page carries a date, ideally written into the markup rather than sitting only in the text. What good looks like The page carries a date, ideally written into the markup rather than sitting only in the text. Why it matters An undated page gives nothing to weigh its age against, so old and new material are treated alike. What we found on this page the page shows the year 2023 in its text, but nothing on the page states it as the date of the content The evidence, taken from the page as served The head of this page, as served
The head of the page was read for a tag stating the date of the content. The year shown above was found in the page's own text. <head> <meta charset="utf-8"/> <style>/* @see https://github.com/aFarkas/lazysizes#broken-image-symbol */.js img.b-lazy:not([src]) { visibility: hidden; }/* @see https://github.com/aFarkas/lazysizes#automatically-setting-the-sizes-attribute */.js img.lazyloaded[data-sizes=auto] { display: block; width: 100%; }</style> <meta name="description" content="The website of Newcastle City Council"/> <meta name="geo.placename" content="Newcastle upon Tyne"/> <link rel="canonical" href="https://newcastle.gov.uk/local-government/access-information-and-data/open-data/crisis-support-funding"/> <link rel="icon" href="favicon.ico"/> <link rel="icon" sizes="16x16" href="/favicon-16x16.png"/> <link rel="icon" sizes="32x32" href="/favicon-32x32.png"/> <link rel="icon" sizes="96x96" href="/favicon-96x96.png"/> <link rel="icon" sizes="192x192" href="/android-chrome-192x192.png"/> <link rel="apple-touch-icon" href="/apple-touch-icon-60x60.png"/> <link rel="apple-touch-icon" sizes="72x72" href="/android-chrome-72x72.png"/> <link rel="apple-touch-icon" sizes="76x76" href="/apple-touch-icon-76x76.png"/> <link rel="apple-touch-icon" sizes="114x114" href="/apple-touch-icon-114x114.png"/> <link rel="apple-toโฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT35 | warning | the copyright line at the foot of this page carries no year, so there is nothing on the page as served to date it by | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The copyright line at the foot of the page, and the year it states. What good looks like The copyright line states the current year. Why it matters An old copyright year reads as a site nobody is looking after, and it dates the page for anything that relies on dates. Content can be treated as years older than it really is. What we found on this page the copyright line at the foot of this page carries no year, so there is nothing on the page as served to date it by The evidence, taken from the page as served The copyright line on this page, as served
This is the copyright line as the page serves it. It was read for a year, and carries none. stagram Find out how we use social media Press Office and News ReciteMe and Accessibility ยฉNewcastle City Council Privacy Notice Terms and conditions Contact Us Covid-19 support Listen and translate {"path":{"baseUrl":"\/","pathPrefix":"","c | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MX10 | warning | 6 links to a file on this page do not say what the file is and how big it is before it is opened. A reader deciding whether to open a file has nothing to judge it by, and on a slow or metered connection an unnamed file is a risk rather than an offer. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Links that open a file, and whether the wording states the format and the size. What good looks like A link to a file states its format and its size. Why it matters A reader deciding whether to open a file has nothing to judge it by, and on a slow or metered connection an unnamed file is a risk rather than an offer. What we found on this page 6 links to a file on this page do not say what the file is and how big it is before it is opened. A reader deciding whether to open a file has nothing to judge it by, and on a slow or metered connection an unnamed file is a risk rather than an offer. The evidence, taken from the page as served The links to a file, and what each one states
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
▸https://newcastle.gov.uk/local-government/access-information-and-data/open-data/housing-benefit-and-council-tax-reduction 30.6% Very likely 13 out of 67
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Fails · 5 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 AI systems are being turned away before they reach the site, and because the barrier sits outside the organisation's own systems, nobody inside can see it happening. Those systems carry on answering questions about the organisation, from other people's material rather than its own, so the conversation about it goes on without it and nobody has decided that. 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.newcastle.gov.uk · resolves to 194.61.173.205
Address trailwww.newcastle.gov.uk
Checked2026-09-17 16:33 UTC · request sent from 54.171.52.206 (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 heading 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)
H2 Main navigation H2 Title H4 Have your say level jumped H1 Housing benefit and council tax reduction scheme data H2 Housing benefit and council tax reduction scheme data H2 This year's data H2 Previous year's data H2 Related Pages H3 Most popular pages H3 We're on social media
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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT43 | fail | 1 fault in this page's construction change the structure anything reading it sees, so what is read is not quite the page that was published | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page's underlying construction holds together, or contains faults that change how it is read. What good looks like The page is built soundly enough that anything reading it sees the structure its author intended. Why it matters Anything reading the page has to take it apart before it can judge anything on it. Faults in construction can move where a section appears to end, place a heading inside a paragraph, or lose part of the page altogether. When that happens, what is read is not quite the page that was published, and neither is the answer built from it. The damage is invisible on screen, because a browser repairs quietly what a plain reader does not. What we found on this page 1 fault in this page's construction change the structure anything reading it sees, so what is read is not quite the page that was published The evidence, taken from the page as served Faults in the page's construction that change how it reads
Found while taking the page apart exactly as a reader would.
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 is built soundly enough that anything reading it sees the structure its author intended. 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 | 4 link wording(s) are used for more than one destination, so the same words point at different pages: โbenefit capped claimsโ, โclaims affected by the 'bedroom tax'โ, โdiscretionary housing paymentsโ and 1 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 Identical links on one page lead to different places, so which one gets followed is a coin toss. A reader or system lands on the wrong page while believing it chose correctly. What we found on this page 4 link wording(s) are used for more than one destination, so the same words point at different pages: โbenefit capped claimsโ, โclaims affected by the 'bedroom tax'โ, โdiscretionary housing paymentsโ and 1 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 href="/sites/default/files/Council Tax/SSSC Bedroom Tax March 2021.pdf" title="Claims affected by the bedroom tax 2020/2021">Claims affected by the 'Bedroom Tax'</a> <a href="/sites/default/files/Council Tax/Bedroom Tax March2020.pdf" title="Claims affected by the bedroom tax 2019/2020">Claims affected by the 'Bedroom Tax'</a> <a href="/sites/default/files/Council%20Tax/SSSC%20March2019.pdf">Claims affected by the 'Bedroom Tax'</a> <a href="/sites/default/files/Bedroom Tax March 2018.pdf" title="Claims affected by the bedroom tax PDF 193kb">Claims affected by the 'Bedroom Tax'</a> <a href="https://newcastle.gov.uk/sites/default/files/Bedroom%20Tax%20March%202017.pdf" title="Claims affected by the bedroom tax 194kb">Claims affected by the 'Bedroom Tax'</a> <a href="/sites/default/files/Bedroom Tax March 2015.pdf" title="claims affected by bedroom tax, pdf, 190kb">Claims affected by the 'Bedroom Tax'</a> <a href="/sites/default/files/2013 Bedroom Tax.pdf" title="claims affected by the bedroom tax pdf 246kb">Claims affected by the 'Bedroom Tax'</a> <a href="/sites/default/files/Council Tax/Bencap March 2021.pdf" title="Benefit capped claims 2020/2021">Benefit Capped claims</a> <a href="/sites/default/files/Council Tax/Copy of Bencap Mar2020.pdf" title="Benefit capped claims 2019/2020">Benefit Capped claims</a> <a href="/sites/default/files/Council%20Tax/Bencap%20claims%20March%202019.pdf">Benefit Capped claims</a> …and 2 more like it. 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 The page's headings begin at its top level, rather than starting part way down. What good looks like The page's headings begin with its top-level heading. Levels skipped further down are weighed under heading hierarchy, and a page with no top-level heading at all under the missing main heading, so each fault is marked once. Why it matters The page's structure starts part way down, below a top level that never opens it. Sections then sit under nothing, and anything filing content by structure starts in the wrong place. 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 (the starting level is marked)
H2 Main navigation level jumped H2 Title H4 Have your say H1 Housing benefit and council tax reduction scheme data H2 Housing benefit and council tax reduction scheme data H2 This year's data H2 Previous year's data H2 Related Pages H3 Most popular pages H3 We're on social media
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 begin with its top-level heading. 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Warnings · 8 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT06 | warning | title length 78 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 that is too short or too long is liable to be rewritten elsewhere, and control of the page's name goes with it. What we found on this page title length 78 chars The evidence, taken from the page as served The page title, as served
<title>Housing benefit and council tax reduction scheme data | Newcastle City Council</title> | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT32 | warning | the page's meta description, the short summary it offers about itself, runs to 37 characters, too short to say what the page is about; a usable summary runs from 50 to 170 characters | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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 the page's meta description, the short summary it offers about itself, runs to 37 characters, too short to say what the page is about; a usable summary runs from 50 to 170 characters The evidence, taken from the page as served The page's description, as served
<meta name="description" content="The website of Newcastle City Council"/> | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT16 | warning | the page states nothing about itself in a form a machine can take as given, so who you are and what the page is about are worked out from its wording | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page states what it is, and the exact facts it carries, in a form a machine can take as given rather than work out from the wording. What good looks like The page states what it is in machine-readable form, and where it carries exact facts it states those too. A page of exact facts stating none of them is a fail; a narrative page without a block is a warning. Why it matters Where a page carries exact facts, an address, opening hours, a price, a date, leaving them only in prose means they are worked out rather than read, and that is where a wrong branch or an old price comes from. What we found on this page the page states nothing about itself in a form a machine can take as given, so who you are and what the page is about are worked out from its wording The evidence, taken from the page as served The head of this page, as served
The page was read for a short block of machine-readable detail saying what it is. The page's own words carry no exact facts of that kind. <head> <meta charset="utf-8"/> <style>/* @see https://github.com/aFarkas/lazysizes#broken-image-symbol */.js img.b-lazy:not([src]) { visibility: hidden; }/* @see https://github.com/aFarkas/lazysizes#automatically-setting-the-sizes-attribute */.js img.lazyloaded[data-sizes=auto] { display: block; width: 100%; }</style> <meta name="description" content="The website of Newcastle City Council"/> <meta name="geo.placename" content="Newcastle upon Tyne"/> <link rel="canonical" href="https://newcastle.gov.uk/local-government/access-information-and-data/open-data/housing-benefit-and-council-tax-reduction"/> <link rel="icon" href="favicon.ico"/> <link rel="icon" sizes="16x16" href="/favicon-16x16.png"/> <link rel="icon" sizes="32x32" href="/favicon-32x32.png"/> <link rel="icon" sizes="96x96" href="/favicon-96x96.png"/> <link rel="icon" sizes="192x192" href="/android-chrome-192x192.png"/> <link rel="apple-touch-icon" href="/apple-touch-icon-60x60.png"/> <link rel="apple-touch-icon" sizes="72x72" href="/android-chrome-72x72.png"/> <link rel="apple-touch-icon" sizes="76x76" href="/apple-touch-icon-76x76.png"/> <link rel="apple-touch-icon" sizes="114x114" href="/apple-touch-icon-114x114.png"/> โฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT40 | warning | the page offers no short summary for the services that show a preview of it, so each one composes its own from whatever it finds first on the page | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The short title, description and image the page offers to services that show a preview of it, and whether they match the page. What good looks like The page offers a summary for preview, and the summary is true to the page. Why it matters This summary travels further than the page does. It is what appears when the address is shared, and several services read it in preference to the page itself because it is short and already written for the purpose. Where it is absent, those services compose their own from whatever they find first, which is often navigation. Where it is present but out of step, the organisation is described to a wide audience by a sentence it wrote once and forgot. What we found on this page the page offers no short summary for the services that show a preview of it, so each one composes its own from whatever it finds first on the page The evidence, taken from the page as served The summary this page offers for preview
Read from the page as served.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT41 | warning | the page does not show where it sits in the site, so anything reading it on its own has nothing to say what it belongs to | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The trail showing the path from the front page to this one, and whether the machine-readable version of that trail says the same. What good looks like The page shows its place in the site, and says the same thing to a machine. Why it matters A page read on its own gives no sense of what it belongs to. The trail supplies it: one product within a range, one policy within a set. A reader deciding whether a page answers a question uses that to judge whether it has the right one, and how to describe it when it quotes it. Where the shown trail and the machine-readable one disagree, the page is placed in two positions at once and neither can be relied on. What we found on this page the page does not show where it sits in the site, so anything reading it on its own has nothing to say what it belongs to The evidence, taken from the page as served The path this page gives to itself
Read from the page as served: the trail shown to a reader, and the trail stated in a form a machine can take as given.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT04 | warning | the page shows the year 2026 in its text, but nothing on the page states it as the date of the content | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The page carries a date, ideally written into the markup rather than sitting only in the text. What good looks like The page carries a date, ideally written into the markup rather than sitting only in the text. Why it matters An undated page gives nothing to weigh its age against, so old and new material are treated alike. What we found on this page the page shows the year 2026 in its text, but nothing on the page states it as the date of the content The evidence, taken from the page as served The head of this page, as served
The head of the page was read for a tag stating the date of the content. The year shown above was found in the page's own text. <head> <meta charset="utf-8"/> <style>/* @see https://github.com/aFarkas/lazysizes#broken-image-symbol */.js img.b-lazy:not([src]) { visibility: hidden; }/* @see https://github.com/aFarkas/lazysizes#automatically-setting-the-sizes-attribute */.js img.lazyloaded[data-sizes=auto] { display: block; width: 100%; }</style> <meta name="description" content="The website of Newcastle City Council"/> <meta name="geo.placename" content="Newcastle upon Tyne"/> <link rel="canonical" href="https://newcastle.gov.uk/local-government/access-information-and-data/open-data/housing-benefit-and-council-tax-reduction"/> <link rel="icon" href="favicon.ico"/> <link rel="icon" sizes="16x16" href="/favicon-16x16.png"/> <link rel="icon" sizes="32x32" href="/favicon-32x32.png"/> <link rel="icon" sizes="96x96" href="/favicon-96x96.png"/> <link rel="icon" sizes="192x192" href="/android-chrome-192x192.png"/> <link rel="apple-touch-icon" href="/apple-touch-icon-60x60.png"/> <link rel="apple-touch-icon" sizes="72x72" href="/android-chrome-72x72.png"/> <link rel="apple-touch-icon" sizes="76x76" href="/apple-touch-icon-76x76.png"/> <link rel="apple-touch-icon" sizes="114x114" href="/apple-touch-icon-114x114.png"/> โฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT35 | warning | the copyright line at the foot of this page carries no year, so there is nothing on the page as served to date it by | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The copyright line at the foot of the page, and the year it states. What good looks like The copyright line states the current year. Why it matters An old copyright year reads as a site nobody is looking after, and it dates the page for anything that relies on dates. Content can be treated as years older than it really is. What we found on this page the copyright line at the foot of this page carries no year, so there is nothing on the page as served to date it by The evidence, taken from the page as served The copyright line on this page, as served
This is the copyright line as the page serves it. It was read for a year, and carries none. stagram Find out how we use social media Press Office and News ReciteMe and Accessibility ยฉNewcastle City Council Privacy Notice Terms and conditions Contact Us Covid-19 support Listen and translate {"path":{"baseUrl":"\/","pathPrefix":"","c | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MX10 | warning | 5 links to a file on this page do not say what the file is and how big it is before it is opened. A reader deciding whether to open a file has nothing to judge it by, and on a slow or metered connection an unnamed file is a risk rather than an offer. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Links that open a file, and whether the wording states the format and the size. What good looks like A link to a file states its format and its size. Why it matters A reader deciding whether to open a file has nothing to judge it by, and on a slow or metered connection an unnamed file is a risk rather than an offer. What we found on this page 5 links to a file on this page do not say what the file is and how big it is before it is opened. A reader deciding whether to open a file has nothing to judge it by, and on a slow or metered connection an unnamed file is a risk rather than an offer. The evidence, taken from the page as served The links to a file, and what each one states
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
▸https://newcastle.gov.uk/fairtrade 31.5% Very likely 11 out of 67
The page https://newcastle.gov.uk/fairtrade
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Fails · 5 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 AI systems are being turned away before they reach the site, and because the barrier sits outside the organisation's own systems, nobody inside can see it happening. Those systems carry on answering questions about the organisation, from other people's material rather than its own, so the conversation about it goes on without it and nobody has decided that. 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.newcastle.gov.uk · resolves to 194.61.173.205
Address trailwww.newcastle.gov.uk
Checked2026-09-17 16:33 UTC · request sent from 54.171.52.206 (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 | 2 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 heading 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 2 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)
H2 Main navigation H2 Title H4 Have your say level jumped H1 Newcastle Fairtrade Partnership H2 Newcastle Fairtrade Partnership H3 The Newcastle Fairtrade Directory H2 The Newcastle upon Tyne Fairtrade Directory H3 Welcome Students! H3 What is Fairtrade? H3 Newcastle is a Fairtrade City H3 Newcastle Fairtrade Partnership H2 Did you know? H2 Related Pages H4 Need more information? level jumped H3 Most popular pages H3 We're on social media
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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT43 | fail | 1 fault in this page's construction change the structure anything reading it sees, so what is read is not quite the page that was published | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page's underlying construction holds together, or contains faults that change how it is read. What good looks like The page is built soundly enough that anything reading it sees the structure its author intended. Why it matters Anything reading the page has to take it apart before it can judge anything on it. Faults in construction can move where a section appears to end, place a heading inside a paragraph, or lose part of the page altogether. When that happens, what is read is not quite the page that was published, and neither is the answer built from it. The damage is invisible on screen, because a browser repairs quietly what a plain reader does not. What we found on this page 1 fault in this page's construction change the structure anything reading it sees, so what is read is not quite the page that was published The evidence, taken from the page as served Faults in the page's construction that change how it reads
Found while taking the page apart exactly as a reader would.
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 is built soundly enough that anything reading it sees the structure its author intended. 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 The page's headings begin at its top level, rather than starting part way down. What good looks like The page's headings begin with its top-level heading. Levels skipped further down are weighed under heading hierarchy, and a page with no top-level heading at all under the missing main heading, so each fault is marked once. Why it matters The page's structure starts part way down, below a top level that never opens it. Sections then sit under nothing, and anything filing content by structure starts in the wrong place. 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 (the starting level is marked)
H2 Main navigation level jumped H2 Title H4 Have your say H1 Newcastle Fairtrade Partnership H2 Newcastle Fairtrade Partnership H3 The Newcastle Fairtrade Directory H2 The Newcastle upon Tyne Fairtrade Directory H3 Welcome Students! H3 What is Fairtrade? H3 Newcastle is a Fairtrade City H3 Newcastle Fairtrade Partnership H2 Did you know? H2 Related Pages H4 Need more information? H3 Most popular pages H3 We're on social media
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 begin with its top-level heading. 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| DS28 | fail | one link to sources on other sites is dead: asked for in full, the address answers that the page is not there. 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 cites as evidence cannot be reached by an AI, whether dead, the address answering that the page is not there or blocked to automated callers, so its claims rest on material an AI cannot check. In a regulated business that is the difference between an evidenced statement and a bare assertion. What we found on this page one link to sources on other sites is dead: asked for in full, the address answers that the page is not there. 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 fails here fails in one of two ways, and the report names them apart. A DEAD link answers, when the page is asked for in full, that the page is not there. An AI-BLOCKED link points at a page that is still published and opens for a person in a browser, but the destination refuses callers that are not a person browsing, so an AI never receives it. Opening such a link by hand proves only the human route; this assessment reflects the AI position, and from the AI position both classes land in the same place: the material this page offers as its support does not come back when it is 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. An AI-blocked 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. An AI-block on 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Warnings · 6 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT16 | warning | the page states nothing about itself in a form a machine can take as given, so who you are and what the page is about are worked out from its wording | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page states what it is, and the exact facts it carries, in a form a machine can take as given rather than work out from the wording. What good looks like The page states what it is in machine-readable form, and where it carries exact facts it states those too. A page of exact facts stating none of them is a fail; a narrative page without a block is a warning. Why it matters Where a page carries exact facts, an address, opening hours, a price, a date, leaving them only in prose means they are worked out rather than read, and that is where a wrong branch or an old price comes from. What we found on this page the page states nothing about itself in a form a machine can take as given, so who you are and what the page is about are worked out from its wording The evidence, taken from the page as served The head of this page, as served
The page was read for a short block of machine-readable detail saying what it is. The page's own words carry no exact facts of that kind. <head> <meta charset="utf-8"/> <style>/* @see https://github.com/aFarkas/lazysizes#broken-image-symbol */.js img.b-lazy:not([src]) { visibility: hidden; }/* @see https://github.com/aFarkas/lazysizes#automatically-setting-the-sizes-attribute */.js img.lazyloaded[data-sizes=auto] { display: block; width: 100%; }</style> <meta name="description" content="The website of Newcastle City Council. Information about Newcastle Fairtrade Partnership."/> <meta name="geo.placename" content="Newcastle upon Tyne"/> <link rel="canonical" href="https://newcastle.gov.uk/fairtrade"/> <link rel="icon" href="favicon.ico"/> <link rel="icon" sizes="16x16" href="/favicon-16x16.png"/> <link rel="icon" sizes="32x32" href="/favicon-32x32.png"/> <link rel="icon" sizes="96x96" href="/favicon-96x96.png"/> <link rel="icon" sizes="192x192" href="/android-chrome-192x192.png"/> <link rel="apple-touch-icon" href="/apple-touch-icon-60x60.png"/> <link rel="apple-touch-icon" sizes="72x72" href="/android-chrome-72x72.png"/> <link rel="apple-touch-icon" sizes="76x76" href="/apple-touch-icon-76x76.png"/> <link rel="apple-touch-icon" sizes="114x114" href="/apple-touch-icon-114x114.png"/> <link rel="apple-touch-icon" sizes=โฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT40 | warning | the page offers no short summary for the services that show a preview of it, so each one composes its own from whatever it finds first on the page | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The short title, description and image the page offers to services that show a preview of it, and whether they match the page. What good looks like The page offers a summary for preview, and the summary is true to the page. Why it matters This summary travels further than the page does. It is what appears when the address is shared, and several services read it in preference to the page itself because it is short and already written for the purpose. Where it is absent, those services compose their own from whatever they find first, which is often navigation. Where it is present but out of step, the organisation is described to a wide audience by a sentence it wrote once and forgot. What we found on this page the page offers no short summary for the services that show a preview of it, so each one composes its own from whatever it finds first on the page The evidence, taken from the page as served The summary this page offers for preview
Read from the page as served.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT41 | warning | the page does not show where it sits in the site, so anything reading it on its own has nothing to say what it belongs to | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The trail showing the path from the front page to this one, and whether the machine-readable version of that trail says the same. What good looks like The page shows its place in the site, and says the same thing to a machine. Why it matters A page read on its own gives no sense of what it belongs to. The trail supplies it: one product within a range, one policy within a set. A reader deciding whether a page answers a question uses that to judge whether it has the right one, and how to describe it when it quotes it. Where the shown trail and the machine-readable one disagree, the page is placed in two positions at once and neither can be relied on. What we found on this page the page does not show where it sits in the site, so anything reading it on its own has nothing to say what it belongs to The evidence, taken from the page as served The path this page gives to itself
Read from the page as served: the trail shown to a reader, and the trail stated in a form a machine can take as given.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT04 | warning | the page shows the year 2025 in its text, but nothing on the page states it as the date of the content | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The page carries a date, ideally written into the markup rather than sitting only in the text. What good looks like The page carries a date, ideally written into the markup rather than sitting only in the text. Why it matters An undated page gives nothing to weigh its age against, so old and new material are treated alike. What we found on this page the page shows the year 2025 in its text, but nothing on the page states it as the date of the content The evidence, taken from the page as served The head of this page, as served
The head of the page was read for a tag stating the date of the content. The year shown above was found in the page's own text. <head> <meta charset="utf-8"/> <style>/* @see https://github.com/aFarkas/lazysizes#broken-image-symbol */.js img.b-lazy:not([src]) { visibility: hidden; }/* @see https://github.com/aFarkas/lazysizes#automatically-setting-the-sizes-attribute */.js img.lazyloaded[data-sizes=auto] { display: block; width: 100%; }</style> <meta name="description" content="The website of Newcastle City Council. Information about Newcastle Fairtrade Partnership."/> <meta name="geo.placename" content="Newcastle upon Tyne"/> <link rel="canonical" href="https://newcastle.gov.uk/fairtrade"/> <link rel="icon" href="favicon.ico"/> <link rel="icon" sizes="16x16" href="/favicon-16x16.png"/> <link rel="icon" sizes="32x32" href="/favicon-32x32.png"/> <link rel="icon" sizes="96x96" href="/favicon-96x96.png"/> <link rel="icon" sizes="192x192" href="/android-chrome-192x192.png"/> <link rel="apple-touch-icon" href="/apple-touch-icon-60x60.png"/> <link rel="apple-touch-icon" sizes="72x72" href="/android-chrome-72x72.png"/> <link rel="apple-touch-icon" sizes="76x76" href="/apple-touch-icon-76x76.png"/> <link rel="apple-touch-icon" sizes="114x114" href="/apple-touch-icon-114x114.png"/> <link rel="apple-touch-icon" sizes=โฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT35 | warning | the copyright line at the foot of this page carries no year, so there is nothing on the page as served to date it by | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The copyright line at the foot of the page, and the year it states. What good looks like The copyright line states the current year. Why it matters An old copyright year reads as a site nobody is looking after, and it dates the page for anything that relies on dates. Content can be treated as years older than it really is. What we found on this page the copyright line at the foot of this page carries no year, so there is nothing on the page as served to date it by The evidence, taken from the page as served The copyright line on this page, as served
This is the copyright line as the page serves it. It was read for a year, and carries none. stagram Find out how we use social media Press Office and News ReciteMe and Accessibility ยฉNewcastle City Council Privacy Notice Terms and conditions Contact Us Covid-19 support Listen and translate {"path":{"baseUrl":"\/","pathPrefix":"","c | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS13 | warning | 2 of 2 iframes untitled | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Each embedded panel on the page carries a title saying what it contains. What good looks like Each embedded panel carries a title saying what it contains. Why it matters Content brought into the page from elsewhere, a map, a form, a video player, carries no name saying what it is. Anything reading the page sees a hole where that content sits. What we found on this page 2 of 2 iframes untitled The evidence, taken from the page as served The iframes with no title attribute, as served
<iframe style="border-style:none;overflow:hidden;" src="https://www.facebook.com/plugins/video.php?height=314&href=https%3A%2F%2Fwww.facebook.com%2Fnewcastlefairtrade%2Fvideos%2F1107758711514983%2F&show_text=false&width=560&t=0" width="560" height="314" scrolling="no" frameborder="0" allowfullscreen="trโฆ <iframe style="border-style:none;overflow:hidden;" allow="autoplay; clipboard-write; encrypted-media; picture-in-picture; web-share" allowfullscreen="true" frameborder="0" height="314" scrolling="no" src="https://www.facebook.com/plugins/video.php?height=314&href=https%3A%2F%2Fwww.facebook.com%2Fnewcastlefairtrade%โฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
▸https://newcastle.gov.uk/get-involved/grants-and-funding 10.1% Extremely likely 13 out of 67
The page https://newcastle.gov.uk/get-involved/grants-and-funding
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Fails · 3 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 AI systems are being turned away before they reach the site, and because the barrier sits outside the organisation's own systems, nobody inside can see it happening. Those systems carry on answering questions about the organisation, from other people's material rather than its own, so the conversation about it goes on without it and nobody has decided that. 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.newcastle.gov.uk · resolves to 194.61.173.205
Address trailwww.newcastle.gov.uk
Checked2026-09-17 16:33 UTC · request sent from 54.171.52.206 (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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| DS18 | fail | the site's own list of its pages offers this page at one address and the page then names a different one as its preferred address, so a reader following the list arrives somewhere the page disowns | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Pages that name more than one preferred address, with the declarations disagreeing. What good looks like A page's preferred-address declarations agree with one another. Why it matters The page gives two different answers about which of its addresses is the official one. A contradiction like that gets ignored, so outside systems decide for themselves which copy of the page to use. What we found on this page the site's own list of its pages offers this page at one address and the page then names a different one as its preferred address, so a reader following the list arrives somewhere the page disowns The evidence, taken from the page as served The address this page is listed at, and the address it prefers
Read from the site's own list of its pages and from the page itself.
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's preferred-address declarations agree with one another. 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| DS35 | fail | the site answered as though it were serving a page, but what came back is a notice about the site itself rather than its content ("thank you for your patience"), running to 292 characters. What was measured here describes that notice, not the organisation's own page. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the address answered with the organisation's own content, or with a notice about the site itself: a queue, an overflow message or a maintenance window. What good looks like The address serves the organisation's own content. Why it matters A site under load or in maintenance often answers as though nothing were wrong, returning a short notice in place of the page. Anything reading it, a person or an AI system, receives that notice as the organisation's page and takes it as what the organisation has to say. Where this happens across the site, an assessment of it describes the notice rather than the estate, and any figure drawn from it has to be read in that light. What we found on this page the site answered as though it were serving a page, but what came back is a notice about the site itself rather than its content ("thank you for your patience"), running to 292 characters. What was measured here describes that notice, not the organisation's own page. The evidence, taken from the page as served What this address served, as served
The address answered as though it were a real page. Its text was read for the wording a site uses when it is telling visitors it cannot serve them right now. Grants and funding | Newcastle City Council Skip to main content Grants and funding Services Menu Main navigation News Pay My portal Listen and translate Search Services menu Adult social care Benefits and money advice Births, deaths, marriages and ceremonies Budget, policies, performance and data Business and commerce Children and families Communities and neighbourhoods Council and elections Council tax Environment, parks and allotments Housing Jobs, careers and skills Libraries Licences and permits Parking and bus lanes Planning and building control Public health Recycling and waste Roads, streets and travel Schools and education Topics Asylum and refugees Climate change Cost of living support Customer commitment Improvements to our website You may notice that some pages look different while we update and improve our online services. During this work you can use our services as normal. 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 address serves the organisation's own 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Warnings · 10 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT16 | warning | the page states nothing about itself in a form a machine can take as given, so who you are and what the page is about are worked out from its wording | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page states what it is, and the exact facts it carries, in a form a machine can take as given rather than work out from the wording. What good looks like The page states what it is in machine-readable form, and where it carries exact facts it states those too. A page of exact facts stating none of them is a fail; a narrative page without a block is a warning. Why it matters Where a page carries exact facts, an address, opening hours, a price, a date, leaving them only in prose means they are worked out rather than read, and that is where a wrong branch or an old price comes from. What we found on this page the page states nothing about itself in a form a machine can take as given, so who you are and what the page is about are worked out from its wording The evidence, taken from the page as served The head of this page, as served
The page was read for a short block of machine-readable detail saying what it is. The page's own words carry no exact facts of that kind. <head> <meta charset="utf-8"/> <meta name="description" content="Financial support for community and voluntary organisations"/> <link rel="canonical" href="https://new.newcastle.gov.uk/communities/grants-funding"/> <meta name="Generator" content="Drupal 10 (LocalGov Drupal | https://localgovdrupal.org)"/> <meta name="MobileOptimized" content="width"/> <meta name="HandheldFriendly" content="true"/> <meta name="viewport" content="width=device-width, initial-scale=1.0"/> <link rel="icon" href="/sites/default/files/ncc-favicon_0.ico" type="image/vnd.microsoft.icon"/> <script src="/sites/default/files/google_tag/ncc_default/google_tag.script.js?tlij1z" defer="defer"/> <title>Grants and funding | Newcastle City Council</title> <link rel="stylesheet" media="all" href="/modules/contrib/localgov_paragraphs/modules/localgov_subsites_paragraphs/css/localgov-subsites-paragraphs.css?tlij1z"/> <link rel="stylesheet" media="all" href="/core/themes/stable9/css/system/components/align.module.css?tlij1z"/> <link rel="stylesheet" media="all" href="/core/themes/stable9/css/system/components/fieldgroup.module.css?tlij1z"/> <link rel="stylesheet" media="all" href="/core/themes/stable9/css/system/componeโฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT40 | warning | the page offers no short summary for the services that show a preview of it, so each one composes its own from whatever it finds first on the page | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The short title, description and image the page offers to services that show a preview of it, and whether they match the page. What good looks like The page offers a summary for preview, and the summary is true to the page. Why it matters This summary travels further than the page does. It is what appears when the address is shared, and several services read it in preference to the page itself because it is short and already written for the purpose. Where it is absent, those services compose their own from whatever they find first, which is often navigation. Where it is present but out of step, the organisation is described to a wide audience by a sentence it wrote once and forgot. What we found on this page the page offers no short summary for the services that show a preview of it, so each one composes its own from whatever it finds first on the page The evidence, taken from the page as served The summary this page offers for preview
Read from the page as served.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT41 | warning | the page shows where it sits in the site but does not state it in a form a machine can take as given | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The trail showing the path from the front page to this one, and whether the machine-readable version of that trail says the same. What good looks like The page shows its place in the site, and says the same thing to a machine. Why it matters A page read on its own gives no sense of what it belongs to. The trail supplies it: one product within a range, one policy within a set. A reader deciding whether a page answers a question uses that to judge whether it has the right one, and how to describe it when it quotes it. Where the shown trail and the machine-readable one disagree, the page is placed in two positions at once and neither can be relied on. What we found on this page the page shows where it sits in the site but does not state it in a form a machine can take as given The evidence, taken from the page as served The path this page gives to itself
Read from the page as served: the trail shown to a reader, and the trail stated in a form a machine can take as given.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT04 | warning | the page carries no date, so there is nothing on it saying how current its content is | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The page carries a date, ideally written into the markup rather than sitting only in the text. What good looks like The page carries a date, ideally written into the markup rather than sitting only in the text. Why it matters An undated page gives nothing to weigh its age against, so old and new material are treated alike. What we found on this page the page carries no date, so there is nothing on it saying how current its content is The evidence, taken from the page as served The head of this page, as served
The head of the page and the page's own text were read for a date. <head> <meta charset="utf-8"/> <meta name="description" content="Financial support for community and voluntary organisations"/> <link rel="canonical" href="https://new.newcastle.gov.uk/communities/grants-funding"/> <meta name="Generator" content="Drupal 10 (LocalGov Drupal | https://localgovdrupal.org)"/> <meta name="MobileOptimized" content="width"/> <meta name="HandheldFriendly" content="true"/> <meta name="viewport" content="width=device-width, initial-scale=1.0"/> <link rel="icon" href="/sites/default/files/ncc-favicon_0.ico" type="image/vnd.microsoft.icon"/> <script src="/sites/default/files/google_tag/ncc_default/google_tag.script.js?tlij1z" defer="defer"/> <title>Grants and funding | Newcastle City Council</title> <link rel="stylesheet" media="all" href="/modules/contrib/localgov_paragraphs/modules/localgov_subsites_paragraphs/css/localgov-subsites-paragraphs.css?tlij1z"/> <link rel="stylesheet" media="all" href="/core/themes/stable9/css/system/components/align.module.css?tlij1z"/> <link rel="stylesheet" media="all" href="/core/themes/stable9/css/system/components/fieldgroup.module.css?tlij1z"/> <link rel="stylesheet" media="all" href="/core/themes/stable9/css/system/componeโฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR13 | warning | only 292 characters of this page read as its own content, so either the page is thin or its own words cannot be told apart from the parts 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 only 292 characters of this page read as its own content, so either the page is thin or its own words cannot be told apart from the parts repeated across the site The evidence, taken from the page as served The main text extracted from the page, as served
Grants and funding Financial support for community and voluntary organisations Funding for voluntary and community organisations Support to help voluntary and community (VCS) organisations run projects and events for Newcastle residents. Give feedback and let us know if this page was helpful | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT35 | warning | the copyright line at the foot of this page carries no year, so there is nothing on the page as served to date it by | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The copyright line at the foot of the page, and the year it states. What good looks like The copyright line states the current year. Why it matters An old copyright year reads as a site nobody is looking after, and it dates the page for anything that relies on dates. Content can be treated as years older than it really is. What we found on this page the copyright line at the foot of this page carries no year, so there is nothing on the page as served to date it by The evidence, taken from the page as served The copyright line on this page, as served
This is the copyright line as the page serves it. It was read for a year, and carries none. ch and comment on planning applications Footer Accessibility Privacy Terms and conditions ยฉNewcastle City Council {"path":{"baseUrl":"\/","pathPrefix":"","currentPath":"node\/277","currentPathIsAdmin":false,"isFront":false,"currentLanguage": | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT24 | warning | the page's own content runs to 292 characters | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The page holds enough main text to be substantive, measured against a 400 character floor. What good looks like The page holds enough main text to be substantive. Why it matters A page of a few sentences offers almost nothing to quote, so it adds little beyond its own existence. What we found on this page the page's own content runs to 292 characters The evidence, taken from the page as served How much of this page is its own content
Counted from the page as served, before any script runs. The page's own content is the part it marks out as its main content; where it marks out none, the whole of its text is counted.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT13 | warning | main content is 16% of the page's text; the shared furniture around it dominates what is read out | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check How much of the page's text sits in the main content region rather than in surrounding furniture. What good looks like Most of the page's text sits in its main content region rather than in the surrounding furniture. Why it matters Most of what this page serves is menus and repeated furniture rather than its own words, so what a system takes away is mostly padding, with the real message diluted or lost. What we found on this page main content is 16% of the page's text; the shared furniture around it dominates what is read out The evidence, taken from the page as served How much of this page is its own content
Counted from the page as served, before any script runs. The rest is the menus, header and foot-of-page text that appear on other pages of the site as well.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AJ07 | warning | 1 required field(s) have no tie in the page's code between the field and its error message, so which field an error belongs to rests on layout alone | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether required form fields are linked in the markup to the error messages about them. What good looks like Each required field is tied in the markup to the message that describes its error. Why it matters An error message sits on the page with nothing tying it to the field it concerns, so the correction has no anchor. What we found on this page 1 required field(s) have no tie in the page's code between the field and its error message, so which field an error belongs to rests on layout alone The evidence, taken from the page as served The required fields with no error association, as served
<input data-drupal-selector="edit-s" placeholder="Search" type="text" id="edit-s--2" name="s" value="" size="30" maxlength="128" class="form-text required" required="required" aria-required="true"/> | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS13 | warning | 1 of 1 iframes untitled | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Each embedded panel on the page carries a title saying what it contains. What good looks like Each embedded panel carries a title saying what it contains. Why it matters Content brought into the page from elsewhere, a map, a form, a video player, carries no name saying what it is. Anything reading the page sees a hole where that content sits. What we found on this page 1 of 1 iframes untitled The evidence, taken from the page as served The iframes with no title attribute, as served
<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-W7BB9DGL" height="0" width="0" style="display:none;visibility:hidden"/> | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
▸https://newcastle.gov.uk/holocaust-memorial-day-2025 30.3% Very likely 12 out of 67
The page https://newcastle.gov.uk/holocaust-memorial-day-2025
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Fails · 6 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 AI systems are being turned away before they reach the site, and because the barrier sits outside the organisation's own systems, nobody inside can see it happening. Those systems carry on answering questions about the organisation, from other people's material rather than its own, so the conversation about it goes on without it and nobody has decided that. 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.newcastle.gov.uk · resolves to 194.61.173.205
Address trailwww.newcastle.gov.uk
Checked2026-09-17 16:33 UTC · request sent from 54.171.52.206 (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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MX01 | fail | the site took 410ms to start answering, past the point where an automated reader gives up and takes its answer from elsewhere | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check How quickly the page starts to answer when it is asked for. What good looks like The page starts answering within 250ms. Between 250 and 345ms is a warning; beyond 345ms is a fail, that being the point at which an automated reader gives up. Why it matters A page that is slow to answer is left behind: the reader gives up and takes its answer from someone else's material, so your own words play no part in it. What we found on this page the site took 410ms to start answering, past the point where an automated reader gives up and takes its answer from elsewhere The evidence, taken from the page as served How long this page took to start answering
Timed from the request leaving our checker to the first part of the answer coming back, on the page as served, so distance from the site plays its part. 345ms is the point beyond which an automated reader gives up.
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 starts answering within 250ms. 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 heading 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)
H2 Main navigation H2 Title H4 Have your say level jumped H1 Holocaust Memorial Day 2025 H2 Holocaust Memorial Day 2025 H2 Holocaust Memorial Day 2025 - For a Better Future H2 Newcastle's Holocaust Memorial Day Programme H4 Numbers and Labels: The Jews of Pardubice - Exhibition level jumped H4 Brundibรกr Arts Festival H4 Brundibรกr Arts festival opening concert: Composers forced to exile in the US H4 Brundibรกr Arts festival: ย Music, Migration and Mobility Exhibition H4 Brundibรกr Arts festival: ย Cabaret - What a Life by Hans Gaฬl H4 A Living Tradition: Remembering the Relief of Belsen H4 Acknowledging the Past for a Better Future - Exhibition H4 Roma Holocaust - Commemorative Event H4 Brundibรกr Arts festival: ย In Exile - Closing concert H4 For a Better Future: Holocaust Memorial Day Commemorative Event H4 Peace is Personal - Talk H4 Turning to Face the Sun - Performance event H4 When the Holocaust became the Holocaust: Changing imaginations of genocide in th H2 Take part in Holocaust Memorial Day H4 Holocaust Memorial Day Online level jumped H4 Organise an activity H4 Light the Darkness H3 Next:
Previous Holocaust Memorial Days H3 Most popular pages H3 We're on social media
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 | fail | this page carries opening hours, and states none of it in a form a machine can take as given, so those facts have to be worked out from the wording around them | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page states what it is, and the exact facts it carries, in a form a machine can take as given rather than work out from the wording. What good looks like The page states what it is in machine-readable form, and where it carries exact facts it states those too. A page of exact facts stating none of them is a fail; a narrative page without a block is a warning. Why it matters Where a page carries exact facts, an address, opening hours, a price, a date, leaving them only in prose means they are worked out rather than read, and that is where a wrong branch or an old price comes from. What we found on this page this page carries opening hours, and states none of it in a form a machine can take as given, so those facts have to be worked out from the wording around them The evidence, taken from the page as served The head of this page, as served
The page was read for a short block of machine-readable detail saying what it is. The page's own words carry opening hours, which is why this weighs as it does. <head> <meta charset="utf-8"/> <style>/* @see https://github.com/aFarkas/lazysizes#broken-image-symbol */.js img.b-lazy:not([src]) { visibility: hidden; }/* @see https://github.com/aFarkas/lazysizes#automatically-setting-the-sizes-attribute */.js img.lazyloaded[data-sizes=auto] { display: block; width: 100%; }</style> <meta name="description" content="The website of Newcastle City Council"/> <meta name="geo.placename" content="Newcastle upon Tyne"/> <link rel="canonical" href="https://newcastle.gov.uk/holocaust-memorial-day-2025"/> <link rel="icon" href="favicon.ico"/> <link rel="icon" sizes="16x16" href="/favicon-16x16.png"/> <link rel="icon" sizes="32x32" href="/favicon-32x32.png"/> <link rel="icon" sizes="96x96" href="/favicon-96x96.png"/> <link rel="icon" sizes="192x192" href="/android-chrome-192x192.png"/> <link rel="apple-touch-icon" href="/apple-touch-icon-60x60.png"/> <link rel="apple-touch-icon" sizes="72x72" href="/android-chrome-72x72.png"/> <link rel="apple-touch-icon" sizes="76x76" href="/apple-touch-icon-76x76.png"/> <link rel="apple-touch-icon" sizes="114x114" href="/apple-touch-icon-114x114.png"/> <link rel="apple-touch-icon" sizes="120x120" href="/apple-touch-icon-โฆ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 states what it is in machine-readable form, and where it carries exact facts it states those too. 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT43 | fail | 1 fault in this page's construction change the structure anything reading it sees, so what is read is not quite the page that was published | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page's underlying construction holds together, or contains faults that change how it is read. What good looks like The page is built soundly enough that anything reading it sees the structure its author intended. Why it matters Anything reading the page has to take it apart before it can judge anything on it. Faults in construction can move where a section appears to end, place a heading inside a paragraph, or lose part of the page altogether. When that happens, what is read is not quite the page that was published, and neither is the answer built from it. The damage is invisible on screen, because a browser repairs quietly what a plain reader does not. What we found on this page 1 fault in this page's construction change the structure anything reading it sees, so what is read is not quite the page that was published The evidence, taken from the page as served Faults in the page's construction that change how it reads
Found while taking the page apart exactly as a reader would.
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 is built soundly enough that anything reading it sees the structure its author intended. 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 The page's headings begin at its top level, rather than starting part way down. What good looks like The page's headings begin with its top-level heading. Levels skipped further down are weighed under heading hierarchy, and a page with no top-level heading at all under the missing main heading, so each fault is marked once. Why it matters The page's structure starts part way down, below a top level that never opens it. Sections then sit under nothing, and anything filing content by structure starts in the wrong place. 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 (the starting level is marked)
H2 Main navigation level jumped H2 Title H4 Have your say H1 Holocaust Memorial Day 2025 H2 Holocaust Memorial Day 2025 H2 Holocaust Memorial Day 2025 - For a Better Future H2 Newcastle's Holocaust Memorial Day Programme H4 Numbers and Labels: The Jews of Pardubice - Exhibition H4 Brundibรกr Arts Festival H4 Brundibรกr Arts festival opening concert: Composers forced to exile in the US H4 Brundibรกr Arts festival: ย Music, Migration and Mobility Exhibition H4 Brundibรกr Arts festival: ย Cabaret - What a Life by Hans Gaฬl H4 A Living Tradition: Remembering the Relief of Belsen H4 Acknowledging the Past for a Better Future - Exhibition H4 Roma Holocaust - Commemorative Event H4 Brundibรกr Arts festival: ย In Exile - Closing concert H4 For a Better Future: Holocaust Memorial Day Commemorative Event H4 Peace is Personal - Talk H4 Turning to Face the Sun - Performance event H4 When the Holocaust became the Holocaust: Changing imaginations of genocide in th H2 Take part in Holocaust Memorial Day H4 Holocaust Memorial Day Online H4 Organise an activity H4 Light the Darkness H3 Next:
Previous Holocaust Memorial Days H3 Most popular pages H3 We're on social media
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 begin with its top-level heading. 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Warnings · 6 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT32 | warning | the page's meta description, the short summary it offers about itself, runs to 37 characters, too short to say what the page is about; a usable summary runs from 50 to 170 characters | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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 the page's meta description, the short summary it offers about itself, runs to 37 characters, too short to say what the page is about; a usable summary runs from 50 to 170 characters The evidence, taken from the page as served The page's description, as served
<meta name="description" content="The website of Newcastle City Council"/> | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT40 | warning | the page offers no short summary for the services that show a preview of it, so each one composes its own from whatever it finds first on the page | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The short title, description and image the page offers to services that show a preview of it, and whether they match the page. What good looks like The page offers a summary for preview, and the summary is true to the page. Why it matters This summary travels further than the page does. It is what appears when the address is shared, and several services read it in preference to the page itself because it is short and already written for the purpose. Where it is absent, those services compose their own from whatever they find first, which is often navigation. Where it is present but out of step, the organisation is described to a wide audience by a sentence it wrote once and forgot. What we found on this page the page offers no short summary for the services that show a preview of it, so each one composes its own from whatever it finds first on the page The evidence, taken from the page as served The summary this page offers for preview
Read from the page as served.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT41 | warning | the page does not show where it sits in the site, so anything reading it on its own has nothing to say what it belongs to | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The trail showing the path from the front page to this one, and whether the machine-readable version of that trail says the same. What good looks like The page shows its place in the site, and says the same thing to a machine. Why it matters A page read on its own gives no sense of what it belongs to. The trail supplies it: one product within a range, one policy within a set. A reader deciding whether a page answers a question uses that to judge whether it has the right one, and how to describe it when it quotes it. Where the shown trail and the machine-readable one disagree, the page is placed in two positions at once and neither can be relied on. What we found on this page the page does not show where it sits in the site, so anything reading it on its own has nothing to say what it belongs to The evidence, taken from the page as served The path this page gives to itself
Read from the page as served: the trail shown to a reader, and the trail stated in a form a machine can take as given.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| IN21 | warning | 2 claims of being best, largest or leading are made on this page with no figure or source beside it, such as โthe largestโ. Taken out and repeated, a claim like this carries the weight of a measured fact while resting on nothing. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Claims of being largest, leading, best or first in the page's words, and whether a figure or a source sits in the same passage. What good looks like A claim of standing carries the figure or the source that supports it. Why it matters A claim of standing with no figure beside it is a statement about the organisation made by the organisation. Taken out and repeated, it carries the weight of a measured fact while resting on nothing. What we found on this page 2 claims of being best, largest or leading are made on this page with no figure or source beside it, such as โthe largestโ. Taken out and repeated, a claim like this carries the weight of a measured fact while resting on nothing. The evidence, taken from the page as served The claims of standing made with no figure or source beside them
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT04 | warning | the page shows the year 2025 in its text, but nothing on the page states it as the date of the content | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The page carries a date, ideally written into the markup rather than sitting only in the text. What good looks like The page carries a date, ideally written into the markup rather than sitting only in the text. Why it matters An undated page gives nothing to weigh its age against, so old and new material are treated alike. What we found on this page the page shows the year 2025 in its text, but nothing on the page states it as the date of the content The evidence, taken from the page as served The head of this page, as served
The head of the page was read for a tag stating the date of the content. The year shown above was found in the page's own text. <head> <meta charset="utf-8"/> <style>/* @see https://github.com/aFarkas/lazysizes#broken-image-symbol */.js img.b-lazy:not([src]) { visibility: hidden; }/* @see https://github.com/aFarkas/lazysizes#automatically-setting-the-sizes-attribute */.js img.lazyloaded[data-sizes=auto] { display: block; width: 100%; }</style> <meta name="description" content="The website of Newcastle City Council"/> <meta name="geo.placename" content="Newcastle upon Tyne"/> <link rel="canonical" href="https://newcastle.gov.uk/holocaust-memorial-day-2025"/> <link rel="icon" href="favicon.ico"/> <link rel="icon" sizes="16x16" href="/favicon-16x16.png"/> <link rel="icon" sizes="32x32" href="/favicon-32x32.png"/> <link rel="icon" sizes="96x96" href="/favicon-96x96.png"/> <link rel="icon" sizes="192x192" href="/android-chrome-192x192.png"/> <link rel="apple-touch-icon" href="/apple-touch-icon-60x60.png"/> <link rel="apple-touch-icon" sizes="72x72" href="/android-chrome-72x72.png"/> <link rel="apple-touch-icon" sizes="76x76" href="/apple-touch-icon-76x76.png"/> <link rel="apple-touch-icon" sizes="114x114" href="/apple-touch-icon-114x114.png"/> <link rel="apple-touch-icon" sizes="120x120" href="/apple-touch-icon-โฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT35 | warning | the copyright line at the foot of this page carries no year, so there is nothing on the page as served to date it by | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The copyright line at the foot of the page, and the year it states. What good looks like The copyright line states the current year. Why it matters An old copyright year reads as a site nobody is looking after, and it dates the page for anything that relies on dates. Content can be treated as years older than it really is. What we found on this page the copyright line at the foot of this page carries no year, so there is nothing on the page as served to date it by The evidence, taken from the page as served The copyright line on this page, as served
This is the copyright line as the page serves it. It was read for a year, and carries none. stagram Find out how we use social media Press Office and News ReciteMe and Accessibility ยฉNewcastle City Council Privacy Notice Terms and conditions Contact Us Covid-19 support Listen and translate {"path":{"baseUrl":"\/","pathPrefix":"","c | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
▸https://newcastle.gov.uk/holocaust-memorial-day-2026 30.0% Very likely 14 out of 68
The page https://newcastle.gov.uk/holocaust-memorial-day-2026
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Fails · 6 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 AI systems are being turned away before they reach the site, and because the barrier sits outside the organisation's own systems, nobody inside can see it happening. Those systems carry on answering questions about the organisation, from other people's material rather than its own, so the conversation about it goes on without it and nobody has decided that. 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.newcastle.gov.uk · resolves to 194.61.173.205
Address trailwww.newcastle.gov.uk
Checked2026-09-17 16:33 UTC · request sent from 54.171.52.206 (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 heading 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)
H2 Main navigation H2 Title H4 Have your say level jumped H1 Holocaust Memorial Day 2026 H2 Holocaust Memorial Day 2026 H2 Holocaust Memorial Day 2026: Bridging Generations H3 Why Bridging Generations? H2 Newcastle's Holocaust Memorial Day Programme H3 The Forgotten Holocaust - exhibition H3 In the footsteps of the Holocaust: The story and letters of a German Jewish fami H3 Holocaust Memorial Day Commemoration H3 Understanding the Holocaust in an Age of Emboldened Racism - lecture H3 Bridging Generations - Roma Commemorative Event H3 Brundibรกr Arts Festival H3 Brundibรกr Arts Festival: opening concert H3 Brundibรกr Arts Festival: short concert 1 H3 Brundibรกr Arts Festival: short concert 2 H3 Brundibรกr Arts Festival: short concert 3 H3 The Last Musician of Auschwitz - film H3 โJust Freddyโ by Joel Stern - book talk H3 Brundibรกr Arts Festival: A Voice Not Stilled H3 Brundibรกr Arts Festival: short concert 4 H3 Brundibรกr Arts Festival: short concert 5 H3 Brundibรกr Arts Festival - Closing concert H2 Take part in Holocaust Memorial Day H3 Holocaust Memorial Day Online H3 Organise an activity H4 Light the Darkness H3 Next:
Holocaust Memorial Day 2025 H3 Most popular pages H3 We're on social media
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 | fail | this page carries opening hours, a telephone number and dates, and states none of it in a form a machine can take as given, so those facts have to be worked out from the wording around them | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page states what it is, and the exact facts it carries, in a form a machine can take as given rather than work out from the wording. What good looks like The page states what it is in machine-readable form, and where it carries exact facts it states those too. A page of exact facts stating none of them is a fail; a narrative page without a block is a warning. Why it matters Where a page carries exact facts, an address, opening hours, a price, a date, leaving them only in prose means they are worked out rather than read, and that is where a wrong branch or an old price comes from. What we found on this page this page carries opening hours, a telephone number and dates, and states none of it in a form a machine can take as given, so those facts have to be worked out from the wording around them The evidence, taken from the page as served The head of this page, as served
The page was read for a short block of machine-readable detail saying what it is. The page's own words carry opening hours, a telephone number and dates, which is why this weighs as it does. <head> <meta charset="utf-8"/> <style>/* @see https://github.com/aFarkas/lazysizes#broken-image-symbol */.js img.b-lazy:not([src]) { visibility: hidden; }/* @see https://github.com/aFarkas/lazysizes#automatically-setting-the-sizes-attribute */.js img.lazyloaded[data-sizes=auto] { display: block; width: 100%; }</style> <meta name="description" content="The website of Newcastle City Council"/> <meta name="geo.placename" content="Newcastle upon Tyne"/> <link rel="canonical" href="https://newcastle.gov.uk/holocaust-memorial-day-2026"/> <link rel="icon" href="favicon.ico"/> <link rel="icon" sizes="16x16" href="/favicon-16x16.png"/> <link rel="icon" sizes="32x32" href="/favicon-32x32.png"/> <link rel="icon" sizes="96x96" href="/favicon-96x96.png"/> <link rel="icon" sizes="192x192" href="/android-chrome-192x192.png"/> <link rel="apple-touch-icon" href="/apple-touch-icon-60x60.png"/> <link rel="apple-touch-icon" sizes="72x72" href="/android-chrome-72x72.png"/> <link rel="apple-touch-icon" sizes="76x76" href="/apple-touch-icon-76x76.png"/> <link rel="apple-touch-icon" sizes="114x114" href="/apple-touch-icon-114x114.png"/> <link rel="apple-touch-icon" sizes="120x120" href="/apple-touch-icon-โฆ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 states what it is in machine-readable form, and where it carries exact facts it states those too. 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT43 | fail | 1 fault in this page's construction change the structure anything reading it sees, so what is read is not quite the page that was published | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page's underlying construction holds together, or contains faults that change how it is read. What good looks like The page is built soundly enough that anything reading it sees the structure its author intended. Why it matters Anything reading the page has to take it apart before it can judge anything on it. Faults in construction can move where a section appears to end, place a heading inside a paragraph, or lose part of the page altogether. When that happens, what is read is not quite the page that was published, and neither is the answer built from it. The damage is invisible on screen, because a browser repairs quietly what a plain reader does not. What we found on this page 1 fault in this page's construction change the structure anything reading it sees, so what is read is not quite the page that was published The evidence, taken from the page as served Faults in the page's construction that change how it reads
Found while taking the page apart exactly as a reader would.
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 is built soundly enough that anything reading it sees the structure its author intended. 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 The page's headings begin at its top level, rather than starting part way down. What good looks like The page's headings begin with its top-level heading. Levels skipped further down are weighed under heading hierarchy, and a page with no top-level heading at all under the missing main heading, so each fault is marked once. Why it matters The page's structure starts part way down, below a top level that never opens it. Sections then sit under nothing, and anything filing content by structure starts in the wrong place. 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 (the starting level is marked)
H2 Main navigation level jumped H2 Title H4 Have your say H1 Holocaust Memorial Day 2026 H2 Holocaust Memorial Day 2026 H2 Holocaust Memorial Day 2026: Bridging Generations H3 Why Bridging Generations? H2 Newcastle's Holocaust Memorial Day Programme H3 The Forgotten Holocaust - exhibition H3 In the footsteps of the Holocaust: The story and letters of a German Jewish fami H3 Holocaust Memorial Day Commemoration H3 Understanding the Holocaust in an Age of Emboldened Racism - lecture H3 Bridging Generations - Roma Commemorative Event H3 Brundibรกr Arts Festival H3 Brundibรกr Arts Festival: opening concert H3 Brundibรกr Arts Festival: short concert 1 H3 Brundibรกr Arts Festival: short concert 2 H3 Brundibรกr Arts Festival: short concert 3 H3 The Last Musician of Auschwitz - film H3 โJust Freddyโ by Joel Stern - book talk H3 Brundibรกr Arts Festival: A Voice Not Stilled H3 Brundibรกr Arts Festival: short concert 4 H3 Brundibรกr Arts Festival: short concert 5 H3 Brundibรกr Arts Festival - Closing concert H2 Take part in Holocaust Memorial Day H3 Holocaust Memorial Day Online H3 Organise an activity H4 Light the Darkness H3 Next:
Holocaust Memorial Day 2025 H3 Most popular pages H3 We're on social media
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 begin with its top-level heading. 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. <iframe title="vimeo-player" src="https://player.vimeo.com/video/1138867737?h=3197ca27e5" width="560" height="315" frameborder="0" referrerpolicy="strict-origin-when-cross-origin" allow="autoplay; fullscreen; picture-in-picture; clipboard-write; encrypted-media; web-share" allowfullscreen=""/> 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Warnings · 8 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MX01 | warning | the site took 260ms to start answering, close to the point where an automated reader gives up | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check How quickly the page starts to answer when it is asked for. What good looks like The page starts answering within 250ms. Between 250 and 345ms is a warning; beyond 345ms is a fail, that being the point at which an automated reader gives up. Why it matters A page that is slow to answer is left behind: the reader gives up and takes its answer from someone else's material, so your own words play no part in it. What we found on this page the site took 260ms to start answering, close to the point where an automated reader gives up The evidence, taken from the page as served How long this page took to start answering
Timed from the request leaving our checker to the first part of the answer coming back, on the page as served, so distance from the site plays its part. 345ms is the point beyond which an automated reader gives up.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT32 | warning | the page's meta description, the short summary it offers about itself, runs to 37 characters, too short to say what the page is about; a usable summary runs from 50 to 170 characters | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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 the page's meta description, the short summary it offers about itself, runs to 37 characters, too short to say what the page is about; a usable summary runs from 50 to 170 characters The evidence, taken from the page as served The page's description, as served
<meta name="description" content="The website of Newcastle City Council"/> | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT40 | warning | the page offers no short summary for the services that show a preview of it, so each one composes its own from whatever it finds first on the page | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The short title, description and image the page offers to services that show a preview of it, and whether they match the page. What good looks like The page offers a summary for preview, and the summary is true to the page. Why it matters This summary travels further than the page does. It is what appears when the address is shared, and several services read it in preference to the page itself because it is short and already written for the purpose. Where it is absent, those services compose their own from whatever they find first, which is often navigation. Where it is present but out of step, the organisation is described to a wide audience by a sentence it wrote once and forgot. What we found on this page the page offers no short summary for the services that show a preview of it, so each one composes its own from whatever it finds first on the page The evidence, taken from the page as served The summary this page offers for preview
Read from the page as served.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT41 | warning | the page does not show where it sits in the site, so anything reading it on its own has nothing to say what it belongs to | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The trail showing the path from the front page to this one, and whether the machine-readable version of that trail says the same. What good looks like The page shows its place in the site, and says the same thing to a machine. Why it matters A page read on its own gives no sense of what it belongs to. The trail supplies it: one product within a range, one policy within a set. A reader deciding whether a page answers a question uses that to judge whether it has the right one, and how to describe it when it quotes it. Where the shown trail and the machine-readable one disagree, the page is placed in two positions at once and neither can be relied on. What we found on this page the page does not show where it sits in the site, so anything reading it on its own has nothing to say what it belongs to The evidence, taken from the page as served The path this page gives to itself
Read from the page as served: the trail shown to a reader, and the trail stated in a form a machine can take as given.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR06 | warning | 3 figures on this page have no source named in the same passage, such as โ200,000โ. A figure with nothing beside it cannot be checked by a reader, or by anything quoting the page. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Percentages and money figures in the page's words, and whether a source is named or linked in the same passage. What good looks like A published figure names its source in the same passage. Why it matters A figure with no source cannot be checked by a reader or by anything quoting it. It travels on the organisation's name alone, and it is repeated that way. What we found on this page 3 figures on this page have no source named in the same passage, such as โ200,000โ. A figure with nothing beside it cannot be checked by a reader, or by anything quoting the page. The evidence, taken from the page as served The figures published with no source in the same passage
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT04 | warning | the page shows the year 2026 in its text, but nothing on the page states it as the date of the content | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The page carries a date, ideally written into the markup rather than sitting only in the text. What good looks like The page carries a date, ideally written into the markup rather than sitting only in the text. Why it matters An undated page gives nothing to weigh its age against, so old and new material are treated alike. What we found on this page the page shows the year 2026 in its text, but nothing on the page states it as the date of the content The evidence, taken from the page as served The head of this page, as served
The head of the page was read for a tag stating the date of the content. The year shown above was found in the page's own text. <head> <meta charset="utf-8"/> <style>/* @see https://github.com/aFarkas/lazysizes#broken-image-symbol */.js img.b-lazy:not([src]) { visibility: hidden; }/* @see https://github.com/aFarkas/lazysizes#automatically-setting-the-sizes-attribute */.js img.lazyloaded[data-sizes=auto] { display: block; width: 100%; }</style> <meta name="description" content="The website of Newcastle City Council"/> <meta name="geo.placename" content="Newcastle upon Tyne"/> <link rel="canonical" href="https://newcastle.gov.uk/holocaust-memorial-day-2026"/> <link rel="icon" href="favicon.ico"/> <link rel="icon" sizes="16x16" href="/favicon-16x16.png"/> <link rel="icon" sizes="32x32" href="/favicon-32x32.png"/> <link rel="icon" sizes="96x96" href="/favicon-96x96.png"/> <link rel="icon" sizes="192x192" href="/android-chrome-192x192.png"/> <link rel="apple-touch-icon" href="/apple-touch-icon-60x60.png"/> <link rel="apple-touch-icon" sizes="72x72" href="/android-chrome-72x72.png"/> <link rel="apple-touch-icon" sizes="76x76" href="/apple-touch-icon-76x76.png"/> <link rel="apple-touch-icon" sizes="114x114" href="/apple-touch-icon-114x114.png"/> <link rel="apple-touch-icon" sizes="120x120" href="/apple-touch-icon-โฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT35 | warning | the copyright line at the foot of this page carries no year, so there is nothing on the page as served to date it by | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The copyright line at the foot of the page, and the year it states. What good looks like The copyright line states the current year. Why it matters An old copyright year reads as a site nobody is looking after, and it dates the page for anything that relies on dates. Content can be treated as years older than it really is. What we found on this page the copyright line at the foot of this page carries no year, so there is nothing on the page as served to date it by The evidence, taken from the page as served The copyright line on this page, as served
This is the copyright line as the page serves it. It was read for a year, and carries none. exhibition Monday 19 to Saturday 31 January. West End Library Romani prisoners in a camp ยฉ USHMM Historians estimate that between 200,000 and 500,000 Roma and Sinti people were murdered by the Nazis and their collaborators with many more im | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS09 | warning | link wording that does not say where it leads: โhereโ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Link wording that names no destination, phrases such as click here, read more and details, and one such wording repeated across many links. What good looks like Link wording names its destination, rather than saying click here or read more. Why it matters The destination is stated nowhere on the link itself, so the choice rests entirely on the text around it. Where one wording such as click here covers many links, they read as one link repeated and nothing in their names tells them apart. What we found on this page link wording that does not say where it leads: โhereโ The evidence, taken from the page as served The links whose text names no destination, as served
<a href="https://forms.office.com/Pages/ResponsePage.aspx?id=wLSfsgQNn0q0YsEpSx4bR4J7jZ4NetdEu2CtoPt_iIlUNUlCNFA4WjJUUVBUR1UxMFZYOUpQQzBSMC4u" data-entity-type="external">here</a> | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
▸https://newcastle.gov.uk/local-government/access-information-and-data/open-data 30.1% Very likely 14 out of 67
The page https://newcastle.gov.uk/local-government/access-information-and-data/open-data
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Fails · 6 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 AI systems are being turned away before they reach the site, and because the barrier sits outside the organisation's own systems, nobody inside can see it happening. Those systems carry on answering questions about the organisation, from other people's material rather than its own, so the conversation about it goes on without it and nobody has decided that. 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.newcastle.gov.uk · resolves to 194.61.173.205
Address trailwww.newcastle.gov.uk
Checked2026-09-17 16:33 UTC · request sent from 54.171.52.206 (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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MX01 | fail | the site took 474ms to start answering, past the point where an automated reader gives up and takes its answer from elsewhere | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check How quickly the page starts to answer when it is asked for. What good looks like The page starts answering within 250ms. Between 250 and 345ms is a warning; beyond 345ms is a fail, that being the point at which an automated reader gives up. Why it matters A page that is slow to answer is left behind: the reader gives up and takes its answer from someone else's material, so your own words play no part in it. What we found on this page the site took 474ms to start answering, past the point where an automated reader gives up and takes its answer from elsewhere The evidence, taken from the page as served How long this page took to start answering
Timed from the request leaving our checker to the first part of the answer coming back, on the page as served, so distance from the site plays its part. 345ms is the point beyond which an automated reader gives up.
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 starts answering within 250ms. 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 heading 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)
H2 Main navigation H2 Title H4 Have your say level jumped H1 Open data H2 Open data H3 Most popular pages H3 We're on social media
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 | fail | this page carries prices or figures, and states none of it in a form a machine can take as given, so those facts have to be worked out from the wording around them | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page states what it is, and the exact facts it carries, in a form a machine can take as given rather than work out from the wording. What good looks like The page states what it is in machine-readable form, and where it carries exact facts it states those too. A page of exact facts stating none of them is a fail; a narrative page without a block is a warning. Why it matters Where a page carries exact facts, an address, opening hours, a price, a date, leaving them only in prose means they are worked out rather than read, and that is where a wrong branch or an old price comes from. What we found on this page this page carries prices or figures, and states none of it in a form a machine can take as given, so those facts have to be worked out from the wording around them The evidence, taken from the page as served The head of this page, as served
The page was read for a short block of machine-readable detail saying what it is. The page's own words carry prices or figures, which is why this weighs as it does. <head> <meta charset="utf-8"/> <style>/* @see https://github.com/aFarkas/lazysizes#broken-image-symbol */.js img.b-lazy:not([src]) { visibility: hidden; }/* @see https://github.com/aFarkas/lazysizes#automatically-setting-the-sizes-attribute */.js img.lazyloaded[data-sizes=auto] { display: block; width: 100%; }</style> <meta name="description" content="The website of Newcastle City Council"/> <meta name="geo.placename" content="Newcastle upon Tyne"/> <link rel="canonical" href="https://newcastle.gov.uk/local-government/access-information-and-data/open-data"/> <link rel="icon" href="favicon.ico"/> <link rel="icon" sizes="16x16" href="/favicon-16x16.png"/> <link rel="icon" sizes="32x32" href="/favicon-32x32.png"/> <link rel="icon" sizes="96x96" href="/favicon-96x96.png"/> <link rel="icon" sizes="192x192" href="/android-chrome-192x192.png"/> <link rel="apple-touch-icon" href="/apple-touch-icon-60x60.png"/> <link rel="apple-touch-icon" sizes="72x72" href="/android-chrome-72x72.png"/> <link rel="apple-touch-icon" sizes="76x76" href="/apple-touch-icon-76x76.png"/> <link rel="apple-touch-icon" sizes="114x114" href="/apple-touch-icon-114x114.png"/> <link rel="apple-touch-icon" sizes="120x12โฆ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 states what it is in machine-readable form, and where it carries exact facts it states those too. 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT43 | fail | 1 fault in this page's construction change the structure anything reading it sees, so what is read is not quite the page that was published | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page's underlying construction holds together, or contains faults that change how it is read. What good looks like The page is built soundly enough that anything reading it sees the structure its author intended. Why it matters Anything reading the page has to take it apart before it can judge anything on it. Faults in construction can move where a section appears to end, place a heading inside a paragraph, or lose part of the page altogether. When that happens, what is read is not quite the page that was published, and neither is the answer built from it. The damage is invisible on screen, because a browser repairs quietly what a plain reader does not. What we found on this page 1 fault in this page's construction change the structure anything reading it sees, so what is read is not quite the page that was published The evidence, taken from the page as served Faults in the page's construction that change how it reads
Found while taking the page apart exactly as a reader would.
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 is built soundly enough that anything reading it sees the structure its author intended. 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 The page's headings begin at its top level, rather than starting part way down. What good looks like The page's headings begin with its top-level heading. Levels skipped further down are weighed under heading hierarchy, and a page with no top-level heading at all under the missing main heading, so each fault is marked once. Why it matters The page's structure starts part way down, below a top level that never opens it. Sections then sit under nothing, and anything filing content by structure starts in the wrong place. 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 (the starting level is marked)
H2 Main navigation level jumped H2 Title H4 Have your say H1 Open data H2 Open data H3 Most popular pages H3 We're on social media
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 begin with its top-level heading. 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Warnings · 8 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT32 | warning | the page's meta description, the short summary it offers about itself, runs to 37 characters, too short to say what the page is about; a usable summary runs from 50 to 170 characters | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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 the page's meta description, the short summary it offers about itself, runs to 37 characters, too short to say what the page is about; a usable summary runs from 50 to 170 characters The evidence, taken from the page as served The page's description, as served
<meta name="description" content="The website of Newcastle City Council"/> | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT40 | warning | the page offers no short summary for the services that show a preview of it, so each one composes its own from whatever it finds first on the page | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The short title, description and image the page offers to services that show a preview of it, and whether they match the page. What good looks like The page offers a summary for preview, and the summary is true to the page. Why it matters This summary travels further than the page does. It is what appears when the address is shared, and several services read it in preference to the page itself because it is short and already written for the purpose. Where it is absent, those services compose their own from whatever they find first, which is often navigation. Where it is present but out of step, the organisation is described to a wide audience by a sentence it wrote once and forgot. What we found on this page the page offers no short summary for the services that show a preview of it, so each one composes its own from whatever it finds first on the page The evidence, taken from the page as served The summary this page offers for preview
Read from the page as served.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT41 | warning | the page does not show where it sits in the site, so anything reading it on its own has nothing to say what it belongs to | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The trail showing the path from the front page to this one, and whether the machine-readable version of that trail says the same. What good looks like The page shows its place in the site, and says the same thing to a machine. Why it matters A page read on its own gives no sense of what it belongs to. The trail supplies it: one product within a range, one policy within a set. A reader deciding whether a page answers a question uses that to judge whether it has the right one, and how to describe it when it quotes it. Where the shown trail and the machine-readable one disagree, the page is placed in two positions at once and neither can be relied on. What we found on this page the page does not show where it sits in the site, so anything reading it on its own has nothing to say what it belongs to The evidence, taken from the page as served The path this page gives to itself
Read from the page as served: the trail shown to a reader, and the trail stated in a form a machine can take as given.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR06 | warning | 2 figures on this page have no source named in the same passage, such as โยฃ250โ. A figure with nothing beside it cannot be checked by a reader, or by anything quoting the page. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Percentages and money figures in the page's words, and whether a source is named or linked in the same passage. What good looks like A published figure names its source in the same passage. Why it matters A figure with no source cannot be checked by a reader or by anything quoting it. It travels on the organisation's name alone, and it is repeated that way. What we found on this page 2 figures on this page have no source named in the same passage, such as โยฃ250โ. A figure with nothing beside it cannot be checked by a reader, or by anything quoting the page. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT04 | warning | the page carries no date, so there is nothing on it saying how current its content is | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The page carries a date, ideally written into the markup rather than sitting only in the text. What good looks like The page carries a date, ideally written into the markup rather than sitting only in the text. Why it matters An undated page gives nothing to weigh its age against, so old and new material are treated alike. What we found on this page the page carries no date, so there is nothing on it saying how current its content is The evidence, taken from the page as served The head of this page, as served
The head of the page and the page's own text were read for a date. <head> <meta charset="utf-8"/> <style>/* @see https://github.com/aFarkas/lazysizes#broken-image-symbol */.js img.b-lazy:not([src]) { visibility: hidden; }/* @see https://github.com/aFarkas/lazysizes#automatically-setting-the-sizes-attribute */.js img.lazyloaded[data-sizes=auto] { display: block; width: 100%; }</style> <meta name="description" content="The website of Newcastle City Council"/> <meta name="geo.placename" content="Newcastle upon Tyne"/> <link rel="canonical" href="https://newcastle.gov.uk/local-government/access-information-and-data/open-data"/> <link rel="icon" href="favicon.ico"/> <link rel="icon" sizes="16x16" href="/favicon-16x16.png"/> <link rel="icon" sizes="32x32" href="/favicon-32x32.png"/> <link rel="icon" sizes="96x96" href="/favicon-96x96.png"/> <link rel="icon" sizes="192x192" href="/android-chrome-192x192.png"/> <link rel="apple-touch-icon" href="/apple-touch-icon-60x60.png"/> <link rel="apple-touch-icon" sizes="72x72" href="/android-chrome-72x72.png"/> <link rel="apple-touch-icon" sizes="76x76" href="/apple-touch-icon-76x76.png"/> <link rel="apple-touch-icon" sizes="114x114" href="/apple-touch-icon-114x114.png"/> <link rel="apple-touch-icon" sizes="120x12โฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT35 | warning | the copyright line at the foot of this page carries no year, so there is nothing on the page as served to date it by | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The copyright line at the foot of the page, and the year it states. What good looks like The copyright line states the current year. Why it matters An old copyright year reads as a site nobody is looking after, and it dates the page for anything that relies on dates. Content can be treated as years older than it really is. What we found on this page the copyright line at the foot of this page carries no year, so there is nothing on the page as served to date it by The evidence, taken from the page as served The copyright line on this page, as served
This is the copyright line as the page serves it. It was read for a year, and carries none. stagram Find out how we use social media Press Office and News ReciteMe and Accessibility ยฉNewcastle City Council Privacy Notice Terms and conditions Contact Us Covid-19 support Listen and translate {"path":{"baseUrl":"\/","pathPrefix":"","c | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MX10 | warning | 2 links to a file on this page do not say what the file is and how big it is before it is opened. A reader deciding whether to open a file has nothing to judge it by, and on a slow or metered connection an unnamed file is a risk rather than an offer. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Links that open a file, and whether the wording states the format and the size. What good looks like A link to a file states its format and its size. Why it matters A reader deciding whether to open a file has nothing to judge it by, and on a slow or metered connection an unnamed file is a risk rather than an offer. What we found on this page 2 links to a file on this page do not say what the file is and how big it is before it is opened. A reader deciding whether to open a file has nothing to judge it by, and on a slow or metered connection an unnamed file is a risk rather than an offer. The evidence, taken from the page as served The links to a file, and what each one states
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS12 | warning | the page's 1 data table carry header cells, and 1 has heading cells that do not say which way they run. A figure lifted from a table arrives with its heading; without a caption there is nothing to say what the table is of, and where headings run down the side as well as across the top, nothing to say which one a figure belongs to | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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 the page's 1 data table carry header cells, and 1 has heading cells that do not say which way they run. A figure lifted from a table arrives with its heading; without a caption there is nothing to say what the table is of, and where headings run down the side as well as across the top, nothing to say which one a figure belongs to The evidence, taken from the page as served The data tables read for a caption and for headings that say which way they run
<table class="table"><caption>Data sets</caption><thead><tr><th>Name</th><th>Description</th></tr></thead><tbody><tr><td>Human Resources</td><td>Available data sets on employee information including sickness and absence.</td></tr><tr><td>Payments over ยฃ250</td><td>Each month we publish a list of all the payments we makโฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
▸https://newcastle.gov.uk/local-government/budget-performance-and-spend/payment-performance-statistics 30.2% Very likely 13 out of 67
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Fails · 6 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 AI systems are being turned away before they reach the site, and because the barrier sits outside the organisation's own systems, nobody inside can see it happening. Those systems carry on answering questions about the organisation, from other people's material rather than its own, so the conversation about it goes on without it and nobody has decided that. 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.newcastle.gov.uk · resolves to 194.61.173.205
Address trailwww.newcastle.gov.uk
Checked2026-09-17 16:33 UTC · request sent from 54.171.52.206 (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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MX01 | fail | the site took 402ms to start answering, past the point where an automated reader gives up and takes its answer from elsewhere | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check How quickly the page starts to answer when it is asked for. What good looks like The page starts answering within 250ms. Between 250 and 345ms is a warning; beyond 345ms is a fail, that being the point at which an automated reader gives up. Why it matters A page that is slow to answer is left behind: the reader gives up and takes its answer from someone else's material, so your own words play no part in it. What we found on this page the site took 402ms to start answering, past the point where an automated reader gives up and takes its answer from elsewhere The evidence, taken from the page as served How long this page took to start answering
Timed from the request leaving our checker to the first part of the answer coming back, on the page as served, so distance from the site plays its part. 345ms is the point beyond which an automated reader gives up.
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 starts answering within 250ms. 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 heading 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)
H2 Main navigation H2 Title H4 Have your say level jumped H1 Payment performance statistics H2 Payment performance statistics H2 Related Pages H3 Most popular pages H3 We're on social media
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 | fail | this page carries prices or figures, and states none of it in a form a machine can take as given, so those facts have to be worked out from the wording around them | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page states what it is, and the exact facts it carries, in a form a machine can take as given rather than work out from the wording. What good looks like The page states what it is in machine-readable form, and where it carries exact facts it states those too. A page of exact facts stating none of them is a fail; a narrative page without a block is a warning. Why it matters Where a page carries exact facts, an address, opening hours, a price, a date, leaving them only in prose means they are worked out rather than read, and that is where a wrong branch or an old price comes from. What we found on this page this page carries prices or figures, and states none of it in a form a machine can take as given, so those facts have to be worked out from the wording around them The evidence, taken from the page as served The head of this page, as served
The page was read for a short block of machine-readable detail saying what it is. The page's own words carry prices or figures, which is why this weighs as it does. <head> <meta charset="utf-8"/> <style>/* @see https://github.com/aFarkas/lazysizes#broken-image-symbol */.js img.b-lazy:not([src]) { visibility: hidden; }/* @see https://github.com/aFarkas/lazysizes#automatically-setting-the-sizes-attribute */.js img.lazyloaded[data-sizes=auto] { display: block; width: 100%; }</style> <meta name="description" content="The website of Newcastle City Council"/> <meta name="geo.placename" content="Newcastle upon Tyne"/> <link rel="canonical" href="https://newcastle.gov.uk/local-government/budget-performance-and-spend/payment-performance-statistics"/> <link rel="icon" href="favicon.ico"/> <link rel="icon" sizes="16x16" href="/favicon-16x16.png"/> <link rel="icon" sizes="32x32" href="/favicon-32x32.png"/> <link rel="icon" sizes="96x96" href="/favicon-96x96.png"/> <link rel="icon" sizes="192x192" href="/android-chrome-192x192.png"/> <link rel="apple-touch-icon" href="/apple-touch-icon-60x60.png"/> <link rel="apple-touch-icon" sizes="72x72" href="/android-chrome-72x72.png"/> <link rel="apple-touch-icon" sizes="76x76" href="/apple-touch-icon-76x76.png"/> <link rel="apple-touch-icon" sizes="114x114" href="/apple-touch-icon-114x114.png"/> <link rel="apple-touโฆ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 states what it is in machine-readable form, and where it carries exact facts it states those too. 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT43 | fail | 1 fault in this page's construction change the structure anything reading it sees, so what is read is not quite the page that was published | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page's underlying construction holds together, or contains faults that change how it is read. What good looks like The page is built soundly enough that anything reading it sees the structure its author intended. Why it matters Anything reading the page has to take it apart before it can judge anything on it. Faults in construction can move where a section appears to end, place a heading inside a paragraph, or lose part of the page altogether. When that happens, what is read is not quite the page that was published, and neither is the answer built from it. The damage is invisible on screen, because a browser repairs quietly what a plain reader does not. What we found on this page 1 fault in this page's construction change the structure anything reading it sees, so what is read is not quite the page that was published The evidence, taken from the page as served Faults in the page's construction that change how it reads
Found while taking the page apart exactly as a reader would.
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 is built soundly enough that anything reading it sees the structure its author intended. 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 The page's headings begin at its top level, rather than starting part way down. What good looks like The page's headings begin with its top-level heading. Levels skipped further down are weighed under heading hierarchy, and a page with no top-level heading at all under the missing main heading, so each fault is marked once. Why it matters The page's structure starts part way down, below a top level that never opens it. Sections then sit under nothing, and anything filing content by structure starts in the wrong place. 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 (the starting level is marked)
H2 Main navigation level jumped H2 Title H4 Have your say H1 Payment performance statistics H2 Payment performance statistics H2 Related Pages H3 Most popular pages H3 We're on social media
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 begin with its top-level heading. 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Warnings · 7 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT32 | warning | the page's meta description, the short summary it offers about itself, runs to 37 characters, too short to say what the page is about; a usable summary runs from 50 to 170 characters | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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 the page's meta description, the short summary it offers about itself, runs to 37 characters, too short to say what the page is about; a usable summary runs from 50 to 170 characters The evidence, taken from the page as served The page's description, as served
<meta name="description" content="The website of Newcastle City Council"/> | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT40 | warning | the page offers no short summary for the services that show a preview of it, so each one composes its own from whatever it finds first on the page | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The short title, description and image the page offers to services that show a preview of it, and whether they match the page. What good looks like The page offers a summary for preview, and the summary is true to the page. Why it matters This summary travels further than the page does. It is what appears when the address is shared, and several services read it in preference to the page itself because it is short and already written for the purpose. Where it is absent, those services compose their own from whatever they find first, which is often navigation. Where it is present but out of step, the organisation is described to a wide audience by a sentence it wrote once and forgot. What we found on this page the page offers no short summary for the services that show a preview of it, so each one composes its own from whatever it finds first on the page The evidence, taken from the page as served The summary this page offers for preview
Read from the page as served.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT41 | warning | the page does not show where it sits in the site, so anything reading it on its own has nothing to say what it belongs to | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The trail showing the path from the front page to this one, and whether the machine-readable version of that trail says the same. What good looks like The page shows its place in the site, and says the same thing to a machine. Why it matters A page read on its own gives no sense of what it belongs to. The trail supplies it: one product within a range, one policy within a set. A reader deciding whether a page answers a question uses that to judge whether it has the right one, and how to describe it when it quotes it. Where the shown trail and the machine-readable one disagree, the page is placed in two positions at once and neither can be relied on. What we found on this page the page does not show where it sits in the site, so anything reading it on its own has nothing to say what it belongs to The evidence, taken from the page as served The path this page gives to itself
Read from the page as served: the trail shown to a reader, and the trail stated in a form a machine can take as given.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR06 | warning | 30 figures on this page have no source named in the same passage, such as โ94.50%โ. A figure with nothing beside it cannot be checked by a reader, or by anything quoting the page. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Percentages and money figures in the page's words, and whether a source is named or linked in the same passage. What good looks like A published figure names its source in the same passage. Why it matters A figure with no source cannot be checked by a reader or by anything quoting it. It travels on the organisation's name alone, and it is repeated that way. What we found on this page 30 figures on this page have no source named in the same passage, such as โ94.50%โ. A figure with nothing beside it cannot be checked by a reader, or by anything quoting the page. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT04 | warning | the page shows the year 2015 in its text, but nothing on the page states it as the date of the content | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The page carries a date, ideally written into the markup rather than sitting only in the text. What good looks like The page carries a date, ideally written into the markup rather than sitting only in the text. Why it matters An undated page gives nothing to weigh its age against, so old and new material are treated alike. What we found on this page the page shows the year 2015 in its text, but nothing on the page states it as the date of the content The evidence, taken from the page as served The head of this page, as served
The head of the page was read for a tag stating the date of the content. The year shown above was found in the page's own text. <head> <meta charset="utf-8"/> <style>/* @see https://github.com/aFarkas/lazysizes#broken-image-symbol */.js img.b-lazy:not([src]) { visibility: hidden; }/* @see https://github.com/aFarkas/lazysizes#automatically-setting-the-sizes-attribute */.js img.lazyloaded[data-sizes=auto] { display: block; width: 100%; }</style> <meta name="description" content="The website of Newcastle City Council"/> <meta name="geo.placename" content="Newcastle upon Tyne"/> <link rel="canonical" href="https://newcastle.gov.uk/local-government/budget-performance-and-spend/payment-performance-statistics"/> <link rel="icon" href="favicon.ico"/> <link rel="icon" sizes="16x16" href="/favicon-16x16.png"/> <link rel="icon" sizes="32x32" href="/favicon-32x32.png"/> <link rel="icon" sizes="96x96" href="/favicon-96x96.png"/> <link rel="icon" sizes="192x192" href="/android-chrome-192x192.png"/> <link rel="apple-touch-icon" href="/apple-touch-icon-60x60.png"/> <link rel="apple-touch-icon" sizes="72x72" href="/android-chrome-72x72.png"/> <link rel="apple-touch-icon" sizes="76x76" href="/apple-touch-icon-76x76.png"/> <link rel="apple-touch-icon" sizes="114x114" href="/apple-touch-icon-114x114.png"/> <link rel="apple-touโฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT35 | warning | the copyright line at the foot of this page carries no year, so there is nothing on the page as served to date it by | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The copyright line at the foot of the page, and the year it states. What good looks like The copyright line states the current year. Why it matters An old copyright year reads as a site nobody is looking after, and it dates the page for anything that relies on dates. Content can be treated as years older than it really is. What we found on this page the copyright line at the foot of this page carries no year, so there is nothing on the page as served to date it by The evidence, taken from the page as served The copyright line on this page, as served
This is the copyright line as the page serves it. It was read for a year, and carries none. stagram Find out how we use social media Press Office and News ReciteMe and Accessibility ยฉNewcastle City Council Privacy Notice Terms and conditions Contact Us Covid-19 support Listen and translate {"path":{"baseUrl":"\/","pathPrefix":"","c | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS12 | warning | the page's 1 data table carry header cells, and 1 has heading cells that do not say which way they run. A figure lifted from a table arrives with its heading; without a caption there is nothing to say what the table is of, and where headings run down the side as well as across the top, nothing to say which one a figure belongs to | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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 the page's 1 data table carry header cells, and 1 has heading cells that do not say which way they run. A figure lifted from a table arrives with its heading; without a caption there is nothing to say what the table is of, and where headings run down the side as well as across the top, nothing to say which one a figure belongs to The evidence, taken from the page as served The data tables read for a caption and for headings that say which way they run
<table><caption>Payment Performance Statistics Table</caption><thead><tr><th>Financial Year</th><th>% of invoices paid within 30 days</th><th>Amount of liability</th><th>Amount of interest actually paid</th></tr></thead><tbody><tr><td>2024/25</td><td>94.50%</td><td>ยฃ142,605.97</td><td>ยฃ0.00</td></tr><tr><td>2023/24</tdโฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
▸https://newcastle.gov.uk/covidtaxiadvice 30.4% Very likely 12 out of 68
The page https://newcastle.gov.uk/covidtaxiadvice
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Fails · 6 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 AI systems are being turned away before they reach the site, and because the barrier sits outside the organisation's own systems, nobody inside can see it happening. Those systems carry on answering questions about the organisation, from other people's material rather than its own, so the conversation about it goes on without it and nobody has decided that. 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.newcastle.gov.uk · resolves to 194.61.173.205
Address trailwww.newcastle.gov.uk
Checked2026-09-17 16:33 UTC · request sent from 54.171.52.206 (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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MX01 | fail | the site took 460ms to start answering, past the point where an automated reader gives up and takes its answer from elsewhere | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check How quickly the page starts to answer when it is asked for. What good looks like The page starts answering within 250ms. Between 250 and 345ms is a warning; beyond 345ms is a fail, that being the point at which an automated reader gives up. Why it matters A page that is slow to answer is left behind: the reader gives up and takes its answer from someone else's material, so your own words play no part in it. What we found on this page the site took 460ms to start answering, past the point where an automated reader gives up and takes its answer from elsewhere The evidence, taken from the page as served How long this page took to start answering
Timed from the request leaving our checker to the first part of the answer coming back, on the page as served, so distance from the site plays its part. 345ms is the point beyond which an automated reader gives up.
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 starts answering within 250ms. 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 heading 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)
H2 Main navigation H2 Title H4 Have your say level jumped H1 Covid-19: Advice for taxi drivers H2 Covid-19: Advice for taxi drivers H2 Government advice H2 Licencing Office and Test Centre H2 Testing for taxi drivers H2 Installation of flexible PVC screens H3 Installing a screen - What to consider H2 Related Pages H3 Most popular pages H3 We're on social media
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 | fail | this page carries a telephone number, and states none of it in a form a machine can take as given, so those facts have to be worked out from the wording around them | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page states what it is, and the exact facts it carries, in a form a machine can take as given rather than work out from the wording. What good looks like The page states what it is in machine-readable form, and where it carries exact facts it states those too. A page of exact facts stating none of them is a fail; a narrative page without a block is a warning. Why it matters Where a page carries exact facts, an address, opening hours, a price, a date, leaving them only in prose means they are worked out rather than read, and that is where a wrong branch or an old price comes from. What we found on this page this page carries a telephone number, and states none of it in a form a machine can take as given, so those facts have to be worked out from the wording around them The evidence, taken from the page as served The head of this page, as served
The page was read for a short block of machine-readable detail saying what it is. The page's own words carry a telephone number, which is why this weighs as it does. <head> <meta charset="utf-8"/> <style>/* @see https://github.com/aFarkas/lazysizes#broken-image-symbol */.js img.b-lazy:not([src]) { visibility: hidden; }/* @see https://github.com/aFarkas/lazysizes#automatically-setting-the-sizes-attribute */.js img.lazyloaded[data-sizes=auto] { display: block; width: 100%; }</style> <meta name="description" content="The website of Newcastle City Council"/> <meta name="geo.placename" content="Newcastle upon Tyne"/> <link rel="canonical" href="https://newcastle.gov.uk/covidtaxiadvice"/> <link rel="icon" href="favicon.ico"/> <link rel="icon" sizes="16x16" href="/favicon-16x16.png"/> <link rel="icon" sizes="32x32" href="/favicon-32x32.png"/> <link rel="icon" sizes="96x96" href="/favicon-96x96.png"/> <link rel="icon" sizes="192x192" href="/android-chrome-192x192.png"/> <link rel="apple-touch-icon" href="/apple-touch-icon-60x60.png"/> <link rel="apple-touch-icon" sizes="72x72" href="/android-chrome-72x72.png"/> <link rel="apple-touch-icon" sizes="76x76" href="/apple-touch-icon-76x76.png"/> <link rel="apple-touch-icon" sizes="114x114" href="/apple-touch-icon-114x114.png"/> <link rel="apple-touch-icon" sizes="120x120" href="/apple-touch-icon-120x120.png"โฆ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 states what it is in machine-readable form, and where it carries exact facts it states those too. 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT43 | fail | 1 fault in this page's construction change the structure anything reading it sees, so what is read is not quite the page that was published | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page's underlying construction holds together, or contains faults that change how it is read. What good looks like The page is built soundly enough that anything reading it sees the structure its author intended. Why it matters Anything reading the page has to take it apart before it can judge anything on it. Faults in construction can move where a section appears to end, place a heading inside a paragraph, or lose part of the page altogether. When that happens, what is read is not quite the page that was published, and neither is the answer built from it. The damage is invisible on screen, because a browser repairs quietly what a plain reader does not. What we found on this page 1 fault in this page's construction change the structure anything reading it sees, so what is read is not quite the page that was published The evidence, taken from the page as served Faults in the page's construction that change how it reads
Found while taking the page apart exactly as a reader would.
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 is built soundly enough that anything reading it sees the structure its author intended. 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 The page's headings begin at its top level, rather than starting part way down. What good looks like The page's headings begin with its top-level heading. Levels skipped further down are weighed under heading hierarchy, and a page with no top-level heading at all under the missing main heading, so each fault is marked once. Why it matters The page's structure starts part way down, below a top level that never opens it. Sections then sit under nothing, and anything filing content by structure starts in the wrong place. 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 (the starting level is marked)
H2 Main navigation level jumped H2 Title H4 Have your say H1 Covid-19: Advice for taxi drivers H2 Covid-19: Advice for taxi drivers H2 Government advice H2 Licencing Office and Test Centre H2 Testing for taxi drivers H2 Installation of flexible PVC screens H3 Installing a screen - What to consider H2 Related Pages H3 Most popular pages H3 We're on social media
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 begin with its top-level heading. 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Warnings · 6 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT32 | warning | the page's meta description, the short summary it offers about itself, runs to 37 characters, too short to say what the page is about; a usable summary runs from 50 to 170 characters | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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 the page's meta description, the short summary it offers about itself, runs to 37 characters, too short to say what the page is about; a usable summary runs from 50 to 170 characters The evidence, taken from the page as served The page's description, as served
<meta name="description" content="The website of Newcastle City Council"/> | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT40 | warning | the page offers no short summary for the services that show a preview of it, so each one composes its own from whatever it finds first on the page | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The short title, description and image the page offers to services that show a preview of it, and whether they match the page. What good looks like The page offers a summary for preview, and the summary is true to the page. Why it matters This summary travels further than the page does. It is what appears when the address is shared, and several services read it in preference to the page itself because it is short and already written for the purpose. Where it is absent, those services compose their own from whatever they find first, which is often navigation. Where it is present but out of step, the organisation is described to a wide audience by a sentence it wrote once and forgot. What we found on this page the page offers no short summary for the services that show a preview of it, so each one composes its own from whatever it finds first on the page The evidence, taken from the page as served The summary this page offers for preview
Read from the page as served.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT41 | warning | the page does not show where it sits in the site, so anything reading it on its own has nothing to say what it belongs to | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The trail showing the path from the front page to this one, and whether the machine-readable version of that trail says the same. What good looks like The page shows its place in the site, and says the same thing to a machine. Why it matters A page read on its own gives no sense of what it belongs to. The trail supplies it: one product within a range, one policy within a set. A reader deciding whether a page answers a question uses that to judge whether it has the right one, and how to describe it when it quotes it. Where the shown trail and the machine-readable one disagree, the page is placed in two positions at once and neither can be relied on. What we found on this page the page does not show where it sits in the site, so anything reading it on its own has nothing to say what it belongs to The evidence, taken from the page as served The path this page gives to itself
Read from the page as served: the trail shown to a reader, and the trail stated in a form a machine can take as given.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT04 | warning | the page carries no date, so there is nothing on it saying how current its content is | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The page carries a date, ideally written into the markup rather than sitting only in the text. What good looks like The page carries a date, ideally written into the markup rather than sitting only in the text. Why it matters An undated page gives nothing to weigh its age against, so old and new material are treated alike. What we found on this page the page carries no date, so there is nothing on it saying how current its content is The evidence, taken from the page as served The head of this page, as served
The head of the page and the page's own text were read for a date. <head> <meta charset="utf-8"/> <style>/* @see https://github.com/aFarkas/lazysizes#broken-image-symbol */.js img.b-lazy:not([src]) { visibility: hidden; }/* @see https://github.com/aFarkas/lazysizes#automatically-setting-the-sizes-attribute */.js img.lazyloaded[data-sizes=auto] { display: block; width: 100%; }</style> <meta name="description" content="The website of Newcastle City Council"/> <meta name="geo.placename" content="Newcastle upon Tyne"/> <link rel="canonical" href="https://newcastle.gov.uk/covidtaxiadvice"/> <link rel="icon" href="favicon.ico"/> <link rel="icon" sizes="16x16" href="/favicon-16x16.png"/> <link rel="icon" sizes="32x32" href="/favicon-32x32.png"/> <link rel="icon" sizes="96x96" href="/favicon-96x96.png"/> <link rel="icon" sizes="192x192" href="/android-chrome-192x192.png"/> <link rel="apple-touch-icon" href="/apple-touch-icon-60x60.png"/> <link rel="apple-touch-icon" sizes="72x72" href="/android-chrome-72x72.png"/> <link rel="apple-touch-icon" sizes="76x76" href="/apple-touch-icon-76x76.png"/> <link rel="apple-touch-icon" sizes="114x114" href="/apple-touch-icon-114x114.png"/> <link rel="apple-touch-icon" sizes="120x120" href="/apple-touch-icon-120x120.png"โฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT35 | warning | the copyright line at the foot of this page carries no year, so there is nothing on the page as served to date it by | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The copyright line at the foot of the page, and the year it states. What good looks like The copyright line states the current year. Why it matters An old copyright year reads as a site nobody is looking after, and it dates the page for anything that relies on dates. Content can be treated as years older than it really is. What we found on this page the copyright line at the foot of this page carries no year, so there is nothing on the page as served to date it by The evidence, taken from the page as served The copyright line on this page, as served
This is the copyright line as the page serves it. It was read for a year, and carries none. stagram Find out how we use social media Press Office and News ReciteMe and Accessibility ยฉNewcastle City Council Privacy Notice Terms and conditions Contact Us Covid-19 support Listen and translate {"path":{"baseUrl":"\/","pathPrefix":"","c | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS09 | warning | link wording that does not say where it leads: โhereโ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Link wording that names no destination, phrases such as click here, read more and details, and one such wording repeated across many links. What good looks like Link wording names its destination, rather than saying click here or read more. Why it matters The destination is stated nowhere on the link itself, so the choice rests entirely on the text around it. Where one wording such as click here covers many links, they read as one link repeated and nothing in their names tells them apart. What we found on this page link wording that does not say where it leads: โhereโ The evidence, taken from the page as served The links whose text names no destination, as served
<a href="https://www.newcastle.gov.uk/services/public-health-wellbeing-and-leisure/public-health-services/coronavirus-covid-19-8"><span><span><span><span>here</span></span></span></span></a> | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
▸https://newcastle.gov.uk/get-involved/communities-team 30.8% Very likely 10 out of 67
The page https://newcastle.gov.uk/get-involved/communities-team
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Fails · 6 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 AI systems are being turned away before they reach the site, and because the barrier sits outside the organisation's own systems, nobody inside can see it happening. Those systems carry on answering questions about the organisation, from other people's material rather than its own, so the conversation about it goes on without it and nobody has decided that. 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.newcastle.gov.uk · resolves to 194.61.173.205
Address trailwww.newcastle.gov.uk
Checked2026-09-17 16:33 UTC · request sent from 54.171.52.206 (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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MX01 | fail | the site took 428ms to start answering, past the point where an automated reader gives up and takes its answer from elsewhere | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check How quickly the page starts to answer when it is asked for. What good looks like The page starts answering within 250ms. Between 250 and 345ms is a warning; beyond 345ms is a fail, that being the point at which an automated reader gives up. Why it matters A page that is slow to answer is left behind: the reader gives up and takes its answer from someone else's material, so your own words play no part in it. What we found on this page the site took 428ms to start answering, past the point where an automated reader gives up and takes its answer from elsewhere The evidence, taken from the page as served How long this page took to start answering
Timed from the request leaving our checker to the first part of the answer coming back, on the page as served, so distance from the site plays its part. 345ms is the point beyond which an automated reader gives up.
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 starts answering within 250ms. 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 heading 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)
H2 Main navigation H2 Title H4 Have your say level jumped H1 Communities Team H2 Communities Team H3 Who we are and what we do H3 Frequently Asked Questions: H2 Related Pages H3 Next:
Grants and Funding H3 Most popular pages H3 We're on social media
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 | fail | this page carries a telephone number, and states none of it in a form a machine can take as given, so those facts have to be worked out from the wording around them | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page states what it is, and the exact facts it carries, in a form a machine can take as given rather than work out from the wording. What good looks like The page states what it is in machine-readable form, and where it carries exact facts it states those too. A page of exact facts stating none of them is a fail; a narrative page without a block is a warning. Why it matters Where a page carries exact facts, an address, opening hours, a price, a date, leaving them only in prose means they are worked out rather than read, and that is where a wrong branch or an old price comes from. What we found on this page this page carries a telephone number, and states none of it in a form a machine can take as given, so those facts have to be worked out from the wording around them The evidence, taken from the page as served The head of this page, as served
The page was read for a short block of machine-readable detail saying what it is. The page's own words carry a telephone number, which is why this weighs as it does. <head> <meta charset="utf-8"/> <style>/* @see https://github.com/aFarkas/lazysizes#broken-image-symbol */.js img.b-lazy:not([src]) { visibility: hidden; }/* @see https://github.com/aFarkas/lazysizes#automatically-setting-the-sizes-attribute */.js img.lazyloaded[data-sizes=auto] { display: block; width: 100%; }</style> <meta name="description" content="Newcastle City Council's Communities Team, what we do..."/> <meta name="geo.placename" content="Newcastle upon Tyne"/> <link rel="canonical" href="https://newcastle.gov.uk/get-involved/communities-team"/> <link rel="icon" href="favicon.ico"/> <link rel="icon" sizes="16x16" href="/favicon-16x16.png"/> <link rel="icon" sizes="32x32" href="/favicon-32x32.png"/> <link rel="icon" sizes="96x96" href="/favicon-96x96.png"/> <link rel="icon" sizes="192x192" href="/android-chrome-192x192.png"/> <link rel="apple-touch-icon" href="/apple-touch-icon-60x60.png"/> <link rel="apple-touch-icon" sizes="72x72" href="/android-chrome-72x72.png"/> <link rel="apple-touch-icon" sizes="76x76" href="/apple-touch-icon-76x76.png"/> <link rel="apple-touch-icon" sizes="114x114" href="/apple-touch-icon-114x114.png"/> <link rel="apple-touch-icon" sizes="120x120" hreโฆ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 states what it is in machine-readable form, and where it carries exact facts it states those too. 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT43 | fail | 1 fault in this page's construction change the structure anything reading it sees, so what is read is not quite the page that was published | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page's underlying construction holds together, or contains faults that change how it is read. What good looks like The page is built soundly enough that anything reading it sees the structure its author intended. Why it matters Anything reading the page has to take it apart before it can judge anything on it. Faults in construction can move where a section appears to end, place a heading inside a paragraph, or lose part of the page altogether. When that happens, what is read is not quite the page that was published, and neither is the answer built from it. The damage is invisible on screen, because a browser repairs quietly what a plain reader does not. What we found on this page 1 fault in this page's construction change the structure anything reading it sees, so what is read is not quite the page that was published The evidence, taken from the page as served Faults in the page's construction that change how it reads
Found while taking the page apart exactly as a reader would.
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 is built soundly enough that anything reading it sees the structure its author intended. 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 The page's headings begin at its top level, rather than starting part way down. What good looks like The page's headings begin with its top-level heading. Levels skipped further down are weighed under heading hierarchy, and a page with no top-level heading at all under the missing main heading, so each fault is marked once. Why it matters The page's structure starts part way down, below a top level that never opens it. Sections then sit under nothing, and anything filing content by structure starts in the wrong place. 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 (the starting level is marked)
H2 Main navigation level jumped H2 Title H4 Have your say H1 Communities Team H2 Communities Team H3 Who we are and what we do H3 Frequently Asked Questions: H2 Related Pages H3 Next:
Grants and Funding H3 Most popular pages H3 We're on social media
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 begin with its top-level heading. 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Warnings · 4 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT40 | warning | the page offers no short summary for the services that show a preview of it, so each one composes its own from whatever it finds first on the page | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The short title, description and image the page offers to services that show a preview of it, and whether they match the page. What good looks like The page offers a summary for preview, and the summary is true to the page. Why it matters This summary travels further than the page does. It is what appears when the address is shared, and several services read it in preference to the page itself because it is short and already written for the purpose. Where it is absent, those services compose their own from whatever they find first, which is often navigation. Where it is present but out of step, the organisation is described to a wide audience by a sentence it wrote once and forgot. What we found on this page the page offers no short summary for the services that show a preview of it, so each one composes its own from whatever it finds first on the page The evidence, taken from the page as served The summary this page offers for preview
Read from the page as served.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT41 | warning | the page does not show where it sits in the site, so anything reading it on its own has nothing to say what it belongs to | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The trail showing the path from the front page to this one, and whether the machine-readable version of that trail says the same. What good looks like The page shows its place in the site, and says the same thing to a machine. Why it matters A page read on its own gives no sense of what it belongs to. The trail supplies it: one product within a range, one policy within a set. A reader deciding whether a page answers a question uses that to judge whether it has the right one, and how to describe it when it quotes it. Where the shown trail and the machine-readable one disagree, the page is placed in two positions at once and neither can be relied on. What we found on this page the page does not show where it sits in the site, so anything reading it on its own has nothing to say what it belongs to The evidence, taken from the page as served The path this page gives to itself
Read from the page as served: the trail shown to a reader, and the trail stated in a form a machine can take as given.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT04 | warning | the page carries no date, so there is nothing on it saying how current its content is | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The page carries a date, ideally written into the markup rather than sitting only in the text. What good looks like The page carries a date, ideally written into the markup rather than sitting only in the text. Why it matters An undated page gives nothing to weigh its age against, so old and new material are treated alike. What we found on this page the page carries no date, so there is nothing on it saying how current its content is The evidence, taken from the page as served The head of this page, as served
The head of the page and the page's own text were read for a date. <head> <meta charset="utf-8"/> <style>/* @see https://github.com/aFarkas/lazysizes#broken-image-symbol */.js img.b-lazy:not([src]) { visibility: hidden; }/* @see https://github.com/aFarkas/lazysizes#automatically-setting-the-sizes-attribute */.js img.lazyloaded[data-sizes=auto] { display: block; width: 100%; }</style> <meta name="description" content="Newcastle City Council's Communities Team, what we do..."/> <meta name="geo.placename" content="Newcastle upon Tyne"/> <link rel="canonical" href="https://newcastle.gov.uk/get-involved/communities-team"/> <link rel="icon" href="favicon.ico"/> <link rel="icon" sizes="16x16" href="/favicon-16x16.png"/> <link rel="icon" sizes="32x32" href="/favicon-32x32.png"/> <link rel="icon" sizes="96x96" href="/favicon-96x96.png"/> <link rel="icon" sizes="192x192" href="/android-chrome-192x192.png"/> <link rel="apple-touch-icon" href="/apple-touch-icon-60x60.png"/> <link rel="apple-touch-icon" sizes="72x72" href="/android-chrome-72x72.png"/> <link rel="apple-touch-icon" sizes="76x76" href="/apple-touch-icon-76x76.png"/> <link rel="apple-touch-icon" sizes="114x114" href="/apple-touch-icon-114x114.png"/> <link rel="apple-touch-icon" sizes="120x120" hreโฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT35 | warning | the copyright line at the foot of this page carries no year, so there is nothing on the page as served to date it by | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The copyright line at the foot of the page, and the year it states. What good looks like The copyright line states the current year. Why it matters An old copyright year reads as a site nobody is looking after, and it dates the page for anything that relies on dates. Content can be treated as years older than it really is. What we found on this page the copyright line at the foot of this page carries no year, so there is nothing on the page as served to date it by The evidence, taken from the page as served The copyright line on this page, as served
This is the copyright line as the page serves it. It was read for a year, and carries none. stagram Find out how we use social media Press Office and News ReciteMe and Accessibility ยฉNewcastle City Council Privacy Notice Terms and conditions Contact Us Covid-19 support Listen and translate {"path":{"baseUrl":"\/","pathPrefix":"","c | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
▸https://newcastle.gov.uk/get-involved/volunteering 31.7% Very likely 10 out of 67
The page https://newcastle.gov.uk/get-involved/volunteering
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Fails · 4 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 AI systems are being turned away before they reach the site, and because the barrier sits outside the organisation's own systems, nobody inside can see it happening. Those systems carry on answering questions about the organisation, from other people's material rather than its own, so the conversation about it goes on without it and nobody has decided that. 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.newcastle.gov.uk · resolves to 194.61.173.205
Address trailwww.newcastle.gov.uk
Checked2026-09-17 16:33 UTC · request sent from 54.171.52.206 (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 heading 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)
H2 Main navigation H2 Title H4 Have your say level jumped H1 Volunteering H2 Volunteering H2 Volunteering for Newcastle City Council H3 What can I expect as a Newcastle City Council volunteer? H3 Is it differentย if I am under 16? H3 Who do I contact about volunteering in the city of Newcastle? H2 Related Pages H3 Most popular pages H3 We're on social media
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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT43 | fail | 1 fault in this page's construction change the structure anything reading it sees, so what is read is not quite the page that was published | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page's underlying construction holds together, or contains faults that change how it is read. What good looks like The page is built soundly enough that anything reading it sees the structure its author intended. Why it matters Anything reading the page has to take it apart before it can judge anything on it. Faults in construction can move where a section appears to end, place a heading inside a paragraph, or lose part of the page altogether. When that happens, what is read is not quite the page that was published, and neither is the answer built from it. The damage is invisible on screen, because a browser repairs quietly what a plain reader does not. What we found on this page 1 fault in this page's construction change the structure anything reading it sees, so what is read is not quite the page that was published The evidence, taken from the page as served Faults in the page's construction that change how it reads
Found while taking the page apart exactly as a reader would.
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 is built soundly enough that anything reading it sees the structure its author intended. 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 The page's headings begin at its top level, rather than starting part way down. What good looks like The page's headings begin with its top-level heading. Levels skipped further down are weighed under heading hierarchy, and a page with no top-level heading at all under the missing main heading, so each fault is marked once. Why it matters The page's structure starts part way down, below a top level that never opens it. Sections then sit under nothing, and anything filing content by structure starts in the wrong place. 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 (the starting level is marked)
H2 Main navigation level jumped H2 Title H4 Have your say H1 Volunteering H2 Volunteering H2 Volunteering for Newcastle City Council H3 What can I expect as a Newcastle City Council volunteer? H3 Is it differentย if I am under 16? H3 Who do I contact about volunteering in the city of Newcastle? H2 Related Pages H3 Most popular pages H3 We're on social media
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 begin with its top-level heading. 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Warnings · 6 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT32 | warning | the page's meta description, the short summary it offers about itself, runs to 37 characters, too short to say what the page is about; a usable summary runs from 50 to 170 characters | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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 the page's meta description, the short summary it offers about itself, runs to 37 characters, too short to say what the page is about; a usable summary runs from 50 to 170 characters The evidence, taken from the page as served The page's description, as served
<meta name="description" content="The website of Newcastle City Council"/> | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT16 | warning | the page states nothing about itself in a form a machine can take as given, so who you are and what the page is about are worked out from its wording | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page states what it is, and the exact facts it carries, in a form a machine can take as given rather than work out from the wording. What good looks like The page states what it is in machine-readable form, and where it carries exact facts it states those too. A page of exact facts stating none of them is a fail; a narrative page without a block is a warning. Why it matters Where a page carries exact facts, an address, opening hours, a price, a date, leaving them only in prose means they are worked out rather than read, and that is where a wrong branch or an old price comes from. What we found on this page the page states nothing about itself in a form a machine can take as given, so who you are and what the page is about are worked out from its wording The evidence, taken from the page as served The head of this page, as served
The page was read for a short block of machine-readable detail saying what it is. The page's own words carry no exact facts of that kind. <head> <meta charset="utf-8"/> <style>/* @see https://github.com/aFarkas/lazysizes#broken-image-symbol */.js img.b-lazy:not([src]) { visibility: hidden; }/* @see https://github.com/aFarkas/lazysizes#automatically-setting-the-sizes-attribute */.js img.lazyloaded[data-sizes=auto] { display: block; width: 100%; }</style> <meta name="description" content="The website of Newcastle City Council"/> <meta name="geo.placename" content="Newcastle upon Tyne"/> <link rel="canonical" href="https://newcastle.gov.uk/get-involved/volunteering"/> <link rel="icon" href="favicon.ico"/> <link rel="icon" sizes="16x16" href="/favicon-16x16.png"/> <link rel="icon" sizes="32x32" href="/favicon-32x32.png"/> <link rel="icon" sizes="96x96" href="/favicon-96x96.png"/> <link rel="icon" sizes="192x192" href="/android-chrome-192x192.png"/> <link rel="apple-touch-icon" href="/apple-touch-icon-60x60.png"/> <link rel="apple-touch-icon" sizes="72x72" href="/android-chrome-72x72.png"/> <link rel="apple-touch-icon" sizes="76x76" href="/apple-touch-icon-76x76.png"/> <link rel="apple-touch-icon" sizes="114x114" href="/apple-touch-icon-114x114.png"/> <link rel="apple-touch-icon" sizes="120x120" href="/apple-touch-icon-12โฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT40 | warning | the page offers no short summary for the services that show a preview of it, so each one composes its own from whatever it finds first on the page | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The short title, description and image the page offers to services that show a preview of it, and whether they match the page. What good looks like The page offers a summary for preview, and the summary is true to the page. Why it matters This summary travels further than the page does. It is what appears when the address is shared, and several services read it in preference to the page itself because it is short and already written for the purpose. Where it is absent, those services compose their own from whatever they find first, which is often navigation. Where it is present but out of step, the organisation is described to a wide audience by a sentence it wrote once and forgot. What we found on this page the page offers no short summary for the services that show a preview of it, so each one composes its own from whatever it finds first on the page The evidence, taken from the page as served The summary this page offers for preview
Read from the page as served.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT41 | warning | the page does not show where it sits in the site, so anything reading it on its own has nothing to say what it belongs to | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The trail showing the path from the front page to this one, and whether the machine-readable version of that trail says the same. What good looks like The page shows its place in the site, and says the same thing to a machine. Why it matters A page read on its own gives no sense of what it belongs to. The trail supplies it: one product within a range, one policy within a set. A reader deciding whether a page answers a question uses that to judge whether it has the right one, and how to describe it when it quotes it. Where the shown trail and the machine-readable one disagree, the page is placed in two positions at once and neither can be relied on. What we found on this page the page does not show where it sits in the site, so anything reading it on its own has nothing to say what it belongs to The evidence, taken from the page as served The path this page gives to itself
Read from the page as served: the trail shown to a reader, and the trail stated in a form a machine can take as given.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT04 | warning | the page carries no date, so there is nothing on it saying how current its content is | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The page carries a date, ideally written into the markup rather than sitting only in the text. What good looks like The page carries a date, ideally written into the markup rather than sitting only in the text. Why it matters An undated page gives nothing to weigh its age against, so old and new material are treated alike. What we found on this page the page carries no date, so there is nothing on it saying how current its content is The evidence, taken from the page as served The head of this page, as served
The head of the page and the page's own text were read for a date. <head> <meta charset="utf-8"/> <style>/* @see https://github.com/aFarkas/lazysizes#broken-image-symbol */.js img.b-lazy:not([src]) { visibility: hidden; }/* @see https://github.com/aFarkas/lazysizes#automatically-setting-the-sizes-attribute */.js img.lazyloaded[data-sizes=auto] { display: block; width: 100%; }</style> <meta name="description" content="The website of Newcastle City Council"/> <meta name="geo.placename" content="Newcastle upon Tyne"/> <link rel="canonical" href="https://newcastle.gov.uk/get-involved/volunteering"/> <link rel="icon" href="favicon.ico"/> <link rel="icon" sizes="16x16" href="/favicon-16x16.png"/> <link rel="icon" sizes="32x32" href="/favicon-32x32.png"/> <link rel="icon" sizes="96x96" href="/favicon-96x96.png"/> <link rel="icon" sizes="192x192" href="/android-chrome-192x192.png"/> <link rel="apple-touch-icon" href="/apple-touch-icon-60x60.png"/> <link rel="apple-touch-icon" sizes="72x72" href="/android-chrome-72x72.png"/> <link rel="apple-touch-icon" sizes="76x76" href="/apple-touch-icon-76x76.png"/> <link rel="apple-touch-icon" sizes="114x114" href="/apple-touch-icon-114x114.png"/> <link rel="apple-touch-icon" sizes="120x120" href="/apple-touch-icon-12โฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT35 | warning | the copyright line at the foot of this page carries no year, so there is nothing on the page as served to date it by | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The copyright line at the foot of the page, and the year it states. What good looks like The copyright line states the current year. Why it matters An old copyright year reads as a site nobody is looking after, and it dates the page for anything that relies on dates. Content can be treated as years older than it really is. What we found on this page the copyright line at the foot of this page carries no year, so there is nothing on the page as served to date it by The evidence, taken from the page as served The copyright line on this page, as served
This is the copyright line as the page serves it. It was read for a year, and carries none. stagram Find out how we use social media Press Office and News ReciteMe and Accessibility ยฉNewcastle City Council Privacy Notice Terms and conditions Contact Us Covid-19 support Listen and translate {"path":{"baseUrl":"\/","pathPrefix":"","c | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
▸https://newcastle.gov.uk/local-government/access-information-and-data/freedom-information 30.6% Very likely 12 out of 67
The page https://newcastle.gov.uk/local-government/access-information-and-data/freedom-information
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Fails · 6 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 AI systems are being turned away before they reach the site, and because the barrier sits outside the organisation's own systems, nobody inside can see it happening. Those systems carry on answering questions about the organisation, from other people's material rather than its own, so the conversation about it goes on without it and nobody has decided that. 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.newcastle.gov.uk · resolves to 194.61.173.205
Address trailwww.newcastle.gov.uk
Checked2026-09-17 16:33 UTC · request sent from 54.171.52.206 (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 heading 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)
H2 Main navigation H2 Title H4 Have your say level jumped H1 Freedom of information H2 Freedom of information H2 What information can I get? H3 Classes of information we hold H3 Compliance statistics 2026/27 H3 Links to frequently asked for information H2 How do I request information under the Freedom of Information Act? H2 Environmental Information Regulations Requests H2 Can I get personal information that the City Council holds on me? H2 Is there any information I cannot get? H2 How much will it cost? H2 How quickly will I get the information? H2 What can I do if I am not satisfied with the Council's decision on my request? H3 Most popular pages H3 We're on social media
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 | fail | this page carries prices or figures and dates, and states none of it in a form a machine can take as given, so those facts have to be worked out from the wording around them | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page states what it is, and the exact facts it carries, in a form a machine can take as given rather than work out from the wording. What good looks like The page states what it is in machine-readable form, and where it carries exact facts it states those too. A page of exact facts stating none of them is a fail; a narrative page without a block is a warning. Why it matters Where a page carries exact facts, an address, opening hours, a price, a date, leaving them only in prose means they are worked out rather than read, and that is where a wrong branch or an old price comes from. What we found on this page this page carries prices or figures and dates, and states none of it in a form a machine can take as given, so those facts have to be worked out from the wording around them The evidence, taken from the page as served The head of this page, as served
The page was read for a short block of machine-readable detail saying what it is. The page's own words carry prices or figures and dates, which is why this weighs as it does. <head> <meta charset="utf-8"/> <style>/* @see https://github.com/aFarkas/lazysizes#broken-image-symbol */.js img.b-lazy:not([src]) { visibility: hidden; }/* @see https://github.com/aFarkas/lazysizes#automatically-setting-the-sizes-attribute */.js img.lazyloaded[data-sizes=auto] { display: block; width: 100%; }</style> <meta name="description" content="The website of Newcastle City Council"/> <meta name="geo.placename" content="Newcastle upon Tyne"/> <link rel="canonical" href="https://newcastle.gov.uk/local-government/access-information-and-data/freedom-information"/> <link rel="icon" href="favicon.ico"/> <link rel="icon" sizes="16x16" href="/favicon-16x16.png"/> <link rel="icon" sizes="32x32" href="/favicon-32x32.png"/> <link rel="icon" sizes="96x96" href="/favicon-96x96.png"/> <link rel="icon" sizes="192x192" href="/android-chrome-192x192.png"/> <link rel="apple-touch-icon" href="/apple-touch-icon-60x60.png"/> <link rel="apple-touch-icon" sizes="72x72" href="/android-chrome-72x72.png"/> <link rel="apple-touch-icon" sizes="76x76" href="/apple-touch-icon-76x76.png"/> <link rel="apple-touch-icon" sizes="114x114" href="/apple-touch-icon-114x114.png"/> <link rel="apple-touch-icon" sizโฆ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 states what it is in machine-readable form, and where it carries exact facts it states those too. 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT43 | fail | 1 fault in this page's construction change the structure anything reading it sees, so what is read is not quite the page that was published | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page's underlying construction holds together, or contains faults that change how it is read. What good looks like The page is built soundly enough that anything reading it sees the structure its author intended. Why it matters Anything reading the page has to take it apart before it can judge anything on it. Faults in construction can move where a section appears to end, place a heading inside a paragraph, or lose part of the page altogether. When that happens, what is read is not quite the page that was published, and neither is the answer built from it. The damage is invisible on screen, because a browser repairs quietly what a plain reader does not. What we found on this page 1 fault in this page's construction change the structure anything reading it sees, so what is read is not quite the page that was published The evidence, taken from the page as served Faults in the page's construction that change how it reads
Found while taking the page apart exactly as a reader would.
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 is built soundly enough that anything reading it sees the structure its author intended. 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: โinformation commissioner's websiteโ; 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 Identical links on one page lead to different places, so which one gets followed is a coin toss. A reader or system lands on the wrong page while believing it chose correctly. 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: โinformation commissioner's websiteโ; 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="http://www.ico.org.uk/">Information Commissioner's website</a> <a href="http://www.ico.org.uk/">Information Commissioner's website</a> <a href="https://ico.org.uk/for-organisations/guide-to-freedom-of-information/">Information Commissioner's website</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 The page's headings begin at its top level, rather than starting part way down. What good looks like The page's headings begin with its top-level heading. Levels skipped further down are weighed under heading hierarchy, and a page with no top-level heading at all under the missing main heading, so each fault is marked once. Why it matters The page's structure starts part way down, below a top level that never opens it. Sections then sit under nothing, and anything filing content by structure starts in the wrong place. 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 (the starting level is marked)
H2 Main navigation level jumped H2 Title H4 Have your say H1 Freedom of information H2 Freedom of information H2 What information can I get? H3 Classes of information we hold H3 Compliance statistics 2026/27 H3 Links to frequently asked for information H2 How do I request information under the Freedom of Information Act? H2 Environmental Information Regulations Requests H2 Can I get personal information that the City Council holds on me? H2 Is there any information I cannot get? H2 How much will it cost? H2 How quickly will I get the information? H2 What can I do if I am not satisfied with the Council's decision on my request? H3 Most popular pages H3 We're on social media
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 begin with its top-level heading. 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Warnings · 6 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT32 | warning | the page's meta description, the short summary it offers about itself, runs to 37 characters, too short to say what the page is about; a usable summary runs from 50 to 170 characters | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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 the page's meta description, the short summary it offers about itself, runs to 37 characters, too short to say what the page is about; a usable summary runs from 50 to 170 characters The evidence, taken from the page as served The page's description, as served
<meta name="description" content="The website of Newcastle City Council"/> | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT40 | warning | the page offers no short summary for the services that show a preview of it, so each one composes its own from whatever it finds first on the page | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The short title, description and image the page offers to services that show a preview of it, and whether they match the page. What good looks like The page offers a summary for preview, and the summary is true to the page. Why it matters This summary travels further than the page does. It is what appears when the address is shared, and several services read it in preference to the page itself because it is short and already written for the purpose. Where it is absent, those services compose their own from whatever they find first, which is often navigation. Where it is present but out of step, the organisation is described to a wide audience by a sentence it wrote once and forgot. What we found on this page the page offers no short summary for the services that show a preview of it, so each one composes its own from whatever it finds first on the page The evidence, taken from the page as served The summary this page offers for preview
Read from the page as served.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT41 | warning | the page does not show where it sits in the site, so anything reading it on its own has nothing to say what it belongs to | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The trail showing the path from the front page to this one, and whether the machine-readable version of that trail says the same. What good looks like The page shows its place in the site, and says the same thing to a machine. Why it matters A page read on its own gives no sense of what it belongs to. The trail supplies it: one product within a range, one policy within a set. A reader deciding whether a page answers a question uses that to judge whether it has the right one, and how to describe it when it quotes it. Where the shown trail and the machine-readable one disagree, the page is placed in two positions at once and neither can be relied on. What we found on this page the page does not show where it sits in the site, so anything reading it on its own has nothing to say what it belongs to The evidence, taken from the page as served The path this page gives to itself
Read from the page as served: the trail shown to a reader, and the trail stated in a form a machine can take as given.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT04 | warning | the page shows the year 2026 in its text, but nothing on the page states it as the date of the content | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The page carries a date, ideally written into the markup rather than sitting only in the text. What good looks like The page carries a date, ideally written into the markup rather than sitting only in the text. Why it matters An undated page gives nothing to weigh its age against, so old and new material are treated alike. What we found on this page the page shows the year 2026 in its text, but nothing on the page states it as the date of the content The evidence, taken from the page as served The head of this page, as served
The head of the page was read for a tag stating the date of the content. The year shown above was found in the page's own text. <head> <meta charset="utf-8"/> <style>/* @see https://github.com/aFarkas/lazysizes#broken-image-symbol */.js img.b-lazy:not([src]) { visibility: hidden; }/* @see https://github.com/aFarkas/lazysizes#automatically-setting-the-sizes-attribute */.js img.lazyloaded[data-sizes=auto] { display: block; width: 100%; }</style> <meta name="description" content="The website of Newcastle City Council"/> <meta name="geo.placename" content="Newcastle upon Tyne"/> <link rel="canonical" href="https://newcastle.gov.uk/local-government/access-information-and-data/freedom-information"/> <link rel="icon" href="favicon.ico"/> <link rel="icon" sizes="16x16" href="/favicon-16x16.png"/> <link rel="icon" sizes="32x32" href="/favicon-32x32.png"/> <link rel="icon" sizes="96x96" href="/favicon-96x96.png"/> <link rel="icon" sizes="192x192" href="/android-chrome-192x192.png"/> <link rel="apple-touch-icon" href="/apple-touch-icon-60x60.png"/> <link rel="apple-touch-icon" sizes="72x72" href="/android-chrome-72x72.png"/> <link rel="apple-touch-icon" sizes="76x76" href="/apple-touch-icon-76x76.png"/> <link rel="apple-touch-icon" sizes="114x114" href="/apple-touch-icon-114x114.png"/> <link rel="apple-touch-icon" sizโฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT35 | warning | the copyright line at the foot of this page carries no year, so there is nothing on the page as served to date it by | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The copyright line at the foot of the page, and the year it states. What good looks like The copyright line states the current year. Why it matters An old copyright year reads as a site nobody is looking after, and it dates the page for anything that relies on dates. Content can be treated as years older than it really is. What we found on this page the copyright line at the foot of this page carries no year, so there is nothing on the page as served to date it by The evidence, taken from the page as served The copyright line on this page, as served
This is the copyright line as the page serves it. It was read for a year, and carries none. stagram Find out how we use social media Press Office and News ReciteMe and Accessibility ยฉNewcastle City Council Privacy Notice Terms and conditions Contact Us Covid-19 support Listen and translate {"path":{"baseUrl":"\/","pathPrefix":"","c | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS12 | warning | the page's 1 data table carry header cells, and 1 carries no caption saying what the table is of and 1 has heading cells that do not say which way they run. A figure lifted from a table arrives with its heading; without a caption there is nothing to say what the table is of, and where headings run down the side as well as across the top, nothing to say which one a figure belongs to | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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 the page's 1 data table carry header cells, and 1 carries no caption saying what the table is of and 1 has heading cells that do not say which way they run. A figure lifted from a table arrives with its heading; without a caption there is nothing to say what the table is of, and where headings run down the side as well as across the top, nothing to say which one a figure belongs to The evidence, taken from the page as served The data tables read for a caption and for headings that say which way they run
<table class="table"><thead><tr><th>Freedom of Information compliance statistics 2026/27</th><th>Quarter 1 (01 April 2026โ 30 June 2026)</th></tr></thead><tbody><tr><td>Total requests received</td><td>404 </td></tr><tr><td>Total requests closed within statutory timescale</td><td>348 </td></tr><tr><td>Total requests cloโฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
▸https://newcastle.gov.uk/local-government/access-information-and-data/open-data/contractual-arrangements 31.3% Very likely 11 out of 68
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Fails · 5 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 AI systems are being turned away before they reach the site, and because the barrier sits outside the organisation's own systems, nobody inside can see it happening. Those systems carry on answering questions about the organisation, from other people's material rather than its own, so the conversation about it goes on without it and nobody has decided that. 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.newcastle.gov.uk · resolves to 194.61.173.205
Address trailwww.newcastle.gov.uk
Checked2026-09-17 16:33 UTC · request sent from 54.171.52.206 (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 heading 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)
H2 Main navigation H2 Title H4 Have your say level jumped H1 Contractual arrangements H2 Contractual arrangements H2 Contractual arrangements H2 Health Care Services (Provider Selection Regime) H2 Commissioning and procurement procedure rules H3 Most popular pages H3 We're on social media
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 | fail | this page carries prices or figures, and states none of it in a form a machine can take as given, so those facts have to be worked out from the wording around them | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page states what it is, and the exact facts it carries, in a form a machine can take as given rather than work out from the wording. What good looks like The page states what it is in machine-readable form, and where it carries exact facts it states those too. A page of exact facts stating none of them is a fail; a narrative page without a block is a warning. Why it matters Where a page carries exact facts, an address, opening hours, a price, a date, leaving them only in prose means they are worked out rather than read, and that is where a wrong branch or an old price comes from. What we found on this page this page carries prices or figures, and states none of it in a form a machine can take as given, so those facts have to be worked out from the wording around them The evidence, taken from the page as served The head of this page, as served
The page was read for a short block of machine-readable detail saying what it is. The page's own words carry prices or figures, which is why this weighs as it does. <head> <meta charset="utf-8"/> <style>/* @see https://github.com/aFarkas/lazysizes#broken-image-symbol */.js img.b-lazy:not([src]) { visibility: hidden; }/* @see https://github.com/aFarkas/lazysizes#automatically-setting-the-sizes-attribute */.js img.lazyloaded[data-sizes=auto] { display: block; width: 100%; }</style> <meta name="description" content="The website of Newcastle City Council"/> <meta name="geo.placename" content="Newcastle upon Tyne"/> <link rel="canonical" href="https://newcastle.gov.uk/local-government/access-information-and-data/open-data/contractual-arrangements"/> <link rel="icon" href="favicon.ico"/> <link rel="icon" sizes="16x16" href="/favicon-16x16.png"/> <link rel="icon" sizes="32x32" href="/favicon-32x32.png"/> <link rel="icon" sizes="96x96" href="/favicon-96x96.png"/> <link rel="icon" sizes="192x192" href="/android-chrome-192x192.png"/> <link rel="apple-touch-icon" href="/apple-touch-icon-60x60.png"/> <link rel="apple-touch-icon" sizes="72x72" href="/android-chrome-72x72.png"/> <link rel="apple-touch-icon" sizes="76x76" href="/apple-touch-icon-76x76.png"/> <link rel="apple-touch-icon" sizes="114x114" href="/apple-touch-icon-114x114.png"/> <link rel="apple-โฆ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 states what it is in machine-readable form, and where it carries exact facts it states those too. 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT43 | fail | 1 fault in this page's construction change the structure anything reading it sees, so what is read is not quite the page that was published | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page's underlying construction holds together, or contains faults that change how it is read. What good looks like The page is built soundly enough that anything reading it sees the structure its author intended. Why it matters Anything reading the page has to take it apart before it can judge anything on it. Faults in construction can move where a section appears to end, place a heading inside a paragraph, or lose part of the page altogether. When that happens, what is read is not quite the page that was published, and neither is the answer built from it. The damage is invisible on screen, because a browser repairs quietly what a plain reader does not. What we found on this page 1 fault in this page's construction change the structure anything reading it sees, so what is read is not quite the page that was published The evidence, taken from the page as served Faults in the page's construction that change how it reads
Found while taking the page apart exactly as a reader would.
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 is built soundly enough that anything reading it sees the structure its author intended. 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 The page's headings begin at its top level, rather than starting part way down. What good looks like The page's headings begin with its top-level heading. Levels skipped further down are weighed under heading hierarchy, and a page with no top-level heading at all under the missing main heading, so each fault is marked once. Why it matters The page's structure starts part way down, below a top level that never opens it. Sections then sit under nothing, and anything filing content by structure starts in the wrong place. 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 (the starting level is marked)
H2 Main navigation level jumped H2 Title H4 Have your say H1 Contractual arrangements H2 Contractual arrangements H2 Contractual arrangements H2 Health Care Services (Provider Selection Regime) H2 Commissioning and procurement procedure rules H3 Most popular pages H3 We're on social media
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 begin with its top-level heading. 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Warnings · 6 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT32 | warning | the page's meta description, the short summary it offers about itself, runs to 37 characters, too short to say what the page is about; a usable summary runs from 50 to 170 characters | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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 the page's meta description, the short summary it offers about itself, runs to 37 characters, too short to say what the page is about; a usable summary runs from 50 to 170 characters The evidence, taken from the page as served The page's description, as served
<meta name="description" content="The website of Newcastle City Council"/> | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT40 | warning | the page offers no short summary for the services that show a preview of it, so each one composes its own from whatever it finds first on the page | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The short title, description and image the page offers to services that show a preview of it, and whether they match the page. What good looks like The page offers a summary for preview, and the summary is true to the page. Why it matters This summary travels further than the page does. It is what appears when the address is shared, and several services read it in preference to the page itself because it is short and already written for the purpose. Where it is absent, those services compose their own from whatever they find first, which is often navigation. Where it is present but out of step, the organisation is described to a wide audience by a sentence it wrote once and forgot. What we found on this page the page offers no short summary for the services that show a preview of it, so each one composes its own from whatever it finds first on the page The evidence, taken from the page as served The summary this page offers for preview
Read from the page as served.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT41 | warning | the page does not show where it sits in the site, so anything reading it on its own has nothing to say what it belongs to | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The trail showing the path from the front page to this one, and whether the machine-readable version of that trail says the same. What good looks like The page shows its place in the site, and says the same thing to a machine. Why it matters A page read on its own gives no sense of what it belongs to. The trail supplies it: one product within a range, one policy within a set. A reader deciding whether a page answers a question uses that to judge whether it has the right one, and how to describe it when it quotes it. Where the shown trail and the machine-readable one disagree, the page is placed in two positions at once and neither can be relied on. What we found on this page the page does not show where it sits in the site, so anything reading it on its own has nothing to say what it belongs to The evidence, taken from the page as served The path this page gives to itself
Read from the page as served: the trail shown to a reader, and the trail stated in a form a machine can take as given.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT04 | warning | the page shows the year 2026 in its text, but nothing on the page states it as the date of the content | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The page carries a date, ideally written into the markup rather than sitting only in the text. What good looks like The page carries a date, ideally written into the markup rather than sitting only in the text. Why it matters An undated page gives nothing to weigh its age against, so old and new material are treated alike. What we found on this page the page shows the year 2026 in its text, but nothing on the page states it as the date of the content The evidence, taken from the page as served The head of this page, as served
The head of the page was read for a tag stating the date of the content. The year shown above was found in the page's own text. <head> <meta charset="utf-8"/> <style>/* @see https://github.com/aFarkas/lazysizes#broken-image-symbol */.js img.b-lazy:not([src]) { visibility: hidden; }/* @see https://github.com/aFarkas/lazysizes#automatically-setting-the-sizes-attribute */.js img.lazyloaded[data-sizes=auto] { display: block; width: 100%; }</style> <meta name="description" content="The website of Newcastle City Council"/> <meta name="geo.placename" content="Newcastle upon Tyne"/> <link rel="canonical" href="https://newcastle.gov.uk/local-government/access-information-and-data/open-data/contractual-arrangements"/> <link rel="icon" href="favicon.ico"/> <link rel="icon" sizes="16x16" href="/favicon-16x16.png"/> <link rel="icon" sizes="32x32" href="/favicon-32x32.png"/> <link rel="icon" sizes="96x96" href="/favicon-96x96.png"/> <link rel="icon" sizes="192x192" href="/android-chrome-192x192.png"/> <link rel="apple-touch-icon" href="/apple-touch-icon-60x60.png"/> <link rel="apple-touch-icon" sizes="72x72" href="/android-chrome-72x72.png"/> <link rel="apple-touch-icon" sizes="76x76" href="/apple-touch-icon-76x76.png"/> <link rel="apple-touch-icon" sizes="114x114" href="/apple-touch-icon-114x114.png"/> <link rel="apple-โฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT35 | warning | the copyright line at the foot of this page carries no year, so there is nothing on the page as served to date it by | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The copyright line at the foot of the page, and the year it states. What good looks like The copyright line states the current year. Why it matters An old copyright year reads as a site nobody is looking after, and it dates the page for anything that relies on dates. Content can be treated as years older than it really is. What we found on this page the copyright line at the foot of this page carries no year, so there is nothing on the page as served to date it by The evidence, taken from the page as served The copyright line on this page, as served
This is the copyright line as the page serves it. It was read for a year, and carries none. stagram Find out how we use social media Press Office and News ReciteMe and Accessibility ยฉNewcastle City Council Privacy Notice Terms and conditions Contact Us Covid-19 support Listen and translate {"path":{"baseUrl":"\/","pathPrefix":"","c | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS09 | warning | link wording that does not say where it leads: โhereโ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Link wording that names no destination, phrases such as click here, read more and details, and one such wording repeated across many links. What good looks like Link wording names its destination, rather than saying click here or read more. Why it matters The destination is stated nowhere on the link itself, so the choice rests entirely on the text around it. Where one wording such as click here covers many links, they read as one link repeated and nothing in their names tells them apart. What we found on this page link wording that does not say where it leads: โhereโ The evidence, taken from the page as served The links whose text names no destination, as served
<a href="https://www.newcastle.gov.uk/local-government/access-information-and-data/open-data/payments-over-ps250-data-sets"><span>here</span></a> | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
▸https://newcastle.gov.uk/local-government/access-information-and-data/open-data/libraries-data-sets 30.8% Very likely 10 out of 67
The page https://newcastle.gov.uk/local-government/access-information-and-data/open-data/libraries-data-sets
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Fails · 6 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 AI systems are being turned away before they reach the site, and because the barrier sits outside the organisation's own systems, nobody inside can see it happening. Those systems carry on answering questions about the organisation, from other people's material rather than its own, so the conversation about it goes on without it and nobody has decided that. 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.newcastle.gov.uk · resolves to 194.61.173.205
Address trailwww.newcastle.gov.uk
Checked2026-09-17 16:33 UTC · request sent from 54.171.52.206 (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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MX01 | fail | the site took 411ms to start answering, past the point where an automated reader gives up and takes its answer from elsewhere | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check How quickly the page starts to answer when it is asked for. What good looks like The page starts answering within 250ms. Between 250 and 345ms is a warning; beyond 345ms is a fail, that being the point at which an automated reader gives up. Why it matters A page that is slow to answer is left behind: the reader gives up and takes its answer from someone else's material, so your own words play no part in it. What we found on this page the site took 411ms to start answering, past the point where an automated reader gives up and takes its answer from elsewhere The evidence, taken from the page as served How long this page took to start answering
Timed from the request leaving our checker to the first part of the answer coming back, on the page as served, so distance from the site plays its part. 345ms is the point beyond which an automated reader gives up.
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 starts answering within 250ms. 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 heading 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)
H2 Main navigation H2 Title H4 Have your say level jumped H1 Libraries data sets H2 Libraries data sets H2 About Newcastle Libraries' data H2 The data sets H3 Most popular pages H3 We're on social media
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 | fail | this page carries opening hours, and states none of it in a form a machine can take as given, so those facts have to be worked out from the wording around them | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page states what it is, and the exact facts it carries, in a form a machine can take as given rather than work out from the wording. What good looks like The page states what it is in machine-readable form, and where it carries exact facts it states those too. A page of exact facts stating none of them is a fail; a narrative page without a block is a warning. Why it matters Where a page carries exact facts, an address, opening hours, a price, a date, leaving them only in prose means they are worked out rather than read, and that is where a wrong branch or an old price comes from. What we found on this page this page carries opening hours, and states none of it in a form a machine can take as given, so those facts have to be worked out from the wording around them The evidence, taken from the page as served The head of this page, as served
The page was read for a short block of machine-readable detail saying what it is. The page's own words carry opening hours, which is why this weighs as it does. <head> <meta charset="utf-8"/> <style>/* @see https://github.com/aFarkas/lazysizes#broken-image-symbol */.js img.b-lazy:not([src]) { visibility: hidden; }/* @see https://github.com/aFarkas/lazysizes#automatically-setting-the-sizes-attribute */.js img.lazyloaded[data-sizes=auto] { display: block; width: 100%; }</style> <meta name="description" content="In Newcastle Libraries we are endeavouring to open up as much of our data as possible. Here is a list of what we publish and where you can find our open data sets."/> <meta name="geo.placename" content="Newcastle upon Tyne"/> <link rel="canonical" href="https://newcastle.gov.uk/local-government/access-information-and-data/open-data/libraries-data-sets"/> <link rel="icon" href="favicon.ico"/> <link rel="icon" sizes="16x16" href="/favicon-16x16.png"/> <link rel="icon" sizes="32x32" href="/favicon-32x32.png"/> <link rel="icon" sizes="96x96" href="/favicon-96x96.png"/> <link rel="icon" sizes="192x192" href="/android-chrome-192x192.png"/> <link rel="apple-touch-icon" href="/apple-touch-icon-60x60.png"/> <link rel="apple-touch-icon" sizes="72x72" href="/android-chrome-72x72.png"/> <link rel="apple-touch-icon" sizes="76x76" href="/apple-toucโฆ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 states what it is in machine-readable form, and where it carries exact facts it states those too. 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT43 | fail | 1 fault in this page's construction change the structure anything reading it sees, so what is read is not quite the page that was published | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page's underlying construction holds together, or contains faults that change how it is read. What good looks like The page is built soundly enough that anything reading it sees the structure its author intended. Why it matters Anything reading the page has to take it apart before it can judge anything on it. Faults in construction can move where a section appears to end, place a heading inside a paragraph, or lose part of the page altogether. When that happens, what is read is not quite the page that was published, and neither is the answer built from it. The damage is invisible on screen, because a browser repairs quietly what a plain reader does not. What we found on this page 1 fault in this page's construction change the structure anything reading it sees, so what is read is not quite the page that was published The evidence, taken from the page as served Faults in the page's construction that change how it reads
Found while taking the page apart exactly as a reader would.
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 is built soundly enough that anything reading it sees the structure its author intended. 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 The page's headings begin at its top level, rather than starting part way down. What good looks like The page's headings begin with its top-level heading. Levels skipped further down are weighed under heading hierarchy, and a page with no top-level heading at all under the missing main heading, so each fault is marked once. Why it matters The page's structure starts part way down, below a top level that never opens it. Sections then sit under nothing, and anything filing content by structure starts in the wrong place. 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 (the starting level is marked)
H2 Main navigation level jumped H2 Title H4 Have your say H1 Libraries data sets H2 Libraries data sets H2 About Newcastle Libraries' data H2 The data sets H3 Most popular pages H3 We're on social media
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 begin with its top-level heading. 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Warnings · 4 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT40 | warning | the page offers no short summary for the services that show a preview of it, so each one composes its own from whatever it finds first on the page | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The short title, description and image the page offers to services that show a preview of it, and whether they match the page. What good looks like The page offers a summary for preview, and the summary is true to the page. Why it matters This summary travels further than the page does. It is what appears when the address is shared, and several services read it in preference to the page itself because it is short and already written for the purpose. Where it is absent, those services compose their own from whatever they find first, which is often navigation. Where it is present but out of step, the organisation is described to a wide audience by a sentence it wrote once and forgot. What we found on this page the page offers no short summary for the services that show a preview of it, so each one composes its own from whatever it finds first on the page The evidence, taken from the page as served The summary this page offers for preview
Read from the page as served.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT41 | warning | the page does not show where it sits in the site, so anything reading it on its own has nothing to say what it belongs to | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The trail showing the path from the front page to this one, and whether the machine-readable version of that trail says the same. What good looks like The page shows its place in the site, and says the same thing to a machine. Why it matters A page read on its own gives no sense of what it belongs to. The trail supplies it: one product within a range, one policy within a set. A reader deciding whether a page answers a question uses that to judge whether it has the right one, and how to describe it when it quotes it. Where the shown trail and the machine-readable one disagree, the page is placed in two positions at once and neither can be relied on. What we found on this page the page does not show where it sits in the site, so anything reading it on its own has nothing to say what it belongs to The evidence, taken from the page as served The path this page gives to itself
Read from the page as served: the trail shown to a reader, and the trail stated in a form a machine can take as given.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT04 | warning | the page carries no date, so there is nothing on it saying how current its content is | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The page carries a date, ideally written into the markup rather than sitting only in the text. What good looks like The page carries a date, ideally written into the markup rather than sitting only in the text. Why it matters An undated page gives nothing to weigh its age against, so old and new material are treated alike. What we found on this page the page carries no date, so there is nothing on it saying how current its content is The evidence, taken from the page as served The head of this page, as served
The head of the page and the page's own text were read for a date. <head> <meta charset="utf-8"/> <style>/* @see https://github.com/aFarkas/lazysizes#broken-image-symbol */.js img.b-lazy:not([src]) { visibility: hidden; }/* @see https://github.com/aFarkas/lazysizes#automatically-setting-the-sizes-attribute */.js img.lazyloaded[data-sizes=auto] { display: block; width: 100%; }</style> <meta name="description" content="In Newcastle Libraries we are endeavouring to open up as much of our data as possible. Here is a list of what we publish and where you can find our open data sets."/> <meta name="geo.placename" content="Newcastle upon Tyne"/> <link rel="canonical" href="https://newcastle.gov.uk/local-government/access-information-and-data/open-data/libraries-data-sets"/> <link rel="icon" href="favicon.ico"/> <link rel="icon" sizes="16x16" href="/favicon-16x16.png"/> <link rel="icon" sizes="32x32" href="/favicon-32x32.png"/> <link rel="icon" sizes="96x96" href="/favicon-96x96.png"/> <link rel="icon" sizes="192x192" href="/android-chrome-192x192.png"/> <link rel="apple-touch-icon" href="/apple-touch-icon-60x60.png"/> <link rel="apple-touch-icon" sizes="72x72" href="/android-chrome-72x72.png"/> <link rel="apple-touch-icon" sizes="76x76" href="/apple-toucโฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT35 | warning | the copyright line at the foot of this page carries no year, so there is nothing on the page as served to date it by | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The copyright line at the foot of the page, and the year it states. What good looks like The copyright line states the current year. Why it matters An old copyright year reads as a site nobody is looking after, and it dates the page for anything that relies on dates. Content can be treated as years older than it really is. What we found on this page the copyright line at the foot of this page carries no year, so there is nothing on the page as served to date it by The evidence, taken from the page as served The copyright line on this page, as served
This is the copyright line as the page serves it. It was read for a year, and carries none. stle Libraries' data To the extent possible under law, Newcastle Libraries has waived all copyright and related or neighbouring rights to its data published on the platforms mentioned below. This data is published from: United Kingdom. If there is a | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
▸https://newcastle.gov.uk/local-government/access-information-and-data/open-data/local-government-transparency-code-fraud 29.8% Very likely 14 out of 67
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Fails · 6 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 AI systems are being turned away before they reach the site, and because the barrier sits outside the organisation's own systems, nobody inside can see it happening. Those systems carry on answering questions about the organisation, from other people's material rather than its own, so the conversation about it goes on without it and nobody has decided that. 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.newcastle.gov.uk · resolves to 194.61.173.205
Address trailwww.newcastle.gov.uk
Checked2026-09-17 16:33 UTC · request sent from 54.171.52.206 (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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MX01 | fail | the site took 406ms to start answering, past the point where an automated reader gives up and takes its answer from elsewhere | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check How quickly the page starts to answer when it is asked for. What good looks like The page starts answering within 250ms. Between 250 and 345ms is a warning; beyond 345ms is a fail, that being the point at which an automated reader gives up. Why it matters A page that is slow to answer is left behind: the reader gives up and takes its answer from someone else's material, so your own words play no part in it. What we found on this page the site took 406ms to start answering, past the point where an automated reader gives up and takes its answer from elsewhere The evidence, taken from the page as served How long this page took to start answering
Timed from the request leaving our checker to the first part of the answer coming back, on the page as served, so distance from the site plays its part. 345ms is the point beyond which an automated reader gives up.
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 starts answering within 250ms. 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 heading 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)
H2 Main navigation H2 Title H4 Have your say level jumped H1 Local Government Transparency Code - Fraud H2 Local Government Transparency Code - Fraud H2 1 April 2024 to 31 March 2025 H2 1 April 2023 to 31 March 2024 H2 1 April 2022 to 31 March 2023 H2 1 April 2021 to 31 March 2022 H2 1 April 2020 to 31 March 2021 H2 1 April 2019 to 31 March 2020 H2 1 April 2018 to 31 March 2019 H3 Most popular pages H3 We're on social media
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 | fail | this page carries prices or figures and dates, and states none of it in a form a machine can take as given, so those facts have to be worked out from the wording around them | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page states what it is, and the exact facts it carries, in a form a machine can take as given rather than work out from the wording. What good looks like The page states what it is in machine-readable form, and where it carries exact facts it states those too. A page of exact facts stating none of them is a fail; a narrative page without a block is a warning. Why it matters Where a page carries exact facts, an address, opening hours, a price, a date, leaving them only in prose means they are worked out rather than read, and that is where a wrong branch or an old price comes from. What we found on this page this page carries prices or figures and dates, and states none of it in a form a machine can take as given, so those facts have to be worked out from the wording around them The evidence, taken from the page as served The head of this page, as served
The page was read for a short block of machine-readable detail saying what it is. The page's own words carry prices or figures and dates, which is why this weighs as it does. <head> <meta charset="utf-8"/> <style>/* @see https://github.com/aFarkas/lazysizes#broken-image-symbol */.js img.b-lazy:not([src]) { visibility: hidden; }/* @see https://github.com/aFarkas/lazysizes#automatically-setting-the-sizes-attribute */.js img.lazyloaded[data-sizes=auto] { display: block; width: 100%; }</style> <meta name="description" content="The website of Newcastle City Council"/> <meta name="geo.placename" content="Newcastle upon Tyne"/> <link rel="canonical" href="https://newcastle.gov.uk/local-government/access-information-and-data/open-data/local-government-transparency-code-fraud"/> <link rel="icon" href="favicon.ico"/> <link rel="icon" sizes="16x16" href="/favicon-16x16.png"/> <link rel="icon" sizes="32x32" href="/favicon-32x32.png"/> <link rel="icon" sizes="96x96" href="/favicon-96x96.png"/> <link rel="icon" sizes="192x192" href="/android-chrome-192x192.png"/> <link rel="apple-touch-icon" href="/apple-touch-icon-60x60.png"/> <link rel="apple-touch-icon" sizes="72x72" href="/android-chrome-72x72.png"/> <link rel="apple-touch-icon" sizes="76x76" href="/apple-touch-icon-76x76.png"/> <link rel="apple-touch-icon" sizes="114x114" href="/apple-touch-icon-114x114.png"/> <โฆ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 states what it is in machine-readable form, and where it carries exact facts it states those too. 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT43 | fail | 1 fault in this page's construction change the structure anything reading it sees, so what is read is not quite the page that was published | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page's underlying construction holds together, or contains faults that change how it is read. What good looks like The page is built soundly enough that anything reading it sees the structure its author intended. Why it matters Anything reading the page has to take it apart before it can judge anything on it. Faults in construction can move where a section appears to end, place a heading inside a paragraph, or lose part of the page altogether. When that happens, what is read is not quite the page that was published, and neither is the answer built from it. The damage is invisible on screen, because a browser repairs quietly what a plain reader does not. What we found on this page 1 fault in this page's construction change the structure anything reading it sees, so what is read is not quite the page that was published The evidence, taken from the page as served Faults in the page's construction that change how it reads
Found while taking the page apart exactly as a reader would.
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 is built soundly enough that anything reading it sees the structure its author intended. 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 The page's headings begin at its top level, rather than starting part way down. What good looks like The page's headings begin with its top-level heading. Levels skipped further down are weighed under heading hierarchy, and a page with no top-level heading at all under the missing main heading, so each fault is marked once. Why it matters The page's structure starts part way down, below a top level that never opens it. Sections then sit under nothing, and anything filing content by structure starts in the wrong place. 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 (the starting level is marked)
H2 Main navigation level jumped H2 Title H4 Have your say H1 Local Government Transparency Code - Fraud H2 Local Government Transparency Code - Fraud H2 1 April 2024 to 31 March 2025 H2 1 April 2023 to 31 March 2024 H2 1 April 2022 to 31 March 2023 H2 1 April 2021 to 31 March 2022 H2 1 April 2020 to 31 March 2021 H2 1 April 2019 to 31 March 2020 H2 1 April 2018 to 31 March 2019 H3 Most popular pages H3 We're on social media
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 begin with its top-level heading. 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Warnings · 8 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT06 | warning | title length 67 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 that is too short or too long is liable to be rewritten elsewhere, and control of the page's name goes with it. What we found on this page title length 67 chars The evidence, taken from the page as served The page title, as served
<title>Local Government Transparency Code - Fraud | Newcastle City Council</title> | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT32 | warning | the page's meta description, the short summary it offers about itself, runs to 37 characters, too short to say what the page is about; a usable summary runs from 50 to 170 characters | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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 the page's meta description, the short summary it offers about itself, runs to 37 characters, too short to say what the page is about; a usable summary runs from 50 to 170 characters The evidence, taken from the page as served The page's description, as served
<meta name="description" content="The website of Newcastle City Council"/> | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT40 | warning | the page offers no short summary for the services that show a preview of it, so each one composes its own from whatever it finds first on the page | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The short title, description and image the page offers to services that show a preview of it, and whether they match the page. What good looks like The page offers a summary for preview, and the summary is true to the page. Why it matters This summary travels further than the page does. It is what appears when the address is shared, and several services read it in preference to the page itself because it is short and already written for the purpose. Where it is absent, those services compose their own from whatever they find first, which is often navigation. Where it is present but out of step, the organisation is described to a wide audience by a sentence it wrote once and forgot. What we found on this page the page offers no short summary for the services that show a preview of it, so each one composes its own from whatever it finds first on the page The evidence, taken from the page as served The summary this page offers for preview
Read from the page as served.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT41 | warning | the page does not show where it sits in the site, so anything reading it on its own has nothing to say what it belongs to | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The trail showing the path from the front page to this one, and whether the machine-readable version of that trail says the same. What good looks like The page shows its place in the site, and says the same thing to a machine. Why it matters A page read on its own gives no sense of what it belongs to. The trail supplies it: one product within a range, one policy within a set. A reader deciding whether a page answers a question uses that to judge whether it has the right one, and how to describe it when it quotes it. Where the shown trail and the machine-readable one disagree, the page is placed in two positions at once and neither can be relied on. What we found on this page the page does not show where it sits in the site, so anything reading it on its own has nothing to say what it belongs to The evidence, taken from the page as served The path this page gives to itself
Read from the page as served: the trail shown to a reader, and the trail stated in a form a machine can take as given.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR06 | warning | 7 figures on this page have no source named in the same passage, such as โยฃ62,000โ. A figure with nothing beside it cannot be checked by a reader, or by anything quoting the page. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Percentages and money figures in the page's words, and whether a source is named or linked in the same passage. What good looks like A published figure names its source in the same passage. Why it matters A figure with no source cannot be checked by a reader or by anything quoting it. It travels on the organisation's name alone, and it is repeated that way. What we found on this page 7 figures on this page have no source named in the same passage, such as โยฃ62,000โ. A figure with nothing beside it cannot be checked by a reader, or by anything quoting the page. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT04 | warning | the page shows the year 2024 in its text, but nothing on the page states it as the date of the content | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The page carries a date, ideally written into the markup rather than sitting only in the text. What good looks like The page carries a date, ideally written into the markup rather than sitting only in the text. Why it matters An undated page gives nothing to weigh its age against, so old and new material are treated alike. What we found on this page the page shows the year 2024 in its text, but nothing on the page states it as the date of the content The evidence, taken from the page as served The head of this page, as served
The head of the page was read for a tag stating the date of the content. The year shown above was found in the page's own text. <head> <meta charset="utf-8"/> <style>/* @see https://github.com/aFarkas/lazysizes#broken-image-symbol */.js img.b-lazy:not([src]) { visibility: hidden; }/* @see https://github.com/aFarkas/lazysizes#automatically-setting-the-sizes-attribute */.js img.lazyloaded[data-sizes=auto] { display: block; width: 100%; }</style> <meta name="description" content="The website of Newcastle City Council"/> <meta name="geo.placename" content="Newcastle upon Tyne"/> <link rel="canonical" href="https://newcastle.gov.uk/local-government/access-information-and-data/open-data/local-government-transparency-code-fraud"/> <link rel="icon" href="favicon.ico"/> <link rel="icon" sizes="16x16" href="/favicon-16x16.png"/> <link rel="icon" sizes="32x32" href="/favicon-32x32.png"/> <link rel="icon" sizes="96x96" href="/favicon-96x96.png"/> <link rel="icon" sizes="192x192" href="/android-chrome-192x192.png"/> <link rel="apple-touch-icon" href="/apple-touch-icon-60x60.png"/> <link rel="apple-touch-icon" sizes="72x72" href="/android-chrome-72x72.png"/> <link rel="apple-touch-icon" sizes="76x76" href="/apple-touch-icon-76x76.png"/> <link rel="apple-touch-icon" sizes="114x114" href="/apple-touch-icon-114x114.png"/> <โฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT35 | warning | the copyright line at the foot of this page carries no year, so there is nothing on the page as served to date it by | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The copyright line at the foot of the page, and the year it states. What good looks like The copyright line states the current year. Why it matters An old copyright year reads as a site nobody is looking after, and it dates the page for anything that relies on dates. Content can be treated as years older than it really is. What we found on this page the copyright line at the foot of this page carries no year, so there is nothing on the page as served to date it by The evidence, taken from the page as served The copyright line on this page, as served
This is the copyright line as the page serves it. It was read for a year, and carries none. stagram Find out how we use social media Press Office and News ReciteMe and Accessibility ยฉNewcastle City Council Privacy Notice Terms and conditions Contact Us Covid-19 support Listen and translate {"path":{"baseUrl":"\/","pathPrefix":"","c | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MS12 | warning | the page's 7 data tables carry header cells, and 7 carry no caption saying what the table is of and 7 have heading cells that do not say which way they run. A figure lifted from a table arrives with its heading; without a caption there is nothing to say what the table is of, and where headings run down the side as well as across the top, nothing to say which one a figure belongs to | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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 the page's 7 data tables carry header cells, and 7 carry no caption saying what the table is of and 7 have heading cells that do not say which way they run. A figure lifted from a table arrives with its heading; without a caption there is nothing to say what the table is of, and where headings run down the side as well as across the top, nothing to say which one a figure belongs to The evidence, taken from the page as served The data tables read for a caption and for headings that say which way they run
<table><thead><tr><th><span><strong>Area</strong></span></th><th><span><strong>Total or amount</strong></span></th></tr></thead><tbody><tr><td><span>Number of occasions powers under the Prevention of Social Housing Fraud (Power to Require Information) (England) Regulations 2014, or similar powers have been used</span><โฆ <table><thead><tr><th><span><strong>Area</strong></span></th><th><span><strong>Total or amount</strong></span></th></tr></thead><tbody><tr><td><span>Number of occasions powers under the Prevention of Social Housing Fraud (Power to Require Information) (England) Regulations 2014, or similar powers have been used</span><โฆ <table><thead><tr><th><span><strong>Area</strong></span></th><th><span><strong>Total or amount</strong></span></th></tr></thead><tbody><tr><td><span>Number of occasions powers under the Prevention of Social Housing Fraud (Power to Require Information) (England) Regulations 2014, or similar powers have been used</span><โฆ <table><thead><tr><th><span><strong>Area</strong></span></th><th><span><strong>Total or amount</strong></span></th></tr></thead><tbody><tr><td><span>Number of occasions powers under the Prevention of Social Housing Fraud (Power to Require Information) (England) Regulations 2014, or similar powers have been used</span><โฆ <table><thead><tr><th><span><strong>Area</strong></span></th><th><span><strong>Total or amount</strong></span></th></tr></thead><tbody><tr><td><span>Number of occasions powers under the Prevention of Social Housing Fraud (Power to Require Information) (England) Regulations 2014, or similar powers have been used</span><โฆ <table><thead><tr><th><span><strong>Area</strong></span></th><th><span><strong>Total or amount</strong></span></th></tr></thead><tbody><tr><td><span>Number of occasions powers under the Prevention of Social Housing Fraud (Power to Require Information) (England) Regulations 2014, or similar powers have been used</span><โฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
▸https://newcastle.gov.uk/local-government/access-information-and-data/open-data/parking-account 30.7% Very likely 11 out of 67
The page https://newcastle.gov.uk/local-government/access-information-and-data/open-data/parking-account
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Fails · 6 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 AI systems are being turned away before they reach the site, and because the barrier sits outside the organisation's own systems, nobody inside can see it happening. Those systems carry on answering questions about the organisation, from other people's material rather than its own, so the conversation about it goes on without it and nobody has decided that. 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.newcastle.gov.uk · resolves to 194.61.173.205
Address trailwww.newcastle.gov.uk
Checked2026-09-17 16:33 UTC · request sent from 54.171.52.206 (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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MX01 | fail | the site took 405ms to start answering, past the point where an automated reader gives up and takes its answer from elsewhere | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check How quickly the page starts to answer when it is asked for. What good looks like The page starts answering within 250ms. Between 250 and 345ms is a warning; beyond 345ms is a fail, that being the point at which an automated reader gives up. Why it matters A page that is slow to answer is left behind: the reader gives up and takes its answer from someone else's material, so your own words play no part in it. What we found on this page the site took 405ms to start answering, past the point where an automated reader gives up and takes its answer from elsewhere The evidence, taken from the page as served How long this page took to start answering
Timed from the request leaving our checker to the first part of the answer coming back, on the page as served, so distance from the site plays its part. 345ms is the point beyond which an automated reader gives up.
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 starts answering within 250ms. 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 heading 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)
H2 Main navigation H2 Title H4 Have your say level jumped H1 Parking Account H2 Parking Account H3 Most popular pages H3 We're on social media
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 | fail | this page carries an address, and states none of it in a form a machine can take as given, so those facts have to be worked out from the wording around them | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page states what it is, and the exact facts it carries, in a form a machine can take as given rather than work out from the wording. What good looks like The page states what it is in machine-readable form, and where it carries exact facts it states those too. A page of exact facts stating none of them is a fail; a narrative page without a block is a warning. Why it matters Where a page carries exact facts, an address, opening hours, a price, a date, leaving them only in prose means they are worked out rather than read, and that is where a wrong branch or an old price comes from. What we found on this page this page carries an address, and states none of it in a form a machine can take as given, so those facts have to be worked out from the wording around them The evidence, taken from the page as served The head of this page, as served
The page was read for a short block of machine-readable detail saying what it is. The page's own words carry an address, which is why this weighs as it does. <head> <meta charset="utf-8"/> <style>/* @see https://github.com/aFarkas/lazysizes#broken-image-symbol */.js img.b-lazy:not([src]) { visibility: hidden; }/* @see https://github.com/aFarkas/lazysizes#automatically-setting-the-sizes-attribute */.js img.lazyloaded[data-sizes=auto] { display: block; width: 100%; }</style> <meta name="description" content="The website of Newcastle City Council"/> <meta name="geo.placename" content="Newcastle upon Tyne"/> <link rel="canonical" href="https://newcastle.gov.uk/local-government/access-information-and-data/open-data/parking-account"/> <link rel="icon" href="favicon.ico"/> <link rel="icon" sizes="16x16" href="/favicon-16x16.png"/> <link rel="icon" sizes="32x32" href="/favicon-32x32.png"/> <link rel="icon" sizes="96x96" href="/favicon-96x96.png"/> <link rel="icon" sizes="192x192" href="/android-chrome-192x192.png"/> <link rel="apple-touch-icon" href="/apple-touch-icon-60x60.png"/> <link rel="apple-touch-icon" sizes="72x72" href="/android-chrome-72x72.png"/> <link rel="apple-touch-icon" sizes="76x76" href="/apple-touch-icon-76x76.png"/> <link rel="apple-touch-icon" sizes="114x114" href="/apple-touch-icon-114x114.png"/> <link rel="apple-touch-icoโฆ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 states what it is in machine-readable form, and where it carries exact facts it states those too. 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT43 | fail | 1 fault in this page's construction change the structure anything reading it sees, so what is read is not quite the page that was published | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page's underlying construction holds together, or contains faults that change how it is read. What good looks like The page is built soundly enough that anything reading it sees the structure its author intended. Why it matters Anything reading the page has to take it apart before it can judge anything on it. Faults in construction can move where a section appears to end, place a heading inside a paragraph, or lose part of the page altogether. When that happens, what is read is not quite the page that was published, and neither is the answer built from it. The damage is invisible on screen, because a browser repairs quietly what a plain reader does not. What we found on this page 1 fault in this page's construction change the structure anything reading it sees, so what is read is not quite the page that was published The evidence, taken from the page as served Faults in the page's construction that change how it reads
Found while taking the page apart exactly as a reader would.
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 is built soundly enough that anything reading it sees the structure its author intended. 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 The page's headings begin at its top level, rather than starting part way down. What good looks like The page's headings begin with its top-level heading. Levels skipped further down are weighed under heading hierarchy, and a page with no top-level heading at all under the missing main heading, so each fault is marked once. Why it matters The page's structure starts part way down, below a top level that never opens it. Sections then sit under nothing, and anything filing content by structure starts in the wrong place. 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 (the starting level is marked)
H2 Main navigation level jumped H2 Title H4 Have your say H1 Parking Account H2 Parking Account H3 Most popular pages H3 We're on social media
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 begin with its top-level heading. 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Warnings · 5 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT32 | warning | the page's meta description, the short summary it offers about itself, runs to 37 characters, too short to say what the page is about; a usable summary runs from 50 to 170 characters | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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 the page's meta description, the short summary it offers about itself, runs to 37 characters, too short to say what the page is about; a usable summary runs from 50 to 170 characters The evidence, taken from the page as served The page's description, as served
<meta name="description" content="The website of Newcastle City Council"/> | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT40 | warning | the page offers no short summary for the services that show a preview of it, so each one composes its own from whatever it finds first on the page | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The short title, description and image the page offers to services that show a preview of it, and whether they match the page. What good looks like The page offers a summary for preview, and the summary is true to the page. Why it matters This summary travels further than the page does. It is what appears when the address is shared, and several services read it in preference to the page itself because it is short and already written for the purpose. Where it is absent, those services compose their own from whatever they find first, which is often navigation. Where it is present but out of step, the organisation is described to a wide audience by a sentence it wrote once and forgot. What we found on this page the page offers no short summary for the services that show a preview of it, so each one composes its own from whatever it finds first on the page The evidence, taken from the page as served The summary this page offers for preview
Read from the page as served.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT41 | warning | the page does not show where it sits in the site, so anything reading it on its own has nothing to say what it belongs to | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The trail showing the path from the front page to this one, and whether the machine-readable version of that trail says the same. What good looks like The page shows its place in the site, and says the same thing to a machine. Why it matters A page read on its own gives no sense of what it belongs to. The trail supplies it: one product within a range, one policy within a set. A reader deciding whether a page answers a question uses that to judge whether it has the right one, and how to describe it when it quotes it. Where the shown trail and the machine-readable one disagree, the page is placed in two positions at once and neither can be relied on. What we found on this page the page does not show where it sits in the site, so anything reading it on its own has nothing to say what it belongs to The evidence, taken from the page as served The path this page gives to itself
Read from the page as served: the trail shown to a reader, and the trail stated in a form a machine can take as given.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT04 | warning | the page shows the year 2025 in its text, but nothing on the page states it as the date of the content | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The page carries a date, ideally written into the markup rather than sitting only in the text. What good looks like The page carries a date, ideally written into the markup rather than sitting only in the text. Why it matters An undated page gives nothing to weigh its age against, so old and new material are treated alike. What we found on this page the page shows the year 2025 in its text, but nothing on the page states it as the date of the content The evidence, taken from the page as served The head of this page, as served
The head of the page was read for a tag stating the date of the content. The year shown above was found in the page's own text. <head> <meta charset="utf-8"/> <style>/* @see https://github.com/aFarkas/lazysizes#broken-image-symbol */.js img.b-lazy:not([src]) { visibility: hidden; }/* @see https://github.com/aFarkas/lazysizes#automatically-setting-the-sizes-attribute */.js img.lazyloaded[data-sizes=auto] { display: block; width: 100%; }</style> <meta name="description" content="The website of Newcastle City Council"/> <meta name="geo.placename" content="Newcastle upon Tyne"/> <link rel="canonical" href="https://newcastle.gov.uk/local-government/access-information-and-data/open-data/parking-account"/> <link rel="icon" href="favicon.ico"/> <link rel="icon" sizes="16x16" href="/favicon-16x16.png"/> <link rel="icon" sizes="32x32" href="/favicon-32x32.png"/> <link rel="icon" sizes="96x96" href="/favicon-96x96.png"/> <link rel="icon" sizes="192x192" href="/android-chrome-192x192.png"/> <link rel="apple-touch-icon" href="/apple-touch-icon-60x60.png"/> <link rel="apple-touch-icon" sizes="72x72" href="/android-chrome-72x72.png"/> <link rel="apple-touch-icon" sizes="76x76" href="/apple-touch-icon-76x76.png"/> <link rel="apple-touch-icon" sizes="114x114" href="/apple-touch-icon-114x114.png"/> <link rel="apple-touch-icoโฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT35 | warning | the copyright line at the foot of this page carries no year, so there is nothing on the page as served to date it by | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The copyright line at the foot of the page, and the year it states. What good looks like The copyright line states the current year. Why it matters An old copyright year reads as a site nobody is looking after, and it dates the page for anything that relies on dates. Content can be treated as years older than it really is. What we found on this page the copyright line at the foot of this page carries no year, so there is nothing on the page as served to date it by The evidence, taken from the page as served The copyright line on this page, as served
This is the copyright line as the page serves it. It was read for a year, and carries none. stagram Find out how we use social media Press Office and News ReciteMe and Accessibility ยฉNewcastle City Council Privacy Notice Terms and conditions Contact Us Covid-19 support Listen and translate {"path":{"baseUrl":"\/","pathPrefix":"","c | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
▸https://newcastle.gov.uk/local-government/access-information-and-data/open-data/payments-over-ps250-data-sets 30.7% Very likely 12 out of 67
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Fails · 6 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 AI systems are being turned away before they reach the site, and because the barrier sits outside the organisation's own systems, nobody inside can see it happening. Those systems carry on answering questions about the organisation, from other people's material rather than its own, so the conversation about it goes on without it and nobody has decided that. 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.newcastle.gov.uk · resolves to 194.61.173.205
Address trailwww.newcastle.gov.uk
Checked2026-09-17 16:33 UTC · request sent from 54.171.52.206 (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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MX01 | fail | the site took 418ms to start answering, past the point where an automated reader gives up and takes its answer from elsewhere | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check How quickly the page starts to answer when it is asked for. What good looks like The page starts answering within 250ms. Between 250 and 345ms is a warning; beyond 345ms is a fail, that being the point at which an automated reader gives up. Why it matters A page that is slow to answer is left behind: the reader gives up and takes its answer from someone else's material, so your own words play no part in it. What we found on this page the site took 418ms to start answering, past the point where an automated reader gives up and takes its answer from elsewhere The evidence, taken from the page as served How long this page took to start answering
Timed from the request leaving our checker to the first part of the answer coming back, on the page as served, so distance from the site plays its part. 345ms is the point beyond which an automated reader gives up.
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 starts answering within 250ms. 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 heading 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)
H2 Main navigation H2 Title H4 Have your say level jumped H1 Payments over ยฃ250 data sets H2 Payments over ยฃ250 data sets H2 Payments to suppliers H2 Relevant Committee Reports H2 Monthly spending reports H3 Most popular pages H3 We're on social media
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 | fail | this page carries prices or figures, and states none of it in a form a machine can take as given, so those facts have to be worked out from the wording around them | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page states what it is, and the exact facts it carries, in a form a machine can take as given rather than work out from the wording. What good looks like The page states what it is in machine-readable form, and where it carries exact facts it states those too. A page of exact facts stating none of them is a fail; a narrative page without a block is a warning. Why it matters Where a page carries exact facts, an address, opening hours, a price, a date, leaving them only in prose means they are worked out rather than read, and that is where a wrong branch or an old price comes from. What we found on this page this page carries prices or figures, and states none of it in a form a machine can take as given, so those facts have to be worked out from the wording around them The evidence, taken from the page as served The head of this page, as served
The page was read for a short block of machine-readable detail saying what it is. The page's own words carry prices or figures, which is why this weighs as it does. <head> <meta charset="utf-8"/> <style>/* @see https://github.com/aFarkas/lazysizes#broken-image-symbol */.js img.b-lazy:not([src]) { visibility: hidden; }/* @see https://github.com/aFarkas/lazysizes#automatically-setting-the-sizes-attribute */.js img.lazyloaded[data-sizes=auto] { display: block; width: 100%; }</style> <meta name="description" content="The website of Newcastle City Council"/> <meta name="geo.placename" content="Newcastle upon Tyne"/> <link rel="canonical" href="https://newcastle.gov.uk/local-government/access-information-and-data/open-data/payments-over-ps250-data-sets"/> <link rel="icon" href="favicon.ico"/> <link rel="icon" sizes="16x16" href="/favicon-16x16.png"/> <link rel="icon" sizes="32x32" href="/favicon-32x32.png"/> <link rel="icon" sizes="96x96" href="/favicon-96x96.png"/> <link rel="icon" sizes="192x192" href="/android-chrome-192x192.png"/> <link rel="apple-touch-icon" href="/apple-touch-icon-60x60.png"/> <link rel="apple-touch-icon" sizes="72x72" href="/android-chrome-72x72.png"/> <link rel="apple-touch-icon" sizes="76x76" href="/apple-touch-icon-76x76.png"/> <link rel="apple-touch-icon" sizes="114x114" href="/apple-touch-icon-114x114.png"/> <link rel="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: the page states what it is in machine-readable form, and where it carries exact facts it states those too. 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT43 | fail | 1 fault in this page's construction change the structure anything reading it sees, so what is read is not quite the page that was published | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page's underlying construction holds together, or contains faults that change how it is read. What good looks like The page is built soundly enough that anything reading it sees the structure its author intended. Why it matters Anything reading the page has to take it apart before it can judge anything on it. Faults in construction can move where a section appears to end, place a heading inside a paragraph, or lose part of the page altogether. When that happens, what is read is not quite the page that was published, and neither is the answer built from it. The damage is invisible on screen, because a browser repairs quietly what a plain reader does not. What we found on this page 1 fault in this page's construction change the structure anything reading it sees, so what is read is not quite the page that was published The evidence, taken from the page as served Faults in the page's construction that change how it reads
Found while taking the page apart exactly as a reader would.
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 is built soundly enough that anything reading it sees the structure its author intended. 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 The page's headings begin at its top level, rather than starting part way down. What good looks like The page's headings begin with its top-level heading. Levels skipped further down are weighed under heading hierarchy, and a page with no top-level heading at all under the missing main heading, so each fault is marked once. Why it matters The page's structure starts part way down, below a top level that never opens it. Sections then sit under nothing, and anything filing content by structure starts in the wrong place. 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 (the starting level is marked)
H2 Main navigation level jumped H2 Title H4 Have your say H1 Payments over ยฃ250 data sets H2 Payments over ยฃ250 data sets H2 Payments to suppliers H2 Relevant Committee Reports H2 Monthly spending reports H3 Most popular pages H3 We're on social media
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 begin with its top-level heading. 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Warnings · 6 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT32 | warning | the page's meta description, the short summary it offers about itself, runs to 37 characters, too short to say what the page is about; a usable summary runs from 50 to 170 characters | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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 the page's meta description, the short summary it offers about itself, runs to 37 characters, too short to say what the page is about; a usable summary runs from 50 to 170 characters The evidence, taken from the page as served The page's description, as served
<meta name="description" content="The website of Newcastle City Council"/> | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT40 | warning | the page offers no short summary for the services that show a preview of it, so each one composes its own from whatever it finds first on the page | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The short title, description and image the page offers to services that show a preview of it, and whether they match the page. What good looks like The page offers a summary for preview, and the summary is true to the page. Why it matters This summary travels further than the page does. It is what appears when the address is shared, and several services read it in preference to the page itself because it is short and already written for the purpose. Where it is absent, those services compose their own from whatever they find first, which is often navigation. Where it is present but out of step, the organisation is described to a wide audience by a sentence it wrote once and forgot. What we found on this page the page offers no short summary for the services that show a preview of it, so each one composes its own from whatever it finds first on the page The evidence, taken from the page as served The summary this page offers for preview
Read from the page as served.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT41 | warning | the page does not show where it sits in the site, so anything reading it on its own has nothing to say what it belongs to | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The trail showing the path from the front page to this one, and whether the machine-readable version of that trail says the same. What good looks like The page shows its place in the site, and says the same thing to a machine. Why it matters A page read on its own gives no sense of what it belongs to. The trail supplies it: one product within a range, one policy within a set. A reader deciding whether a page answers a question uses that to judge whether it has the right one, and how to describe it when it quotes it. Where the shown trail and the machine-readable one disagree, the page is placed in two positions at once and neither can be relied on. What we found on this page the page does not show where it sits in the site, so anything reading it on its own has nothing to say what it belongs to The evidence, taken from the page as served The path this page gives to itself
Read from the page as served: the trail shown to a reader, and the trail stated in a form a machine can take as given.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT04 | warning | the page shows the year 2026 in its text, but nothing on the page states it as the date of the content | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The page carries a date, ideally written into the markup rather than sitting only in the text. What good looks like The page carries a date, ideally written into the markup rather than sitting only in the text. Why it matters An undated page gives nothing to weigh its age against, so old and new material are treated alike. What we found on this page the page shows the year 2026 in its text, but nothing on the page states it as the date of the content The evidence, taken from the page as served The head of this page, as served
The head of the page was read for a tag stating the date of the content. The year shown above was found in the page's own text. <head> <meta charset="utf-8"/> <style>/* @see https://github.com/aFarkas/lazysizes#broken-image-symbol */.js img.b-lazy:not([src]) { visibility: hidden; }/* @see https://github.com/aFarkas/lazysizes#automatically-setting-the-sizes-attribute */.js img.lazyloaded[data-sizes=auto] { display: block; width: 100%; }</style> <meta name="description" content="The website of Newcastle City Council"/> <meta name="geo.placename" content="Newcastle upon Tyne"/> <link rel="canonical" href="https://newcastle.gov.uk/local-government/access-information-and-data/open-data/payments-over-ps250-data-sets"/> <link rel="icon" href="favicon.ico"/> <link rel="icon" sizes="16x16" href="/favicon-16x16.png"/> <link rel="icon" sizes="32x32" href="/favicon-32x32.png"/> <link rel="icon" sizes="96x96" href="/favicon-96x96.png"/> <link rel="icon" sizes="192x192" href="/android-chrome-192x192.png"/> <link rel="apple-touch-icon" href="/apple-touch-icon-60x60.png"/> <link rel="apple-touch-icon" sizes="72x72" href="/android-chrome-72x72.png"/> <link rel="apple-touch-icon" sizes="76x76" href="/apple-touch-icon-76x76.png"/> <link rel="apple-touch-icon" sizes="114x114" href="/apple-touch-icon-114x114.png"/> <link rel="aโฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT35 | warning | the copyright line at the foot of this page carries no year, so there is nothing on the page as served to date it by | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The copyright line at the foot of the page, and the year it states. What good looks like The copyright line states the current year. Why it matters An old copyright year reads as a site nobody is looking after, and it dates the page for anything that relies on dates. Content can be treated as years older than it really is. What we found on this page the copyright line at the foot of this page carries no year, so there is nothing on the page as served to date it by The evidence, taken from the page as served The copyright line on this page, as served
This is the copyright line as the page serves it. It was read for a year, and carries none. stagram Find out how we use social media Press Office and News ReciteMe and Accessibility ยฉNewcastle City Council Privacy Notice Terms and conditions Contact Us Covid-19 support Listen and translate {"path":{"baseUrl":"\/","pathPrefix":"","c | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MX10 | warning | 2 links to a file on this page do not say what the file is and how big it is before it is opened. A reader deciding whether to open a file has nothing to judge it by, and on a slow or metered connection an unnamed file is a risk rather than an offer. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Links that open a file, and whether the wording states the format and the size. What good looks like A link to a file states its format and its size. Why it matters A reader deciding whether to open a file has nothing to judge it by, and on a slow or metered connection an unnamed file is a risk rather than an offer. What we found on this page 2 links to a file on this page do not say what the file is and how big it is before it is opened. A reader deciding whether to open a file has nothing to judge it by, and on a slow or metered connection an unnamed file is a risk rather than an offer. The evidence, taken from the page as served The links to a file, and what each one states
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
▸https://newcastle.gov.uk/local-government/access-information-and-data/open-data/public-health-funerals-data 30.7% Very likely 11 out of 67
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Fails · 6 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 AI systems are being turned away before they reach the site, and because the barrier sits outside the organisation's own systems, nobody inside can see it happening. Those systems carry on answering questions about the organisation, from other people's material rather than its own, so the conversation about it goes on without it and nobody has decided that. 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.newcastle.gov.uk · resolves to 194.61.173.205
Address trailwww.newcastle.gov.uk
Checked2026-09-17 16:33 UTC · request sent from 54.171.52.206 (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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MX01 | fail | the site took 405ms to start answering, past the point where an automated reader gives up and takes its answer from elsewhere | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check How quickly the page starts to answer when it is asked for. What good looks like The page starts answering within 250ms. Between 250 and 345ms is a warning; beyond 345ms is a fail, that being the point at which an automated reader gives up. Why it matters A page that is slow to answer is left behind: the reader gives up and takes its answer from someone else's material, so your own words play no part in it. What we found on this page the site took 405ms to start answering, past the point where an automated reader gives up and takes its answer from elsewhere The evidence, taken from the page as served How long this page took to start answering
Timed from the request leaving our checker to the first part of the answer coming back, on the page as served, so distance from the site plays its part. 345ms is the point beyond which an automated reader gives up.
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 starts answering within 250ms. 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT09 | fail | 2 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 heading 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 2 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)
H2 Main navigation H2 Title H4 Have your say level jumped H1 Public Health Funerals Data H2 Public Health Funerals Data H4 Need more information? level jumped H3 Most popular pages H3 We're on social media
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 | fail | this page carries a telephone number, and states none of it in a form a machine can take as given, so those facts have to be worked out from the wording around them | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page states what it is, and the exact facts it carries, in a form a machine can take as given rather than work out from the wording. What good looks like The page states what it is in machine-readable form, and where it carries exact facts it states those too. A page of exact facts stating none of them is a fail; a narrative page without a block is a warning. Why it matters Where a page carries exact facts, an address, opening hours, a price, a date, leaving them only in prose means they are worked out rather than read, and that is where a wrong branch or an old price comes from. What we found on this page this page carries a telephone number, and states none of it in a form a machine can take as given, so those facts have to be worked out from the wording around them The evidence, taken from the page as served The head of this page, as served
The page was read for a short block of machine-readable detail saying what it is. The page's own words carry a telephone number, which is why this weighs as it does. <head> <meta charset="utf-8"/> <style>/* @see https://github.com/aFarkas/lazysizes#broken-image-symbol */.js img.b-lazy:not([src]) { visibility: hidden; }/* @see https://github.com/aFarkas/lazysizes#automatically-setting-the-sizes-attribute */.js img.lazyloaded[data-sizes=auto] { display: block; width: 100%; }</style> <meta name="description" content="The website of Newcastle City Council"/> <meta name="geo.placename" content="Newcastle upon Tyne"/> <link rel="canonical" href="https://newcastle.gov.uk/local-government/access-information-and-data/open-data/public-health-funerals-data"/> <link rel="icon" href="favicon.ico"/> <link rel="icon" sizes="16x16" href="/favicon-16x16.png"/> <link rel="icon" sizes="32x32" href="/favicon-32x32.png"/> <link rel="icon" sizes="96x96" href="/favicon-96x96.png"/> <link rel="icon" sizes="192x192" href="/android-chrome-192x192.png"/> <link rel="apple-touch-icon" href="/apple-touch-icon-60x60.png"/> <link rel="apple-touch-icon" sizes="72x72" href="/android-chrome-72x72.png"/> <link rel="apple-touch-icon" sizes="76x76" href="/apple-touch-icon-76x76.png"/> <link rel="apple-touch-icon" sizes="114x114" href="/apple-touch-icon-114x114.png"/> <link rel="appโฆ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 states what it is in machine-readable form, and where it carries exact facts it states those too. 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT43 | fail | 1 fault in this page's construction change the structure anything reading it sees, so what is read is not quite the page that was published | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page's underlying construction holds together, or contains faults that change how it is read. What good looks like The page is built soundly enough that anything reading it sees the structure its author intended. Why it matters Anything reading the page has to take it apart before it can judge anything on it. Faults in construction can move where a section appears to end, place a heading inside a paragraph, or lose part of the page altogether. When that happens, what is read is not quite the page that was published, and neither is the answer built from it. The damage is invisible on screen, because a browser repairs quietly what a plain reader does not. What we found on this page 1 fault in this page's construction change the structure anything reading it sees, so what is read is not quite the page that was published The evidence, taken from the page as served Faults in the page's construction that change how it reads
Found while taking the page apart exactly as a reader would.
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 is built soundly enough that anything reading it sees the structure its author intended. 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 The page's headings begin at its top level, rather than starting part way down. What good looks like The page's headings begin with its top-level heading. Levels skipped further down are weighed under heading hierarchy, and a page with no top-level heading at all under the missing main heading, so each fault is marked once. Why it matters The page's structure starts part way down, below a top level that never opens it. Sections then sit under nothing, and anything filing content by structure starts in the wrong place. 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 (the starting level is marked)
H2 Main navigation level jumped H2 Title H4 Have your say H1 Public Health Funerals Data H2 Public Health Funerals Data H4 Need more information? H3 Most popular pages H3 We're on social media
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 begin with its top-level heading. 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Warnings · 5 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT32 | warning | the page's meta description, the short summary it offers about itself, runs to 37 characters, too short to say what the page is about; a usable summary runs from 50 to 170 characters | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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 the page's meta description, the short summary it offers about itself, runs to 37 characters, too short to say what the page is about; a usable summary runs from 50 to 170 characters The evidence, taken from the page as served The page's description, as served
<meta name="description" content="The website of Newcastle City Council"/> | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT40 | warning | the page offers no short summary for the services that show a preview of it, so each one composes its own from whatever it finds first on the page | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The short title, description and image the page offers to services that show a preview of it, and whether they match the page. What good looks like The page offers a summary for preview, and the summary is true to the page. Why it matters This summary travels further than the page does. It is what appears when the address is shared, and several services read it in preference to the page itself because it is short and already written for the purpose. Where it is absent, those services compose their own from whatever they find first, which is often navigation. Where it is present but out of step, the organisation is described to a wide audience by a sentence it wrote once and forgot. What we found on this page the page offers no short summary for the services that show a preview of it, so each one composes its own from whatever it finds first on the page The evidence, taken from the page as served The summary this page offers for preview
Read from the page as served.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT41 | warning | the page does not show where it sits in the site, so anything reading it on its own has nothing to say what it belongs to | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The trail showing the path from the front page to this one, and whether the machine-readable version of that trail says the same. What good looks like The page shows its place in the site, and says the same thing to a machine. Why it matters A page read on its own gives no sense of what it belongs to. The trail supplies it: one product within a range, one policy within a set. A reader deciding whether a page answers a question uses that to judge whether it has the right one, and how to describe it when it quotes it. Where the shown trail and the machine-readable one disagree, the page is placed in two positions at once and neither can be relied on. What we found on this page the page does not show where it sits in the site, so anything reading it on its own has nothing to say what it belongs to The evidence, taken from the page as served The path this page gives to itself
Read from the page as served: the trail shown to a reader, and the trail stated in a form a machine can take as given.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT04 | warning | the page carries no date, so there is nothing on it saying how current its content is | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The page carries a date, ideally written into the markup rather than sitting only in the text. What good looks like The page carries a date, ideally written into the markup rather than sitting only in the text. Why it matters An undated page gives nothing to weigh its age against, so old and new material are treated alike. What we found on this page the page carries no date, so there is nothing on it saying how current its content is The evidence, taken from the page as served The head of this page, as served
The head of the page and the page's own text were read for a date. <head> <meta charset="utf-8"/> <style>/* @see https://github.com/aFarkas/lazysizes#broken-image-symbol */.js img.b-lazy:not([src]) { visibility: hidden; }/* @see https://github.com/aFarkas/lazysizes#automatically-setting-the-sizes-attribute */.js img.lazyloaded[data-sizes=auto] { display: block; width: 100%; }</style> <meta name="description" content="The website of Newcastle City Council"/> <meta name="geo.placename" content="Newcastle upon Tyne"/> <link rel="canonical" href="https://newcastle.gov.uk/local-government/access-information-and-data/open-data/public-health-funerals-data"/> <link rel="icon" href="favicon.ico"/> <link rel="icon" sizes="16x16" href="/favicon-16x16.png"/> <link rel="icon" sizes="32x32" href="/favicon-32x32.png"/> <link rel="icon" sizes="96x96" href="/favicon-96x96.png"/> <link rel="icon" sizes="192x192" href="/android-chrome-192x192.png"/> <link rel="apple-touch-icon" href="/apple-touch-icon-60x60.png"/> <link rel="apple-touch-icon" sizes="72x72" href="/android-chrome-72x72.png"/> <link rel="apple-touch-icon" sizes="76x76" href="/apple-touch-icon-76x76.png"/> <link rel="apple-touch-icon" sizes="114x114" href="/apple-touch-icon-114x114.png"/> <link rel="appโฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT35 | warning | the copyright line at the foot of this page carries no year, so there is nothing on the page as served to date it by | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The copyright line at the foot of the page, and the year it states. What good looks like The copyright line states the current year. Why it matters An old copyright year reads as a site nobody is looking after, and it dates the page for anything that relies on dates. Content can be treated as years older than it really is. What we found on this page the copyright line at the foot of this page carries no year, so there is nothing on the page as served to date it by The evidence, taken from the page as served The copyright line on this page, as served
This is the copyright line as the page serves it. It was read for a year, and carries none. stagram Find out how we use social media Press Office and News ReciteMe and Accessibility ยฉNewcastle City Council Privacy Notice Terms and conditions Contact Us Covid-19 support Listen and translate {"path":{"baseUrl":"\/","pathPrefix":"","c | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
▸https://newcastle.gov.uk/local-government/access-information-and-data/open-data/public-sector-apprenticeship-target 9.7% Extremely likely 13 out of 67
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Fails · 7 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 AI systems are being turned away before they reach the site, and because the barrier sits outside the organisation's own systems, nobody inside can see it happening. Those systems carry on answering questions about the organisation, from other people's material rather than its own, so the conversation about it goes on without it and nobody has decided that. 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.newcastle.gov.uk · resolves to 194.61.173.205
Address trailwww.newcastle.gov.uk
Checked2026-09-17 16:33 UTC · request sent from 54.171.52.206 (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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MX01 | fail | the site took 397ms to start answering, past the point where an automated reader gives up and takes its answer from elsewhere | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check How quickly the page starts to answer when it is asked for. What good looks like The page starts answering within 250ms. Between 250 and 345ms is a warning; beyond 345ms is a fail, that being the point at which an automated reader gives up. Why it matters A page that is slow to answer is left behind: the reader gives up and takes its answer from someone else's material, so your own words play no part in it. What we found on this page the site took 397ms to start answering, past the point where an automated reader gives up and takes its answer from elsewhere The evidence, taken from the page as served How long this page took to start answering
Timed from the request leaving our checker to the first part of the answer coming back, on the page as served, so distance from the site plays its part. 345ms is the point beyond which an automated reader gives up.
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 starts answering within 250ms. 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 heading 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)
H2 Main navigation H2 Title H4 Have your say level jumped H1 Public sector apprenticeship target H2 Public sector apprenticeship target H2 Data H3 April 2021 to March 2022 H3 April 2020ย to March 2021 H3 April 2019ย to March 2020 H3 April 2018ย to March 2019 H3 April 2017ย to March 2018 H3 Most popular pages H3 We're on social media
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 | fail | this page carries prices or figures and dates, and states none of it in a form a machine can take as given, so those facts have to be worked out from the wording around them | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page states what it is, and the exact facts it carries, in a form a machine can take as given rather than work out from the wording. What good looks like The page states what it is in machine-readable form, and where it carries exact facts it states those too. A page of exact facts stating none of them is a fail; a narrative page without a block is a warning. Why it matters Where a page carries exact facts, an address, opening hours, a price, a date, leaving them only in prose means they are worked out rather than read, and that is where a wrong branch or an old price comes from. What we found on this page this page carries prices or figures and dates, and states none of it in a form a machine can take as given, so those facts have to be worked out from the wording around them The evidence, taken from the page as served The head of this page, as served
The page was read for a short block of machine-readable detail saying what it is. The page's own words carry prices or figures and dates, which is why this weighs as it does. <head> <meta charset="utf-8"/> <style>/* @see https://github.com/aFarkas/lazysizes#broken-image-symbol */.js img.b-lazy:not([src]) { visibility: hidden; }/* @see https://github.com/aFarkas/lazysizes#automatically-setting-the-sizes-attribute */.js img.lazyloaded[data-sizes=auto] { display: block; width: 100%; }</style> <meta name="description" content="The website of Newcastle City Council"/> <meta name="geo.placename" content="Newcastle upon Tyne"/> <link rel="canonical" href="https://newcastle.gov.uk/local-government/access-information-and-data/open-data/public-sector-apprenticeship-target"/> <link rel="icon" href="favicon.ico"/> <link rel="icon" sizes="16x16" href="/favicon-16x16.png"/> <link rel="icon" sizes="32x32" href="/favicon-32x32.png"/> <link rel="icon" sizes="96x96" href="/favicon-96x96.png"/> <link rel="icon" sizes="192x192" href="/android-chrome-192x192.png"/> <link rel="apple-touch-icon" href="/apple-touch-icon-60x60.png"/> <link rel="apple-touch-icon" sizes="72x72" href="/android-chrome-72x72.png"/> <link rel="apple-touch-icon" sizes="76x76" href="/apple-touch-icon-76x76.png"/> <link rel="apple-touch-icon" sizes="114x114" href="/apple-touch-icon-114x114.png"/> <link โฆ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 states what it is in machine-readable form, and where it carries exact facts it states those too. 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT43 | fail | 1 fault in this page's construction change the structure anything reading it sees, so what is read is not quite the page that was published | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page's underlying construction holds together, or contains faults that change how it is read. What good looks like The page is built soundly enough that anything reading it sees the structure its author intended. Why it matters Anything reading the page has to take it apart before it can judge anything on it. Faults in construction can move where a section appears to end, place a heading inside a paragraph, or lose part of the page altogether. When that happens, what is read is not quite the page that was published, and neither is the answer built from it. The damage is invisible on screen, because a browser repairs quietly what a plain reader does not. What we found on this page 1 fault in this page's construction change the structure anything reading it sees, so what is read is not quite the page that was published The evidence, taken from the page as served Faults in the page's construction that change how it reads
Found while taking the page apart exactly as a reader would.
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 is built soundly enough that anything reading it sees the structure its author intended. 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 The page's headings begin at its top level, rather than starting part way down. What good looks like The page's headings begin with its top-level heading. Levels skipped further down are weighed under heading hierarchy, and a page with no top-level heading at all under the missing main heading, so each fault is marked once. Why it matters The page's structure starts part way down, below a top level that never opens it. Sections then sit under nothing, and anything filing content by structure starts in the wrong place. 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 (the starting level is marked)
H2 Main navigation level jumped H2 Title H4 Have your say H1 Public sector apprenticeship target H2 Public sector apprenticeship target H2 Data H3 April 2021 to March 2022 H3 April 2020ย to March 2021 H3 April 2019ย to March 2020 H3 April 2018ย to March 2019 H3 April 2017ย to March 2018 H3 Most popular pages H3 We're on social media
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 begin with its top-level heading. 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 | 5 of 5 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 5 of 5 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> <tbody> <tr> <td> <p><span><span><span><span><span>Number of employees on 31 March 202</span></span><span><span>1</span></span></span></span></span></p> </td> <td> <p><span><span><span><span><span>5,627</span></span></span></span></span></p> </td> </tr> <tr> <td> <p><span><span><span><span><span>Number of emploโฆ <table> <tbody> <tr> <td> <p><span><span><span><span><span>Number of employees on 31 March 2020</span></span></span></span></span></p> </td> <td> <p><span><span><span><span><span>5,783</span></span></span></span></span></p> </td> </tr> <tr> <td> <p><span><span><span><span><span>Number of employees on 31 March 2021</spaโฆ <table> <tbody> <tr> <td> <p><span><span><span><span><span>Number of employees on 31 March 2019</span></span></span></span></span></p> </td> <td> <p><span><span><span><span><span>5,870</span></span></span></span></span></p> </td> </tr> <tr> <td> <p><span><span><span><span><span>Number of employees on 31 March 2020</spaโฆ <table> <tbody> <tr> <td> <p><span><span><span><span><span>Number of employees on 31 March 2018</span></span></span></span></span></p> </td> <td> <p><span><span><span><span><span>5,959</span></span></span></span></span></p> </td> </tr> <tr> <td> <p><span><span><span><span><span>Number of employees on 31 March 2019</spaโฆ <table> <tbody> <tr> <td> <p><span><span><span><span><span>Number of employees on 31 March 2017</span></span></span></span></span></p> </td> <td> <p><span><span><span><span><span>7,130</span></span></span></span></span></p> </td> </tr> <tr> <td> <p><span><span><span><span><span>Number of employees on 31 March 2018</spaโฆ 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Warnings · 6 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT32 | warning | the page's meta description, the short summary it offers about itself, runs to 37 characters, too short to say what the page is about; a usable summary runs from 50 to 170 characters | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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 the page's meta description, the short summary it offers about itself, runs to 37 characters, too short to say what the page is about; a usable summary runs from 50 to 170 characters The evidence, taken from the page as served The page's description, as served
<meta name="description" content="The website of Newcastle City Council"/> | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT40 | warning | the page offers no short summary for the services that show a preview of it, so each one composes its own from whatever it finds first on the page | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The short title, description and image the page offers to services that show a preview of it, and whether they match the page. What good looks like The page offers a summary for preview, and the summary is true to the page. Why it matters This summary travels further than the page does. It is what appears when the address is shared, and several services read it in preference to the page itself because it is short and already written for the purpose. Where it is absent, those services compose their own from whatever they find first, which is often navigation. Where it is present but out of step, the organisation is described to a wide audience by a sentence it wrote once and forgot. What we found on this page the page offers no short summary for the services that show a preview of it, so each one composes its own from whatever it finds first on the page The evidence, taken from the page as served The summary this page offers for preview
Read from the page as served.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT41 | warning | the page does not show where it sits in the site, so anything reading it on its own has nothing to say what it belongs to | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The trail showing the path from the front page to this one, and whether the machine-readable version of that trail says the same. What good looks like The page shows its place in the site, and says the same thing to a machine. Why it matters A page read on its own gives no sense of what it belongs to. The trail supplies it: one product within a range, one policy within a set. A reader deciding whether a page answers a question uses that to judge whether it has the right one, and how to describe it when it quotes it. Where the shown trail and the machine-readable one disagree, the page is placed in two positions at once and neither can be relied on. What we found on this page the page does not show where it sits in the site, so anything reading it on its own has nothing to say what it belongs to The evidence, taken from the page as served The path this page gives to itself
Read from the page as served: the trail shown to a reader, and the trail stated in a form a machine can take as given.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR06 | warning | 36 figures on this page have no source named in the same passage, such as โ2.3 percentโ. A figure with nothing beside it cannot be checked by a reader, or by anything quoting the page. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Percentages and money figures in the page's words, and whether a source is named or linked in the same passage. What good looks like A published figure names its source in the same passage. Why it matters A figure with no source cannot be checked by a reader or by anything quoting it. It travels on the organisation's name alone, and it is repeated that way. What we found on this page 36 figures on this page have no source named in the same passage, such as โ2.3 percentโ. A figure with nothing beside it cannot be checked by a reader, or by anything quoting the page. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT04 | warning | the page shows the year 2022 in its text, but nothing on the page states it as the date of the content | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The page carries a date, ideally written into the markup rather than sitting only in the text. What good looks like The page carries a date, ideally written into the markup rather than sitting only in the text. Why it matters An undated page gives nothing to weigh its age against, so old and new material are treated alike. What we found on this page the page shows the year 2022 in its text, but nothing on the page states it as the date of the content The evidence, taken from the page as served The head of this page, as served
The head of the page was read for a tag stating the date of the content. The year shown above was found in the page's own text. <head> <meta charset="utf-8"/> <style>/* @see https://github.com/aFarkas/lazysizes#broken-image-symbol */.js img.b-lazy:not([src]) { visibility: hidden; }/* @see https://github.com/aFarkas/lazysizes#automatically-setting-the-sizes-attribute */.js img.lazyloaded[data-sizes=auto] { display: block; width: 100%; }</style> <meta name="description" content="The website of Newcastle City Council"/> <meta name="geo.placename" content="Newcastle upon Tyne"/> <link rel="canonical" href="https://newcastle.gov.uk/local-government/access-information-and-data/open-data/public-sector-apprenticeship-target"/> <link rel="icon" href="favicon.ico"/> <link rel="icon" sizes="16x16" href="/favicon-16x16.png"/> <link rel="icon" sizes="32x32" href="/favicon-32x32.png"/> <link rel="icon" sizes="96x96" href="/favicon-96x96.png"/> <link rel="icon" sizes="192x192" href="/android-chrome-192x192.png"/> <link rel="apple-touch-icon" href="/apple-touch-icon-60x60.png"/> <link rel="apple-touch-icon" sizes="72x72" href="/android-chrome-72x72.png"/> <link rel="apple-touch-icon" sizes="76x76" href="/apple-touch-icon-76x76.png"/> <link rel="apple-touch-icon" sizes="114x114" href="/apple-touch-icon-114x114.png"/> <link โฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT35 | warning | the copyright line at the foot of this page carries no year, so there is nothing on the page as served to date it by | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The copyright line at the foot of the page, and the year it states. What good looks like The copyright line states the current year. Why it matters An old copyright year reads as a site nobody is looking after, and it dates the page for anything that relies on dates. Content can be treated as years older than it really is. What we found on this page the copyright line at the foot of this page carries no year, so there is nothing on the page as served to date it by The evidence, taken from the page as served The copyright line on this page, as served
This is the copyright line as the page serves it. It was read for a year, and carries none. stagram Find out how we use social media Press Office and News ReciteMe and Accessibility ยฉNewcastle City Council Privacy Notice Terms and conditions Contact Us Covid-19 support Listen and translate {"path":{"baseUrl":"\/","pathPrefix":"","c | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
▸https://newcastle.gov.uk/local-government/access-information-and-data/open-data/purchase-card-expenditure 31.0% Very likely 12 out of 67
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Fails · 5 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 AI systems are being turned away before they reach the site, and because the barrier sits outside the organisation's own systems, nobody inside can see it happening. Those systems carry on answering questions about the organisation, from other people's material rather than its own, so the conversation about it goes on without it and nobody has decided that. 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.newcastle.gov.uk · resolves to 194.61.173.205
Address trailwww.newcastle.gov.uk
Checked2026-09-17 16:33 UTC · request sent from 54.171.52.206 (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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MX01 | fail | the site took 381ms to start answering, past the point where an automated reader gives up and takes its answer from elsewhere | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check How quickly the page starts to answer when it is asked for. What good looks like The page starts answering within 250ms. Between 250 and 345ms is a warning; beyond 345ms is a fail, that being the point at which an automated reader gives up. Why it matters A page that is slow to answer is left behind: the reader gives up and takes its answer from someone else's material, so your own words play no part in it. What we found on this page the site took 381ms to start answering, past the point where an automated reader gives up and takes its answer from elsewhere The evidence, taken from the page as served How long this page took to start answering
Timed from the request leaving our checker to the first part of the answer coming back, on the page as served, so distance from the site plays its part. 345ms is the point beyond which an automated reader gives up.
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 starts answering within 250ms. 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 heading 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)
H2 Main navigation H2 Title H4 Have your say level jumped H1 Purchase card expenditure H2 Purchase card expenditure H3 April 2026 to March 2027 H3 April 2025 to March 2026 H3 April 2024 to March 2025 H3 April 2023 to March 2024 H3 April 2022 to March 2023 H3 April 2021 to March 2022 H3 April 2020 to March 2021 H3 April 2019 to March 2020 H3 Most popular pages H3 We're on social media
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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT43 | fail | 1 fault in this page's construction change the structure anything reading it sees, so what is read is not quite the page that was published | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page's underlying construction holds together, or contains faults that change how it is read. What good looks like The page is built soundly enough that anything reading it sees the structure its author intended. Why it matters Anything reading the page has to take it apart before it can judge anything on it. Faults in construction can move where a section appears to end, place a heading inside a paragraph, or lose part of the page altogether. When that happens, what is read is not quite the page that was published, and neither is the answer built from it. The damage is invisible on screen, because a browser repairs quietly what a plain reader does not. What we found on this page 1 fault in this page's construction change the structure anything reading it sees, so what is read is not quite the page that was published The evidence, taken from the page as served Faults in the page's construction that change how it reads
Found while taking the page apart exactly as a reader would.
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 is built soundly enough that anything reading it sees the structure its author intended. 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 The page's headings begin at its top level, rather than starting part way down. What good looks like The page's headings begin with its top-level heading. Levels skipped further down are weighed under heading hierarchy, and a page with no top-level heading at all under the missing main heading, so each fault is marked once. Why it matters The page's structure starts part way down, below a top level that never opens it. Sections then sit under nothing, and anything filing content by structure starts in the wrong place. 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 (the starting level is marked)
H2 Main navigation level jumped H2 Title H4 Have your say H1 Purchase card expenditure H2 Purchase card expenditure H3 April 2026 to March 2027 H3 April 2025 to March 2026 H3 April 2024 to March 2025 H3 April 2023 to March 2024 H3 April 2022 to March 2023 H3 April 2021 to March 2022 H3 April 2020 to March 2021 H3 April 2019 to March 2020 H3 Most popular pages H3 We're on social media
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 begin with its top-level heading. 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Warnings · 7 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT32 | warning | the page's meta description, the short summary it offers about itself, runs to 37 characters, too short to say what the page is about; a usable summary runs from 50 to 170 characters | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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 the page's meta description, the short summary it offers about itself, runs to 37 characters, too short to say what the page is about; a usable summary runs from 50 to 170 characters The evidence, taken from the page as served The page's description, as served
<meta name="description" content="The website of Newcastle City Council"/> | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT16 | warning | the page states nothing about itself in a form a machine can take as given, so who you are and what the page is about are worked out from its wording | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the page states what it is, and the exact facts it carries, in a form a machine can take as given rather than work out from the wording. What good looks like The page states what it is in machine-readable form, and where it carries exact facts it states those too. A page of exact facts stating none of them is a fail; a narrative page without a block is a warning. Why it matters Where a page carries exact facts, an address, opening hours, a price, a date, leaving them only in prose means they are worked out rather than read, and that is where a wrong branch or an old price comes from. What we found on this page the page states nothing about itself in a form a machine can take as given, so who you are and what the page is about are worked out from its wording The evidence, taken from the page as served The head of this page, as served
The page was read for a short block of machine-readable detail saying what it is. The page's own words carry no exact facts of that kind. <head> <meta charset="utf-8"/> <style>/* @see https://github.com/aFarkas/lazysizes#broken-image-symbol */.js img.b-lazy:not([src]) { visibility: hidden; }/* @see https://github.com/aFarkas/lazysizes#automatically-setting-the-sizes-attribute */.js img.lazyloaded[data-sizes=auto] { display: block; width: 100%; }</style> <meta name="description" content="The website of Newcastle City Council"/> <meta name="geo.placename" content="Newcastle upon Tyne"/> <link rel="canonical" href="https://newcastle.gov.uk/local-government/access-information-and-data/open-data/purchase-card-expenditure"/> <link rel="icon" href="favicon.ico"/> <link rel="icon" sizes="16x16" href="/favicon-16x16.png"/> <link rel="icon" sizes="32x32" href="/favicon-32x32.png"/> <link rel="icon" sizes="96x96" href="/favicon-96x96.png"/> <link rel="icon" sizes="192x192" href="/android-chrome-192x192.png"/> <link rel="apple-touch-icon" href="/apple-touch-icon-60x60.png"/> <link rel="apple-touch-icon" sizes="72x72" href="/android-chrome-72x72.png"/> <link rel="apple-touch-icon" sizes="76x76" href="/apple-touch-icon-76x76.png"/> <link rel="apple-touch-icon" sizes="114x114" href="/apple-touch-icon-114x114.png"/> <link rel="appleโฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT40 | warning | the page offers no short summary for the services that show a preview of it, so each one composes its own from whatever it finds first on the page | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The short title, description and image the page offers to services that show a preview of it, and whether they match the page. What good looks like The page offers a summary for preview, and the summary is true to the page. Why it matters This summary travels further than the page does. It is what appears when the address is shared, and several services read it in preference to the page itself because it is short and already written for the purpose. Where it is absent, those services compose their own from whatever they find first, which is often navigation. Where it is present but out of step, the organisation is described to a wide audience by a sentence it wrote once and forgot. What we found on this page the page offers no short summary for the services that show a preview of it, so each one composes its own from whatever it finds first on the page The evidence, taken from the page as served The summary this page offers for preview
Read from the page as served.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT41 | warning | the page does not show where it sits in the site, so anything reading it on its own has nothing to say what it belongs to | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The trail showing the path from the front page to this one, and whether the machine-readable version of that trail says the same. What good looks like The page shows its place in the site, and says the same thing to a machine. Why it matters A page read on its own gives no sense of what it belongs to. The trail supplies it: one product within a range, one policy within a set. A reader deciding whether a page answers a question uses that to judge whether it has the right one, and how to describe it when it quotes it. Where the shown trail and the machine-readable one disagree, the page is placed in two positions at once and neither can be relied on. What we found on this page the page does not show where it sits in the site, so anything reading it on its own has nothing to say what it belongs to The evidence, taken from the page as served The path this page gives to itself
Read from the page as served: the trail shown to a reader, and the trail stated in a form a machine can take as given.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT04 | warning | the page shows the year 2026 in its text, but nothing on the page states it as the date of the content | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The page carries a date, ideally written into the markup rather than sitting only in the text. What good looks like The page carries a date, ideally written into the markup rather than sitting only in the text. Why it matters An undated page gives nothing to weigh its age against, so old and new material are treated alike. What we found on this page the page shows the year 2026 in its text, but nothing on the page states it as the date of the content The evidence, taken from the page as served The head of this page, as served
The head of the page was read for a tag stating the date of the content. The year shown above was found in the page's own text. <head> <meta charset="utf-8"/> <style>/* @see https://github.com/aFarkas/lazysizes#broken-image-symbol */.js img.b-lazy:not([src]) { visibility: hidden; }/* @see https://github.com/aFarkas/lazysizes#automatically-setting-the-sizes-attribute */.js img.lazyloaded[data-sizes=auto] { display: block; width: 100%; }</style> <meta name="description" content="The website of Newcastle City Council"/> <meta name="geo.placename" content="Newcastle upon Tyne"/> <link rel="canonical" href="https://newcastle.gov.uk/local-government/access-information-and-data/open-data/purchase-card-expenditure"/> <link rel="icon" href="favicon.ico"/> <link rel="icon" sizes="16x16" href="/favicon-16x16.png"/> <link rel="icon" sizes="32x32" href="/favicon-32x32.png"/> <link rel="icon" sizes="96x96" href="/favicon-96x96.png"/> <link rel="icon" sizes="192x192" href="/android-chrome-192x192.png"/> <link rel="apple-touch-icon" href="/apple-touch-icon-60x60.png"/> <link rel="apple-touch-icon" sizes="72x72" href="/android-chrome-72x72.png"/> <link rel="apple-touch-icon" sizes="76x76" href="/apple-touch-icon-76x76.png"/> <link rel="apple-touch-icon" sizes="114x114" href="/apple-touch-icon-114x114.png"/> <link rel="appleโฆ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CT35 | warning | the copyright line at the foot of this page carries no year, so there is nothing on the page as served to date it by | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The copyright line at the foot of the page, and the year it states. What good looks like The copyright line states the current year. Why it matters An old copyright year reads as a site nobody is looking after, and it dates the page for anything that relies on dates. Content can be treated as years older than it really is. What we found on this page the copyright line at the foot of this page carries no year, so there is nothing on the page as served to date it by The evidence, taken from the page as served The copyright line on this page, as served
This is the copyright line as the page serves it. It was read for a year, and carries none. stagram Find out how we use social media Press Office and News ReciteMe and Accessibility ยฉNewcastle City Council Privacy Notice Terms and conditions Contact Us Covid-19 support Listen and translate {"path":{"baseUrl":"\/","pathPrefix":"","c | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MX10 | warning | one link to a file on this page does not say what the file is and how big it is before it is opened. A reader deciding whether to open a file has nothing to judge it by, and on a slow or metered connection an unnamed file is a risk rather than an offer. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Links that open a file, and whether the wording states the format and the size. What good looks like A link to a file states its format and its size. Why it matters A reader deciding whether to open a file has nothing to judge it by, and on a slow or metered connection an unnamed file is a risk rather than an offer. What we found on this page one link to a file on this page does not say what the file is and how big it is before it is opened. A reader deciding whether to open a file has nothing to judge it by, and on a slow or metered connection an unnamed file is a risk rather than an offer. The evidence, taken from the page as served The links to a file, and what each one states
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
▸PDF documents 5 documents · click to view
The first documents discovered on the estate, scored separately from pages.
▸https://www.newcastle.gov.uk/sites/default/files/MEES/MEES%20Quick%20Guide.pdf 56.3% Likely 3 out of 28
The document https://www.newcastle.gov.uk/sites/default/files/MEES/MEES%20Quick%20Guide.pdf
| Document information | |
|---|---|
| Title | Landlord's guide to Minimum Energey Efficiency Standards (MEES) |
| Author | not set |
| PDF version, pages, size | 1.6 ยท 6 pages ยท 183 KB |
| Found on | https://newcastle.gov.uk/MEES |
| Check | Result | Evidence | |||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Fails · 2 | |||||||||||||||||||||
| PD21 | fail | the document names no author, so nothing in it says who is answerable for what it states | |||||||||||||||||||
What we check Whether the author field names a person or an organisation, rather than a placeholder or a tool name. What good looks like The author field names a person or an organisation, not a placeholder or a tool name. Why it matters With no named author the document carries no accountable source, so nothing shows who stands behind it. What we found on this page the document names no author, so nothing in it says who is answerable for what it states 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 named author.
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 author field names a person or an organisation, not a placeholder or a tool name. 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 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. | |||||||||||||||||||||
| PD16 | fail | the document writes out 2 web addresses as plain text but saves none of them as real, clickable links, so the addresses sit in the text with no link behind them to follow to the source | |||||||||||||||||||
What we check Whether the document's links are recorded as real links, or just web addresses typed as plain text. What good looks like The document's links are recorded as real links, not web addresses typed as plain text. Why it matters When a source is only typed out as text, there is no link behind it to follow, so the reference cannot be opened or checked. What we found on this page the document writes out 2 web addresses as plain text but saves none of them as real, clickable links, so the addresses sit in the text with no link behind them to follow to the source The evidence, taken from the page as served The web addresses written out in the text, with no link behind them
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's links are recorded as real links, not web addresses typed as plain text. 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. | |||||||||||||||||||||
| Warnings · 1 | |||||||||||||||||||||
| PD08 | warning | filename "MEES%20Quick%20Guide.pdf" is a code or generic name; on its own it does not say what the document is. The file's own title, "Landlord's guide to Minimum Energey Efficiency Standards (MEES)", identifies it. | |||||||||||||||||||
What we check The file's name, read together with the title in the file's own properties: whether its words, dates and period markers say what the document is. What good looks like A name whose words and dates identify the document, such as FY_2025_Announcement.pdf, passes. A WARNING means the name only half-identifies it: a single hinting word, period markers without a subject (FY25_Q3.pdf), or a weak name that the file's own title completes. A FAIL means a code or generic name, such as IMG_1234.pdf, with no title in the properties either, so nothing anywhere says what the document is. Why it matters The document has no usable name anywhere, neither in its file name nor in its own properties. Nobody, human or AI, can tell what it is without opening it, so it gets quoted blind or passed over. What we found on this page filename "MEES%20Quick%20Guide.pdf" is a code or generic name; on its own it does not say what the document is. The file's own title, "Landlord's guide to Minimum Energey Efficiency Standards (MEES)", identifies it. The evidence, taken from the page as served This document's properties, as recorded in the file
The file name and the file's own properties are read together: a title in the properties can complete a name that is weak on its own.
| |||||||||||||||||||||
| Alerts · 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.
| |||||||||||||||||||||
▸https://www.newcastle.gov.uk/sites/default/files/2024-08/Energy%20Performance%20Financial%20Enforcement%20Policy%202024.pdf 28.3% Very likely 5 out of 29
| Document information | |
|---|---|
| Title | not set |
| Author | David |
| PDF version, pages, size | 1.7 ยท 19 pages ยท 377 KB |
| Found on | https://newcastle.gov.uk/MEES |
| Check | Result | Evidence | |||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Fails · 5 | |||||||||||||||||||||||
| PD09 | fail | the document has no title set in its properties, so it can only be identified by its file name or the link text pointing to it | |||||||||||||||||||||
What we check Whether the document carries a title in its own properties, not just a name on the link to it. What good looks like The document carries a title in its own properties. Why it matters Without a title the document is identified by its file name and by whatever the links to it happen to say. What we found on this page the document has no title set in its properties, so it can only be identified by its file name or the link text pointing to it 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 title.
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 carries a title in its own properties. 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. | |||||||||||||||||||||||
| PD08 | fail | filename "Energy%20Performance%20Financial%20Enforcement%20Policy%202024.pdf" is a code or generic name: nothing in it says what the document is, and the file's own properties carry no title either. | |||||||||||||||||||||
What we check The file's name, read together with the title in the file's own properties: whether its words, dates and period markers say what the document is. What good looks like A name whose words and dates identify the document, such as FY_2025_Announcement.pdf, passes. A WARNING means the name only half-identifies it: a single hinting word, period markers without a subject (FY25_Q3.pdf), or a weak name that the file's own title completes. A FAIL means a code or generic name, such as IMG_1234.pdf, with no title in the properties either, so nothing anywhere says what the document is. Why it matters The document has no usable name anywhere, neither in its file name nor in its own properties. Nobody, human or AI, can tell what it is without opening it, so it gets quoted blind or passed over. What we found on this page filename "Energy%20Performance%20Financial%20Enforcement%20Policy%202024.pdf" is a code or generic name: nothing in it says what the document is, and the file's own properties carry no title either. The evidence, taken from the page as served This document's properties, as recorded in the file
The file name and the file's own properties are read together: a title in the properties can complete a name that is weak on its own.
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 name whose words and dates identify the document, such as FY_2025_Announcement.pdf, passes. 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. | |||||||||||||||||||||||
| 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
1 Energy Performance. Financial Penalty Enforcement Policy. August 2024. Version 1. Directorate of City Operations, Neighbourhoods and Regulatory Services. Energy Performance. Financial Penalty Enforcement Policy The Energy Performance of Buildings (England and Wales) Regulations 2012. (SI 2012 No.3118) As amended by the Energy Performance of Buildings (England and Wales) (Amendment) (No.2) Regulations 2015 (SI 2015 No.1681) 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 | fail | 2 of 2 image(s) carry no text description, so what those images show is missing from the document's text | |||||||||||||||||||||
What we check Whether the document's images carry a text description of what they show. What good looks like Images in the document carry a text description of what they show. An image with none is a fail: what it shows is missing from the text. Why it matters Some images in the document have no text description, so whatever they show is missing from the document's text. A chart is the classic loss: the picture holds the figures and the text never states them. What we found on this page 2 of 2 image(s) carry no text description, so what those images show is missing from the document's text The evidence, taken from the page as served The images, page by page: where each sits and what the file records about it
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: images in the document carry a text 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. | |||||||||||||||||||||||
| PD28 | fail | 3 font(s) drawing text on 8 page(s) carry no character map of their own and rely on a standard encoding to be read at all, which the file does not guarantee to any reader | |||||||||||||||||||||
What we check Whether the fonts that actually draw text in the document state which character each shape stands for, in a character map or a standard encoding. What good looks like The fonts drawing text state their characters. A font stating them nowhere, neither a map nor a standard encoding, is a fail whatever its spread. A font relying on a standard encoding alone is allowed once on up to four pages, and fails beyond that. Damage seen in the reading is a fail in any case. Why it matters A document stores its text as shapes; unless the font says which character each shape is, a reader can see the words but cannot know what they say. Text that cannot be named cannot be quoted, searched or read aloud correctly. What we found on this page 3 font(s) drawing text on 8 page(s) carry no character map of their own and rely on a standard encoding to be read at all, which the file does not guarantee to any reader The evidence, taken from the page as served The fonts whose text has no character map, and where each is used
A font stores shapes. The map from those shapes back to real characters is what lets the words be read out of the file. Without it the shapes still print correctly on paper, so the document looks perfect, while the text taken from it comes out as the wrong characters. Carrying the font inside the document and recording that map are two separate things: a font can be carried in full and still record no map, and that is the more serious case, because nothing looks wrong at any point and the wrong characters appear only once the document is read by machine. Each font below states which of the two applies to it.
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 fonts drawing text state their characters. 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. | |||||||||||||||||||||||
| Alerts · 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.
| |||||||||||||||||||||||
▸https://www.newcastle.gov.uk/sites/default/files/2019-01/planning_for_the_future_core_strategy_and_urban_core_plan_2010-2030.pdf 22.3% Very likely 13 out of 28
| Document information | |
|---|---|
| Title | not set |
| Author | not set |
| PDF version, pages, size | 1.7 ยท 360 pages ยท 49198 KB |
| Found on | https://newcastle.gov.uk/Plot12PlanningAppeal |
| Check | Result | Evidence | ||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Fails · 10 | ||||||||||||||||||||||||||||||||||||||||||
| PD21 | fail | the document names no author, so nothing in it says who is answerable for what it states | ||||||||||||||||||||||||||||||||||||||||
What we check Whether the author field names a person or an organisation, rather than a placeholder or a tool name. What good looks like The author field names a person or an organisation, not a placeholder or a tool name. Why it matters With no named author the document carries no accountable source, so nothing shows who stands behind it. What we found on this page the document names no author, so nothing in it says who is answerable for what it states 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 named author.
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 author field names a person or an organisation, not a placeholder or a tool name. 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 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. | ||||||||||||||||||||||||||||||||||||||||||
| PD26 | fail | the document is 10 years old (last dated 2015-10); content this old is a weak, less trustworthy source | ||||||||||||||||||||||||||||||||||||||||
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 10 years old (last dated 2015-10); content this old is a weak, less trustworthy source 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.
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's most recent internal date is recent rather than long past. 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. | ||||||||||||||||||||||||||||||||||||||||||
| PD22 | fail | the document's dates disagree: the file records 2015-10 as its own date, while the address it is served under carries 2019-01. A reader cannot tell which is true, and the newer date on the address hides how old the content is | ||||||||||||||||||||||||||||||||||||||||
What we check Whether the document records when it was created or last changed, alongside the software that made it. What good looks like The document records when it was created or last changed. Why it matters With no dates on the file there is no way to tell a document written last month from one written a decade ago. What we found on this page the document's dates disagree: the file records 2015-10 as its own date, while the address it is served under carries 2019-01. A reader cannot tell which is true, and the newer date on the address hides how old the content is The evidence, taken from the page as served This document's properties, as recorded in the file
The file's own dates were read and compared with the date carried in the document's web address.
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 records when it was created or last changed. 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 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. | ||||||||||||||||||||||||||||||||||||||||||
| PD19 | fail | the document is 48.0MB, past the size at which readers take a document in part or skip it, so its later sections carry no weight | ||||||||||||||||||||||||||||||||||||||||
What we check The size of the document as the site serves it, and whether the same content is also published as an ordinary web page. What good looks like The document is under 3.7MB, or the same content is also published as an ordinary web page. From 3.7MB it is a warning, and beyond 7.2MB a fail, unless that web version exists. Why it matters A very large document is taken in part or skipped, so its later sections carry no weight, and that is usually where the figures and the detail sit. What we found on this page the document is 48.0MB, past the size at which readers take a document in part or skip it, so its later sections carry no weight The evidence, taken from the page as served How large this document is
Measured from the file as the site served it. Where the same content is also published as an ordinary web page, this size does not count against the organisation, since nothing then depends on the file being read.
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 is under 3.7MB, or the same content is also published as an ordinary web page. 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 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. | ||||||||||||||||||||||||||||||||||||||||||
| PD09 | fail | the document has no title set in its properties, so it can only be identified by its file name or the link text pointing to it | ||||||||||||||||||||||||||||||||||||||||
What we check Whether the document carries a title in its own properties, not just a name on the link to it. What good looks like The document carries a title in its own properties. Why it matters Without a title the document is identified by its file name and by whatever the links to it happen to say. What we found on this page the document has no title set in its properties, so it can only be identified by its file name or the link text pointing to it 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 title.
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 carries a title in its own properties. 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. | ||||||||||||||||||||||||||||||||||||||||||
| 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
Planning for the Future Core Strategy and Urban Core Plan for Gateshead and Newcastle upon Tyne 2010-2030 Adopted March 2015 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 | fail | the document has images and none carries a text description, so what the images show is missing from the document's text | ||||||||||||||||||||||||||||||||||||||||
What we check Whether the document's images carry a text description of what they show. What good looks like Images in the document carry a text description of what they show. An image with none is a fail: what it shows is missing from the text. Why it matters Some images in the document have no text description, so whatever they show is missing from the document's text. A chart is the classic loss: the picture holds the figures and the text never states them. What we found on this page the document has images and none carries a text description, so what the images show is missing from the document's text The evidence, taken from the page as served The images, page by page: where each sits and what the file records about it
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: images in the document carry a text 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 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. | ||||||||||||||||||||||||||||||||||||||||||
| PD16 | fail | the document writes out 1 web address as plain text but saves none of them as real, clickable links, so the address sits in the text with no link behind it to follow to the source | ||||||||||||||||||||||||||||||||||||||||
What we check Whether the document's links are recorded as real links, or just web addresses typed as plain text. What good looks like The document's links are recorded as real links, not web addresses typed as plain text. Why it matters When a source is only typed out as text, there is no link behind it to follow, so the reference cannot be opened or checked. What we found on this page the document writes out 1 web address as plain text but saves none of them as real, clickable links, so the address sits in the text with no link behind it to follow to the source The evidence, taken from the page as served The web addresses written out in the text, with no link behind them
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's links are recorded as real links, not web addresses typed as plain text. 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. | ||||||||||||||||||||||||||||||||||||||||||
| PD28 | fail | 6 font(s) drawing text on 5 page(s) carry no character map of their own and rely on a standard encoding to be read at all, which the file does not guarantee to any reader | ||||||||||||||||||||||||||||||||||||||||
What we check Whether the fonts that actually draw text in the document state which character each shape stands for, in a character map or a standard encoding. What good looks like The fonts drawing text state their characters. A font stating them nowhere, neither a map nor a standard encoding, is a fail whatever its spread. A font relying on a standard encoding alone is allowed once on up to four pages, and fails beyond that. Damage seen in the reading is a fail in any case. Why it matters A document stores its text as shapes; unless the font says which character each shape is, a reader can see the words but cannot know what they say. Text that cannot be named cannot be quoted, searched or read aloud correctly. What we found on this page 6 font(s) drawing text on 5 page(s) carry no character map of their own and rely on a standard encoding to be read at all, which the file does not guarantee to any reader The evidence, taken from the page as served The fonts whose text has no character map, and where each is used
A font stores shapes. The map from those shapes back to real characters is what lets the words be read out of the file. Without it the shapes still print correctly on paper, so the document looks perfect, while the text taken from it comes out as the wrong characters. Carrying the font inside the document and recording that map are two separate things: a font can be carried in full and still record no map, and that is the more serious case, because nothing looks wrong at any point and the wrong characters appear only once the document is read by machine. Each font below states which of the two applies to it.
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 fonts drawing text state their characters. 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. | ||||||||||||||||||||||||||||||||||||||||||
| PD33 | fail | 2 pairs of pages are near-identical (pages 4 and 5 at 99%, pages 6 and 7 at 100%), so the same content sits in the file more than once and the copies can go stale apart | ||||||||||||||||||||||||||||||||||||||||
What we check Pages that repeat almost word for word inside the same document, across the pages sampled. What good looks like No pages repeat almost word for word inside the document. Why it matters Repeated pages can carry an old version beside the new one, so superseded wording sits inside the same file. What we found on this page 2 pairs of pages are near-identical (pages 4 and 5 at 99%, pages 6 and 7 at 100%), so the same content sits in the file more than once and the copies can go stale apart The evidence, taken from the page as served The near-identical pages, side by side
Each pair is shown as the text reads out of the file, first 320 characters of each page, so the repetition can be seen and the file corrected. page 4 and page 5 share 99% of their words
) )) ) ) ) ) ) ) ) ) ) ) ) ))) ) ) ))) ) ) ) ) ) ) ) ) ) ) ) ) ) ) 9 45 44 43 42 41 40 39 37 36 35 34 38 33 32 31 30 29 27 28 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 !(8 !(7 !(6 !(5 !(4 !(3 !(2 !(1 This map is based upon Ordnance Survey material with the permission of Ordnance Survey on behalf of the Contro ) )) ) ) ) ) ) ) ) ) ) ) ) ))) ) ) ))) ) ) ) ) ) ) ) ) ) ) ) ) ) ) 9 45 44 43 42 41 40 39 37 36 35 34 38 33 32 31 30 29 27 28 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 !(8 !(7 !(6 !(5 !(4 !(3 !(2 !(1 This map is based upon Ordnance Survey material with the permission o f Ordnance Survey on behalf of the Contr page 6 and page 7 share 100% of their words
Ryton Greenside High Spen Chopwell Blackhall Mill Rowlands Gill Blaydon Sunniside Whickham Dunston Hill Kibblesworth Leam Lane Development and Enterprise PLANNING FOR THE FUTURE CORE STRATEGY AND URBAN CORE POLICIES MAP Drawn by: HD Date: Scale Bar ยฉ Crown copyright and database rights 2014 Ordnance Survey Ga Ryton Greenside High Spen Chopwell Blackhall Mill Rowlands Gill Blaydon Sunniside Whickham Dunston Hill Kibblesworth Leam Lane Development and Enterprise PLANNING FOR THE FUTURE CORE STRATEGY AND URBAN CORE POLICIES MAP Drawn by: HD Date: Scale Bar ยฉ Crown copyright and database rights 2014 Ordnance Survey Ga 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 pages repeat almost word for word inside the document. 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. | ||||||||||||||||||||||||||||||||||||||||||
| Warnings · 3 | ||||||||||||||||||||||||||||||||||||||||||
| PD20 | warning | the document is 360 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 360 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.
| ||||||||||||||||||||||||||||||||||||||||||
| 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 With no built-in markers for headings, tables and reading order, the file records only where things sit on the page, so its structure comes 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.
| ||||||||||||||||||||||||||||||||||||||||||
| 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.
| ||||||||||||||||||||||||||||||||||||||||||
| Alerts · 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.
| ||||||||||||||||||||||||||||||||||||||||||
▸https://www.newcastle.gov.uk/sites/default/files/2020-06/DAP%20FINAL%20Adoption%20-%20Online%20Version.pdf 45.3% Likely 8 out of 28
The document https://www.newcastle.gov.uk/sites/default/files/2020-06/DAP%20FINAL%20Adoption%20-%20Online%20Version.pdf
| Document information | |
|---|---|
| Title | not set |
| Author | not set |
| PDF version, pages, size | 1.7 ยท 147 pages ยท 8174 KB |
| Found on | https://newcastle.gov.uk/Plot12PlanningAppeal |
| Check | Result | Evidence | ||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Fails · 6 | ||||||||||||||||||||||||||||||||||||||||||
| PD21 | fail | the document names no author, so nothing in it says who is answerable for what it states | ||||||||||||||||||||||||||||||||||||||||
What we check Whether the author field names a person or an organisation, rather than a placeholder or a tool name. What good looks like The author field names a person or an organisation, not a placeholder or a tool name. Why it matters With no named author the document carries no accountable source, so nothing shows who stands behind it. What we found on this page the document names no author, so nothing in it says who is answerable for what it states 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 named author.
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 author field names a person or an organisation, not a placeholder or a tool name. 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 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. | ||||||||||||||||||||||||||||||||||||||||||
| PD19 | fail | the document is 8.0MB, past the size at which readers take a document in part or skip it, so its later sections carry no weight | ||||||||||||||||||||||||||||||||||||||||
What we check The size of the document as the site serves it, and whether the same content is also published as an ordinary web page. What good looks like The document is under 3.7MB, or the same content is also published as an ordinary web page. From 3.7MB it is a warning, and beyond 7.2MB a fail, unless that web version exists. Why it matters A very large document is taken in part or skipped, so its later sections carry no weight, and that is usually where the figures and the detail sit. What we found on this page the document is 8.0MB, past the size at which readers take a document in part or skip it, so its later sections carry no weight The evidence, taken from the page as served How large this document is
Measured from the file as the site served it. Where the same content is also published as an ordinary web page, this size does not count against the organisation, since nothing then depends on the file being read.
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 is under 3.7MB, or the same content is also published as an ordinary web page. 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 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. | ||||||||||||||||||||||||||||||||||||||||||
| PD09 | fail | the document has no title set in its properties, so it can only be identified by its file name or the link text pointing to it | ||||||||||||||||||||||||||||||||||||||||
What we check Whether the document carries a title in its own properties, not just a name on the link to it. What good looks like The document carries a title in its own properties. Why it matters Without a title the document is identified by its file name and by whatever the links to it happen to say. What we found on this page the document has no title set in its properties, so it can only be identified by its file name or the link text pointing to it 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 title.
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 carries a title in its own properties. 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. | ||||||||||||||||||||||||||||||||||||||||||
| PD08 | fail | filename "DAP%20FINAL%20Adoption%20-%20Online%20Version.pdf" is a code or generic name: nothing in it says what the document is, and the file's own properties carry no title either. | ||||||||||||||||||||||||||||||||||||||||
What we check The file's name, read together with the title in the file's own properties: whether its words, dates and period markers say what the document is. What good looks like A name whose words and dates identify the document, such as FY_2025_Announcement.pdf, passes. A WARNING means the name only half-identifies it: a single hinting word, period markers without a subject (FY25_Q3.pdf), or a weak name that the file's own title completes. A FAIL means a code or generic name, such as IMG_1234.pdf, with no title in the properties either, so nothing anywhere says what the document is. Why it matters The document has no usable name anywhere, neither in its file name nor in its own properties. Nobody, human or AI, can tell what it is without opening it, so it gets quoted blind or passed over. What we found on this page filename "DAP%20FINAL%20Adoption%20-%20Online%20Version.pdf" is a code or generic name: nothing in it says what the document is, and the file's own properties carry no title either. The evidence, taken from the page as served This document's properties, as recorded in the file
The file name and the file's own properties are read together: a title in the properties can complete a name that is weak on its own.
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 name whose words and dates identify the document, such as FY_2025_Announcement.pdf, passes. 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. | ||||||||||||||||||||||||||||||||||||||||||
| 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
Newcastle upon Tyne Development and Allocations Plan 2015-2030 Adopted June 2020 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 | fail | the document has images and none carries a text description, so what the images show is missing from the document's text | ||||||||||||||||||||||||||||||||||||||||
What we check Whether the document's images carry a text description of what they show. What good looks like Images in the document carry a text description of what they show. An image with none is a fail: what it shows is missing from the text. Why it matters Some images in the document have no text description, so whatever they show is missing from the document's text. A chart is the classic loss: the picture holds the figures and the text never states them. What we found on this page the document has images and none carries a text description, so what the images show is missing from the document's text The evidence, taken from the page as served The images, page by page: where each sits and what the file records about it
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: images in the document carry a text 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 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. | ||||||||||||||||||||||||||||||||||||||||||
| Warnings · 2 | ||||||||||||||||||||||||||||||||||||||||||
| PD26 | warning | the document is over 5 years old (last dated 2020-06); a document this old is a weaker, less current source | ||||||||||||||||||||||||||||||||||||||||
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 5 years old (last dated 2020-06); a document this old is a weaker, less current source 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.
| ||||||||||||||||||||||||||||||||||||||||||
| 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 With no built-in markers for headings, tables and reading order, the file records only where things sit on the page, so its structure comes 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.
| ||||||||||||||||||||||||||||||||||||||||||
| Alerts · 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.
| ||||||||||||||||||||||||||||||||||||||||||
▸https://www.newcastle.gov.uk/sites/default/files/2019-01/tall_buildings_spd_text_version.pdf 43.3% Likely 8 out of 28
The document https://www.newcastle.gov.uk/sites/default/files/2019-01/tall_buildings_spd_text_version.pdf
| Document information | |
|---|---|
| Title | Microsoft Word - final text version tallbuildings spd dec06.doc |
| Author | k3282 |
| PDF version, pages, size | 1.3 ยท 34 pages ยท 205 KB |
| Found on | https://newcastle.gov.uk/Plot12PlanningAppeal |
| Check | Result | Evidence | ||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Fails · 6 | ||||||||||||||||||||||||||||||||||||||
| PD26 | fail | the document is 19 years old (last dated 2007-01); content this old is a weak, less trustworthy source | ||||||||||||||||||||||||||||||||||||
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 19 years old (last dated 2007-01); content this old is a weak, less trustworthy source 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.
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's most recent internal date is recent rather than long past. 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. | ||||||||||||||||||||||||||||||||||||||
| PD22 | fail | the document's dates disagree: the file records 2007-01 as its own date, while the address it is served under carries 2019-01. A reader cannot tell which is true, and the newer date on the address hides how old the content is | ||||||||||||||||||||||||||||||||||||
What we check Whether the document records when it was created or last changed, alongside the software that made it. What good looks like The document records when it was created or last changed. Why it matters With no dates on the file there is no way to tell a document written last month from one written a decade ago. What we found on this page the document's dates disagree: the file records 2007-01 as its own date, while the address it is served under carries 2019-01. A reader cannot tell which is true, and the newer date on the address hides how old the content is The evidence, taken from the page as served This document's properties, as recorded in the file
The file's own dates were read and compared with the date carried in the document's web address.
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 records when it was created or last changed. 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 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. | ||||||||||||||||||||||||||||||||||||||
| 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
Tall Buildings Guidance SPD 1 Tall Buildings Guidance for Newcastle upon Tyne Supplementary Planning Document (SPD) www.newcastle.gov.uk 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 | fail | the document has images and none carries a text description, so what the images show is missing from the document's text | ||||||||||||||||||||||||||||||||||||
What we check Whether the document's images carry a text description of what they show. What good looks like Images in the document carry a text description of what they show. An image with none is a fail: what it shows is missing from the text. Why it matters Some images in the document have no text description, so whatever they show is missing from the document's text. A chart is the classic loss: the picture holds the figures and the text never states them. What we found on this page the document has images and none carries a text description, so what the images show is missing from the document's text The evidence, taken from the page as served The images, page by page: where each sits and what the file records about it
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: images in the document carry a text 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 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. | ||||||||||||||||||||||||||||||||||||||
| PD16 | fail | the document writes out 1 web address as plain text but saves none of them as real, clickable links, so the address sits in the text with no link behind it to follow to the source | ||||||||||||||||||||||||||||||||||||
What we check Whether the document's links are recorded as real links, or just web addresses typed as plain text. What good looks like The document's links are recorded as real links, not web addresses typed as plain text. Why it matters When a source is only typed out as text, there is no link behind it to follow, so the reference cannot be opened or checked. What we found on this page the document writes out 1 web address as plain text but saves none of them as real, clickable links, so the address sits in the text with no link behind it to follow to the source The evidence, taken from the page as served The web addresses written out in the text, with no link behind them
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's links are recorded as real links, not web addresses typed as plain text. 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. | ||||||||||||||||||||||||||||||||||||||
| PD28 | fail | 4 font(s) drawing text on 8 page(s) carry no character map of their own and rely on a standard encoding to be read at all, which the file does not guarantee to any reader | ||||||||||||||||||||||||||||||||||||
What we check Whether the fonts that actually draw text in the document state which character each shape stands for, in a character map or a standard encoding. What good looks like The fonts drawing text state their characters. A font stating them nowhere, neither a map nor a standard encoding, is a fail whatever its spread. A font relying on a standard encoding alone is allowed once on up to four pages, and fails beyond that. Damage seen in the reading is a fail in any case. Why it matters A document stores its text as shapes; unless the font says which character each shape is, a reader can see the words but cannot know what they say. Text that cannot be named cannot be quoted, searched or read aloud correctly. What we found on this page 4 font(s) drawing text on 8 page(s) carry no character map of their own and rely on a standard encoding to be read at all, which the file does not guarantee to any reader The evidence, taken from the page as served The fonts whose text has no character map, and where each is used
A font stores shapes. The map from those shapes back to real characters is what lets the words be read out of the file. Without it the shapes still print correctly on paper, so the document looks perfect, while the text taken from it comes out as the wrong characters. Carrying the font inside the document and recording that map are two separate things: a font can be carried in full and still record no map, and that is the more serious case, because nothing looks wrong at any point and the wrong characters appear only once the document is read by machine. Each font below states which of the two applies to it.
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 fonts drawing text state their characters. 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. | ||||||||||||||||||||||||||||||||||||||
| Warnings · 2 | ||||||||||||||||||||||||||||||||||||||
| 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 With no built-in markers for headings, tables and reading order, the file records only where things sit on the page, so its structure comes 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.
| ||||||||||||||||||||||||||||||||||||||
| 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.
| ||||||||||||||||||||||||||||||||||||||
| Alerts · 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.
| ||||||||||||||||||||||||||||||||||||||
▸How the scores work method and bands · click to view
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 “None found”: no regulator statements, and the established sector carries no statutory regulator. Listed company reads “No”: not a company with publicly traded shares (government-restricted domain).
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 207 checks, 150 ran automatically in this Foundations stage. 43 are questions for the person accountable for the content, asked at the next stage. 5 are built and found nothing of their kind published on this site, so they had nothing to read. One is defined in the register and not yet built. 7 need information supplied by the organisation. Each check that did not run is listed in the exports, with its reason.
About us
Built on evidence, not assumptions.
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.
3.7
Trillion
Data points, with each result kept since the beginning: probably the largest experience and compliance dataset of its kind. Our AI is trained on factual, controlled, real-world evidence.
$106
Billion
Estimated manual effort avoided through automation. An estimate, and a conservative one: since ARTY was introduced, we have removed 95% of costs and delivered efficiency gains beyond 70x.
119
Million
Websites analysed and mapped for content fundamentals, from the outside in. AI Readiness begins by removing the human issues that undermine Value and create unnecessary Risk.
25
Years
When we started, we were labelled 'the pioneers' of website automation and checking. In 2023, we launched our first AI analysis tools.
Who’s talking about us
