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. Peters wrote: 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: 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 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. Peterswrote: 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 that has absolute positioning and a z-index that covers the content until the user clicks enter or whatever, then it does an ajax call to lett the server the user has verified they want to see the content and removes the div. I would suggest a tagName "splashscreen" for this purpose. It would have the same properties as a div only it would have semantic meaning so that people using screen readers would know it is important. An aria landmark of splashscreen would also properly distinguish it from complementary which is what I currently use for it (I would use banner but only one banner landmark per page is allowed). Just a thought, I won't defend the thought but if it seems reasonable to the powers that be, I think it is worth it. These splash screens do serve a different purpose than any other semantic tag.
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: 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 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. Peterswrote: 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 that has absolute positioning and a z-index that covers the content until the user clicks enter or whatever, then it does an ajax call to lett the server the user has verified they want to see the content and removes the div. I would suggest a tagName "splashscreen" for this purpose. It would have the same properties as a div only it would have semantic meaning so that people using screen readers would know it is important. An aria landmark of splashscreen would also properly distinguish it from complementary which is what I currently use for it (I would use banner but only one banner landmark per page is allowed). Just a thought, I won't defend the thought but if it seems reasonable to the powers that be, I think it is worth it. These splash screens do serve a different purpose than any other semantic tag.
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 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 >>>> wrote: >> >>> 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 that has absolute positioning and a >>> z-index that covers the content until the user clicks enter or >>> whatever, >>> then it does an ajax call to lett the server the user has verified they >>> want to see the content and removes the div. >>> >>> I would suggest a tagName "splashscreen" for this purpose. It would >>> have >>> the same properties as a div only it would have semantic meaning so >>> that >>> people using screen readers would know it is important. >>> >>> An aria landmark of splashscreen would also properly distinguish it >>> from >>> complementary which is what I currently use for it (I would use >>> banner but >>> only one banner landmark per page is allowed). >>> >>> Just a thought, I won't defend the thought but if it seems >>> reasonable to >>> the powers that be, I think it is worth it. >>> >>> These splash screens do serve a different purpose than any other >>> semantic >>> tag. >>> >
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. Peterswrote: 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 that has absolute positioning and a z-index that covers the content until the user clicks enter or whatever, then it does an ajax call to lett the server the user has verified they want to see the content and removes the div. I would suggest a tagName "splashscreen" for this purpose. It would have the same properties as a div only it would have semantic meaning so that people using screen readers would know it is important. An aria landmark of splashscreen would also properly distinguish it from complementary which is what I currently use for it (I would use banner but only one banner landmark per page is allowed). Just a thought, I won't defend the thought but if it seems reasonable to the powers that be, I think it is worth it. These splash screens do serve a different purpose than any other semantic tag.
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. Peterswrote: > 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 that has absolute positioning and a > z-index that covers the content until the user clicks enter or whatever, > then it does an ajax call to lett the server the user has verified they > want to see the content and removes the div. > > I would suggest a tagName "splashscreen" for this purpose. It would have > the same properties as a div only it would have semantic meaning so that > people using screen readers would know it is important. > > An aria landmark of splashscreen would also properly distinguish it from > complementary which is what I currently use for it (I would use banner but > only one banner landmark per page is allowed). > > Just a thought, I won't defend the thought but if it seems reasonable to > the powers that be, I think it is worth it. > > These splash screens do serve a different purpose than any other semantic > tag. >
[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 that has absolute positioning and a z-index that covers the content until the user clicks enter or whatever, then it does an ajax call to lett the server the user has verified they want to see the content and removes the div. I would suggest a tagName "splashscreen" for this purpose. It would have the same properties as a div only it would have semantic meaning so that people using screen readers would know it is important. An aria landmark of splashscreen would also properly distinguish it from complementary which is what I currently use for it (I would use banner but only one banner landmark per page is allowed). Just a thought, I won't defend the thought but if it seems reasonable to the powers that be, I think it is worth it. These splash screens do serve a different purpose than any other semantic tag.
Re: [whatwg] New tag
On Fri, Apr 1, 2016 at 5:55 PM, Karl Dubostwrote: > > 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 > http://www.la-grange.net/karl/ > > I get a scents we should be worried about network congestion. -- Brian Kardell :: @briankardell :: hitchjs.com
Re: [whatwg] New tag
Le 2 avr. 2016 à 04:04, Daniel Murphya é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 http://www.la-grange.net/karl/
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 Murphywrote: > 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 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 that old student of Biology Sciences >> who is not anymore. >> >> But you have hit the nail with your delicate sense of humour. Really. >> >> Kind regards >> >> --- >> >> Delfi Ramirez >> >> My digital signature [1] >> >> +34 633 589231 >> del...@segonquart.net [2] >> >> twitter: delfinramirez >> >> IRC: segonquart Skype: segonquart [3] >> >> http://segonquart.net >> >> http://delfiramirez.info >> [4] >> >> On 2016-04-01 18:09, Garrett Smith wrote: >> >> > 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, >> > -- >> > Garrett >> > Guitar Videos https://www.youtube.com/channel/UCY_uK9hur86KEuiG8s7yvWw >> > @xkit >> >> >> Links: >> -- >> [1] http://delfiramirez.info/public/dr_public_key.asc >> [2] mail:%20del...@segonquart.net >> [3] skype:segonquart >> [4] http://delfiramirez.info >> >
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 Ramirezwrote: > 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 that old student of Biology Sciences > who is not anymore. > > But you have hit the nail with your delicate sense of humour. Really. > > Kind regards > > --- > > Delfi Ramirez > > My digital signature [1] > > +34 633 589231 > del...@segonquart.net [2] > > twitter: delfinramirez > > IRC: segonquart Skype: segonquart [3] > > http://segonquart.net > > http://delfiramirez.info > [4] > > On 2016-04-01 18:09, Garrett Smith wrote: > > > 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, > > -- > > Garrett > > Guitar Videos https://www.youtube.com/channel/UCY_uK9hur86KEuiG8s7yvWw > > @xkit > > > Links: > -- > [1] http://delfiramirez.info/public/dr_public_key.asc > [2] mail:%20del...@segonquart.net > [3] skype:segonquart > [4] http://delfiramirez.info >
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 Ramirezwrote: > > 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 that old student of Biology Sciences who is not > anymore. > > But you have hit the nail with your delicate sense of humour. Really. > > Kind regards > > --- > Delfi Ramirez > My digital signature > > +34 633 589231 > del...@segonquart.net > twitter: delfinramirez > IRC: segonquart Skype: segonquart > http://segonquart.net > http://delfiramirez.info > > >> On 2016-04-01 18:09, Garrett Smith wrote: >> >> 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, >> -- >> Garrett >> Guitar Videos https://www.youtube.com/channel/UCY_uK9hur86KEuiG8s7yvWw >> @xkit
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 that old student of Biology Sciences who is not anymore. But you have hit the nail with your delicate sense of humour. Really. Kind regards --- Delfi Ramirez My digital signature [1] +34 633 589231 del...@segonquart.net [2] twitter: delfinramirez IRC: segonquart Skype: segonquart [3] http://segonquart.net http://delfiramirez.info [4] On 2016-04-01 18:09, Garrett Smith wrote: > 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, > -- > Garrett > Guitar Videos https://www.youtube.com/channel/UCY_uK9hur86KEuiG8s7yvWw > @xkit Links: -- [1] http://delfiramirez.info/public/dr_public_key.asc [2] mail:%20del...@segonquart.net [3] skype:segonquart [4] http://delfiramirez.info
[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, -- Garrett Guitar Videos https://www.youtube.com/channel/UCY_uK9hur86KEuiG8s7yvWw @xkit