Skip to content

Making component accessible  #126

Open

Description

@pietrop

Is your feature request related to a problem? Please describe.
Web Accessibility

Describe the solution you'd like
It be great if the component was accessible, for users with accessibility needs.

Describe alternatives you've considered
Not making it accessible

Additional context

Background info

Identify what is needed to

  • make it keyboard navigable
  • accessibility hierarchy of elements to move in and out of the text area (eg using h1 for title? to move to top level player controls? or a hidden anchor link)
  • test with Mac OSX default screen reader
  • DraftJs accessibility)
  • figure out if the accessibility interaction to edit text, play media etc.. effects the current UX and whether we need to revisit that with those constraints

Activity

  1. self-assigned this
    on Apr 2, 2019
  2. pinned this issue on Apr 26, 2019
  3. Laurian commented on May 13, 2019

    @Laurian
    Contributor

    look also at the player accessibility https://ableplayer.github.io/ableplayer/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Enhancementa request for improvementhelp wantedExtra attention is needed

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions