In short (not part of the statement)
- We want people with disabilities to be able to learn about, buy and use LivingRoom and our website.
- We aim for WCAG 2.2 level AA but do not claim to meet it; some parts do not work well yet (section 5).
- No screen-reader test or outside audit has been done yet.
- Found a barrier? E-mail [email protected]. We aim to reply within 5 business days.
LivingRoom Accessibility Statement Draft 2 of 2026-10-25 - not yet in effect
This Accessibility Statement is published by Point of the Mountain Software LLC, a Utah limited liability company ("Company", "we", "us", "our"), for its LivingRoom software ("Software") and for our website at https://livingroomlogistics.com ("Website"). Words with capital letters have the meaning given in our End User License Agreement ("EULA") and our Terms of Service.
1. Our commitment
1.1 We want everyone to be able to use the Software, including people who use a keyboard, a screen reader, magnification or other assistive technology.
1.2 We are a small company and cannot promise that every part is accessible today. We do promise to say honestly what works and what does not (sections 4 and 5), to read and answer every accessibility report (section 8), and to work on problems in our normal Updates, starting with those that stop someone from doing their work.
2. What this statement covers
2.1 The Software (with its setup program and phone pages, EULA section 7.2), the Website, the Documentation and the Reseller Portal once it opens [not yet available].
2.2 Not services others run, even where we link to them, such as Paddle's checkout, Third-Party Services' websites, Windows, or the programs that open our PDF and spreadsheet files. If one stops you, tell us anyway (section 8): we will try to help.
3. The standard we aim for
3.1 Website: WCAG 2.2 level AA (W3C's Web Content Accessibility Guidelines).
3.2 Software: the same, as W3C's WCAG2ICT guidance (not a standard) applies it to non-web software.
3.3 A goal, not a claim. We have not measured either against every WCAG success criterion, and parts of the Software fall short (section 5). We do not claim that the Website or the Software conforms to WCAG 2.2, fully or partly. [to be confirmed]
4. What works in the Software today (version 2.0)
4.1 Keyboard: Alt+F and Alt+E open the File and Edit menus; Ctrl+K searches while a Company File is open (see 5.2); shortcuts open the main pages, and ? lists them; Escape closes most dialogs, asking first about unsaved changes.
4.2 Focus: fields, lists, check boxes, option buttons and standard buttons show a focus outline.
4.3 Screen readers (built in, not yet tested: 5.1): standard dialogs are labelled, hold the focus and return it (confirmation questions differ: 5.14); messages, page regions, switches and almost all icon-only buttons are marked or named.
4.4 Colour: white text on the standard blue buttons is about 5.2 to 1 (level AA asks for 4.5 to 1).
4.5 Time limits: you are warned, with a Stay logged in button, before an idle sign-out (8 hours by default; an Admin can change it). A Support Session ends when its Support Token expires and cannot be extended.
4.6 Signing in: passwords can be pasted; there is no puzzle to prove you are a person.
4.7 Phone pages label their sign-in fields, set their language and can be zoomed.
5. Known limitations
We plan to fix these in Updates, but cannot yet say when. [to be confirmed]
5.1 Not tested with screen readers (such as Narrator, NVDA or JAWS), speech recognition, or Windows' magnification, scaling, text size or contrast themes; nor is the setup program.
5.2 Some rows open only by mouse (for example on Purchase Orders, Products, Customers and some reports). Workaround: Ctrl+K reaches products, purchase orders, vendors, receiving records and invoices.
5.3 Some labels are not linked to their fields (for example in Settings and product details), so a screen reader may not say the field's name.
5.4 Light grey text (hints, details, placeholders, some icons): about 2.6 to 1, below level AA's 4.5 to 1.
5.5 Brand colour: a colour chosen in App Branding is not checked for readable white text; choose a dark one, or keep the standard blue.
5.6 No zoom or text size setting; Windows scaling and zoom keys are untested. The window needs at least 1024 by 680 pixels, may not fit at high scaling on a small screen, and does not rearrange for a narrower window.
5.7 Light colours only: no dark mode or "reduce animations" support; contrast themes untested.
5.8 Messages close after 5 seconds (errors after 8) and cannot be paused; a link in one goes with it.
5.9 Single-key shortcuts (G then a letter, ?) cannot be turned off or changed. They do not work while you type or a dialog is open, but can be set off by accident, for example by speech recognition.
5.10 Charts have no text summary or focus outline (the tooltip shows instead).
5.11 PDF files the Software creates are not tagged for screen readers; the same information is on screen.
5.12 English only: the Software, the Website and the Documentation.
5.13 AI Assistant: a Coming Soon Feature in the current release: it is not available. We will review its accessibility before it is switched on.
5.14 Confirmation questions take the focus and close with Escape, but Tab can leave them for the page behind, and the focus does not go back to where you were.
6. The Website and the Reseller Portal
6.1 We build each Website page to section 3.1 and, before publishing it, check it from the keyboard alone and with an automated accessibility checker. [to be confirmed]
6.2 When you buy or renew a License, you buy it from Paddle, our online reseller and Merchant of Record (Terms of Service section 2). If you cannot complete Paddle's checkout (section 2.2), e-mail [email protected] and we will try to help you complete the purchase through Paddle (for example with Paddle's buyer support, or a Paddle invoice if Paddle offers us Paddle Invoicing). We do not take payment directly. [to be confirmed]
6.3 The Reseller Portal [not yet available] labels its form fields but is not tested with assistive technology.
7. How we check accessibility
7.1 Our checks so far are our own: design and code reviews in October 2026, the fixes that followed, and some automated tests.
7.2 No outside audit yet of the Software or the Website, no automated accessibility checker run on the Software, and no published Accessibility Conformance Report (VPAT). [to be confirmed]
7.3 We use no "overlay" or plug-in that claims to make a website accessible automatically.
8. Feedback and help
8.1 If something is hard to use, e-mail [email protected] (subject "Accessibility") and tell us what happened and any assistive technology you use.
8.2 We aim to reply within 5 business days [to be confirmed], a target, not a guarantee. If we cannot fix the problem quickly, we will tell you whether and roughly when we plan to.
8.3 Meanwhile, we will try to help you another way, for example by e-mail or, if you ask, in a Support Session (EULA section 10).
8.4 Bought from a Reseller? It is your first contact for support, but you may always write to us about accessibility.
9. Other formats
On request and at no charge, we will send the Documentation, this statement or any of our legal documents in another format we can reasonably produce, such as plain text, Word or large print. [to be confirmed]
10. Compatibility
10.1 The Software runs on Windows 11, 64-bit (Windows 10 22H2 may work, untested). It uses a built-in Chromium engine, so we expect assistive technology that supports Chromium browsers to work, but we have tested none.
10.2 Windows Magnifier enlarges the Software (whether it follows the focus is untested). Other Windows features will be listed here once tested. [to be confirmed]
10.3 The phone pages are made for a current phone browser on the Customer's office network.
10.4 The Website is made for current versions of the main web browsers. [to be confirmed]
11. About this statement
11.1 We prepared this statement on not yet in effect from our own review of version 2.0 of the Software.
11.2 We will review it at least every 12 months and with each Major Version or Update that changes how the Software looks or is used. [to be confirmed]
11.3 This statement describes our goals and what we know today. It is not a warranty or a promise that the Software or the Website meets any accessibility standard, and it does not change the EULA or the Terms of Service.
12. Contact
Point of the Mountain Software LLC, [email protected] (subject "Accessibility").