Accessibility statement
We want repagevia.site to be usable by everyone, including people who use screen readers, keyboards, magnification or other assistive technology. This statement explains what we aim for, what we have tested and what we know is not yet right.
Our target
Our yardstick for repagevia.site is WCAG 2.2 (the Web Content Accessibility Guidelines), at conformance level AA. WCAG 2.2 is published by the W3C and added nine success criteria to the previous version1. As a private business, we are not covered by the NZ Government Web Standards2, but we use the same guidelines because they give a clear, testable target.
What we have done
- Structure. Every page carries a single H1, with subheadings that step down in order. Landmarks mark the header, navigation, main content and footer. A skip link at the top of each page jumps straight to the main content.
- Keyboard. You can reach and operate each link, button, menu and form field from the keyboard alone. A visible focus outline shows where you are, and we checked that its contrast is at least 3 to 1 against every background on the site.
- Colour and contrast. Body text meets a contrast ratio of at least 4.5 to 1 against its background. Information is never conveyed by colour alone.
- Text size. Pages reflow at narrow widths and when text is enlarged, without horizontal scrolling at 320 CSS pixels wide.
- Targets. Buttons and links are at least 24 by 24 CSS pixels or have enough spacing, in line with WCAG 2.2's target size criterion. Main buttons are at least 44 pixels tall.
- Images. The site's illustrations are decorative and hidden from screen readers. Where an illustration carries meaning, such as the before-and-after concepts, the meaning is described in text nearby.
- Forms. Every field has a visible label. Errors are listed in a summary at the top of the form, which receives focus, and each field's error is linked to the field.
- Motion. Animations are minimal and are switched off when your device asks for reduced motion.
- Without JavaScript. Navigation, content and the contact form work without JavaScript. The concept sliders show the before and after drawings together instead, stacked in one column on phones, and the planner shows its questions as a printable list.
- Tables. Data tables have captions and header cells. On narrow screens they reflow into labelled cards.
How we tested
Testing so far has covered:
- Keyboard-only navigation, including a scripted check that every focus stop on the main page types shows an outline with at least 3:1 contrast
- Automated checks for colour contrast, headings, labels, page titles and duplicate identifiers
- Narrow screen widths down to 320 pixels, browser zoom and text reflow
- JavaScript turned off
We have not yet tested the site by hand with screen readers. Manual testing with NVDA on Windows, VoiceOver on macOS and iPhone, and TalkBack on Android is planned, with a target date of 31 March 2027. Until then, the screen reader support described above is based on standard markup and automated checks, not on hands-on testing.
Known limitations
- Redesign planner. The planner needs JavaScript to build a brief. Without JavaScript, the form is hidden so nothing typed into it can be submitted by mistake, and the sixteen questions appear as a printable list instead.
- Screen readers. Not yet tested by hand; see the plan above.
- Concept sliders. The before-and-after drawings are simplified illustrations. Their content is described in text on the page, but the drawings themselves are not described element by element.
- Linked sources. Our guides link to external websites, including government PDFs. We cannot control how accessible those are.
If you find a problem we have not listed, please tell us.
Reporting a problem
Email hello@repagevia.site with the page address and a description of the problem. Tell us what assistive technology you were using, if any, and we will try to reproduce it. We aim to fix confirmed problems promptly. If we cannot fix something straight away, we will provide the information in another way.
Accessibility in our work
We test the pages we build for clients against WCAG 2.2 at level AA. Our WCAG 2.2 guide explains what the standard covers and how to check a site yourself.
Compatibility
The site is built with standard HTML, CSS and a small amount of JavaScript. It is designed to work with current versions of the main desktop and mobile browsers. It uses standard HTML landmarks, headings and labels so that screen readers can interpret it; hands-on screen reader testing is still to come. Older browsers may display a simpler layout, but content and navigation remain available.
Accessibility questions
Can I get information from the site in another format?
Yes. Email hello@repagevia.site and tell us what you need, such as a plain text version of a guide. We will do our best to provide it.
Do you test with people who use assistive technology?
So far our testing has covered keyboard-only use, zoom and reflow, and automated checks; screen reader testing by hand is planned for early 2027. Reports from people who rely on assistive technology every day are especially valuable, so please tell us about any barrier you meet.
Sources
Each source was opened and checked against the sentence it supports on 3 November 2026.
- What's New in WCAG 2.2 Standards body
- NZ Government Web Standards Government
Ready to plan your redesign?
Tell us what your current site does well and what holds it back. You get a written, fixed quote in NZD before any work starts.