W3C home > Mailing lists > Public > public-web-notification@w3.org > July 2012

Re: a11y & i18n of Web Notifications / was: Web Notifications I18N Review: [I18N-ISSUE-161, I18N-ISSUE-162]

From: Anne van Kesteren <annevk@annevk.nl>
Date: Wed, 4 Jul 2012 18:23:43 +0200
Message-ID: <CADnb78gwcZKGm5kE0U4V2C7uAzaEdwcdbtQwYxJGW298rHU9eA@mail.gmail.com>
To: Artur Ortega <Artur@ortegalink.com>
Cc: public-web-notification@w3.org, w3@norbertlindenberg.com
On Sun, Jul 1, 2012 at 1:24 AM, Artur Ortega <Artur@ortegalink.com> wrote:
> *  title:
> The title is textual content. For making sure the title of the Web
> Notification is read correctly by the screen reader it has to provide
> additionally the used language.

See the other thread. Even if we allow setting it, that does not mean
it's a) available, b) actually end up getting used by the notification

> WCAG 2.0 Guideline 1.1 "Provide text alternatives for any non-text
> content so that it can be changed into other forms people need, such
> as large print, braille, speech, symbols or simpler language."
> Further information can be found at:
> http://www.w3.org/TR/UNDERSTANDING-WCAG20/text-equiv.html
> Proposed fix: an icon-alt and icon-lang element

The notification icon, like the favicon, is not content.

>   The Web Notification document mentions additionally that the
> notification " object offers a click event".  A click event is not a
> device independent event.

It is actually. It entirely depends on how it's implemented and
there's no reason it cannot be implemented in a sane way.

Received on Wednesday, 4 July 2012 16:24:11 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:53:14 UTC