Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

BETA: Applied Accessibility: Improve Accessibility of Audio Content with the audio Element, not detecting closing </audio> tag.

See original GitHub issue

Applied Accessibility: Improve Accessibility of Audio Content with the audio Element

https://beta.freecodecamp.org/en/challenges/applied-accessibility/improve-accessibility-of-audio-content-with-the-audio-element

Issue Description

I tried to complete the task at hand. I believe it is done correctly, but it is saying that I still require a closing audio tag. You can see from the image below that I do have one in there and it is still not passing.

Browser Information

Note that this was performed in Chrome.

Browser Name, Version: Chrome, latest version
Operating System: Windows 10
Mobile, Desktop, or Tablet: Desktop

Your Code

<body>
  <header>
    <h1>Real Coding Ninjas</h1>
  </header>
  <main>
    <p>A sound clip of Zersiax's screen reader in action.</p>
  <audio controls>
    <source src="https://s3.amazonaws.com/freecodecamp/screen-reader.mp3" type="audio/mpeg" />    </audio>   
  </main>
</body>

Screenshot

audio

Issue Analytics

State:
Created 6 years ago
Comments:6 (1 by maintainers)

Top GitHub Comments

5reactions

cffntdcommented, Jun 13, 2018

Ran into this same issue tonight. For everyone still having trouble, do not include an id attribute in your audio tag. It seemed to accept my answer after I removed the id attribute completely.

    <audio controls>
      <source src="https://s3.amazonaws.com/freecodecamp/screen-reader.mp3" type="audio/mpeg" />
    </audio>

0reactions

johanvlcommented, Jun 8, 2018

still not fixed

Top Results From Across the Web

[Beta] Applied Accessibility - Tests fails to check for closing ...

The issue with this challenge is that you can use the opening <audio> tag and leave out the closing </audio> tag and the...

Make your Vidyard players more accessible

This article outlines what you can do improve the accessibility of your Vidyard players for viewers with disabilities.

Change Accessibility settings on Mac - Apple Support

Change Accessibility settings on Mac. If you have vision, hearing, or mobility difficulties, try out the wide range of Accessibility settings on your...

Web Content Accessibility Guidelines (WCAG) 2.2 - W3C

Web Content Accessibility Guidelines (WCAG) 2.2 covers a wide range of recommendations for making Web content more accessible.

Tackle accessibility in your designs with these useful plugins

Tackle accessibility challenges color contrast and keyboard navigation as part of your design process in Figma with 4 useful plugins.