ServOS Accessibility Statement Published by: ServOS App Inc, a company incorporated in the State of Delaware, United States, trading as “ServOS” (“ServOS”, “we”, “us”, “our”). Registered office: 251 Little Falls Drive, Wilmington, New Castle County, Delaware 19808. Accessibility contact: support@serv-os.app | Website: https://www.serv-os.app Effective date: 24 August 2026 | Version: 1.1 | Next review: 24 August 2027
Our promise. Hospitality is for everybody. The person ordering at your kiosk, the chef reading the kitchen screen, the manager checking a rota at 6am, the owner who is losing their sight — all of them should be able to use ServOS. We are building one platform to replace a whole stack, and if that platform locks people out, we have not done the job.
So we will be straight with you. ServOS is a young product. We design and build to WCAG 2.2 Level AA, and much of the platform already meets it. Some of it does not yet. This statement sets out where we stand, what we know is not good enough, what we are doing about it, and how to tell us when we get it wrong. We would rather publish an honest statement with gaps in it than a polished one that overclaims.
1.1 This statement applies to: ● Our websites — https://www.serv-os.app and any marketing, documentation and support pages we operate. ● Staff-facing product surfaces — the ServOS point of sale, floor and bar screens, kitchen display system (KDS), handheld, orders hub, time clock, back office, and the owner and manager apps. ● Customer-facing product surfaces — self-service kiosk, QR-code ordering, online ordering, digital menu boards, loyalty and gift-card pages, and any page a diner reaches from a venue running ServOS. ● Hardware we supply — the terminals, kiosks, printers and peripherals we sell or configure as part of an installation (§6).
1.2 It does not cover: content a venue creates and publishes itself using ServOS tools (menu descriptions, images, marketing emails — see §7); the appearance of the platform once a venue has customised it — colours, backgrounds, themes, imagery and typography (§7.4); the websites, apps and terms of our payment processors, delivery partners and other third parties (§8); or third-party hardware a venue sources independently.
2.1 Target: WCAG 2.2 Level AA. The Web Content Accessibility Guidelines 2.2 at Level AA are our design and build standard across every digital surface listed in §1.1. Where a surface is a native or kiosk application rather than a web page, we apply the equivalent success criteria and, for hardware, the relevant clauses of EN 301 549.
2.2 Current status: partially conformant. ServOS is partially conformant with WCAG 2.2 Level AA. “Partially conformant” means some parts of the platform do not yet fully conform to the standard. The known exceptions are listed in §4.
2.3 No formal third-party audit has been completed yet. Our current assessment is based on internal review and testing (§9). We have committed to an independent audit — see §5.
3.1 The following are in place across the surfaces assessed to date: ● Keyboard and switch access to core ordering, payment and back-office flows, with a visible focus indicator. ● Screen-reader support using standard semantic markup and accessible names on interactive controls. ● Contrast meeting or exceeding 4.5:1 for body text and 3:1 for large text and interface components, in both the light and dark themes as we ship them. Themes a venue customises are that venue’s responsibility (§7.4). ● Text sizing — layouts reflow without loss of content or function when text is enlarged to 200%. ● Touch targets sized for use with limited dexterity, and no interaction that requires a path-based gesture or fine motor precision without an alternative. ● No colour-only meaning — order states, allergen flags, 86’d items and alerts are conveyed by text or icon as well as colour. ● Motion and timing — no essential content depends on animation; time-outs on payment and session screens can be extended. ● Offline-first behaviour that does not strand a user mid-task when a connection drops.
3.2 These are commitments about how the platform is built, not a claim that every screen has been independently verified against every success criterion. §4 is the honest counterweight.
4.1 The following are known not to conform, or not yet to have been assessed. Each is listed with the WCAG 2.2 criterion it relates to and a target date. ● Kiosk — no audio output mode for blind users; screen-reader mode not yet implemented. WCAG 1.1.1, 1.4.5. Target: Q2 2027. ● Digital menu boards — display-only surface; content presented visually with no non-visual equivalent at the board itself. WCAG 1.1.1. Target: Q2 2027. ● Reports / Daily Trading P&L — complex data tables lack full header associations; some charts have no text alternative. WCAG 1.3.1, 1.1.1. Target: Q2 2027. ● Floor plan editor — drag-and-drop table layout has no keyboard-only equivalent. WCAG 2.1.1, 2.5.7. Target: Q2 2027. ● PDF exports — generated PDFs are not tagged for screen readers. WCAG 1.3.1. Target: Q2 2027. ● Third-party embeds — payment and mapping components rendered by third parties are outside our direct control — see §8. Target: ongoing.
4.2 Disproportionate burden. We are not currently claiming disproportionate burden for any part of the platform. If we ever do, we will name the specific content, explain the assessment, and say what alternative we offer instead.
4.3 Content outside scope of the regulations. Archived documentation and any pre-recorded media published before 24 August 2026 may not meet the standard. We will provide an accessible alternative on request.
5.1 Our remediation plan: ● Q4 2026 — Complete an internal audit of all surfaces in §1.1 against WCAG 2.2 AA and publish the results in §4. ● Q1 2027 — Commission an independent third-party accessibility audit, including testing with assistive technology users, before general availability. ● Q2 2027 — Remediate all Level A and Level AA findings, prioritising customer-facing surfaces (kiosk, QR and online ordering) where the diner has no alternative route. ● Ongoing — Accessibility acceptance criteria on every new feature, automated checks in the build pipeline, and manual keyboard and screen-reader testing before release.
5.2 We will not ship a new customer-facing surface that we know to be inaccessible without saying so here first.
6.1 Where we supply hardware as part of an installation, we specify equipment intended to meet the accessibility clauses of EN 301 549 for self-service terminals, including: interactive elements within reach range, adjustable brightness and contrast, magnification, a standard 3.5mm headphone socket for private audio output, hearing-aid compatibility where the device carries audio, tactile or audible confirmation of key presses, and no requirement for fine motor control or simultaneous actions.
6.2 Kiosks are never the only way to order. Where a venue deploys a ServOS kiosk, we require in our installation guidance that a staffed counter or table-service route to the same menu and the same prices remains available. A kiosk must be an option, never a barrier.
6.3 Accessibility features vary by hardware model. If a specific requirement matters to your venue or your customers, ask us before you order and we will tell you plainly what a given device does and does not do.
7.1 ServOS is the platform. When a diner orders from your venue, you are the service provider to that diner and the duties under the Equality Act 2010 to make reasonable adjustments are yours. We give you the tools; how you configure and use them is your decision.
7.2 What stays with you: ● The content you publish — menu item names and descriptions, image alternative text, uploaded PDFs, allergen and dietary information, and the marketing you send. ● Configuration choices — themes and colour overrides (§7.4), font sizes, kiosk placement and mounting height, and whether a staffed alternative is available. ● Your own website, if it is not one we built and host for you.
7.3 What we will do to help: sensible accessible defaults, contrast-safe theme options, alternative-text fields wherever an image can be uploaded, and guidance in our documentation on writing menu content that reads well aloud. If you would like a walkthrough of the accessibility settings for your sites, ask.
7.4.1 ServOS is customisable by design. You can set your own colours, backgrounds, background and header images, logos, button and text colours, dark or light mode, font choices and sizes, kiosk and menu-board artwork, receipt branding, and the layout and labelling of your own screens. That flexibility is deliberate: your venue should look like your venue, not like us.
7.4.2 The themes and colour combinations we ship as standard are designed and tested to meet WCAG 2.2 Level AA contrast requirements (success criteria 1.4.3 Contrast (Minimum), 1.4.6 where applicable, and 1.4.11 Non-text Contrast). Any combination you create yourself is not.
7.4.3 Where you change the appearance of the platform, responsibility for the accessibility of the result passes to you. ServOS is not responsible, and accepts no liability, for any accessibility barrier, contrast failure, legibility problem or non-conformity with WCAG 2.2 AA, the Equality Act 2010, the European Accessibility Act or any other accessibility standard or law, to the extent that it arises from: ● colours, background colours, background or hero images, gradients or overlays you have selected or uploaded; ● text, button, icon or border colours you have overridden; ● fonts, font sizes, weights or letter spacing you have chosen; ● images, artwork, video or animated content you have uploaded to any screen, menu board, kiosk or ordering page; ● custom CSS, theme files, brand kits or design assets you or a third party acting for you have applied; or ● any other appearance setting you have changed from the ServOS default.
7.4.4 Common ways a custom theme breaks accessibility — worth knowing before you brand your sites: light grey text on a white background; brand colours that look good on a printed menu but fall below 4.5:1 on screen; text placed over a photographic background; a highlight colour that is the only signal distinguishing an unavailable item; and font sizes reduced to fit more items on a kiosk screen. Each of these is a WCAG failure and, in a customer-facing surface, a potential Equality Act problem for your venue.
7.4.5 What we do to help you get it right. Where the platform can tell that a colour combination you have chosen falls below the WCAG 2.2 AA contrast threshold, it will warn you at the point you choose it. Proceeding past that warning is your decision and confirms that you accept responsibility for the result. We keep the accessible default theme available at all times, and you can revert to it in one step from your appearance settings. If you would like us to review a theme before you roll it out across your sites, send it to us at support@serv-os.app and we will check it and tell you what we find, at no charge.
7.4.6 This does not reduce your own legal duties. You remain the service provider to your customers and staff. Making your venue’s ordering surfaces usable by disabled people is a reasonable adjustment you are required to make under the Equality Act 2010, and choosing a theme that defeats it does not transfer that duty to us. Equally, nothing in this section limits our responsibility for the accessibility of the platform as we supply it.
8.1 Parts of the experience are delivered by third parties acting for us or for you — our payment processor (Adyen), delivery and aggregator partners, mapping and address providers, and messaging providers. Their interfaces are governed by their own accessibility standards and statements.
8.2 We raise accessibility defects with these providers and, where a defect materially blocks a diner or a staff member, we will look for an alternative route or an alternative provider. We will tell you here where a known third-party barrier exists.
9.1 Our assessment approach combines: ● Automated accessibility checks in the build pipeline. ● Manual keyboard-only testing of every core flow. ● Screen-reader testing with VoiceOver on iOS and macOS, NVDA on Windows, and TalkBack on Android. ● Contrast and reflow checks at 200% and 400% zoom. ● Physical testing of kiosk and terminal hardware against EN 301 549 reach, audio and tactile clauses. ● Planned: testing with disabled users and assistive-technology users as part of the independent audit in §5.1.
9.2 This statement was prepared on 24 August 2026. It was last reviewed on 24 August 2026. It is based on an internal self-assessment carried out by ServOS.
10.1 If you hit a barrier in ServOS — as an operator, a member of staff, or a diner using a venue that runs on us — tell us. Email support@serv-os.app, or use any support channel in the platform and ask for it to be routed to the accessibility team.
10.2 Please include, if you can: what you were trying to do, which screen or device, what assistive technology you were using, and what happened. It helps us reproduce and fix it faster.
10.3 Our commitment: we will acknowledge within 2 working days and give you a substantive response — a fix, a workaround, or an honest timetable — within 10 working days. If a barrier stops you completing something urgent, say so and we will find you a way through the same day.
10.4 Alternative formats. If you need any of our documents — this statement, our Terms, our Privacy Policy, contracts, invoices or reports — in large print, plain text, accessible PDF, audio or another format, ask and we will provide it at no charge.
11.1 United Kingdom. Service providers have a duty under the Equality Act 2010 to make reasonable adjustments so that disabled people are not put at a substantial disadvantage. If you are unhappy with how we have responded to your accessibility complaint, you can contact the Equality Advisory and Support Service (EASS) at https://www.equalityadvisoryservice.com. The Equality and Human Rights Commission (EHRC) is responsible for enforcing the Act.
11.2 European Union. Where we place products or offer services in the EU, the European Accessibility Act (Directive (EU) 2019/882) applies. It has applied to products placed on the market and services provided since 28 June 2025, with transitional arrangements for self-service terminals already in use before that date. The harmonised technical standard is EN 301 549. Complaints can be made to the enforcement body in the relevant member state.
11.3 United States. Where ServOS is used by venues in the United States, the Americans with Disabilities Act (ADA) may apply to those venues’ public-facing ordering surfaces. We support our US operators in meeting it; the duty as a place of public accommodation sits with the venue.
12.1 We review this statement at least annually and after any significant platform release. When the picture changes — for better or worse — we update §4 and §5 rather than leaving them stale. Previous versions are available on request.
13.1 Accessibility: support@serv-os.app General: ServOS App Inc (trading as ServOS), 251 Little Falls Drive, Wilmington, New Castle County, Delaware 19808, https://www.serv-os.app