BuiltUp Technologies Ltd wants this site to work for everyone who needs it, including people using a keyboard only, a screen reader, magnification, or a phone in poor light on a wet site. This statement says what we have done, what we know is still wrong, and how to tell us when something stops you getting your work done.
1. What This Statement Covers
This statement applies to the BuiltUp marketing website at builtup.io, including the product pages, pricing, help guides, blog and legal pages.
It does not cover the BuiltUp mobile apps for iOS and Android, the BuiltClip browser extension, or third-party services embedded in a page such as the payment forms hosted by our payment provider. Those are separate products on separate release cycles, and it would be misleading to fold them into one claim. If accessibility in the mobile app matters to your team, write to us and we will tell you where it currently stands rather than guess here.
2. The Standard We Work To
We target the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. That is the benchmark used across UK public sector procurement and the one most main contractors will ask about.
We describe the site as partially conformant with WCAG 2.2 AA. Partially conformant means most of the site meets the standard, and the exceptions we know about are listed in section 5. We have not had an independent accessibility audit, so this is our own assessment and we would rather label it honestly than borrow a word like "fully" that we cannot evidence.
3. What the Site Actually Does
These are decisions built into the design system, so they apply to every page rather than to the handful someone remembered to fix.
- Contrast is measured, not guessedEvery text colour in the design system has a recorded contrast ratio against the ground it sits on, and nothing ships below the AA threshold. Body copy runs well above it. The values are held in the stylesheet next to the colours themselves so they cannot drift.
- 48px tap targetsEvery link, button, nav row and form control is at least 48 by 48 pixels with 8 pixels of clearance. That is a site-wide rule, not a mobile-only one. This is a trade audience, and people tap this site with gloves on and a phone in one hand.
- A visible focus ring, everywhereOne focus style covers the whole site: a 3 pixel outline in our deep brand colour with a 2 pixel offset, which clears 3:1 against both the light and the paper grounds. Focus is never removed, only styled.
- Nothing hides behind the headerThe header is sticky, so headings and jump targets carry a scroll margin. Follow an in-page link with a keyboard and the destination lands below the header rather than underneath it.
- Keyboard navigable menusNavigation, dropdowns, the mobile menu and dialogs can be opened, moved through and closed with a keyboard alone. Focus is trapped inside an open dialog and returns to the control that opened it.
- Reduced motion is respectedIf your operating system is set to reduce motion, animation and transitions are cut to effectively nothing and smooth scrolling is switched off. The reduced state is the finished state, so nothing is left mid-animation or invisible.
- Semantic structureReal headings in order, real lists, real tables with header cells, real buttons and links. Long legal pages carry a contents list so you can jump rather than scroll. Landmarks are used so a screen reader can skip to the main content.
- Alt text on informative imagesImages that carry meaning have a text alternative. Images that are pure decoration are hidden from assistive technology instead of being read out as filenames.
- Text that reflowsPages work at 320 pixels wide and at 400 percent zoom without a horizontal scrollbar on the body. Wide content such as tables scrolls inside its own box rather than pushing the page sideways.
4. How We Check It
- Automated checks in the build. Colour contrast and design token rules are enforced by scripts that run before the site can be published, so a failing colour stops the build rather than reaching a page.
- Manual keyboard passes. New pages are walked through with the tab key alone: reachable, in a sensible order, visibly focused, and nothing that can be entered but not left.
- Zoom and reflow. Pages are checked at 400 percent zoom and at a 320 pixel viewport before release.
- Reduced motion. Checked with the operating system setting turned on, to confirm the still state is the correct state.
We do not currently commission third-party accessibility testing, and we have no external audit report to send you.
5. Known Limitations
These are the gaps we are aware of. If you hit something that is not on this list, section 6 is how to tell us.
Product screenshots
Several pages show generated screenshots of the product: a priced schedule of rates, a take-off summary, a project board. Each carries descriptive alt text explaining what the screen is and what it demonstrates. The underlying figures inside those images, the individual line items and rates, are not separately available as text on the page. Anyone using a screen reader gets the point of the image but not the numbers in it. Putting that data on the page as real text is on the list.
The mobile apps are not covered
The iOS and Android apps are outside the scope of this statement. They have not been assessed against WCAG 2.2 AA and we make no claim about them here.
Embedded third-party content
Checkout and card entry are rendered by our payment provider inside their own frame. We do not control the markup, so we cannot guarantee it meets the same standard as the rest of the site.
Older blog posts
Some articles published before the current design system may have heading levels that skip a step, or images whose alt text is thinner than it should be. We correct these as we come across them and when they are reported.
6. Report a Problem
If any part of this site stops you doing something, tell us. It is genuinely useful, and it is the fastest way for a fix to happen. Email support@builtup.io with "Accessibility" in the subject line and, if you can, include:
- The page address.
- What you were trying to do and what happened instead.
- What you were using: browser, device, and any assistive technology such as VoiceOver, NVDA, JAWS or Dragon.
What we will do
- Acknowledge within 2 working days. A reply from a person, confirming we have it.
- Answer properly within 10 working days. Whether we can reproduce it, what we think the cause is, and when it will be fixed.
- Offer another route in the meantime. If a fix will take time, we will get you the information or complete the task another way, by phone or email, at no cost to you.
- Update this page. Anything we cannot fix quickly goes into section 5 so the next person knows about it.
7. If We Get It Wrong
We take our duty to make reasonable adjustments under the Equality Act 2010 seriously. If you report an accessibility problem and you are not happy with how we handled it, reply to us and ask for it to be escalated. It will be looked at by someone who has not already dealt with it.
In the UK, the Equality Advisory and Support Service (EASS) gives free advice to people who believe they have been discriminated against. You are entitled to approach them at any point, whether or not you have raised it with us first.
8. Review
This statement was prepared in August 2026 based on our own assessment of the site. We review it at least once a year, and whenever we change the design system or ship a significant new area of the site.
For how we handle your data, see the Privacy Policy. For how we handle the platform itself, see the security page.