Accessibility Statement
Arca · arcaportfolio.com · Last reviewed September 23, 2026
Everyone who owns part of a business should be able to read what it is doing. We want Arca — this site, the Owner Portal, and the installable app — to work for people who use a keyboard, a screen reader, magnification, voice control, or a phone held in one hand.
Our standard
We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. Arca is currently partially conformant: most of it meets the standard, and the exceptions we know about are listed below.
What we have done
- Automated testing. On September 23, 2026 we tested the public pages, the sign-in screen, every portal tab and Management sub-tab, and the Settings and Notifications panels with axe-core 4.13 against WCAG 2.0, 2.1 and 2.2 A and AA rules. Every issue it found was fixed, and the final run reported none.
- Contrast. Text meets at least 4.5:1 against its background, including secondary grey text on the lighter card surfaces.
- Labels. Every form field and dropdown has a name that assistive technology announces, including the ones inside tables.
- Keyboard. Tabs, buttons, menus, dialogs and forms work from the keyboard, with a visible focus outline. On the ownership chart, each box is a tab stop and Enter opens its details; the chart itself can be focused and scrolled with the arrow keys. Escape closes dialogs.
- Charts. The charts in Management → Reports have a data table beneath them, so every value can be read without a mouse or sight of the chart, and the chart colours were chosen to stay distinguishable with common forms of colour blindness.
- Touch. On phones, tap targets are at least 32px and usually 40px or more, and nothing makes the page scroll sideways.
- Motion. The animated loading indicators and the sign-in animation hold still when your device asks for reduced motion.
- Zoom and reflow. Pages can be zoomed to 200% and read on a 320px-wide screen; phones get a navigator in place of the ownership chart, listing each box's owners and holdings as text.
Known limitations
- Dragging on the ownership chart. On a computer, moving boxes around the chart and connecting two existing boxes are done by dragging. Every box's details can be opened and edited from the keyboard, and a new connected box can be added from a box's details, but connecting two existing boxes needs a pointer. If that blocks you, contact us and we will make the change for you.
- Documents you upload. Statements, invoices and other files are shown as they were uploaded. How accessible a PDF is depends on how it was made; a scanned image has no text a screen reader can read.
- Screen reader testing. We have not yet done a full audit with VoiceOver, NVDA and JAWS. Automated tools catch many problems but not all, and we plan to complete that audit.
- Third-party screens. Payment (Stripe), QuickBooks and Google sign-in screens are run by those companies and follow their own accessibility commitments.
Feedback and help
If something in Arca is hard or impossible for you to use, tell us — including what you were trying to do and the device, browser and any assistive technology you use. Email info@arcaportfolio.com. We aim to reply within five business days, and if we can't fix the problem quickly we will help you get what you need another way.
Technical details
Arca is built with HTML, CSS, JavaScript and WAI-ARIA, and relies on them to work with your browser and assistive technology. It supports current versions of Safari, Chrome, Edge and Firefox on desktop and mobile.
ARCA