Re: [bug?] Is the format of tables in the documentation broken in PG 13?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "tsunakawa(dot)takay(at)fujitsu(dot)com" <tsunakawa(dot)takay(at)fujitsu(dot)com>
Cc: "'Daniel Gustafsson'" <daniel(at)yesql(dot)se>, 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 01:00:13
Message-ID: 1267581.1592269213@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"tsunakawa(dot)takay(at)fujitsu(dot)com" <tsunakawa(dot)takay(at)fujitsu(dot)com> writes:
> From: Daniel Gustafsson <daniel(at)yesql(dot)se>
>> 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.

Please do. I looked at the referenced link a bit, but it wasn't clear
to me that they suggested anything useful to do :-(.

It'd probably be best to discuss this on the pgsql-docs list.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2020-06-16 01:02:21 Re: 回复:回复:how to create index concurrently on partitioned table
Previous Message Bruce Momjian 2020-06-16 00:59:56 Re: pg_upgrade fails if vacuum_defer_cleanup_age > 0