| From: | "tsunakawa(dot)takay(at)fujitsu(dot)com" <tsunakawa(dot)takay(at)fujitsu(dot)com> |
|---|---|
| To: | 'Daniel Gustafsson' <daniel(at)yesql(dot)se> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | RE: [bug?] Is the format of tables in the documentation broken in PG 13? |
| Date: | 2020-06-16 00:21:52 |
| Message-ID: | TYAPR01MB299071A031D0D04E867CEAB7FE9D0@TYAPR01MB2990.jpnprd01.prod.outlook.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
From: Daniel Gustafsson <daniel(at)yesql(dot)se>
> Yes, this was a deliberate change made to be able to fit more expansive
> descriptions of columns etc.
Thanks for your quick response and information. I'm relieved to know that it was not broken.
> That's less good. The W3C Web Accessibility Initiative has guidance for
> multi-
> level header tables which might be useful here.
>
> https://www.w3.org/WAI/tutorials/tables/multi-level/
>
> Maybe if we use the id and headers attributes we can give screen readers
> enough
> clues to make sense of the information?
Hm, I think I'll look into this.
Regards
Takayuki Tsunakawa
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2020-06-16 00:23:42 | Re: language cleanups in code and docs |
| Previous Message | Tom Lane | 2020-06-15 23:54:25 | Re: language cleanups in code and docs |