> For the complete documentation index, see [llms.txt](https://ccsdrupalguide.uoguelph.ca/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ccsdrupalguide.uoguelph.ca/accessiblecontentguide/tables.md).

# Tables

Tables are useful for organizing information into a grid of cells. To make sure a table is accessible, it is important to keep it fairly simple. If your table is complex, with split or merged cells, consider dividing the information into multiple tables if possible. In order to assess complexity, imagine hearing the information over the phone. Can the it be understood without a visual aid?

**/! Strong Recomendation**: The AODA Team strongly suggests that tables are purely used for tabluar data and not for layout. If you require assistance in terms of layout, please speak with your Web Manager/Site Owner for assistance.

## Using Tables in Drupal

1. Start by selecting the table button in the Drupal text editor.

    ![Highlight of the table button in the Drupal text editor](/files/-Ldu94zgJ0MgJTbhBgTd)
2. The following dialog box will appear. Enter the appropriate number of rows and columns.

    ![Table properties dialog box](/files/-Ldu94zjwClrT0Tb8Zjc)
3. Using the drop-down `Headers` menu, select your preference for column and row headers. This will bold the text in the selected cells.
4. Add a caption to the table. This will serve as its title. 
5. Add a summary if appropriate. This is useful if the table is meant to convey certain findings that can be briefly summarized in text.
6. Click `OK`. The empty cells will appear in the Drupal text editor for you to fill in:

    ![Empty table cells](/files/-Ldu94zlPi7tADsAjYht)
7. Click `Save`.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://ccsdrupalguide.uoguelph.ca/accessiblecontentguide/tables.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.