imbahub
Menu +
US
Talk to us
IMBAHUB / Websites

Keep table relationships useful when the whole grid is not visible.

ImbaHub can develop data tables for product specifications, service comparisons and other genuine tabular content. The project connects the source, HTML structure and mobile presentation so values retain their correct headers and units.

Four relationships the component must preserve
  1. Row

    Which object does the value describe?

  2. Column

    Which property is represented?

  3. Unit

    How should the number be interpreted?

  4. Exception

    What does a missing value or footnote mean?

Visual order cannot replace explicit data structure.

An empty weight is imported as zero. Just a layout detail?

No. It changes the meaning. Correct the data model and tests before accepting the table.

Start with the comparison the reader needs

Select real data and the question it should answer. Define row identifiers, column names, units and source. A list may be better if the content lacks a tabular relationship.

A fictional materials supplier compares dimensions, weight and intended use. A missing weight is not zero. Decide how unknown values, ranges and footnotes appear before building the component.

Model headers alongside values

Simple tables can use clear row and column headers. More complex headers need explicit associations that follow the data structure. Color and position alone do not communicate those relationships.

We can build a bounded component and editing format that preserve meaning. Sorting and filtering are included only when scoped and tested; semantic HTML does not automatically provide them.

ElementDecisionTest
IdentityStable row and useful nameRecognize the correct product after changes
HeaderRelation to each valueReview programmatic association
UnitClear meaning and formatWeight is not confused with dimensions
Missing valueDistinguish unknown from zeroNo invented comparison
MobileReadable route through dataColumns reachable without page overflow

Test narrow views without losing context

A wide table may need a bounded scrolling area with a clear route to remaining data. An alternative mobile layout must retain value labels rather than merely stack cells visually.

Test keyboard, text zoom and representative screen-reader cases within agreed scope. Automated checks supplement manual relationship tests. A tool finding no errors does not establish that every comparison is understandable.

Hand over the component and editing rules

A first delivery can cover one table type, one dataset and selected languages. Documentation covers fields, missing data, footnotes, local number formats and checks after editing. Imports, exports and advanced data grids are scoped separately.

Pricing reflects data quality, complexity and existing technology. The result is a tested component with defined ownership, rather than a certificate for whole-site accessibility or legal compliance.

Sources and further reading

Questions, answered

Must every table be interactive?

No. Ordinary HTML can suit a reading comparison. Add sorting or filters only when the task warrants them.

Can a picture replace the table?

It loses useful data relationships and readable text values. Important tabular information should remain understandable HTML.

IMBAHUB

Let’s plan your website

Bring a real table and describe the comparison customers need to make on mobile.

Talk to us
Existing English product interface with fictional demonstration content; reused for the US website.

Existing English product interface with fictional demonstration content; reused for the US website.