Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Video #107

Open
govuk-design-system opened this issue Jan 15, 2018 · 4 comments

Comments

@govuk-design-system
Copy link
Collaborator

commented Jan 15, 2018

What

Accessible video player for GOV.UK.

Why

More research is required to establish when video is the most appropriate format for government information.

Anything else

@joelanman

This comment has been minimized.

Copy link
Member

commented Apr 5, 2018

Are there any services that use video?

@nickcolley

This comment has been minimized.

Copy link
Contributor

commented Apr 6, 2018

GOV.UK Publishing does: http://govuk-static.herokuapp.com/component-guide/govspeak/with_youtube_embed

See it in context here: https://www.gov.uk/government/case-studies/out-of-syria-back-into-school

Problems with the current implementation:

  1. Captions cannot be used with this custom player (https://docs.google.com/document/d/1YQaBeUltDHZWOLWmwo0i1R3Kx6K_EWEuJO23T7TknLQ/edit#heading=h.xst0yemqxbl3)
  2. YouTube embeds track users by sending requests to 'ad words' domain.

There are questions if the basic YouTube player would be better, we have not had time to test this.

We could consider doing something similar to Medium that informs users with 'Do Not Track' enabled, before they consume third-party content.

If successful this pattern could be used for general embedded content.

screen shot 2018-04-06 at 10 51 43

https://medium.com/policy/how-we-handle-do-not-track-requests-on-medium-f2b4b4fb7c5e

Edit: I did some more work to explore a general purpose pattern for this: https://do-not-track-third-party-embeds.glitch.me/

@timpaul timpaul added the pattern label May 21, 2018

@amyhupe

This comment has been minimized.

Copy link
Contributor

commented Jan 29, 2019

Dropbox Paper audit

On 29 January 2019 the Design System team reviewed a Dropbox Paper document discussing video content.

The aim was to reduce the number of places containing guidance and code by:

  • migrating relevant, useful content into the Design System itself
  • recording important research findings in the community backlog
  • removing the original Dropbox Paper page

Below is a record of the outcomes of that review.

If you need to, you can see the original Dropbox Paper content in the internet archive.

Guidance and examples from Dropbox

The following guidance was shared in the Dropbox Paper files and seemed useful:

  1. Do not use video until you have clear user evidence that the topic is easier to understand using moving images.
  2. If you decide to use a video, ensure that you have a transcript available for people who cannot view moving images.
  3. Try testing the content with the transcript of the video only. If the content works with the transcript alone, consider removing the video.
  4. If your video consists of an image of a person talking, consider replacing it with a transcript.
@selfthinker

This comment has been minimized.

Copy link
Member

commented May 31, 2019

As part of accessibility work for GOV.UK I looked into various web video players because the currently used Nomensa video player is very outdated and has a couple of accessibility issues. I tested a few of players for mostly accessibility but also other things like web performance, design options, how well it is maintained, etc.
The outcome was that we plan to use the pure YouTube embed video player on GOV.UK while also fixing a couple of issues with it. I cannot point to anything public yet, but we will publish a blog post in due time. I have posted findings to various cross-government communities.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
6 participants
You can’t perform that action at this time.