[bug?] Is the format of tables in the documentation broken in PG 13?
Hello,
The tables for pg_stat_ views in the following page, starting from Table 27.3, have only one column in PG 13. They had 3 columns in PG 12 and earlier.
https://www.postgresql.org/docs/13/monitoring-stats.html
Is this intentional? It has become a bit unfriendly to read for me, a visually impaired user who uses screen reader software.
The tables for functions in Chapter 9 are similar.
Regards
Takayuki Tsunakawa
On 15 Jun 2020, at 09:49, tsunakawa.takay@fujitsu.com wrote:
Is this intentional?
Yes, this was a deliberate change made to be able to fit more expansive
descriptions of columns etc.
It has become a bit unfriendly to read for me, a visually impaired user who uses screen reader software.
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?
cheers ./daniel
From: Daniel Gustafsson <daniel@yesql.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
"tsunakawa.takay@fujitsu.com" <tsunakawa.takay@fujitsu.com> writes:
From: Daniel Gustafsson <daniel@yesql.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