I want everyone who visits this website to be able to read it, use it and get in touch with me. That includes people who use a screen reader, a magnifier, voice control, a switch or a keyboard instead of a mouse, and people who find dense pages or movement on screen hard going. This statement sets out the standard I am working to, what the site is built to do, where it may still fall short and how to tell me when something gets in your way.
I run this site myself as a solo consultant in London, so there is no support desk between us. When you report a problem, you are talking to the person who can fix it.
The standard I am working to
The target is level AA of the Web Content Accessibility Guidelines (WCAG) 2.2, published by the W3C in October 2023. WCAG sorts its requirements into three levels. Level A covers the essentials, AA adds the requirements UK public sector websites are expected to meet, and AAA is stricter again and rarely achievable across a whole site.
Aiming for AA is not the same as meeting it. I will only say the site meets the standard once it has been checked against it, and this page lists anything that did not pass.
Last checked: 5 October 2026, on the build of the site prepared for launch. The checks made are listed under “Testing and known limitations” below. They cover part of WCAG 2.2 AA, not all of it, so I do not yet claim that the site conforms to the standard.
What the site is built to do
These are the aims the site was designed and built around. They describe intent rather than the outcome of an audit; what testing found is in the next section.
Keyboard use
Every link, button, menu, form and tool should work with a keyboard alone, in a sensible order, without trapping you anywhere. A “Skip to content” link should be the first thing the Tab key reaches on each page, so you can jump straight past the menu.
Visible focus
Whatever has keyboard focus should carry a clear outline, on light and dark sections alike, so you can always see where you are on the page.
Colour contrast
Text should meet the AA colour contrast ratios: 4.5:1 for normal text and 3:1 for large text. The parts of buttons and form fields you need to see in order to use them should reach 3:1 as well, and colour should never be the only way information is shown.
Images
Images that carry meaning should have alt text that says what they show and why it matters. Purely decorative images should be hidden from screen readers so they do not add noise.
Reduced motion
If you have switched on “reduce motion” in your device or browser settings, the site should turn off its animations, transitions and smooth scrolling. Nothing on the site should flash.
Zoom, reflow and page structure
Pages should stay readable when zoomed to 400% or viewed on a narrow phone, without scrolling sideways to read a line, because the layout uses responsive design. Each page should have one main heading with a logical order of heading tags beneath it, so screen reader users can move around by headings. The page language should be declared as British English so that screen readers pronounce words correctly.
Forms and cookie choices
Form fields should have visible labels, and error messages should say in words what went wrong and how to put it right. The cookie banner should work by keyboard and screen reader, with Accept and Reject given equal weight, and you can change your choices at any time from the Cookie settings button in the footer. The cookie policy explains what each choice controls.
Plain language
I write in plain English and explain technical terms the first time they appear, often with a link to a short definition in the digital marketing glossary, so you do not need any marketing background to follow a page.
Testing and known limitations
On 5 October 2026 I checked the build of the site prepared for launch. These checks passed:
- An automated colour contrast check of the main page templates, which met the AA ratios.
- Keyboard focus is visible on links, buttons and form fields as you tab through a page.
- Pages do not scroll sideways at 320 and 375 pixels wide. A width of 320 pixels is roughly what a desktop browser shows when zoomed to 400%.
- Each page has one main heading.
- Images have alt text.
- Animations stop when “reduce motion” is switched on in the device or browser settings.
- The cookie banner can be reached and used with a keyboard alone.
A full manual audit with assistive technology, such as screen readers, magnifiers and voice control, has not been done yet. Until it has, there may be problems these checks did not catch, so please tell me about anything that gets in your way. When a fuller audit is done, I will add what it covered and what it found to this page.
I check the site again after any significant change to its design, templates or tools, and update this page when I do.
Parts of the site that need the most care
Some areas are harder to get right than ordinary pages of text, so I look at them most closely:
- The free marketing calculators and checkers, where results appear on the page without it reloading. The aim is for a screen reader to announce each result, not only display it. If a tool does not work with your setup, email me the figures you wanted to enter and I will run them and send you the result.
- Content supplied by other companies, such as an embedded map or video, wherever a page uses one. I cannot change how these are built. Wherever one gets in your way, email and phone remain open as another route to the same information.
- Tables in the guides and checklists, which should have proper header rows so a screen reader can read them cell by cell with the right column names.
Reporting a problem
If something on the site does not work for you, or you need information in a different format, please tell me. You do not need to know which guideline is involved; a plain description is enough.
- Email: contact@sudeshnathapa.com
- Phone: +44 7352129369. If you use Relay UK, through the app or a textphone, you can call the same number.
- The enquiry form on my contact page, if the form itself works for you.
It helps to include the address of the page, what you were trying to do, what happened instead, and the device, browser and any assistive technology you were using. Leave out anything you would rather not share; I can work from whatever you send.
What happens next
I read every report myself. I will reply to confirm what I have understood and tell you whether and how I can fix it. While a fix is under way, I will get you the information or service you were trying to reach by another route, and I will let you know when the fix is live so you can check it works for you. Anything you send me is handled as described in my privacy policy.
Adjustments when working with me
Accessibility does not stop at the website. If you are a client, or thinking of becoming one, tell me what makes working together easier and I will build it in from the start. Some examples:
- A phone call or an email exchange instead of a video call, or the other way round.
- A written summary after each call, so you do not have to take notes while we talk.
- Audits, reports and proposals in a format that works with your software, such as a plain text document rather than a slide deck or PDF.
- More time to read documents before a decision is needed.
Making the site easier to use on your own device
Your own browser and device can do a lot of the work. Most browsers zoom with Ctrl and the plus key on Windows, or Cmd and the plus key on a Mac, and phones and computers come with built-in screen readers, magnifiers, text size controls and colour filters. My Computer My Way, a free guide from the UK charity AbilityNet, explains step by step how to change these settings on most devices.
If you are not happy with my response
Please tell me first, so I have the chance to put things right. If you are still not satisfied, the Equality Advisory and Support Service gives free advice on discrimination in England, Scotland and Wales, where the Equality Act 2010 applies. In Northern Ireland, the Equality Commission for Northern Ireland offers similar advice.
About this statement
I review this statement whenever the site’s design, templates or tools change in a way that could affect accessibility, and after every new accessibility check. The “Updated” date on this page shows when it last changed.
Updated