Coetio is intended to work for every student and advisor, including people who use a keyboard, a screen reader, or other assistive technology. The target is WCAG 2.1 Level AA. That standard is not yet met on every screen, and this page states plainly what is done and what is not.
Where things stand
Coetio is partially conformant with WCAG 2.1 Level AA. “Partially conformant” means parts of the app meet the standard, and parts have not been checked or do not yet meet it.
The list of problems below is specific by design. A known barrier is named here, along with a way around it. A vague accessibility page is less useful than none, since an unstated gap surfaces only when a person is blocked by it.
Based on Coetio's internal review of the app on August 8, 2026, re-checked on August 17, 2026 after two further rounds of changes. No outside audit has been performed, and not every screen reader has been tested.
What works today
- A visible focus outline on links, buttons, and form fields, in both light and dark themes, so keyboard users can always see where they are.
- A “Skip to content” link at the top of the main app screens, so keyboard users can jump past the navigation.
- Labels on form fields, and text for screen readers on icon-only buttons.
- Buttons are at least 40 pixels tall on the standard styles, controls that sit in a list row are a uniform 36 pixels, and every control in the app clears the 24-pixel minimum in WCAG 2.2. The tick target on a task step used to be about 20 pixels and is now 36.
- Nothing in Coetio can only be done by dragging. The task board has a labeled button on each card to move it between columns, the dashboard sections have Move up and Move down buttons beside the drag handle, and the meeting agenda's timeline has labeled minus-5-minute and plus-5-minute buttons beside every bar, for both when an item starts and how long it runs.
- The view strips, like list-or-month on the calendar or board-or-list on tasks, are one shared control that marks the current choice on the accessibility attribute itself, and the highlight is drawn from that attribute. The choice a screen reader announces and the one that looks selected cannot disagree.
- Dark mode that follows the device's setting, plus a manual switch.
- Reduced motion works two ways: Coetio honors the device's reduce-motion setting, and a “Reduce motion” switch on the Profile page turns off animations across the app. Two gaps were closed this update: animation delays are now zeroed as well, so nothing sits invisible before appearing, and the in-app switch now also silences vibration, which previously followed only the device setting.
- A short buzz confirms a successful check-in and flags an undo message, on devices whose browser supports vibration. In practice that means Android. iPhones do not let websites vibrate at all, so on an iPhone nothing is broken; the feature does not exist there. The buzz is skipped when either reduce-motion switch is on.
- Errors, confirmations, and status messages are announced to screen readers. Refusals got more honest this month: the dashboard now shows the message when an action is refused, search no longer says “nothing found” when it actually meant “not allowed”, and buttons unavailable to a given role are no longer drawn only to redirect a visitor elsewhere.
- In meeting mode, the agenda's controls say their state in words. The Start button names its item, the check-off says “Mark it covered”, a covered line says “Covered”, and on the member view a member's own line says “Mark your part done” and, once done, offers the undo by name.
- Deleting asks first, in words that say what goes along: removing a step that has smaller steps under it says how many go with it, and taking someone off a task warns that their part of the record goes too.
- The “add Coetio to your home screen” invitation is a bottom sheet, not a modal. The page behind it keeps working, Escape closes it, closing hands focus back where it was, and it only ever appears on a quiet page, never over check-in or a form. Declining it twice retires it for good.
- Progress bars on a task and in meeting mode report their number, so “3 of 7 steps done” is spoken rather than shown only as a filled strip.
- The picker for choosing who is on a task keeps focus inside itself while it is open, closes with Escape, hands focus back to the button that opened it, and announces the running count as choices are made.
- Coetio aims for text contrast that meets AA in both themes. The meeting screens are the one part of the app with color and gradients, and their contrast was measured against every club color rather than eyeballed.
- Attendance does not require a camera. When scanning a QR code is not workable, a leader can mark a member present by hand, or a club can use kiosk mode, where a member taps their own name.
- On a phone, the month calendar is replaced by a simpler week strip, so no screen requires reading a seven-column grid at that width.
What still needs work
A complete list, stated before it is encountered.
Task steps that do not say whether they are checked
On a task's own page, the step check-off button reads out the same words whether the step is done or not. Done is shown by a filled marker and a line through the text, and neither of those is spoken. Meeting mode had the same problem and was fixed this month; the task page is the remaining place, and the largest known barrier. Two ways around it: the small (i) beside each step reports whether it is done, when, and who did it; and the event page's own checklist covers the same items and does announce “Check off” and “Uncheck” correctly.
Finished and unfinished shown without words
On several read-only lists, a finished item is marked with an icon and a line through the text and nothing else, so a screen reader reads the same sentence either way. This affects agenda lines belonging to someone else in a member's view of meeting mode, a club's setup checklist, a member's involvement record, and the projector view. A member's own lines in meeting mode, the dashboard, and the calendar all say it in words.
A filter that shows its selection with color alone
On the calendar, the active club filter is signaled only by the color of the chip. The list-or-month switch above it and the view strips elsewhere mark the current choice properly. The calendar's club chips do not yet, and the dashboard's events-section club chips have the same problem.
Two extras that only appear under a mouse pointer
On the Tasks page, a preview panel opens under a row on hover, and the names behind a “+3” chip appear on hover when a task has more people on it than fit in the row. Neither opens on keyboard focus, and neither works on a touch screen. Nothing is only in them. Everything both show is on the task's own page, which the task title links to.
Smaller problems already known
- The event page's checklist progress bar has no name, so a screen reader announces a bare percentage instead of how many items are done. The count is written out in text beside it.
- The meeting timer: when it reaches zero, the pause button is replaced, so keyboard focus drops back to the top of the page. Nothing is announced when the time is up either.
- The small (i) buttons on task steps read their label twice on some screen readers, and they do not close with Escape. Pressing the (i) again closes it.
- The club color picker in Settings can read as a row of unlabeled radio buttons on some screen readers. The club icon picker had the same problem and was rebuilt as a labeled text box with named suggestions, so that half is fixed, and the committee versions of both pickers are labeled.
- A ⋯ menu stays open when focus tabs out of it. Escape closes it.
- On the event form, picking a previously used place fills in the address and room boxes without announcing that it happened.
- On the phone week strip, the dots that mean “something happens this day” are not announced.
- A few wide tables scroll sideways on a small phone: the permissions grid in Settings and the hours transcript.
- Not every screen has been tested on every screen reader, so some labels and reading orders are likely still awkward.
- No independent accessibility audit has been done.
- Content that club leaders write is their own. Coetio cannot guarantee that an uploaded image, document, or poster is accessible.
- The bot check on the sign-up and club join forms is provided by Cloudflare, and Coetio does not control its accessibility.
Reported problems are fixed first, ahead of the rest of this list.
Report a barrier
A barrier encountered while using Coetio can be reported by email to support@coetio.com with the page involved, the task being attempted, and the device or assistive technology in use. Coetio aims to reply within a few days, with a workaround where one exists while the underlying problem is fixed. The feedback form can also be used.