Fix accessibility issue: Add title attribute to Google Tag Manager iframe #1312
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…rame Resolves issue joomla#1310 - Accessibility error and alert joomla 5.4.2 Added 'title' attribute to iframe element to provide accessible name This fixes WCAG compliance error: Embedded content requires an accessible name
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resolves issue #1310 - Accessibility error and alert joomla 5.4.2
Problem
The Google Tag Manager iframe element in templates/index.twig was missing an accessible name (title or aria-label attribute), causing a WCAG accessibility compliance error:
'Embedded content requires an accessible name that describes its contents.'
Solution
Added the 'title' attribute with value 'Google Tag Manager' to the iframe element.
Changes
This fix ensures compliance with WCAG guidelines and resolves the accessibility error reported in issue #1310.