Re: Mental Health, Videos and Personalization

Hello Rachael and all, Yes I am very involved in this but this metadata that John pointed to via schema.org<http://schema.org> is at the page level or what we are using it for is at the EPUB (electronic book) level for the entire book.
Element level semantics hasn’t really been defined which is why we need this level of support with personalization and semantics at the element level.

Thanks
EOM
Charles LaPierre
Technical Lead, DIAGRAM and Born Accessible
Twitter: @CLaPierreA11Y
Skype: charles_lapierre


On Jan 27, 2020, at 2:13 PM, John Foliot <john.foliot@deque.com<mailto:john.foliot@deque.com>> wrote:

> Can scheme (Schema - JF) be applied at an element level?

Uhm... sort of, but it's a bit verbose. I looked at it in the context of SC 1.3.5, and at that time the biggest issue was the lack of taxonomy (values). However, using Microdata, yes, you can scope Shema.org<http://Shema.org> values to elements (or blocks) on a page.

When I say verbose, it's because to use Microdata in that fashion, you need to scope the application (itemscope), you need to indicate the type (itemtype), and then you need to apply the relevant property values (itemprop). Looking quickly, I found this example<http://schema.org/accessibilityHazard> for a book (which was, I believe, Benetech's primary focus). None-the-less, I think it is a good illustration of the pattern and application of Microdata in this use-case:


  1.  <div itemscope=" " [I beleive because this is in a <div> it is inferred as scoped to the div - JF] itemtype="http://schema.org/Book">
  2.     <meta itemprop="bookFormat" content="EBook/DAISY3"/>
  3.     <meta itemprop="accessibilityFeature" content="largePrint/CSSEnabled"/>
  4.     <meta itemprop="accessibilityFeature" content="highContrast/CSSEnabled"/>
  5.     <meta itemprop="accessibilityFeature" content="resizeText/CSSEnabled"/>
  6.     <meta itemprop="accessibilityFeature" content="displayTransformability"/>
  7.     <meta itemprop="accessibilityFeature" content="longDescription"/>
  8.     <meta itemprop="accessibilityFeature" content="alternativeText"/>
  9.     <meta itemprop="accessibilityControl" content="fullKeyboardControl"/>
  10.    <meta itemprop="accessibilityControl" content="fullMouseControl"/>
  11.    <meta itemprop="accessibilityHazard" content="noFlashingHazard"/>
  12.    <meta itemprop="accessibilityHazard" content="noMotionSimulationHazard"/>
  13.    <meta itemprop="accessibilityHazard" content="noSoundHazard"/>
  14.    <meta itemprop="accessibilityAPI" content="ARIA"/>
  15. <p>On screen content here</p> </div>

Hope that helps.

JF

On Mon, Jan 27, 2020 at 12:55 PM Rachael Bradley Montgomery <rachael@accessiblecommunity.org<mailto:rachael@accessiblecommunity.org>> wrote:
John,

Thank you for sending this.  I can think of examples where element level content would benefit from tags such as these. For example, a news page might include a video report, transcript, and a second video of taped footage. The report and transcript might be written to avoid upsetting content but the taped footage of what happened might need to be marked.

Can scheme be applied at an element level?

Best regards,

Rachael

On Mon, Jan 27, 2020 at 1:43 PM John Foliot <john.foliot@deque.com<mailto:john.foliot@deque.com>> wrote:
Hi Rachel,

Thanks for the clarification. Are y'all aware of this already?

https://schema.org/accessibilityFeature

   and this:
http://schema.org/accessibilityHazard


I suspect the use-case(s) you are envisioning would be to use metadata at the page level (versus the element level, which is where Personalization is currently headed).

I'd personally rather see COGA efforts focus on the existing solution(s) (which I think are mostly lacking in tooling support), rather than trying to tease it out of our Personalization work (fun fact: Charles L. was actively involved with that work as well, right Charles?) Additionally, because Charles was previously involved, I'm sure he could assist if one or more specific "hazard values" is currently missing (I assert it is easier to build on top of existing effort, rather than start fresh elsewhere).

Schema dot Org already has strong support with the major search engine vendors, which includes Google, Microsoft, Yandex, and Baidu.

JF

On Mon, Jan 27, 2020 at 10:12 AM Rachael Bradley Montgomery <rachael@accessiblecommunity.org<mailto:rachael@accessiblecommunity.org>> wrote:
Hello,

I took us down the wrong track with regards to video and the mental health paper and I think you should revisit the issues Lisa raised at another Personalization meeting. There was too little time left today so I didn't jump back in. For personalization, I believe the suggestions are:

1. To consider adding a tag that identifies content that could trigger anxiety, PTSD or other mental health conditions. This would add to the sense of safety on the web for some individuals.
2. To consider adding a tag that indicates alternative versions of the same content.

Lisa - please correct me if I have misunderstood. Thank you again for the discussion on today's call. I will update you as Essential Controls continues.

Best regards,

Rachael
--
Rachael Montgomery, PhD
Director, Accessible Community
rachael@accessiblecommunity.org<mailto:rachael@accessiblecommunity.org>

"I will paint this day with laughter;
I will frame this night in song."
 - Og Mandino



--
​John Foliot | Principal Accessibility Strategist | W3C AC Representative
Deque Systems - Accessibility for Good
deque.com<http://deque.com/>



--
Rachael Montgomery, PhD
Director, Accessible Community
rachael@accessiblecommunity.org<mailto:rachael@accessiblecommunity.org>

"I will paint this day with laughter;
I will frame this night in song."
 - Og Mandino



--
​John Foliot | Principal Accessibility Strategist | W3C AC Representative
Deque Systems - Accessibility for Good
deque.com<http://deque.com/>