OwndUp is a tool people use every working day, sometimes without a mouse and sometimes with a screen reader. This page says where we stand, what we have fixed, and what we know is still wrong. It is deliberately specific, because a statement that only says we care is of no use to anyone buying software.
Our aim, and what we do not claim
We aim for WCAG 2.1 level AA. That is the target we build against and the standard we measure ourselves by.
We do not claim to conform to it. No independent party has audited OwndUp against WCAG 2.1 AA, so we publish no conformity level and no certificate. What follows is our own assessment, based on our own testing. If your purchasing process needs an external audit, tell us and we will discuss what that would take.
How we tested
In July 2026 we ran the app end to end using only the keyboard, from signing in to creating a list, adding a column, entering a date, setting a reminder and finding a row through the search shortcut. We inspected the accessibility tree at every step rather than only looking at the screen. That run produced a list of concrete faults, and the section below is what we did with it.
What we changed
All of the following is live:
- Every full screen overlay is a real dialog. The welcome screen, the row editor and every popup announce themselves by name, keep the keyboard inside them, and close on Escape. The page behind the welcome screen is taken out of the accessibility tree entirely.
- The app speaks. There is one live region through which every confirmation runs: a saved list, an added column, a set reminder, a cell somebody else changed first, the result of a bulk action, and the number of rows left after a filter. Before this, a saved reminder was completely silent, which cost one tester a duplicate reminder.
- Column headers work from the keyboard. Renaming a column, changing its type, switching deadline watching on and deleting it were reachable by mouse only. The header is now a button, and the editor it opens has a move left and move right for reordering without dragging.
- Rows of buttons say which one is on. The column type picker, the card and table switch, the list filters and the new list sources now carry aria-pressed instead of a colour difference only.
- Cells have names. A text cell used to be called "-" and every date cell in the list was called "Date". Each cell now announces its column and its row, so "End date, Fire extinguisher inspection" instead of a hyphen.
- The search shortcut is a proper list. Ctrl+K results are a listbox with arrow key navigation, the highlighted result is reported, the number of results is spoken, and opening a result puts the cursor in that row instead of somewhere on the page.
- Focus comes back. Closing any dialog returns the keyboard to the control that opened it, and Enter in a name field submits the form instead of asking for thirteen more tab presses.
Known limitations
These are real and we know about them:
- Date fields follow your browser, not our app. We use the browser's own date control, and it lays out its day, month and year segments in the browser's language, not in the app's. In an English browser, typing 01-12-2026 gives 12 January, not 1 December. We name the expected order under the field while it has focus, and we refuse impossible years, but we cannot reorder the control itself.
- In the grid, each cell is its own tab stop and the arrow keys do not move between cells. Tab and Enter do work across and down, spreadsheet style, but a long list is a long tab journey.
- Reordering lists and groups on the overview is still drag and drop only. Column reordering has a keyboard route; list reordering does not yet.
- We have not tested with VoiceOver or TalkBack on a phone. The overlays now carry the same dialog semantics as on the desktop, which was the cause of what we saw there, but that is reasoning, not a test result.
- This statement covers the app. The public website has had less attention, and the mobile menu in particular has not been through the same round.
Anything not on this list is not automatically fine. It means we have not found it yet.
If something blocks you
If a part of OwndUp stops you from doing your work, we want to hear the specific step, not a general remark. Tell us which screen, which key and what you expected, and we will tell you honestly whether we can fix it, when, and what to do in the meantime.
Contact
Email hello@owndup.com with "accessibility" in the subject line.
We reply within five working days. If we cannot solve it, we will say so and describe the workaround we do have.