Below is a table that shows savings and checking accounts that were forcast compared to actual amounts for years 2012 and 2013. Table headers are in the first three rows.
2012 | 2013 | |||||||
---|---|---|---|---|---|---|---|---|
Forcast | Actual | Forcast | Actual | |||||
Savings | Checking | Savings | Checking | Savings | Checking | Savings | Checking | |
January | $100 | 200 | 400 | 340 | 230 | 765 | 876 | 343 |
February | $80 | 780 | 787 | 453 | 245 | 454 | 454 | 243 |
This is a text only, If I was coaching someone, I will tell them to split this table up into two saparate tables. But this is to see if actually works.
All three layers of column headers read properly in JAWS 13, and 14, and NVDA 2012, and in NVDA. Both in IE 10 and FF 22
Is it a failure of WCAG to not mark this up with headers and ids, if Assistive Technology has overcome the prooblems with this type of complex table. I would say no. It is accessibility supported.