ampproject / ampproject/amphtml

inline iframes require title attributes (specifically with amp-brightcove) - a11y

Open
#38,530 1 comment 0 reactions 0 assignees View on GitHub
P3: When Possible Stale Type: Bug WG: components
Dominant language
JavaScript
Stars
14.9k
Forks
4.1k
PR merge metrics
No merged PRs in 30d

Description

### Description

This is a contnuation/reopening of bug [#29874](https://github.com/ampproject/amphtml/issues/29874)

AMP components that create inline iframes do not have a title attribute. This is against [WCAG guidelines](https://www.w3.org/TR/WCAG20-TECHS/H64.html) and fails [Lighthouse audits](https://web.dev/frame-title/?utm_source=lighthouse&utm_medium=devtools).

It appears based on the comments in the bug mentioned above that this issue was resolved for amp-youtube elements but not resolved for amp-brightcove. While running the [Access Assistant](https://chrome.google.com/webstore/detail/access-assistant/ojiighldhdmahfdnhfdebnpmlbiemdfm) extension to test accessibility on a page containing amp-brightcove elements, there remains an issue with the iframes containing the brightcove player not having a valid title attribute.

### Reproduction Steps

1. Visit https://s3-componentsexperiments-sbx01-cac1-01.s3.ca-central-1.amazonaws.com/AMP/index.html
2. Inspect the iframe that contains the brightcove player. There is no title attribute.

Upon running Access Assistant on the above link, this issue comes up:
Screen Shot 2022-11-04 at 12 07 36 PM

### Relevant Logs

_No response_

### Browser(s) Affected

Chrome, Firefox, Safari, Edge, UC Browser

### OS(s) Affected

_No response_

### Device(s) Affected

_No response_

### AMP Version Affected

2210211855000

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the issue at the linked AMP test page and inspecting the iframe created by amp-brightcove. Trace that component's iframe creation path, then verify the resulting brightcove iframe has a valid title attribute and that the accessibility audit no longer reports the issue.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
accessibility, frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.