- From: Charles Myers <charlesm@benetech.org>
- Date: Wed, 2 Oct 2013 10:17:08 +0000
- To: Andy Heath <andyheath@axelrod.plus.com>
- CC: Emmanuelle Gutiérrez y Restrepo <emmanuelle@sidar.org>, Madeleine Rothberg <madeleine_rothberg@wgbh.org>, "<a11y-metadata-project@googlegroups.com>" <a11y-metadata-project@googlegroups.com>, "<public-vocabs@w3.org>" <public-vocabs@w3.org>
Matt and I have been found out. Sorry for that. We've been much less than happy with Googledocs for this project. And the wiki technology has not been our friend either. That's part of why the "practical properties guide" is in the wiki... it was MUCH easier to format this in the wiki than in google docs (and we tried a few different ways). Once this content is firm, we can look to publish with real tools, whether non-wiki HTML editors, indesign, or something else. But it's pointless to do that until we have a firm base. For now, I will update the spec to refer to wcag2.3, and hope that WCAG2.3 will take on the larger set of hazards than just ones that are expected in HTML (sound, motion) On Oct 2, 2013, at 3:08 AM, Andy Heath <andyheath@axelrod.plus.com> wrote: > My apologies for being silly, its just the links in the index that point out to googledocs, the text is there in the pdf (andy needs to work with more haste less speed). > > The text is there in the best practice guide but would it not be wise to also link it to that checkpoint in WCAG ? > > andy >> Charles, >> >> This is behind a google-docs authentication so I can't read it - are you >> able to change settings so I can ? I presume its very similar to what >> we defined in AfA 3.0 and points to the WCAG checkpoint ? (why re-invent >> wheels unless they don't roll). >> >> Over a slightly longer timescale it might be appropriate for a >> definition to be incorporated in the ISO 24751 registry that RTFL/GPII >> are planning to host. >> >> Best >> >> andy >>> This is one of the problems with simple names that a person would type >>> into an attribute vs. the deeper meaning. >>> >>> The deeper meaning is defined in the best practices guide at >>> http://www.a11ymetadata.org/wp-content/uploads/2013/09/A11yMetadataProjectBestPracticesGuide_V.6final.pdf >>> >>> >>> >>> /Hazards >>> Some digital media can be physically dangerous to those who access it. >>> It is commonly known >>> that rates of flashing faster than 3Hz (3 times per second) can cause >>> seizures, but loud >>> repetitive sounds can have the same effect. Nausea is another hazard >>> that can be brought on by >>> motion simulation in visual resources. >>> When a resource is known to contain such physical hazards, the user >>> needs to discover their >>> presence before accessing the content. Although adding warnings to the >>> page may seem sufficient, / >>> /such warnings are easily missed. >>> The accessHazardproperty allows these physiological dangers to be >>> identified so that a >>> search engine can report the hazard. It has three predefined values to >>> account for the >>> abovementioned situations: flashing, soundand motionSimulation./ >>> >>> I think that this is covered, especially as people would understand that >>> this is a flashing hazard, not just a flashing attribute (part of why it >>> is split into accessHazard and not a mediaFeature). >>> >>> On Oct 1, 2013, at 3:56 PM, Emmanuelle Gutiérrez y Restrepo >>> <emmanuelle@sidar.org <mailto:emmanuelle@sidar.org>> wrote: >>> >>>> 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>[mailto:a11y-metadata-project@googlegroups.com >>>> >>>> <mailto: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 >>>> <mailto:a11y-metadata-project@googlegroups.com>;public-vocabs@w3.org >>>> <mailto: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 toa11y-metadata-project+unsubscribe@googlegroups.com >>>> <mailto:a11y-metadata-project+unsubscribe@googlegroups.com>. >>>> To post to this group, send email >>>> toa11y-metadata-project@googlegroups.com >>>> <mailto:a11y-metadata-project@googlegroups.com>. >>>> For more options, visithttps://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 toa11y-metadata-project+unsubscribe@googlegroups.com >>>> <mailto:a11y-metadata-project+unsubscribe@googlegroups.com>. >>>> To post to this group, send email >>>> toa11y-metadata-project@googlegroups.com >>>> <mailto:a11y-metadata-project@googlegroups.com>. >>>> For more options, visithttps://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 toa11y-metadata-project+unsubscribe@googlegroups.com >>>> <mailto:a11y-metadata-project+unsubscribe@googlegroups.com>. >>>> To post to this group, send email >>>> toa11y-metadata-project@googlegroups.com >>>> <mailto:a11y-metadata-project@googlegroups.com>. >>>> For more options, visithttps://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 toa11y-metadata-project+unsubscribe@googlegroups.com >>>> <mailto:a11y-metadata-project+unsubscribe@googlegroups.com>. >>>> To post to this group, send email >>>> toa11y-metadata-project@googlegroups.com >>>> <mailto:a11y-metadata-project@googlegroups.com>. >>>> For more options, visithttps://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 > andyheath@axelrod.plus.com > -- > __________________ > Andy Heath > http://axelafa.com >
Received on Wednesday, 2 October 2013 10:17:54 UTC