Example Consultation Document
Chapter 4 - Tables
Data tables vs Layout tables
Tables are often used in documents in two ways:
- To present data in an easily readable format
- For layout puposes for example highlighting text
When showing documents online, layout tables should not be used as this is not good practice for accessibility. Data tables can be left in their current format, however layout tables should be removed and the text presented in a "flattened" format. Below is an example of a table used for layout and how this can easliy be presented in an accessible text format:
A layout table example
A |
High rate of decline - this scenario assumes an annual decline in the amount of waste per household of 1.48%. This reflects the historic trend seen between 2007 and 2019. However, this timeframe includes a large drop in household waste arisings between 2007 and 2008 which is likely to be due to the recession and may not be representative of longer-term trends. |
B |
Low rate of decline - this scenario assumes an annual decline in the amount of waste per household of 0.58%. This reflects the historic trend seen between 2008 and 2019 and therefore excludes the possible recessionary impact between 2007 and 2008. This scenario would result in an increase of less than 10,000 tonnes per annum of LACW by 2038. Although this scenario assumes a decline in the amount of waste per household, the increased number of households by 2038 would result in overall growth. |
C |
No change - this scenario assumes 0% change in the amount of waste produced per household going forward based on the most recent 2019 figures. This scenario would result in increase of around 80,000 tonnes per annum of LACW by 2038. Although this scenario assumes no change in the amount of waste per household, the increased number of households by 2038 would result in overall growth. |
Data from table displayed in a non-tabular format:
A - High rate of decline
This scenario assumes an annual decline in the amount of waste per household of 1.48%. This reflects the historic trend seen between 2007 and 2019. However, this timeframe includes a large drop in household waste arisings between 2007 and 2008 which is likely to be due to the recession and may not be representative of longer-term trends.
B - Low rate of decline
This scenario assumes an annual decline in the amount of waste per household of 0.58%. This reflects the historic trend seen between 2008 and 2019 and therefore excludes the possible recessionary impact between 2007 and 2008. This scenario would result in an increase of less than 10,000 tonnes per annum of LACW by 2038. Although this scenario assumes a decline in the amount of waste per household, the increased number of households by 2038 would result in overall growth.
C - No change
This scenario assumes 0% change in the amount of waste produced per household going forward based on the most recent 2019 figures. This scenario would result in increase of around 80,000 tonnes per annum of LACW by 2038. Although this scenario assumes no change in the amount of waste per household, the increased number of households by 2038 would result in overall growth.
Wide tables
When using data tables online, if the table is very wide problems can arise when viewing the data on smaller screens (such as mobiles). Even on desktops some tables are just too wide to be viewed on the screen. If possible very wide tables should be avoided or reduced to fit on screens - but if there is no alternative scrollbars can be added so all the data can be viewed by scrolling across the screen. This keeps the data visible and the table intact. A similar method to scrolling across the whole table is to fix a column and allow the other columns to scroll. Finally, if neither of the other solutions is suitable, then for small screens the table can be transformed to a vertical structure. The examples below show each of these methods in action.
Here is the original table which is too wide to be visible on the screen.
Original wide table
Site |
2018 |
2019 |
2020 |
2021 |
2022 |
2023 |
2024 |
2025 |
2026 |
2027 |
2028 |
2029 |
2030 |
2031 |
2032 |
2033 |
2034 |
2035 |
2036 |
Site A1234 |
3012345 |
301211 |
3076 |
307889 |
30** |
305443 |
309987 |
30123 |
305443 |
30123 |
3054 |
3078960 |
300097 |
30 |
305545 |
30 |
30 |
30 |
30 |
Site B1234 |
140677 |
1405678 |
1408765 |
140763 |
1406511 |
1406700 |
1409981 |
1408976 |
140333 |
140 |
140 |
140 |
140* |
||||||
Site C1234 |
140876655 |
140 |
14077666 |
140 |
140 |
1406655 |
|||||||||||||
Site D1234 |
120343 |
1206544 |
120333 |
127660 |
12087777 |
||||||||||||||
Site E1234 |
1203232 |
120986 |
1202333 |
1206622 |
1208766 |
120 |
1207654 |
1208789 |
120 |
12077 |
120 |
1205433 |
120 |
120 |
For the first example a scrollbar is added to the bottom of the table to allow users to scroll and see the rest of the data.
Example 1 - a scrollbar
Site |
2018 |
2019 |
2020 |
2021 |
2022 |
2023 |
2024 |
2025 |
2026 |
2027 |
2028 |
2029 |
2030 |
2031 |
2032 |
2033 |
2034 |
2035 |
2036 |
Site A1234 |
3012345 |
301211 |
3076 |
307889 |
30** |
305443 |
309987 |
30123 |
305443 |
30123 |
3054 |
3078960 |
300097 |
30 |
305545 |
30 |
30 |
30 |
30 |
Site B1234 |
140677 |
1405678 |
1408765 |
140763 |
1406511 |
1406700 |
1409981 |
1408976 |
140333 |
140 |
140 |
140 |
140* |
||||||
Site C1234 |
140876655 |
140 |
14077666 |
140 |
140 |
1406655 |
|||||||||||||
Site D1234 |
120343 |
1206544 |
120333 |
127660 |
12087777 |
||||||||||||||
Site E1234 |
1203232 |
120986 |
1202333 |
1206622 |
1208766 |
120 |
1207654 |
1208789 |
120 |
12077 |
120 |
1205433 |
120 |
120 |
In this second example, a scrollbar is added to the bottom of the table again but in this case the first column is fixed so the user can see the site name as they scroll through the data.
Example 2 - fixed column and scrollbar
Site |
2018 |
2019 |
2020 |
2021 |
2022 |
2023 |
2024 |
2025 |
2026 |
2027 |
2028 |
2029 |
2030 |
2031 |
2032 |
2033 |
2034 |
2035 |
2036 |
Site A1234 |
3012345 |
301211 |
3076 |
307889 |
30** |
305443 |
309987 |
30123 |
305443 |
30123 |
3054 |
3078960 |
300097 |
30 |
305545 |
30 |
30 |
30 |
30 |
Site B1234 |
140677 |
1405678 |
1408765 |
140763 |
1406511 |
1406700 |
1409981 |
1408976 |
140333 |
140 |
140 |
140 |
140* |
||||||
Site C1234 |
140876655 |
140 |
14077666 |
140 |
140 |
1406655 |
|||||||||||||
Site D1234 |
120343 |
1206544 |
120333 |
127660 |
12087777 |
||||||||||||||
Site E1234 |
1203232 |
120986 |
1202333 |
1206622 |
1208766 |
120 |
1207654 |
1208789 |
120 |
12077 |
120 |
1205433 |
120 |
120 |
The final example, a table is too wide to fit on a small screen (such as a mobile). Some tables can be modified to display in a vertical structure which removes the need for scrolling altogether. Not all tables will suit this method - but it can be useful for certain cases.
Example 3 - Vertical structure:
Original table
Area |
A. LDP Alloc |
B. Complete |
C. Completed but not forming part of allocated figure. |
D. Committed |
E. Residual Supply (A-B-D=E) |
---|---|---|---|---|---|
PC1 - Carmarthen |
19.14 |
0 |
0 |
2.18 |
16.96 |
PC2 - Llanelli |
15.77 |
0 |
0 |
0 |
15.77 |
PC3 – Ammanford/ Cross Hands |
35.48 |
0 |
0 |
10.39 |
25.09 |
Service Centres |
7.54 |
0 |
0 |
3.93 |
3.61 |
Sustainable Villages |
0 |
0 |
0 |
0 |
0 |
Rural Villages |
0 |
0 |
0 |
0 |
0 |
Total |
77.93 |
0 |
0 |
16.50 |
61.43 |
This is how the table would be presented on a small screen such as a mobile - some of the columns are cut off. In this case a scrollbar could be added (as in the examples above) or the table could be displayed in a vertical format. This is only really suitable for short tables with few columns.
See below for the same table in a vertical structure:
A. LDP Alloc |
B. Complete |
C. Completed but not forming part of allocated figure. |
D. Committed |
E. Residual Supply (A-B-D=E) |
|
---|---|---|---|---|---|
PC1 - Carmarthen |
19.14 |
0 |
0 |
2.18 |
16.96 |
PC2 - Llanelli |
15.77 |
0 |
0 |
0 |
15.77 |
PC3 – Ammanford/ Cross Hands |
35.48 |
0 |
0 |
10.39 |
25.09 |
Service Centres |
7.54 |
0 |
0 |
3.93 |
3.61 |
Sustainable Villages |
0 |
0 |
0 |
0 |
0 |
Rural Villages |
0 |
0 |
0 |
0 |
0 |
Total |
77.93 |
0 |
0 |
16.50 |
61.43 |
Any or all of the above methods for table display can be used in a document depending on the size of table and type of data. However, as mentioned previously, it is best to check if tables are really necessary and move data into a flattened structure if possible to help with accessibility.