- From: Marc Haunschild <marc.haunschild@accessibility.consulting>
- Date: Wed, 28 Feb 2024 18:57:55 +0100
- To: Oliver Odgaard <olod@mapspeople.com>
- Cc: w3c-wai-ig@w3.org
- Message-Id: <6D804440-EE05-4FAC-B151-FFC139489109@accessibility.consulting>
It’s completely find to change the mouse pointer on links and other interactive elements. If this was the question? It’s much more likely to get answers, if you put a little more effort in your question. ;-) > Am 28.02.2024 um 16:10 schrieb Oliver Odgaard <olod@mapspeople.com>: > > Hi there WAI team, > > Can you help us with this? See thread. > ---------- Forwarded message ---------- > From: Denis Ah-Kang <denis@w3.org> > Date: 28 Feb 2024 at 15.59 +0100 > To: Oliver Odgaard <olod@mapspeople.com> > Subject: Re: W3C Recommendations Pointer Question > >> Sorry, I didn't understand you were looking for answers related to >> accessibility. I would suggest to write an email to the WAI Interest >> Group at w3c-wai-ig@w3.org (archives at [1]). They should be able >> to provide a more accurate answer than me :) >> >> You may also find some resources on their website [2]. >> >> Regards, >> >> Denis >> >> [1] https://lists.w3.org/Archives/Public/w3c-wai-ig/ >> [2] https://www.w3.org/WAI/ >> >> >> >> On 28/02/2024 18:37, Oliver Odgaard wrote: >>> Hi Denis, thanks for the super fast reply. So that means, from reading >>> the links you sent, we can still be WCAG 2.1 AA compliant if we use a >>> pointer on clickable elements? Is that correct? >>> >>> -- >>> >>> >>> Kind regards, >>> >>> *Oliver Odgaard* >>> Lead Product Designer >>> >>> <https://www.mapspeople.com/> >>> e. olod@mapspeople.com <mailto:olod@mapspeople.com> >>> >>> w. mapspeople.com <http://mapspeople.com/> >>> >>> >>> <https://www.linkedin.com/company/mapspeople/> >>> <https://www.facebook.com/mapspeople> >>> <https://twitter.com/mapspeople?lang=en> >>> <https://www.youtube.com/c/MapsPeople/videos> >>> >>> On 28. feb. 2024 15.19 +0100, Denis Ah-Kang <denis@w3.org>, wrote: >>>> Hi Oliver, >>>> >>>> I'm guessing you are referring to [1] but that issue was actually >>>> discussed [2] and the newest version of the spec has the pointer cursor >>>> indicating an interactive element [3]. >>>> So there's no problem using a pointer on clickable elements. >>>> >>>> HTH, >>>> >>>> Denis >>>> >>>> >>>> [1] https://www.w3.org/TR/CSS21/ui.html#cursor-props >>>> [2] https://github.com/w3c/csswg-drafts/issues/1936 >>>> [3] https://www.w3.org/TR/css-ui-3/#cursor >>>> >>>> >>>> >>>> On 28/02/2024 08:50, Oliver Odgaard wrote: >>>>> Hi Denis, >>>>> >>>>> Can you help me regarding use of a pointer on our web application? >>>>> >>>>> The W3C recommendations says to use a pointer on "The cursor is a >>>>> pointer that indicates a link.", but if we choose to use a pointer on >>>>> clickable elements like buttons (that aren't links) and interactive >>>>> elements inside our product, will that mean we can't say we are not W3C >>>>> compliant? >>>>> >>>>> We would love the added affordance that the pointer adds, making >>>>> interactive elements clearly recognizable and usable for all users. >>>>> >>>>> -- >>>>> >>>>> >>>>> Kind regards, >>>>> >>>>> *Oliver Odgaard* >>>>> Lead Product Designer >>>>> >>>>> <https://www.mapspeople.com/> >>>>> e. olod@mapspeople.com <mailto:olod@mapspeople.com> >>>>> >>>>> w. mapspeople.com <http://mapspeople.com/> >>>>> >>>>> >>>>> <https://www.linkedin.com/company/mapspeople/> >>>>> <https://www.facebook.com/mapspeople> >>>>> <https://twitter.com/mapspeople?lang=en> >>>>> <https://www.youtube.com/c/MapsPeople/videos> >>>>>
Received on Wednesday, 28 February 2024 17:58:12 UTC