- From: Harry Loots <harry.loots@ieee.org>
- Date: Tue, 27 Apr 2021 11:32:09 +0200
- To: Steven Mouret <steven.mouret@gmail.com>
- Cc: "Patrick H. Lauke" <redux@splintered.co.uk>, W3C WAI ig <w3c-wai-ig@w3.org>
- Message-ID: <CA++-QFcS=uWf7xtgfRu3kq7=xxVCkFgqzRNnme-ns8j3Urq3BA@mail.gmail.com>
Hi Steven The GDPR banner is intrusive by design. It should not be confused with a simple cookie banner advising users that session cookies are collected to enable them to use the site. For a simple session cookie, the banner is nice to have, but not required, as no personal data is collected. For the banner, where compliance is sought under GDPR - i.e., personal data is collected, the user should be forced to explicitly accept the collection of cookies before continuing to use the site. In this case, the user must click okay or whatever, which enables one to hide the banner. Kindest regards Harry On Tue, 27 Apr 2021, 10:38 Steven Mouret, <steven.mouret@gmail.com> wrote: > Hello Harry, > > Not always, especially when the user has not made a choice. > These banners are ergonomically a disaster in terms of rendering, they are > very intrusive. I'm looking for a solution to respect both all users with a > good ergonomics, the WCAG and of course the GDPR. > But I'm going off topic ;) > > Thank you > > -- > Steven Mouret > > > Le mar. 27 avr. 2021 à 10:20, Harry Loots <harry.loots@ieee.org> a écrit : > >> It's worth bearing in mind that these banners are designed to 'disappear' >> once the user accepts the conditions. I.e., once clicked on it should no >> longer be 'visible' to the user. >> >> Kind regards >> Harry >> >> >> On Tue, 27 Apr 2021 at 10:11, Steven Mouret <steven.mouret@gmail.com> >> wrote: >> >>> Ok, I understand, thank you. >>> >>> -- >>> Steven Mouret >>> >>> >>> Le mar. 27 avr. 2021 à 09:58, Patrick H. Lauke <redux@splintered.co.uk> >>> a écrit : >>> >>>> On 27/04/2021 08:38, Steven Mouret wrote: >>>> > Hello Patrick thank you for your response. About the compliance it's >>>> ok. >>>> > About the keyboard users, are they not hampered in their navigation? >>>> I >>>> > am thinking in particular of the visually impaired person using a >>>> screen >>>> > magnifier. >>>> > Wouldn't it be better to position the banner at the top of the page >>>> and >>>> > make it easier to navigate? >>>> >>>> If the user is navigating using the keyboard, their magnified view wil >>>> lfollow their keyboard focus, so assuming the banner is visually at the >>>> bottom of the page, but structurally/in focus order comes at the start >>>> of the DOM, then this won't be an issue for these users. >>>> >>>> The only issue here may be users that navigate with a mouse and use >>>> screen magnification, yes. But that issue specifically is not covered >>>> by >>>> WCAG. Of course, you can go above and beyond the normative >>>> requirements, >>>> and if you feel that the banner should also be visually at the top of >>>> the viewport, then by all means go for it...but not doing so does not >>>> fail WCAG. >>>> >>>> P >>>> -- >>>> Patrick H. Lauke >>>> >>>> https://www.splintered.co.uk/ | https://github.com/patrickhlauke >>>> https://flickr.com/photos/redux/ | https://www.deviantart.com/redux >>>> twitter: @patrick_h_lauke | skype: patrick_h_lauke >>>> >>>>
Received on Tuesday, 27 April 2021 09:32:33 UTC