Re: [whatwg] new tag and possible new aria role

Was just informed that using aria-hidden solves the problem of content being there that shouldn't be seen in a screen reader until agreed, so that issue has a solution too. I guess none of this really is meaningful to this list - sorry for the noise. On 11/12/2017 04:18 AM, Michael A.

Re: [whatwg] new tag and possible new aria role

Yes but since I always have the div first in HTML the user is likely to always be aware of it, so skipping it in a screen reader is really little different than just pressing the agree button - they have been informed of the type of content. On 11/12/2017 04:09 AM, Johannes Spangenberg wrote:

Re: [whatwg] new tag and possible new aria role

There is another problem with Modals on webpages. When there is a modal created through HTML and CSS, the user can still select items in the background by pressing tab. It seems that there is no good solution to prevent it. Am 12.11.2017 um 09:59 schrieb Michael A. Peters: > Thank you! That

Re: [whatwg] new tag and possible new aria role

Thank you! That does seem like it is exactly what I need. On 11/12/2017 12:11 AM, Yay295 wrote: I think the alertdialog role fits here. https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/ARIA_Techniques/Using_the_alertdialog_role On Sun, Nov 12, 2017 at 1:03 AM, Michael A. Peters

Re: [whatwg] new tag and possible new aria role

I think the alertdialog role fits here. https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/ARIA_Techniques/Using_the_alertdialog_role On Sun, Nov 12, 2017 at 1:03 AM, Michael A. Peters wrote: > On webites that either are age restricted and/or have content

[whatwg] new tag and possible new aria role

On webites that either are age restricted and/or have content that may be offensive to some people, often (but not as often as I'd like) there is a warning splashscreen that the server puts in the page if the user has not already agreed to see such content. One way to do this is with a div

Re: [whatwg] New tag

On Fri, Apr 1, 2016 at 5:55 PM, Karl Dubost wrote: > > Le 2 avr. 2016 à 04:04, Daniel Murphy a écrit : > > we wouldn't want to waste our expensive > > smell synthesis technology on the likes of webcrawlers and other robots > who > > wouldn't benefit. > > >

Re: [whatwg] New tag

Le 2 avr. 2016 à 04:04, Daniel Murphy a écrit : > we wouldn't want to waste our expensive > smell synthesis technology on the likes of webcrawlers and other robots who > wouldn't benefit. Yup. User agent sniffing definitely stinks. -- Karl Dubost 

Re: [whatwg] New tag

We need the detection api because we wouldn't want to waste our expensive smell synthesis technology on the likes of webcrawlers and other robots who wouldn't benefit. On Fri, Apr 1, 2016 at 12:01 PM Daniel Murphy wrote: > Don't forget, we also need: > > *SmellEvent* > >

Re: [whatwg] New tag

Don't forget, we also need: *SmellEvent* - "onsmellchanged" - "onsmellstart" - "onsmellend" - "ongoodsmell" - "onbadsmell" And the new detection api: window.doesUserHaveNose() : Promise On Fri, Apr 1, 2016 at 11:14 AM Delfi Ramirez wrote: > Garrett et

Re: [whatwg] New tag

Just a lighthearted April Fools, and that's it. Sorry if it made anyone upset. Sent from my bathroom Attachment: poo.sm > On Apr 1, 2016, at 11:14 AM, Delfi Ramirez wrote: > > Garrett et al: > > I really appreciate your delicate sense of humour. Not sure if all the

Re: [whatwg] New tag

Garrett et al: I really appreciate your delicate sense of humour. Not sure if all the people in the list does the same. We all know a computer-- opossite to we human beings - is unable to interpret correctly, unconciently, the information pheromones and smells have. I am speaking now like

[whatwg] New tag

There has been good progress in HTML5 for and . But the tag has been missing — why? Well no longer, now thanks to a new game-changing proposal: But it occurred to me: This could be huge paradigm shift in towards Internet Odorous Things. boolean `navigator.isSmellEnabled` Thank you, --