W3C home > Mailing lists > Public > public-vocabs@w3.org > October 2013

RE: [a11y-metadata-project] accessHazard

From: Emmanuelle Gutiérrez y Restrepo <emmanuelle@sidar.org>
Date: Wed, 2 Oct 2013 02:04:51 +0200
To: "'Andy Heath'" <andyheath@axelrod.plus.com>
Cc: "'Madeleine Rothberg'" <madeleine_rothberg@wgbh.org>, <a11y-metadata-project@googlegroups.com>, <public-vocabs@w3.org>
Message-ID: <014901cebf03$04b7bb00$0e273100$@sidar.org>
Thanks Andy  for the reference,

So we have to find a way to indicate that the content has some element that
flashes but not to the point of being able to generate a seizure.

Is that they are two different use cases. One for people with photosensitive
epilepsy and one for people with attention deficit and other cognitive
deficits. Or maybe certain circumstances due to the device or to the context
of use that can make the person, even without any deficiency, prefer content
that does not blink.

Best,

Emmanuelle Gutiérrez y Restrepo
Patrono y Directora General
Fundación Sidar - Acceso Universal
Email: coordina@sidar.org
Personal: Emmanuelle@sidar.org
Web: http://sidar.org


-----Mensaje original-----
De: Andy Heath [mailto:andyheathaxelrod@googlemail.com] En nombre de Andy
Heath
Enviado el: miércoles, 02 de octubre de 2013 1:12
Para: Emmanuelle Gutiérrez y Restrepo
CC: 'Madeleine Rothberg'; a11y-metadata-project@googlegroups.com;
public-vocabs@w3.org
Asunto: Re: [a11y-metadata-project] accessHazard

Emmanuelle,

You are perfectly correct.
The definition we gave the term flashing in AfA 3.0 was

"A resource whose visual pattern flashes more than three times in any one
second; this level of flashing can cause seizures in some users
(WCAG2 Guideline 2.3.2):

     http://www.w3.org/TR/WCAG20/#seizure].
"

It isn't sufficient that there is just a term in a vocabulary - it needs
precise definition somewhere also. I'm not sure what the plans in this
project are for definitions like this but I would guess its somewhere in the
development pipeline.

Best

andy
axelafa.com
> Hi all,
>
> I am concerned that the term "flashing" can be misleading or confusing.
> Something that flashes is not bad in itself, everything depends on the 
> ratio of flashes per second. At least not for everyone. While 
> something that flashes to any ratio can be annoying and even disabling 
> for a person with attention deficit is not for everyone. And for 
> something that flashes generate a seizure, certain conditions must be met.
>
> I think we need to be more precise.
>
> Perhaps there could be a general indicator for something that flashes 
> and another for something that can generate seizures in some people.
>
> /Emmanuelle Gutiérrez y Restrepo/
>
> Patrono y Directora General
>
> Fundación Sidar - Acceso Universal
>
> Email: coordina@sidar.org <mailto:coordina@sidar.org>
>
> Personal: Emmanuelle@sidar.org <mailto:Emmanuelle@sidar.org>
>
> Web: http://sidar.org
>
> *De:*a11y-metadata-project@googlegroups.com
> [mailto:a11y-metadata-project@googlegroups.com] *En nombre de 
> *Madeleine Rothberg *Enviado el:* miércoles, 02 de octubre de 2013 
> 0:43
> *Para:* a11y-metadata-project@googlegroups.com; public-vocabs@w3.org
> *Asunto:* Re: [a11y-metadata-project] accessHazard
>
> Yes! Even better.
>
> Madeleine
>
>
> On 2013-10-01, at 6:11 PM, "Charles Myers" <charlesm@benetech.org 
> <mailto:charlesm@benetech.org>> wrote:
>
>     Charles McN had a great idea when he brought this up.  But it may
>     actually be a bit simpler to specify.
>
>     Rather than sav
>
>       * noFlashing
>       * noMotionSimulation
>       * noSound
>
>     in addition to the three properties we have today
>
>       * flashing
>       * motionSimulation
>       * sound
>
>     we might just want to have a state of "none" (saying that you
>     checked and that there are no hazards that you are aware of).
>
>     That would change the spec to
>
>       * flashing
>       * motionSimulation
>       * sound
>       * none (or noHazard)
>
>     which makes it cleaner.  I think that saying the negative to each of
>     the three properties would be a bit tedious.  And, of course, not
>     having the property means that it has not been checked.
>
>     On Oct 1, 2013, at 1:38 PM, Madeleine Rothberg
>     <madeleine_rothberg@wgbh.org <mailto:madeleine_rothberg@wgbh.org>>
>
>       wrote:
>
>
>
>     Chuck has updated the issues list to include the discussion of whether
>     accessHazard should state positive or negative information. See that
>     post
>     and my comments, which are also below, at:
>
[http://www.w3.org/wiki/WebSchemas/Accessibility/Issues_Tracker#accessHazar
>     d_-_Ok_as_is.2C_or_should_it_be_negated_in_sense.3F]
>
>     I believe we need both accessHazard=flashing and
>     accessHazard=noFlashing,
>     etc.. This is because there are three cases we'd like to distinguish:
>
>     1. checked and it's fine
>     2. checked and it is NOT fine
>     3. didn't check
>
>     "Didn't check" can be signified by no metadata -- this will be most
>     of the
>     content on the Web. In cases where someone has checked, let's record
>     both
>     positive and negative states.
>
>     -Madeleine
>
>     --
>     You received this message because you are subscribed to the Google
>     Groups "Accessibility Metadata Project" group.
>     To unsubscribe from this group and stop receiving emails from it,
>     send an email to a11y-metadata-project+unsubscribe@googlegroups.com
>     <mailto:a11y-metadata-project+unsubscribe@googlegroups.com>.
>     To post to this group, send email to
>     a11y-metadata-project@googlegroups.com
>     <mailto:a11y-metadata-project@googlegroups.com>.
>     For more options, visit https://groups.google.com/groups/opt_out.
>
>     --
>     You received this message because you are subscribed to the Google
>     Groups "Accessibility Metadata Project" group.
>     To unsubscribe from this group and stop receiving emails from it,
>     send an email to a11y-metadata-project+unsubscribe@googlegroups.com
>     <mailto:a11y-metadata-project+unsubscribe@googlegroups.com>.
>     To post to this group, send email to
>     a11y-metadata-project@googlegroups.com
>     <mailto:a11y-metadata-project@googlegroups.com>.
>     For more options, visit https://groups.google.com/groups/opt_out.
>
> --
> You received this message because you are subscribed to the Google 
> Groups "Accessibility Metadata Project" group.
> To unsubscribe from this group and stop receiving emails from it, send 
> an email to a11y-metadata-project+unsubscribe@googlegroups.com
> <mailto:a11y-metadata-project+unsubscribe@googlegroups.com>.
> To post to this group, send email to
> a11y-metadata-project@googlegroups.com
> <mailto:a11y-metadata-project@googlegroups.com>.
> For more options, visit https://groups.google.com/groups/opt_out.
>
> --
> You received this message because you are subscribed to the Google 
> Groups "Accessibility Metadata Project" group.
> To unsubscribe from this group and stop receiving emails from it, send 
> an email to a11y-metadata-project+unsubscribe@googlegroups.com.
> To post to this group, send email to
a11y-metadata-project@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.




andy
andyheath@axelrod.plus.com
--
__________________
Andy Heath
http://axelafa.com
Received on Wednesday, 2 October 2013 00:05:20 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:29:32 UTC