HTML from Word doc - good for T&Cs | UniSC | University of the Sunshine Coast, Queensland, Australia

Accessibility links

HTML from Word doc - good for T&Cs

To use AI chat to create a properly structured, accessible HTML table from a word doc

  • Click the button to copy the HTML table prompt to your clipboard.
  • Paste into Copilot chat add a One Drive link to the Word doc send the prompt.
  • Copilot will return structured HTML

You can copy the prompt from here at any time.

This page is hidden from search, so best to bookmark it for easy access.

# Role

Word document to HTML conversion specialist.


# Task

Convert the content from the supplied Word document into clean, structured HTML.

The document contains terms and conditions and may include:

* Automatically numbered lists created using Microsoft Word
* Numbered lists with multiple levels
* Lettered lists, such as a), b), c) or A, B, C
* Roman numeral lists, such as i), ii), iii) or I, II, III
* Bulleted lists
* Nested lists
* Paragraphs and headings
* Lists that continue across multiple paragraphs or sections

Your task is to preserve the **exact content and list structure** of the Word document while converting it to semantic HTML.

## Content preservation

**Do not change the content in any way.**

This includes:

* Do not rewrite, rephrase or simplify text
* Do not correct spelling, grammar or punctuation
* Do not add or remove words
* Do not change capitalisation
* Do not change numbers
* Do not change dates
* Do not change names, titles or terminology
* Do not add content that is not in the document
* Do not remove content that is in the document
* Do not combine or split content unless required to accurately represent the existing Word structure in HTML

The visible text must remain exactly as supplied.


## List structure

Preserve the hierarchy and numbering of lists from the Word document.

Use semantic HTML list elements:

* `<ol>` for ordered/numbered lists
* `<ul>` for unordered/bulleted lists
* `<li>` for each list item

Where the Word document uses a specific numbering style, preserve it using the appropriate HTML list structure and attributes.

Examples include:

* 1, 2, 3 → `<ol>`
* a, b, c → `<ol type="a">`
* A, B, C → `<ol type="A">`
* i, ii, iii → `<ol type="i">`
* I, II, III → `<ol type="I">`

Preserve nested list levels by nesting `<ol>` or `<ul>` elements inside the relevant `<li>`.

Do not manually type list numbers, letters or Roman numerals into the text when the numbering can be represented by HTML.

For example, do not convert:

`1. First item`

into:

`<p>1. First item</p>`

Instead, use:

`<ol><li>First item</li></ol>`

Similarly, do not treat automatically generated Word numbering as ordinary text. Determine the underlying list structure and represent it using semantic HTML.

## Mixed and nested lists

If a list contains nested lists, preserve the exact hierarchy and marker style.

For example, if the source structure is:

1. Main item
   a. Sub-item
   b. Sub-item
2. Main item

the HTML should represent the hierarchy using nested `<ol>` elements and the appropriate numbering type.

Do not flatten nested lists.

If numbering restarts at a particular point in the source document, preserve that numbering behaviour where possible using appropriate HTML attributes such as `start`.

## Paragraphs and headings

Preserve paragraphs using `<p>` elements.

Where the Word document clearly identifies headings, use appropriate semantic heading elements such as `<h2>`, `<h3>` or `<h4>`.

Do not invent headings or change ordinary paragraphs into headings.

## Formatting

Preserve meaningful structural formatting where it exists, but do not introduce unnecessary styling.

Use semantic HTML rather than inline CSS wherever possible.

Do not add:

* CSS
* JavaScript
* classes
* IDs
* unnecessary `<div>` elements
* inline styles

unless they are necessary to accurately preserve the supplied structure.

## Output

Return **HTML code only**.

The result must be provided as actual code that I can copy and paste into a CMS.

**Do not provide a rendered preview of the HTML.**

**Do not describe what the HTML will look like.**

**Do not provide an explanation of the changes.**

**Do not provide accessibility commentary.**

**Do not provide a summary.**

**Do not provide Markdown outside the code output.**

The returned result must use the AI interface's normal **copy code** functionality so the HTML can be copied directly.

The output must be ready to paste directly into the CMS.

## Accuracy priority

The priority order is:

1. Preserve all original content exactly
2. Preserve the original list hierarchy
3. Preserve the original numbering, lettering, Roman numeral and bullet styles
4. Produce valid, semantic HTML
5. Avoid unnecessary HTML or formatting

Before returning the result, check that:

* No content has been added
* No content has been removed
* No content has been rewritten
* All list items are present
* All nested lists retain their original hierarchy
* Numbering and marker styles are preserved
* Automatically generated Word numbering has been converted to semantic HTML rather than copied as plain text
* The HTML is valid and ready to paste into the CMS

Return only the HTML code block.