W3C home > Mailing lists > Public > whatwg@whatwg.org > November 2017

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

From: Yay295 <yay295@gmail.com>
Date: Sun, 12 Nov 2017 01:11:54 -0700
Message-ID: <CAH+HUiYGXNsRs0PFkBbp-NeD1Up_iuYv39qY6OwE1kPSeqDAiQ@mail.gmail.com>
To: "Michael A. Peters" <mpeters@domblogger.net>
Cc: whatwg@whatwg.org
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 <mpeters@domblogger.net>
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.
>
Received on Sunday, 12 November 2017 08:12:23 UTC

This archive was generated by hypermail 2.3.1 : Sunday, 12 November 2017 08:12:23 UTC