Schedule security and accessibility: review, fixes and known exceptions
What the November 2026 security review of Scheduling found and fixed, the tests that keep every route and action authorised, the WCAG 2.2 AA accessibility audit, the automated accessibility gate, and the exceptions that remain.
On this page
This page sums up two checks of the Schedule tool, both made in November 2026: an adversarial security review and a WCAG 2.2 AA accessibility audit. It says what each one found, what was fixed, how the fixes stay fixed, and what is still open. It describes our own testing. It isn’t a certification or a third-party audit.
Security review
The review covered every Schedule REST handler (192 of them), every Schedule server action (164), the offline field mode, the schedule assistant, XER, P6 XML, XLSX and layout-file imports, CSV, XLSX and PDF exports, the cross-project features and the database migrations.
No critical or high findings. No route or action let one company read or write another company’s data, and none let a user reach a project above their Schedule permission level.
Six medium findings, all fixed:
- Three API token scope gaps. A token granted only Schedule could read titles and statuses of linked RFIs, submittals and purchase orders, change-event references, and daily-log entries. Each of those reads now also needs the owning tool’s scope.
- Offline sync on a shared device. If a second person signed in on a device where the first person’s session had expired, the first person’s queued progress could be saved under the second person’s name. The server now refuses a queue that belongs to someone else.
- An oversized XER import could use several gigabytes of memory. The parser now caps the total number of cells.
- A spreadsheet formula could slip through the cost dashboard CSV export when it started with a negative number. Only plain numbers are left unescaped now.
Fourteen low findings, nine fixed. The fixes add private, no-store caching and nosniff headers to every Schedule response and download, check an import’s size before reading it, stop a search from confirming activities you can’t see, add missing permission checks to two actions, add database guards on two references, and tell the assistant that schedule text is data, not instructions. The ninth fix makes a queued cross-project leveling job use the requesting API token’s scopes, exactly as a leveling run that finishes straight away does.
The other five are open or accepted, each with its reason:
- Link alerts send an activity’s name to the linked item’s recipients without checking that they can see the activity. This needs a product decision.
- Offline data stays on a device when a session ends without Sign out. This is documented in field mode.
- The owner of a shared template can rename or archive it with read-only Schedule access.
- Some older, high-volume tables rely on the app, not a database trigger, to keep references inside one company. Every writer re-checks them.
- An import sent in chunks, without a declared size, is read in full before its size is checked.
Tests that keep it fixed
Every fix has a regression test. Two structural tests also guard against new gaps:
- Routes. A test reads the source of every Schedule route and fails unless authentication comes first, before the request body or the database is touched. The token scope must match the method, every response and error must be private and no-store, and every download must send
nosniff. Ten routes accept a read scope for a POST or DELETE because they save no schedule data, such as previews and the presence heartbeat. They’re allow-listed by name, and the test fails if the list goes stale. - Server actions. A test reads every Schedule server action and fails unless it loads the signed-in user first and authorises before its next database call.
A new route or action that breaks these rules fails these tests, so it doesn’t depend on a reviewer noticing.
Accessibility (WCAG 2.2 AA)
The audit covered every Schedule page and the company schedule pages, at desktop width and at 390 px on touch, in the light and dark themes, with reduced motion. axe-core scanned 150 page states, including planner views, menus and dialogs. A keyboard and code review covered what axe can’t see: Gantt bar contrast, focus after a dialog closes, live announcements, alternatives to dragging, and motion.
Serious or critical violations went from 192 to 8. The 8 left are the touch activity card exception below. The fixes include:
- Contrast. Tertiary text now meets 4.5:1 in both themes. Gantt bars drawn in P6’s exact colours get a thin ring where a colour falls under 3:1 against the row, and the colours themselves are unchanged.
- Names. Buttons and links now have accessible names that match their visible text, and lists, tables and definition lists are marked up correctly.
- Keyboard. Focus returns to the row or bar after the activity menu or a dialog closes. The active grid cell is announced, and wide tables scroll from the keyboard.
- Dragging and targets. Column widths can be typed as well as dragged, and checkboxes are 24 px on touch screens.
- Announcements and motion. Leveling and program results are announced, and the last smooth scroll respects reduced motion.
The axe gate. A browser test runs axe on the Schedule pages and fails on any serious or critical violation that isn’t a listed exception. It also fails if focus is lost when the activity menu or a dialog closes.
Known exceptions
- Touch activity cards. Each card is one large button. Its spoken name starts with the activity ID and name you see, then reads the status and dates as a summary, not in visual order (WCAG 2.5.3).
- Pane dividers between the grid and the Gantt, and beside Activity Details, can be dragged or moved with the keyboard. The layout buttons give the same result with a single tap (WCAG 2.5.7).
- Deleting an activity from its menu leaves focus on the page, because the row it came from is gone. The grid is one Tab away (WCAG 2.4.3).
- Form-field borders are lighter than 3:1 across the app. Fields are identified by their labels, and focus shows a strong outline. This waits on a design-system change (WCAG 1.4.11).
- The PDF print Gantt uses P6’s exact colours on white, so yellow baselines and light-green bars are faint on paper. Choose the default bar preset for print.
- Two best-practice notes, not WCAG failures, come from the shared app shell and empty-state component.
Related
Keep exploring
Related across os.construction
- DocsSchedule: CPM planning, field tasks and the look-aheadPlan the project in a native critical path Planner or bring in a P6 or Microsoft Project file, then publish reviewed dates to the field task list your team reads as a list, 3-week look-ahead, calendar and Gantt.
- DocsField mode (offline)Use the schedule on a site with no signal. Keep a project's activities, last calculated dates and three-week lookahead on your phone, record progress offline, and sync it as one new version when signal returns, with every conflict put to you.
- GlossarySubmittalShop drawings, product data, samples or other documents a contractor sends to the design team for review before buying or installing materials.
- GlossaryField Mode (Offline Sync)A way to keep a schedule on a phone, record progress on site without signal, and sync the updates as one new version when the connection returns.
- BlogHow to build a three-week look-ahead schedule the field will actually useThe master schedule says what has to happen. The three-week look-ahead says who does it, where, and what has to be cleared first. Here is how to pull it from the master, break it down to crew level, screen every activity for constraints, get commitments from the trades, and roll it forward each week, with a worked example.
- ExplainerChoosing what to put in the data core firstA migration plan for os.construction: which records go in first, what the import tool brings over today, and what is a file, a manual step or planned.
Was this helpful?
Run it on your own project.
Start a 14-day free trial. Want a say in what ships next? Join the founding program.
14-day free trial. Pricing for paid plans isn't set yet. Talk to us. Already have an account? Sign in →