Re: Adding visual clues that accesskey exists

2023-01-20 Thread Corey Huinker
On Fri, Jan 20, 2023 at 6:07 AM Peter Eisentraut < peter.eisentr...@enterprisedb.com> wrote: > On 18.01.23 22:49, Corey Huinker wrote: > > Attached is a patch to add the nav- tags to the header (could just as > > easily have done the footer) for up/down/left/right and the javascript > > to find th

Re: Adding visual clues that accesskey exists

2023-01-20 Thread Peter Eisentraut
On 18.01.23 22:49, Corey Huinker wrote: Attached is a patch to add the nav- tags to the header (could just as easily have done the footer) for up/down/left/right and the javascript to find those ids and simulate a click. I've tested this on chrome (where accesskeys work with alt+ ) and firefox

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

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