Re: Adding visual clues that accesskey exists

2023-01-18 Thread Peter Eisentraut
On 13.01.23 23:07, Corey Huinker wrote: 1. Add static hints to each link, so "Next" becomes "Next [n]". Fairly simple, but visually clumsy, and it might not actually clue the user that they need to hit ALT+n, not just "n". This chrome extension is an example of how it might look https://chrome

broken link

2023-01-18 Thread PG Doc comments form
The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/15/index.html Description: The FAQ page https://wiki.postgresql.org/wiki/FAQ has a broken link at the very bottom: "Bruce Momjian's presentation" http://momjian.us/main/presentations/features

Re: broken link

2023-01-18 Thread Bruce Momjian
On Wed, Jan 18, 2023 at 06:17:27PM +, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/15/index.html > Description: > > The FAQ page https://wiki.postgresql.org/wiki/FAQ has a broken link at the > very

Re: Adding visual clues that accesskey exists

2023-01-18 Thread Corey Huinker
> > I agree that hot key discoverability could be better, but I don't think > this is an issue in the PostgreSQL documentation; it's something the > browser should handle. The job of the HTML markup is to declare the key > -- then it's up to the browser how to present it. Otherwise, every > singl