Dealing with complex tables

[declares]

Would like to hear from other departments/agencies on how they deal with complex tables, i.e., col/row spans, multi cells, etc. Wanting to discuss ways to simplify in an effective manner.

[thomasgohard]

I've often found that people try to put too much into a single table. So the first question I would ask is: Can I split this complex table into multiple simpler tables?

It's sometimes better to split the information into multiple simple tables instead of putting it in a single massive, complex table. Not only does it make the tables easier to code, it also makes it easier to read the tables. Large, complex tables are also often hard to fit into the page layout, especially on small-screen devices.

[duboisp]

What is the use case, the tabular context?

By tabular context, I am looking to find the following information:

• The reasoning that justify the use of a table. Example: an invoice table, a financial table, create a bar charts, ...
• The complex tabular HTML code.
• A visual (screen shoot) of what the complex table look like.

That would help, this discussion, to find multiple ways on how to simplify complex table in an effective manner.

:smiley:

---

FYI - Here some documentation

12 techniques about how to structure a complex table Enhance the accessibility of a complex table by using this HTML Table Validator tools Case Studies 1 Case Studies 2 - Nutrition Facts table Case Studies 3 - Ottawa Senators vs. Buffalo Sabres - Game ID # 270519002 Zebra Stripping - Invoice Table

[mankev]

The only real solution is to break out a complex table into one or more basic tables.

Justification:

• The time and effort used to mark up a complex table is excessive.
• Complex tables require advanced skills, simplified tables can be marked-up by anyone.
• The end result while technically meeting the requirements is not very usable from a screen reader's perspective (too many dimensions attached to data cells).
• A series of basic tables is usually more understandable by all.

[thomasgohard]

@mankev Great summary of the reasons for breaking up complex tables into multiple simpler tables. :+1:

[declares]

Thanks very much – exactly my thoughts but was wondering if there was something I may have been missing.

Have a great long weekend everyone!!

[Pacoup]

We've come to use strictly scope (CIHR). We find it easier than headers and IDs when manually coding tables, and it can handle quite a few complexities: 4.9 Tabular data — HTML Standard

[duboisp]

@declares can you post some complex table example (directly or by providing link to a gist) from your departement?

@Pacoup did you try the HTML Table Validator to set the headers/ids on complex table?

[LaurentGoderre]

Can we close this issue?

[declares]

Yes please

Sandy Declare

Web Communications Officer/Agente de communication web

Web, Publishing and Creative Services/Web, publication et services créatifs

Communications Branch/Direction générale des communications

Fontaine Building/Édifice fontaine

7th Floor, Room 749/ 7e étage, salle 749

200 Sacré-coeur, Gatineau (QC) K1A 0H3

sandy.declare@ec.gc.ca mailto:sandy.declare@ec.gc.ca

819-997-2756

From: Laurent Goderre [mailto:notifications@github.com] Sent: June 17, 2014 11:42 AM To: wet-boew/wet-boew Cc: Declare,Sandy [NCR] Subject: Re: [wet-boew] Dealing with complex tables (#2788)

Can we close this issue?

— Reply to this email directly or view it on GitHub https://github.com/wet-boew/wet-boew/issues/2788#issuecomment-46324683 .