This statement is for every page of NoticeWise that anyone can read, and the forms on them. It does not cover the pages for the people who run the website, once they have signed in, or the emails the website sends.
How accessible this website is
We want everyone who needs the library to be able to use it, so we design and build every page to meet the Web Content Accessibility Guidelines (WCAG) version 2.2 at level AA. The pages are built so that you can:
- get to everything with a keyboard alone, and always see where you are, marked by a yellow and black outline
- skip straight to the main content of any page
- read every piece of text against its background, with a contrast of at least 4.5 to 1
- tell links apart from other words, because every link is underlined
- use the website on a phone without scrolling sideways
- use every page with JavaScript switched off, because none of them uses any
Compliance status
On 14 November 2026 every page of NoticeWise that anyone can read, with its forms, conformed to the Web Content Accessibility Guidelines 2.2 at level AA. Those pages are the library and every one of its guides, its topics and its search; the page that lists what a council has to publish; the sign-up for emails and the pages that follow it; the privacy policy, the complaints policy and this statement; and the page where the people who run the website sign in.
We made the checks ourselves. No independent specialist has audited the website. The logo at the foot of each of these pages is W3C's, and stands for our claim, not for a review by W3C.
We know of no problem on any page. We have not tried the website with speech recognition software.
Tell us about a problem
If anything on this website is hard to use, or you need any of it in another format, please tell us:
- By email: hello@jolora.co.uk
- By post: Jolora Ltd, coWorkz, Minerva Avenue, Chester, CH1 4QL, United Kingdom
How we test this website
The website's own tests open every kind of page in a web browser and check it with an automated accessibility checker, axe, at the width of a computer screen and of a phone. A page fails if the checker finds anything wrong, or anything it is unsure of, or if the page scrolls sideways on a phone. The tests also check that, when the sign-up form cannot be sent, the keyboard is taken to the list of what needs putting right. Every change to the website has to pass these tests.
On 14 November 2026 a program also went through every page of the website in Chrome, and its forms once filled in and once refused. It pressed the Tab key from the top of each page to the bottom and checked that every link, button and form control could be reached, one after another as they come on the page, with the yellow and black outline showing, on screen and not hidden behind anything. It read every page in a window 320 pixels wide, with the text twice as large, with the wider spacing between lines, paragraphs, letters and words that WCAG 2.2 sets out, and 320 pixels wide with that spacing, and checked that nothing scrolled sideways or was cut off. And it read what each page gives a screen reader: a title of its own, one main heading and no skipped heading levels, its landmarks, and a name for every link, button and form control. It found three things, which we put right: on a phone, the note of how often each email comes made the sign-up form scroll sideways; the logo did not shrink to fit a narrow window when the text was made larger; and a list of questions for one country, and a page of search results, had the same title as the page they came from.
The same day a person went through the website with the VoiceOver screen reader, and with a keyboard alone and the text twice as large in Safari and Firefox, and found nothing wrong.
An automated checker finds only some kinds of problem, which is why a person checks as well.
Technical information
The pages are written in HTML and CSS, and rely on nothing else. They use no JavaScript.
Preparation of this statement
This statement was prepared on 13 November 2026 and last updated on 14 November 2026, when we made the claim above. We will update it whenever a change to the website changes what it says.