Question
Minitab worksheet export to Microsoft Excel: preserved semantics or data only
Mira Nova
0 reputation · 01 Dec 2023, 16:46 UTC
40.7K views
Loading…
0 reputation · 01 Dec 2023, 16:46 UTC
The goal is to decide whether Minitab's export to Microsoft Excel is an accessible reporting channel or only a raw data-exchange step. The integration boundary is between Minitab worksheets, graphs, and output panes and the resulting Excel workbook.
Minitab can import tabular data and return worksheet values to Excel, but whether that return path preserves semantics for assistive technology is unresolved. Column headers, data types, sheet names, missing-value markers, and logical reading order may survive as visible formatting yet remain unavailable to a screen reader. Graph meaning, labels, and explanatory context may not carry over at all. Results can also vary by Minitab release, operating system, and installed assistive software, so the installed release's supported-format and accessibility documentation should be reviewed before the behavior is treated as a requirement.
Does the exported workbook retain row and column headers, sheet names, and reading order announced by a screen reader? Should the accessible deliverable be the Excel workbook, a companion report, or Minitab's in-product output? Which export settings control semantic preservation rather than visible formatting only?
35775 reputation · 02 Dec 2023, 03:58 UTC
Minitab's export to Excel keeps the visible layout — column headers, sheet names and the order of rows and columns appear as normal cells in the workbook — but it does not embed accessibility metadata that screen readers can interpret reliably. Consequently, a screen reader may announce the header text but will not always convey the intended meaning, data type, or missing‑value markers.
Because Minitab writes a standard spreadsheet without adding ARIA‑like properties, the semantic relationship between rows, columns and data types is lost. Visual formatting survives, but a screen reader that depends on programmatic headers may treat the header cell as ordinary text, leading to ambiguous or incorrect announcements.
The key export setting that affects semantics is the “Preserve data types” option (if available) and the choice between “Export worksheet” and “Export graph data”. Selecting the former may embed type information, but full semantic accessibility still depends on the assistive software’s interpretation of the resulting .xlsx.
If reliable accessibility is required, treat the Excel workbook as a supplementary deliverable and provide a separate accessible report (e.g., a PDF with proper heading structure) or keep the analysis in Minitab’s built‑in output pane.
Please specify which Minitab version and operating system you are using, and which screen‑reader application you plan to test with, because export behavior can differ across releases and platforms.
Use comments to ask for clarification. Post a solution as an answer.
35,775 reputation · 01 Dec 2023, 18:55 UTC
The existing answer correctly notes that Minitab writes visible headers without accessibility metadata. A quick way to confirm the gap and create a screen-reader-friendly structure is to open the exported .xlsx, select the data range, and press Ctrl+T to convert it to an Excel Table — this adds the <table> element, header-row repetition, and auto-filter markers that NVDA and JAWS recognize. You can also rename the file to .zip and inspect xl/worksheets/sheet1.xml; absence of <tableParts> and <autoFilter> confirms Minitab emitted no structural markup. For missing values, Minitab’s internal * becomes a literal asterisk — run a find/replace to NA() or true blanks before finalizing. Graphs and session-window output remain separate; use Copy > Copy as Text for narrative and embed manually with alt text.
minitab