Home Accessibility
Help
Accessibility statement
How we build and test EquipPoint and this website for people who use a keyboard, a screen reader, zoom, high contrast or a phone, what does not work well yet, and how to tell us about a problem.
Last updated: 31 October 2026
What this statement covers
- The EquipPoint app: the web part on a SharePoint page or full page, the Microsoft Teams personal app and team tab, and the Viva Connections card in the same package.
- This website, equippoint.app: its pages, the trial and contact forms, and the public scan page that the labels of connected registers open, with its fault, found and inspection upload forms.
- Not covered: the optional EquipPoint Intune Connector package, the optional Copilot agent (it answers inside Microsoft 365 Copilot's own interface), and SharePoint and Microsoft Teams themselves, which have Microsoft's own accessibility statements.
Standard and approach
We build and test EquipPoint and this website against the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. That is the standard we test against, not a certified claim: no independent audit has been done yet, and the gaps we know about are listed below. A school or trust can use this statement when it assesses EquipPoint for its own accessibility duties, and ask us about it.
How the app is built
- Microsoft's Fluent UI controls, the same family SharePoint and Teams use, each with its own keyboard and screen reader behaviour. EquipPoint adds no custom control where Fluent has one.
- Colours come from the theme, so the SharePoint site theme, the Teams default, dark and contrast themes and Windows high contrast (forced colours) are followed. A site's own theme colour carries white text only where the contrast reaches 4.5:1.
- Every status is given in words next to its colour: Available, Overdue, Failed inspection, Read-only and so on.
- Keyboard: Tab and Shift+Tab move between controls; arrow keys move inside the section tabs, the register's action bar and menus; Enter and Space activate; Escape closes a dialog or panel and returns focus to the control that opened it.
- Screens are labelled: the section tabs are a tab list, dialogs and panels have titles, and row buttons name their row ("Open asset OAK-PRJ-0002").
- The register reflows from 320 px wide: on a phone it becomes one card per asset, and only wide tables scroll inside their own box. Text follows the browser's zoom and EquipPoint's own Text size setting (Small, Medium, Large).
- EquipPoint adds no animation of its own, and nothing times out while someone is reading or typing; messages that disappear repeat what is already on the screen.
How this website is built
- Pages are plain HTML from our server, with a skip link, one main heading, landmarks for the header, navigation, main content and footer, and a visible focus outline on every link, button and field.
- Form fields have their own labels. When something needs fixing, a summary at the top links to each field, and the field says what to change.
- Every page reflows at 320 px without sideways scrolling, text can be enlarged with the browser, and colours meet the AA contrast ratios. In Windows high contrast, buttons keep their outline.
- Diagrams have a text description and the same steps written out beside them; decorative images are hidden from screen readers.
- No animation beyond short colour changes, and none when your device asks for reduced motion. A form stays open for up to a day, so there is no time limit while you read or type.
What is tested, and how often
| Part | Check | How | When |
|---|---|---|---|
| App | Automated rules (axe-core 4.10) | Every screen rendered with test data: register, asset panel and history, add and bulk edit, setup, Licence, Help, section tabs, scan, labels, check-out and receipt, check-in, My kit, loans, bookings, import and export, dashboard, inspections, faults, tasks, stocktake, uploads | Every build; a failure stops the release |
| App | Keyboard walk-throughs | The main tasks by keyboard only, on a live test site: add, scan by typed code, check-out with a typed-name receipt, check-in, stocktake, Help, Licence | In each quality pass before a release |
| App | Reflow | Every tab at 320, 375 and 422 px and at 1366 px: nothing past the edge, no whole-page sideways scroll | In each quality pass before a release |
| App | Contrast | Every visible text against its background, on every tab, light theme: no pair under 4.5:1 (3:1 for large text) | In the quality passes before a release |
| App | Phones | Android at 375 px; the Teams mobile rules checked in code | In each quality pass before a release |
| Website | Automated rules (axe-core 4.10: WCAG 2.0, 2.1 and 2.2 at A and AA, and best practice) | Every public page, the trial key page, and the scan page's states and forms, at 320, 375 and 1280 px, in a real browser | Every release, and again on the live site after each update |
| Website | Reflow | No sideways scroll on any page at 320 and 375 px | Every release, and after each update |
| Website | Forms end to end | The trial form to its key page, a fault report with a photo, and a contractor's inspection upload | Every release |
Automated rules find many problems but not every one, which is why the known limits below include what has not yet been checked by hand.
Known limits
| Area | Limit | What to use instead |
|---|---|---|
| Camera scanning (app) | Needs a camera and a steady view of the label, so it is not usable without sight | Type the asset number, serial number or label link in "Handheld scanner or code" in the Scan dialog, or use a USB or Bluetooth scanner, which types into the page. Every scan action has a typed equivalent |
| Drawn signature (app) | Signing a receipt on the screen needs a pointer | "Type my name" signs the same receipt, or the person acknowledges in My kit with their own sign-in |
| Receipt PDFs (app) | Receipts are untagged PDFs, so some screen readers read them as one block | The same details are in the app: the loan in Loans and the asset's History |
| Label sheets (app) | Labels are made for printing; a QR code has no text alternative on paper | The default label prints the asset number and name next to the code |
| Screen readers (app and website) | Names, roles and states are checked in the page and by automated rules; a full run with NVDA, JAWS, Narrator and VoiceOver has not been done yet | Planned. Please tell us about any problem (below) |
| High contrast (app) | Windows high contrast and the Teams contrast theme are covered by Fluent's theme and by tests, not yet checked by eye | Planned. Please tell us about any problem |
| Dashboard charts (app) | A chart is a picture of numbers | Each chart has a table with the same values in words |
| Forms on this website | The trial form and the scan page's report and upload forms need JavaScript for their automatic bot check (there is nothing to solve: it runs by itself in a few seconds) | Each form says so when JavaScript is off. Or use the contact form, email us, or tell a member of staff where the equipment is |
| Text from organisations | The public scan page shows asset names and notes that the organisation wrote; we do not check their wording | Contact the organisation that owns the item, or us |
| SharePoint and Teams | The page around the app (SharePoint's navigation, the Teams frame) is Microsoft's | Microsoft's accessibility statements for SharePoint and Teams |
Report a problem
Tell us through the support form (choose "Help with EquipPoint (support)" and say it is about accessibility) or email info@apps365ltd.com. Please say which page or screen, what you were trying to do, and the browser or assistive technology you use, if you know it.
We aim to reply within one working day: Monday to Friday, 9:00 to 17:30 UK time, except UK bank holidays. We fix accessibility problems at source, with a test that would have caught them, as for any other fault, and tell you when the fix is live. If you need something from EquipPoint in another way while we fix it, ask and we will help. More help: EquipPoint support.