Add note about lack of standardized sound hazards

[mattgarrish]

Prior to transferring issue #1302, I've changed the link to the github issue to a note that there isn't a precise way of determining when content presents a sound hazard, so authors will have to use their discretion on whether to set.

On a minor note, I added parallax scrolling to the list of motion simulation causes and sudden volume changes to sound.

• Accessibility preview
• Accessibility diff

[iherman]

The issue was discussed in a meeting on 2021-11-11

List of resolutions:

• Resolution No. 1: Approve PR 1903.

View the transcript

3. a11y and audio: #1302.

Matt Garrish: almost a given that this will happen at this point.

See github issue epub-specs#1302.

Avneesh Singh: issue is about audio hazards, which are underspecified currently.

See github pull request epub-specs#1903.

Avneesh Singh: what should be considered an audio hazard?.

Matt Garrish: we're referencing here the Schema metadata (which was formerly IMS metadata), so not much we can do.
… lack of standard on when audio constitutes a hazard.
… next step will be to pursue this in the new vocabulary CG.

Avneesh Singh: if we want to put pressure on WAI, would it make more sense to keep this issue in epub 33 wg.

Matt Garrish: we should maybe open an issue in WAI tracker.

Tzviya Siegman: +1 to mgarrish.

Matt Garrish: you sent an email to them earlier this year to put it on their radar, but it may have been forgotten now.

Proposed resolution: Approve PR 1903. (Avneesh Singh)

Matt Garrish: +1.

Wendy Reid: +1.

Matthew Chan: +1.

Gregorio Pellegrino: +1.

Wendy Reid: george: +1.

Murata Makoto: +1.

Resolution #1: Approve PR 1903.

John Foliot: i would recommend that we not take this to a11y guidelines wg, it'll get lost.
… they are very busy now.
… maybe take this to APA, research questions TF.

Matt Garrish: great! Thank you..

John Foliot: two categories of sound hazards I can think of: 1) auto-start/loud, and 2) specific types of sounds like explosions.
… this sort of thing is perfect for the research questions TF.

Avneesh Singh: APA is also more research oriented.

John Foliot: AG is focused on a11y scoring issue right now. You can log the issue against WCAG3 if you want, but I would not recommend.

George Kerscher: maybe this is something that can go into DaisyKB, that people are aware of volumes, that if there are sudden amplitude jumps that a hazard should be entered into epub metadata.

Matt Garrish: yeah, we can certainly do that. Within our domain..

Avneesh Singh: we will discuss that further via email.
… for now mgarrish please open the issue with APA.
… and we may point AG to this issue again in future.
… and also email WAI group to raise this question.

[iherman]

The issue was discussed in a meeting on 2021-11-11

List of resolutions:

• Resolution No. 1: Approve PR 1903.

View the transcript

3. a11y and audio: #1302.

Matt Garrish: almost a given that this will happen at this point.

See github issue epub-specs#1302.

Avneesh Singh: issue is about audio hazards, which are underspecified currently.

See github pull request epub-specs#1903.

Avneesh Singh: what should be considered an audio hazard?.

Matt Garrish: we're referencing here the Schema metadata (which was formerly IMS metadata), so not much we can do.
… lack of standard on when audio constitutes a hazard.
… next step will be to pursue this in the new vocabulary CG.

Avneesh Singh: if we want to put pressure on WAI, would it make more sense to keep this issue in epub 33 wg.

Matt Garrish: we should maybe open an issue in WAI tracker.

Tzviya Siegman: +1 to mgarrish.

Matt Garrish: you sent an email to them earlier this year to put it on their radar, but it may have been forgotten now.

Proposed resolution: Approve PR 1903. (Avneesh Singh)

Matt Garrish: +1.

Wendy Reid: +1.

Matthew Chan: +1.

Gregorio Pellegrino: +1.

Wendy Reid: george: +1.

Murata Makoto: +1.

Resolution #1: Approve PR 1903.

John Foliot: i would recommend that we not take this to a11y guidelines wg, it'll get lost.
… they are very busy now.
… maybe take this to APA, research questions TF.

Matt Garrish: great! Thank you..

John Foliot: two categories of sound hazards I can think of: 1) auto-start/loud, and 2) specific types of sounds like explosions.
… this sort of thing is perfect for the research questions TF.

Avneesh Singh: APA is also more research oriented.

John Foliot: AG is focused on a11y scoring issue right now. You can log the issue against WCAG3 if you want, but I would not recommend.

George Kerscher: maybe this is something that can go into DaisyKB, that people are aware of volumes, that if there are sudden amplitude jumps that a hazard should be entered into epub metadata.

Matt Garrish: yeah, we can certainly do that. Within our domain..

Avneesh Singh: we will discuss that further via email.
… for now mgarrish please open the issue with APA.
… and we may point AG to this issue again in future.
… and also email WAI group to raise this question.

[iherman]

The issue was discussed in a meeting on 2021-11-11

List of resolutions:

• Resolution No. 1: Approve PR 1903.

View the transcript

3. a11y and audio: #1302.

Matt Garrish: almost a given that this will happen at this point.

See github issue epub-specs#1302.

Avneesh Singh: issue is about audio hazards, which are underspecified currently.

See github pull request epub-specs#1903.

Avneesh Singh: what should be considered an audio hazard?.

Matt Garrish: we're referencing here the Schema metadata (which was formerly IMS metadata), so not much we can do.
… lack of standard on when audio constitutes a hazard.
… next step will be to pursue this in the new vocabulary CG.

Avneesh Singh: if we want to put pressure on WAI, would it make more sense to keep this issue in epub 33 wg.

Matt Garrish: we should maybe open an issue in WAI tracker.

Tzviya Siegman: +1 to mgarrish.

Matt Garrish: you sent an email to them earlier this year to put it on their radar, but it may have been forgotten now.

Proposed resolution: Approve PR 1903. (Avneesh Singh)

Matt Garrish: +1.

Wendy Reid: +1.

Matthew Chan: +1.

Gregorio Pellegrino: +1.

Wendy Reid: george: +1.

Murata Makoto: +1.

Resolution #1: Approve PR 1903.

John Foliot: i would recommend that we not take this to a11y guidelines wg, it'll get lost.
… they are very busy now.
… maybe take this to APA, research questions TF.

Matt Garrish: great! Thank you..

John Foliot: two categories of sound hazards I can think of: 1) auto-start/loud, and 2) specific types of sounds like explosions.
… this sort of thing is perfect for the research questions TF.

Avneesh Singh: APA is also more research oriented.

John Foliot: AG is focused on a11y scoring issue right now. You can log the issue against WCAG3 if you want, but I would not recommend.

George Kerscher: maybe this is something that can go into DaisyKB, that people are aware of volumes, that if there are sudden amplitude jumps that a hazard should be entered into epub metadata.

Matt Garrish: yeah, we can certainly do that. Within our domain..

Avneesh Singh: we will discuss that further via email.
… for now mgarrish please open the issue with APA.
… and we may point AG to this issue again in future.
… and also email WAI group to raise this question.

[clapierre]

A little late but this looks great as always ;)