Gantt accessibility audit
A repeatable check of keyboard behaviour and of what the browser hands to assistive technology, for any page with a Gantt chart. It answers the same 16 questions on every page and writes a table (protocol version 2; version 1 results are kept).
What it is: an automated browser (Chromium, through Playwright) pressing keys and reading the accessibility tree. What it is not: a test with a screen reader, a test with people, or a statement about WCAG conformance. A "pass" means the behaviour was observed in the browser, nothing more. PROTOCOL.md lists, for each check, how it is done and what it does not prove.
Latest results (2026-11-16-v2)
This audit checks keyboard behaviour and what the browser hands to assistive technology, in an automated browser (Chromium 159.0.8154.6). It is not a test with a screen reader and not a statement about WCAG conformance. See PROTOCOL.md for what each check does, what each result means and what it does not prove, and its threats to validity.
Baseline. The columns "without the extension" are what the extension is compared with: the same demo pages of this repository, with the same data and gantt-a11y turned off (
?a11y=off), so they show the library's own behaviour: dhtmlx-gantt 10.0.3, frappe-gantt (version not visible on the page). Measured automatically on 2026-11-16; this does not replace a check with a screen reader.
Results: pass; fail; tree only (present in the accessibility tree, but not on anything keyboard focus reaches and not after a documented command); no path (no documented keyboard path); n/a (not applicable); ? (could not determine). † marks a cell that differs from the version 1 run of 2026-11-16 (audit/results/2026-11-16.md); the reasons are listed under the table.
| Check | dhtmlx-gantt demo with gantt-a11y | dhtmlx-gantt demo without the extension | frappe-gantt demo with gantt-a11y | frappe-gantt demo without the extension |
|---|---|---|---|---|
| Keyboard focus reaches a task row | pass | pass | pass | fail |
| Keyboard focus reaches a task bar | fail | fail | fail | fail |
| A task's name is available | pass | pass | pass | fail |
| A task's dates are available | pass | pass | pass | fail |
| Dependencies are available as text | pass | tree only † | pass | fail |
| Dependencies name the tasks | pass | tree only † | pass | n/a |
| Level in the hierarchy is available | pass | pass | n/a | fail |
| Position in the list is available | pass † | fail | pass † | fail |
| The page has a live region | pass | fail | pass | fail |
| The result of an edit reaches the user | pass † | pass † | pass | no path † |
| Dates can be changed from the keyboard | pass | pass † | pass | no path † |
| Duration can be changed from the keyboard | pass | pass † | pass | no path † |
| A link can be created from the keyboard | pass | no path † | pass | no path † |
| Focus returns to the task after closing the form | pass | pass | n/a | ? |
| The page tells the user which keys exist | pass † | pass † | pass † | pass † |
| The extension's keys do not overlap the library's documented keys |
Changes since version 1 (2026-11-16)
| Page | Check | Version 1 | Version 2 | Why |
|---|---|---|---|---|
| dhtmlx-gantt demo without the extension | Dependencies are available as text | pass | tree only | Version 1 counted dependency text anywhere in the accessibility tree; version 2 requires it on an element that keyboard focus reaches, or after a documented command. |
| dhtmlx-gantt demo without the extension | Dependencies name the tasks | pass | tree only | Version 2 looks only at dependency text that can be reached from the keyboard. |
| dhtmlx-gantt demo with gantt-a11y | Position in the list is available | fail | pass | Version 2 looks at the row that holds keyboard focus, and at documented commands (gantt-a11y's Shift+W). |
| frappe-gantt demo with gantt-a11y | Position in the list is available | fail | pass | Version 2 looks at the row that holds keyboard focus, and at documented commands (gantt-a11y's Shift+W). |
| dhtmlx-gantt demo with gantt-a11y | The result of an edit reaches the user | fail | pass | Replaces “text in a live region after an edit”: a live region, an alert or status, or a change of the focused element's name all count. |
| dhtmlx-gantt demo without the extension | The result of an edit reaches the user | fail | pass | Replaces “text in a live region after an edit”: a live region, an alert or status, or a change of the focused element's name all count. |
| frappe-gantt demo without the extension | The result of an edit reaches the user | fail | no path | Replaces “text in a live region after an edit”: a live region, an alert or status, or a change of the focused element's name all count. |
| dhtmlx-gantt demo without the extension | Dates can be changed from the keyboard | fail | pass | Version 2 follows the keyboard paths documented by each library (sources in profiles.js); without one the result is “no documented keyboard path”. |
| frappe-gantt demo without the extension | Dates can be changed from the keyboard | fail | no path | Version 2 follows the keyboard paths documented by each library (sources in profiles.js); without one the result is “no documented keyboard path”. |
| dhtmlx-gantt demo without the extension | Duration can be changed from the keyboard | fail | pass | Version 2 follows the keyboard paths documented by each library (sources in profiles.js); without one the result is “no documented keyboard path”. |
| frappe-gantt demo without the extension | Duration can be changed from the keyboard | fail | no path | Version 2 follows the keyboard paths documented by each library (sources in profiles.js); without one the result is “no documented keyboard path”. |
| dhtmlx-gantt demo without the extension | A link can be created from the keyboard | fail | no path | Version 2 follows the keyboard paths documented by each library (sources in profiles.js); without one the result is “no documented keyboard path”. |
| frappe-gantt demo without the extension | A link can be created from the keyboard | fail | no path | Version 2 follows the keyboard paths documented by each library (sources in profiles.js); without one the result is “no documented keyboard path”. |
| dhtmlx-gantt demo with gantt-a11y | The page tells the user which keys exist | (new check) | pass | New check in version 2. |
| dhtmlx-gantt demo without the extension | The page tells the user which keys exist | (new check) | pass | New check in version 2. |
| frappe-gantt demo with gantt-a11y | The page tells the user which keys exist | (new check) | pass | New check in version 2. |
| frappe-gantt demo without the extension | The page tells the user which keys exist | (new check) | pass | New check in version 2. |
Pages
dhtmlx-gantt demo with gantt-a11y
- URL: /demo/index.html
- Library: dhtmlx-gantt 10.0.3; gantt-a11y: on
- Found: 11 task rows, 8 bars, 10 link elements
- Status: checked
| Check | Result | Evidence |
|---|---|---|
| Keyboard focus reaches a task row | pass | Tab ×3: focus on row “Website redesign. Project, 1 to 23 June, 10 tasks. 0 percent done.” |
| Keyboard focus reaches a task bar | fail | Tab ×40 and ArrowRight never put focus on a bar; 0 of 8 bars have a tabindex |
| A task's name is available | pass | a) tree: row “Implementation. 5 to 13 June, 8 days. 0 percent done.”. b) focus: focus: row “Implementation. 5 to 13 June, 8 days. 0 percent done.”. c) command: no documented command |
| A task's dates are available | pass | a) tree: “Implementation. 5 to 13 June, 8 days. 0 percent done.”. b) focus: focus: row “Implementation. 5 to 13 June, 8 days. 0 percent done.”. c) command: no documented command |
| Dependencies are available as text | pass | a) tree: link elements: image “Link Software design (end) Implementation (start)”; image “Link Implementation (end) Code review (end)”; image “Link Implementation (start) Documentation (start)”; image “Link Implementation (end) Testing (start)”; image “Link Launch (start) Marketing prep & PR (end)”. b) focus: no. c) command: Shift+D: “Depends on: Software design. Required by 3. Documentation, start to start. Code review, finish to finish. Testing.” |
| Dependencies name the tasks | pass | In reachable dependency text: “Software design”, “Testing”, “Documentation”, “Code review” |
| Level in the hierarchy is available | pass | a) tree: row: level 2. b) focus: row holding focus: level 2. c) command: Shift+W: “Implementation. In Website redesign. Level 2, 2 of 10.” |
| Position in the list is available | pass | a) tree: no. b) focus: no. c) command: Shift+W: “Implementation. In Website redesign. Level 2, 2 of 10.” Without explicit attributes a screen reader counts the rows in the DOM, which is right only while every row is rendered and none is filtered out. |
| The page has a live region | pass | 1: aria-live=polite |
| The result of an edit reaches the user | pass | After the date edit: accessible name of the focused element changed: “Cancelled. Nothing changed.” → “Starts Saturday 6 June, ends Sunday 14 June. 3 conflicts. Largest: Testing, 1 day too early.”. |
| Dates can be changed from the keyboard | pass | Steps: Alt+Shift+ArrowRight. 1 bar(s) moved.Sources: gantt-a11y README.md, section Keys (this repository). |
| Duration can be changed from the keyboard | pass | Steps: Alt+Shift+ArrowUp. 1 bar(s) changed width.Sources: gantt-a11y README.md, section Keys (this repository). |
| A link can be created from the keyboard | pass | Steps: Shift+L, ArrowDown, ArrowDown, ArrowDown, ArrowDown, ArrowDown, Shift+L. link elements 10 → 11.Sources: gantt-a11y README.md, section Keys (this repository). |
| Focus returns to the task after closing the form | pass | Enter opened “05 June 2026 - 13 June 2026 Implementation”; after Escape focus is back on the same task row (row “Cancelled. Nothing changed.”) |
| The page tells the user which keys exist | pass | Shift+H (documented command): “Reading, 1 of 6. Dependencies, Shift D key. Same time, Shift O key. Ends before, Shift B key. Starts after, Shift A key.”. text on the page outside the chart (written by the page's authors): “to enter the chart and move between tasks with the arrow keys.” |
dhtmlx-gantt demo without the extension
- URL: /demo/index.html?a11y=off
- Library: dhtmlx-gantt 10.0.3; gantt-a11y: off
- Found: 11 task rows, 8 bars, 10 link elements
- Status: checked
| Check | Result | Evidence |
|---|---|---|
| Keyboard focus reaches a task row | pass | Tab ×3: focus on row “Task: Website redesign Start date: 2026-06-01 End date: 2026-06-23” |
| Keyboard focus reaches a task bar | fail | Tab ×40 and ArrowRight never put focus on a bar; 0 of 8 bars have a tabindex |
| A task's name is available | pass | a) tree: row “Task: Implementation Start date: 2026-06-05 End date: 2026-06-13”. b) focus: focus: row “Task: Implementation Start date: 2026-06-05 End date: 2026-06-13”. c) command: no documented command |
| A task's dates are available | pass | a) tree: “Task: Implementation Start date: 2026-06-05 End date: 2026-06-13”. b) focus: focus: row “Task: Implementation Start date: 2026-06-05 End date: 2026-06-13”. c) command: no documented command |
| Dependencies are available as text | present but not reachable | a) tree: link elements: image “Link Software design (end) Implementation (start)”; image “Link Implementation (end) Code review (end)”; image “Link Implementation (start) Documentation (start)”; image “Link Implementation (end) Testing (start)”; image “Link Launch (start) Marketing prep & PR (end)”. b) focus: no. c) command: no documented command |
| Dependencies name the tasks | present but not reachable | Only in the accessibility tree: “Software design”, “Testing”, “Documentation”, “Code review” |
| Level in the hierarchy is available | pass | a) tree: row: level 2. b) focus: row holding focus: level 2. c) command: no documented command |
| Position in the list is available | fail | a) tree: no. b) focus: no. c) command: no documented command Without explicit attributes a screen reader counts the rows in the DOM, which is right only while every row is rendered and none is filtered out. |
| The page has a live region | fail | No aria-live region or status/log/alert role on the page |
| The result of an edit reaches the user | pass | After the date edit: accessible name of the focused element changed: “Task: Implementation Start date: 2026-06-05 End date: 2026-06-13” → “Task: Implementation Start date: 2026-06-06 End date: 2026-06-14”. |
| Dates can be changed from the keyboard | pass | Steps: Enter, Tab to .gantt_cal_light .gantt_time_selects select, .gantt_cal_light .gantt_section_time select, type “6” in the list box (was “5”), Tab to [role="button"][aria-label="Save"], .gantt_save_btn_set, Enter. 1 bar(s) moved.Sources: https://docs.dhtmlx.com/gantt/guides/keyboard-navigation/. |
| Duration can be changed from the keyboard | pass | Steps: Enter, Tab to .gantt_duration_inc, Space, Tab to [role="button"][aria-label="Save"], .gantt_save_btn_set, Enter. 1 bar(s) changed width.Sources: https://docs.dhtmlx.com/gantt/guides/keyboard-navigation/. |
| A link can be created from the keyboard | no documented keyboard path | The documented shortcuts for task rows, task cells and the form do not include creating a link (links are created by dragging).Sources: https://docs.dhtmlx.com/gantt/guides/keyboard-navigation/. |
| Focus returns to the task after closing the form | pass | Enter opened “05 June 2026 - 13 June 2026 Implementation”; after Escape focus is back on the same task row (row “Task: Implementation Start date: 2026-06-05 End date: 2026-06-13”) |
| The page tells the user which keys exist | pass | text on the page outside the chart (written by the page's authors): “to enter the chart and move between tasks with the arrow keys.” Only the page's own text: a product configured differently may have none. |
frappe-gantt demo with gantt-a11y
- URL: /demo/frappe.html
- Library: frappe-gantt (version not visible on the page); gantt-a11y: on
- Found: 9 task rows, 9 bars, 7 link elements
- Status: checked
| Check | Result | Evidence |
|---|---|---|
| Keyboard focus reaches a task row | pass | Tab ×3: focus on option “Software design. 1 to 4 June, 4 days. 100 percent done.” |
| Keyboard focus reaches a task bar | fail | Tab ×40 and ArrowRight never put focus on a bar; 0 of 9 bars have a tabindex |
| A task's name is available | pass | a) tree: option “Testing. 13 to 17 June, 5 days. 40 percent done.”. b) focus: focus: option “Testing. 13 to 17 June, 5 days. 40 percent done.”. c) command: no documented command |
| A task's dates are available | pass | a) tree: “Testing. 13 to 17 June, 5 days. 40 percent done.”. b) focus: focus: option “Testing. 13 to 17 June, 5 days. 40 percent done.”. c) command: no documented command |
| Dependencies are available as text | pass | a) tree: no. b) focus: no. c) command: Shift+D: “Depends on: Implementation. Required by: Launch.” |
| Dependencies name the tasks | pass | In reachable dependency text: “Implementation”, “Launch” |
| Level in the hierarchy is available | not applicable | A flat list of options has no levels. |
| Position in the list is available | pass | a) tree: no. b) focus: no. c) command: Shift+W: “Testing. Top level, 6 of 9.” Without explicit attributes a screen reader counts the rows in the DOM, which is right only while every row is rendered and none is filtered out. |
| The page has a live region | pass | 1: aria-live=polite |
| The result of an edit reaches the user | pass | After the date edit: live region: “Starts Sunday 14 June, ends Thursday 18 June. Conflict. Launch is now 1 day too early.”; accessible name of the focused element changed: “Testing. 13 to 17 June, 5 days. 40 percent done.” → “Testing. 14 to 18 June, 5 days. 40 percent done.”. |
| Dates can be changed from the keyboard | pass | Steps: Alt+Shift+ArrowRight. 1 bar(s) moved.Sources: gantt-a11y README.md, section Keys (this repository). |
| Duration can be changed from the keyboard | pass | Steps: Alt+Shift+ArrowUp. 1 bar(s) changed width.Sources: gantt-a11y README.md, section Keys (this repository). |
| A link can be created from the keyboard | pass | Steps: Shift+L, ArrowDown, ArrowDown, ArrowDown, Shift+L. link elements 7 → 8.Sources: gantt-a11y README.md, section Keys (this repository). |
| Focus returns to the task after closing the form | not applicable | Enter on a task row opened no dialog. |
| The page tells the user which keys exist | pass | Shift+H (documented command): “Reading, 1 of 6. Dependencies, Shift D key. Same time, Shift O key. Ends before, Shift B key. Starts after, Shift A key.”. text on the page outside the chart (written by the page's authors): “. frappe-gantt has no keyboard navigation of its own, so the adapter adds the task list on the left: Tab into it, move with Up and Down.” |
frappe-gantt demo without the extension
- URL: /demo/frappe.html?a11y=off
- Library: frappe-gantt (version not visible on the page); gantt-a11y: off
- Found: 9 task rows, 9 bars, 7 link elements
- Status: checked
| Check | Result | Evidence |
|---|---|---|
| Keyboard focus reaches a task row | fail | Tab ×120 (and ArrowDown inside the chart) never put focus on a task row; last focus: body “gantt-a11y demo with frappe-gantt The same engine as the dh…” |
| Keyboard focus reaches a task bar | fail | Tab ×40 and ArrowRight never put focus on a bar; 0 of 9 bars have a tabindex |
| A task's name is available | fail | a) tree: no. b) focus: focus never reached a task row. c) command: no documented command |
| A task's dates are available | fail | a) tree: no. b) focus: focus never reached a task row. c) command: no documented command |
| Dependencies are available as text | fail | a) tree: no. b) focus: focus never reached a task row. c) command: no documented command |
| Dependencies name the tasks | not applicable | No dependency text found at any level. |
| Level in the hierarchy is available | fail | a) tree: no. b) focus: focus never reached a task row. c) command: no documented command |
| Position in the list is available | fail | a) tree: no. b) focus: focus never reached a task row. c) command: no documented command Without explicit attributes a screen reader counts the rows in the DOM, which is right only while every row is rendered and none is filtered out. |
| The page has a live region | fail | No aria-live region or status/log/alert role on the page |
| The result of an edit reaches the user | no documented keyboard path | No documented keyboard path for any edit. |
| Dates can be changed from the keyboard | no documented keyboard path | frappe-gantt has no keyboard handling.Sources: frappe-gantt 1.2.2: README and source in node_modules/frappe-gantt (no keyboard handling, no keydown listener). |
| Duration can be changed from the keyboard | no documented keyboard path | frappe-gantt has no keyboard handling.Sources: frappe-gantt 1.2.2: README and source in node_modules/frappe-gantt (no keyboard handling, no keydown listener). |
| A link can be created from the keyboard | no documented keyboard path | frappe-gantt has no keyboard handling.Sources: frappe-gantt 1.2.2: README and source in node_modules/frappe-gantt (no keyboard handling, no keydown listener). |
| Focus returns to the task after closing the form | could not determine | Focus never reached a task row. |
| The page tells the user which keys exist | pass | text on the page outside the chart (written by the page's authors): “. frappe-gantt has no keyboard navigation of its own, so the adapter adds the task list on the left: Tab into it, move with Up and Down.” Only the page's own text: a product configured differently may have none. |
Notes on this run
Written after reading the evidence in 2026-11-16-v2.md. Only the four demos of this repository are published; see PROTOCOL.md, "Pages of other libraries".
Results that depend on the demo, not the product
- Our own demos without the extension, "The page tells the user which keys exist": pass comes from the demo pages' introductory text, written for this project ("Press Tab to enter the chart…"). The libraries themselves give no help; a product page without such text would fail.
The protocol
The same questions for any page with a Gantt chart, answered in an automated Chromium browser with Playwright (audit/run.js).
This is not a test with a screen reader and says nothing about WCAG conformance. It shows what reaches the keyboard and the accessibility tree; what a screen reader then speaks, and whether a person can use it, are separate questions.
Version 1 (results of 2026-11-16 in results/2026-11-16.*) is kept as it was. Version 2 changed how information is judged, how edits are attempted and announced, and added a check for keyboard help; results/<date>-v2.md marks every cell that differs from version 1 and says why.
Pages of other libraries
profiles.js has profiles for public demos of other Gantt libraries (a dhtmlx-gantt sample, Bryntum Gantt, Syncfusion Gantt, Kendo UI Gantt), with their keys and keyboard paths according to the vendor documentation, each with its source URL. Their results are not published until they have been confirmed by hand: an automated run on someone else's demo can describe the audit's own limits as the product's (see "Threats to validity"). A run writes everything to audit/private/results/, which is not in the repository, and only the four demos of this repository to results/.
Results
| Result | Meaning |
|---|---|
| pass | The behaviour was observed. For information: it is on an element that keyboard focus reaches, or it appears after a documented keyboard command. |
| fail | It was looked for and not observed. For an edit: the documented keys were pressed and nothing changed, or a step of the documented path could not be taken (the evidence says which, and notes that the demo's configuration may be the reason). |
| present but not reachable | (Shown as "tree only".) The information is in the accessibility tree, but not on anything keyboard focus reaches and not after a documented command. A screen reader user might find it by exploring with the screen reader's own commands, if at all. |
| no documented keyboard path | (Shown as "no path".) The library's documentation, as read for the profile, describes no keyboard way to do this. Not a fail: a way may exist undocumented. The sources are listed with the result. |
| not applicable | The question does not apply (for example, Enter opens no form, so there is no focus to return; a flat list has no levels). |
| could not determine | The audit could not look (focus never reached a row; it has no information on the library's keys; it did not recognise a date format). A limit of the audit, not a finding about the page. |
Every result comes with evidence: roles, accessible names and texts as the browser exposes them, the keys pressed, and for edits the documentation sources.
How a page is described
A profile (profiles.js) gives CSS selectors for the chart, a task row, a bar and a link (there is no standard role for a bar or a dependency line), documented keyboard commands (for example gantt-a11y's Shift+D), and documented keyboard paths for the three edits, each with its sources. Keys are taken only from official documentation; typing into a focused text field or list box is ordinary keyboard use and needs no source.
Public demos are loaded once per run, like a visitor would: no login, no cookie or consent dialogs accepted, no protections bypassed, a pause between key presses. The tool is debugged on the local demos and on two local test pages (fixtures/), not on public pages.
Information checks: three levels
The checks for name, dates, dependencies, level and position look on three levels and report all three:
- a) tree: the information is somewhere in the accessibility tree (a task row's name, link elements' names, ARIA attributes on rows), read before any key press;
- b) focus: it is in the accessible name or description of an element that keyboard focus lands on: the task row (or cell) reached with Tab and the arrow keys, and the cells the Right arrow reaches in the same row; or, for dependencies, link elements that can take focus;
- c) command: it appears after a documented keyboard command (a live region, an alert or status, or a change of the focused element's name).
The summary is pass for b or c, present but not reachable for a alone, fail for none.
Accessible names, descriptions, roles and levels come from Chromium's accessibility tree (DevTools Protocol, Accessibility.getPartialAXTree). When the focused element uses aria-activedescendant, the element it points to counts as focused.
The checks
1. Keyboard focus reaches a task row
How. From the top of the page, press Tab up to 120 times (300 on public pages). When focus is inside the chart but not on a row, press Down up to three times. Pass when focus is on a task row or inside one. Pass / fail. Focus reached a task row / did not. Does not prove that the row is announced usefully, that the rest of the chart can be reached, or that the Tab order is sensible.
2. Keyboard focus reaches a task bar
How. Run last: press Tab up to 40 more times, then Right up to four times. Also counts bars with a tabindex. Pass / fail. Focus landed on a bar / did not. Does not prove that a bar can be operated from the keyboard. A fail is not necessarily a problem when everything a bar shows is also available from its row. The result depends on where focus was before, which the earlier checks change.
3. A task's name is available (three levels)
b) The focused element's accessible name or description is not empty. Does not prove that the name is the task's name rather than another cell's text, or that it is understandable.
4. A task's dates are available (three levels)
b) A date appears in the name or description of the focused element or of a cell the Right arrow reaches in the same row (the evidence says which; a date on another cell is heard only after moving to it). Does not prove that the dates are the right ones, or that they are spoken as dates.
5. Dependencies are available as text (three levels)
a) Names of up to five link elements. b) The focused element or a cell in its row: a cell under a "Predecessors", "Successors" or "Dependencies" column with text, or text with a dependency word and another task's name; or link elements that can take focus. c) The profile's command for dependencies. Does not prove that the direction (which task depends on which) is clear, or that the list is complete.
6. Dependencies name the tasks
How. Pass when dependency text reachable from the keyboard (b or c of check 5) contains another task's name; present but not reachable when only the tree's text does; not applicable when there is no dependency text. Does not prove that the names are unambiguous.
7. Level in the hierarchy is available (three levels)
a) A task row's level in the tree. b) The level of the row that holds focus. c) The profile's "where am I" command mentions a level. Not applicable to a flat list of options. Does not prove that the screen reader announces the level, or that parent and child are clear.
8. Position in the list is available (three levels)
a) Any task row with aria-posinset and aria-setsize, or aria-rowindex. b) The row holding focus has aria-posinset and aria-setsize, or aria-rowindex with aria-rowcount on its grid. c) The "where am I" command gives "n of m". Does not prove a problem when it fails: without these, a screen reader counts the rows in the DOM, which is right while every row is rendered and none is filtered out.
9. The page has a live region
How. Counts elements with aria-live (not "off") or the roles status, log and alert. Does not prove that anything useful is ever announced through it.
10. The result of an edit reaches the user
How. After the first edit that worked (check 11, 12 or 13, in that order), any of: new text in a live region; new text in a role alert or status; a change of the focused element's accessible name while focus stays on the same row and cell (the name before is taken after moving to the cell). The evidence names the way that worked. Pass / fail. One of the ways worked / none did. Not applicable when no edit worked; no documented keyboard path when there is none for any edit. Does not prove that the result is spoken, spoken in full, or understandable; a changed name is heard only when the screen reader reads the element again (screen readers usually do when it is re-rendered with focus).
11, 12. Dates and duration can be changed from the keyboard
How. Follow the profile's documented path (for example: arrow keys to the Start cell, F2, type the date a day later in the same format, F2), then compare the bars: a moved bar for dates, a wider or narrower bar for duration. Pass / fail / no documented keyboard path as defined above. A step that cannot be taken (no such column in the demo, a field not reached) is a fail with the reason; an unrecognised date format is "could not determine". Does not prove that the right task changed, that the change is what the user intended, or that an undocumented path does not exist.
13. A link can be created from the keyboard
How. Follow the documented path and compare the number of link elements. Does not prove that the link has the intended type or direction.
14. Focus returns to the task after closing the form
How. Press Enter on the task row. If a new dialog appears (role="dialog", aria-modal, or dhtmlx's form) that was not there before, press Escape once and check that focus is back on the same row. Pass / fail / not applicable (no new dialog). Does not prove that the form itself is accessible, or that saving behaves like cancelling. On grids with cell editing, Enter may open a cell editor, which this check counts as a form; editors that need Escape twice then fail here.
15. The page tells the user which keys exist
How. Any of: the profile's documented help command gives text; elements with aria-keyshortcuts; a description (aria-describedby) of the chart or grid that mentions keys; text on the page outside the chart that mentions pressing keys. The evidence says which, and marks page text as written by the page's authors. Does not prove that the help is complete or correct, or that a user would find it. Text written for a demo page is not part of the product.
16. The extension's keys do not overlap the library's documented keys
How. Compares gantt-a11y's default keys (DEFAULT_KEYS in src/core/engine.js) with the keys the library documents (the list and its sources are in the profile, libraryKeys), after putting both in one form (modifiers in one order, "esc" as "escape"). On a page with the extension it also counts how many of the extension's keys are bound on task rows (dhtmlx-gantt's public getShortcutHandler). Pass / fail. No key in common / the keys in common are listed. Not applicable on pages without a gantt-a11y adapter; the evidence still lists which keys would overlap, as information for a future adapter. Does not prove that the keys are free in the browser, the operating system or a screen reader (see docs/KEYS.md), that an application has not added keys of its own, or that keys the documentation does not mention are free.
Threats to validity
- Demos are not products. Public demos show one configuration chosen by the vendor (which columns, whether editing is on, which features are enabled). A product built with the same library may do better or worse. Our own demos are configured by the author of the extension.
- An automated browser is not a screen reader. The audit reads Chromium's accessibility tree and presses keys; screen readers build their own model from the platform API, have their own navigation modes and may intercept keys. Safari and Firefox build their trees differently.
- Keyboard profiles may be incomplete. Keys are taken from the documentation pages listed in each profile; a library may support more than its documentation says, or document keys on pages the audit did not read. "No documented keyboard path" is a statement about the documentation read, not about the product.
- The audit's own heuristics. Selectors for rows, bars and links; the date pattern; matching field labels; counting a cell editor as a form; the order of checks (check 2 runs last and starts from wherever focus is). The evidence is kept so that each result can be reviewed; known doubts about a run are written next to it (
results/<date>-v2-notes.md). - One run on one date. Public demos change without notice; network timing and page load differ between runs. Each public page was loaded once for the version 2 results.
- No colour, zoom, motion or pointer checks. Only keyboard behaviour and the accessibility tree.