ARTinez › Legal › Accessibility Statement
Accessibility Statement
What we have actually tested, what we know is not right yet, and how to tell us if something stops you using this site.
Honest position
This website is built with accessibility in mind, but it has not been audited by a third-party accessibility specialist. The statement below says exactly what has and has not been tested. We would rather be precise about the limits than claim a conformance level we have not verified.
1. Conformance status
The website is designed against WCAG 2.1 Level AA as a target. We do not make a formal conformance claim, because no independent audit has been carried out. A formal audit will be commissioned before ARTinez works with public-sector or otherwise regulated organisations.
2. What has been built in
- Semantic HTML throughout, with a single page-level
h1and a sensible heading hierarchy on every page. - A skip-to-content link, visible when focused, that moves keyboard users past the navigation.
- Visible focus styling on every interactive element — links, buttons, form fields and the chip toggles in the Vision builder.
- Every form field has an associated
<label>. No field relies on placeholder text alone, and the error messages that appear are associated with the form rather than floating free of it. - Colour contrast designed to meet WCAG 2.1 AA for body text (4.5:1) and for large text and interface components (3:1).
- Responsive layout supporting viewport widths from 320px upwards, with no horizontal scrolling at any width tested.
- Touch targets of at least 44 by 44 CSS pixels on small viewports.
- Correct ARIA on the mobile navigation drawer (
aria-expanded,aria-hidden) and on the Vision submission dialog (role="dialog",aria-modal,aria-labelledby). - Alt text on every image. Decorative images use empty alt text so that screen readers skip them.
- Respect for
prefers-reduced-motion: scroll-triggered reveals are reduced when the user has that preference set. - The whole site can be operated using the keyboard alone.
- No information is conveyed by colour alone.
- Print and save-as-PDF styling on every legal page, so a reader can produce a clean copy of any policy.
3. What has actually been tested
- Manual code review of every HTML, CSS and JavaScript file for semantic correctness, label association, ARIA usage, heading hierarchy and keyboard order.
- Automated accessibility checking of the pages, with the issues that were identified corrected in the version now published.
- Keyboard-only walkthrough of every page — tabbing, shift-tabbing, Enter, Space, arrow keys and Escape — confirming that every interactive element can be reached and operated and that focus is always visible.
- Responsive walkthrough at viewport widths from 320px to 1920px, including on a physical Android handset, confirming that the layout adapts, that nothing is clipped or hidden, and that there is no horizontal overflow.
- Link checking across every page, confirming that each link resolves and that no link points at a missing file.
4. What has not been tested
To be straightforward about the gaps:
- Screen reader testing with VoiceOver, NVDA, JAWS or TalkBack. The code is written to be screen-reader friendly, but a full pass with each reader has not been completed.
- Formal WCAG 2.1 AA audit by an accessibility specialist.
- Testing with disabled users, or user testing with people who use assistive technologies.
- Screen magnification, switch control and eye-tracking.
- High-contrast mode and forced-colours mode in Windows.
If any of these matters for how you need to use this site, please tell us — see section 7 — and we will prioritise it.
5. Known limitations
- The display typeface is a high-contrast serif that may be harder to read at small sizes. Minimum font sizes are set to mitigate this, but the mitigation is not exhaustive.
- Some hover and scroll animations are visually strong for users with vestibular sensitivities. The reduced-motion setting reduces them, but does not remove every animation.
- In the ARTinez Vision builder, the selectable options wrap onto several lines on a narrow screen, which is slower to navigate with a screen reader than a native control would be. Each option is a properly labelled button, and the wrapping does not change the order.
- Focus is not currently trapped inside the mobile navigation drawer while it is open, so tabbing can move behind it. The drawer can be dismissed with the close button, the escape key, or by tapping outside it.
- The legal pages contain long tables. On a narrow screen these scroll horizontally within the table rather than wrapping, which keeps the data aligned but requires a sideways scroll.
6. Third-party content
This website does not embed third-party content that we do not control: no video players, no social media widgets, no live chat, no advertising tags. Every file the site loads — including the web fonts and the images — is served from our own server, so there is no third-party embed that could behave differently from what we have tested, and nothing that can fail independently of our own hosting.
7. Reporting a barrier
If anything on this site stops you using it — something you cannot reach with the keyboard, a contrast problem, an unreadable element, a missing label, a form error that is not explained — please email office@artinez.co.uk with the subject line "Accessibility". Please include:
- the page address where you found it;
- what you were trying to do;
- the browser, device and any assistive technology you were using.
We aim to acknowledge within 3 working days and to provide a fix or a workaround within 30 days, depending on how complex it is. There is no charge, and you do not need to tell us who you are.
8. Enforcement
The Equality and Human Rights Commission is responsible for enforcing accessibility requirements in the UK. If you contact us about an accessibility barrier and you are not satisfied with our response, you can refer the matter to the EHRC at equalityhumanrights.com.
As a private business, ARTinez is not directly subject to the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018, but it adopts WCAG 2.1 AA as a design target for the reasons set out in section 1.