Accessibility statement

Conformance claim

gantts.app is partially conformant with WCAG 2.2 Level AA. Partially conformant means most of the tool meets the standard and some parts do not yet. The known exceptions are listed below rather than left for you to discover.

This is a self-assessment. It has not been audited by a third party, and the editor has not yet been tested with a screen reader by a person who uses one daily. Both of those are real limits on how much weight this statement can carry, and we would rather say so than imply a level of assurance we have not earned.

What works

The Gantt chart is the hard part of this problem: a bar chart encodes meaning in position and length, which is spatial information a screen reader cannot convey by describing one bar at a time. Four separate paths exist so that the chart is not the only way to use the tool.

• Every task bar is reachable by keyboard and carries a description of everything the bar shows visually — its dates, duration, progress, assignee, whether it is on the critical path, and how many tasks it depends on.
• Arrow keys move and resize tasks. Left and right move by one working day, Shift by a week, Alt resizes the end. The resulting dates are announced, so you hear where the task landed rather than that a key was pressed.
• The chart is one tab stop, not two hundred. A roving tabindex means Tab moves past the chart in a single press; arrow keys navigate inside it.
• Nudge buttons reschedule by clicking — move back or forward a day or a week, lengthen or shorten by a day, with no dragging at all. Along with the date fields and the dependency picker in the task panel, this means nothing requires a drag.
• A plain-table view renders the whole plan as a real HTML table with row and column headers. Many people will work entirely from this, and it doubles as the print view and the thing you paste into an email.
• A summary sentence describes the chart as a whole — task count, date range, how many tasks are on the critical path, how many are overdue — so arriving at it does not mean exploring every bar to learn its shape.
• The critical path is not marked by colour alone. Critical bars carry a diagonal hatch and a distinct border; dependency arrows on the critical path are dashed. This survives greyscale, printing and colour blindness. The same is true of the S-curve, where the three lines differ by dash pattern as well as colour.
• Windows High Contrast is supported. Forced-colors mode replaces colours and drops background images, which would otherwise remove both critical-path cues at once, so critical bars get a dashed border there instead.
• Touch works. The chart uses Pointer Events, so it can be operated with a finger or a stylus, and hit targets grow on touch screens.
• Reduced motion is respected via prefers-reduced-motion.
• Content pages — the guides, templates and this page — use ordinary semantic HTML with a single h1, ordered headings, real landmarks and visible focus.

What does not conform yet

These are the gaps we know about. If you hit something not on this list, please tell us — that is more useful than anything else on this page.

• No screen-reader testing has been done. The chart has been built against the specification and verified in code, which is not the same as being usable. NVDA, JAWS and VoiceOver may each behave differently from what we expect. This is the largest gap in this statement.
• Creating a dependency by dragging from the dot on a bar has a click-only alternative in the task panel, but the drag itself is still the more discoverable route. The alternative works; it is not yet as easy to find.
• Reordering rows uses native drag-and-drop in the task list. There is a keyboard alternative (Alt with the up and down arrows) but no click-only one.
• Some export dialogs — the PDF options in particular — have not been reviewed for keyboard order or labelling as carefully as the main interface.
• No formal audit or VPAT. If you need one for procurement, contact us and tell us what format you need.

How this was assessed

Reviewed against WCAG 2.2 Level AA using manual keyboard testing, inspection of the accessibility tree, computed-style checks for contrast and forced-colors behaviour, and automated checks that run on every build — including one that fails the build if a chart element loses its label. Browsers used: recent Chrome and Edge on Windows.

Not used: a screen reader, a formal audit tool suite, or testing by disabled users. Those are the next steps, in that order.

Why this page exists

Most Gantt tools either publish nothing about accessibility or hide a conformance report behind an email request. That makes it impossible to tell, before committing to a tool, whether you will be able to use it. We would rather publish something specific and incomplete than nothing at all — and rather be told we are wrong than not know.

Last reviewed 19 July 2026. This statement is updated when the tool changes, not on a schedule.