Loading
What this site is built to target, what has actually been done, and what has not been tested.
It is a structural draft prepared so that a qualified legal adviser has something concrete to review, amend or replace. It is not legal advice, it has not been approved, and it must not be relied on as a statement of your rights or of our obligations until a professional review is complete. Sections marked [TO BE CONFIRMED] are decisions that have not yet been made.
This website is built to target the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. It has not been formally audited, and we do not claim that it conforms.
Targeting a standard and meeting it are different things. Accessibility has been designed in and checked during development, but no independent audit has taken place, and no conformance claim is made on this page. When an audit is carried out, this statement will be replaced with one that reports what it actually found.
This is a voluntary statement. It is not made under the Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018, which apply to public sector bodies rather than to this website.
The following are implemented across the site. They are a description of the build, not a conformance claim.
| Keyboard operation | Every interactive control is reachable and operable with a keyboard.The mobile menu can be closed with Escape and keeps focus inside it while open. |
|---|---|
| Visible focus | A high-contrast focus ring is shown on every focused control.Focus styling is never suppressed, and focus is not removed on click-only interaction. |
| Skip link | A skip link at the top of each page jumps straight to the main content. |
| Semantic structure | Landmarks, one first-level heading per page, and headings in a logical order.Lists, tables and forms use the corresponding HTML elements rather than styled div elements. |
| Labelled controls | Every form control has a real label. Placeholders are never used as labels.Required and optional fields are marked in words, not by an asterisk or colour alone. |
| Error handling | Errors are announced, linked to the field they belong to, and repeated in a focusable summary at the top of the form. |
| Colour and contrast | Text and interface colours are checked against the AA contrast thresholds.The primary red is reserved for large text, fills and borders; a brighter red is used wherever red text is small. |
| Meaning never carried by colour alone | Every status is stated in text; the coloured dot beside it is a redundant cue. |
| Reduced motion | All animation respects the operating system reduced-motion setting and has a static equivalent.No content is hidden behind an animation that does not run, and there is no scroll hijacking or auto-playing media. |
| Touch targets | Navigation links, buttons and form controls are sized to at least 44 pixels high. Checkboxes are 24 pixels, with the adjacent label forming part of the target. |
| Text and zoom | Layouts use relative units and reflow, so text can be enlarged and the browser can be zoomed. |
| Native controls | Native form controls are used in preference to custom widgets, including for select menus. |
| Non-text content | Decorative illustrations are hidden from assistive technology; meaningful graphics carry a text equivalent. |
Assessment so far has been self-assessment during development: reviewing markup and heading structure, operating pages by keyboard, checking colour pairs against the contrast thresholds, and testing with reduced motion enabled.
Self-assessment finds obvious problems. It does not find everything, and it is not a substitute for testing with people who use assistive technology daily.
These are the gaps we know about. There may be others we have not found.
If you cannot use part of this site, or you find something that is hard to use with your assistive technology, please tell us. A specific report — the page, what you were trying to do, and what happened — is the most useful thing we can receive, and it is how most of these problems get found.
| support@peptideswales.co.uk | |
| Telephone | [SUPPORT PHONE] |
| Opening hours | [OPENING HOURS] |
You can also use the contact page. If your feedback concerns how we handle your personal information, the data protection rights and complaints page has a form that records a reference.
We cannot promise a response time we have not agreed: [TO BE CONFIRMED: feedback response timescale]. We will read what you send.
The version number and last-updated date at the top of this page identify the current statement. It will be rewritten once an audit has been carried out, so that what it says reflects evidence rather than intent.