- πΊπΈUnited States aaronpinero
I wonder if it would be useful to follow this accessibility guidance:
https://a11y-guidelines.orange.com/en/articles/technical-iframe/I would consider the google tag manager iframe to be a technical iframe (as opposed to an iframe that is providing content to the user. For accessibility compliance and for hiding the iframe from the accessibility API, it is recommended that:
- the iframe has a title that identifies it as a technical element rather than a content element
- it has the attribute aria-hidden="true"
- it has tabindex="-1" - Open in Jenkins β Open on Drupal.org βCore: 10.1.x + Environment: PHP 8.1 & MySQL 5.7 updated depslast update
over 1 year ago 1 pass - πΊπΈUnited States aaronpinero
Uploading new patch with previously mentioned accessibility recommendations.
- last update
about 1 year ago 54 pass - πͺπΈSpain cbccharlie
Although the issue is from version 8.x, I also upload a patch for version 2.0.2.
- πͺπΈSpain cbccharlie
Although the issue is from version 8.x, I also upload a patch for version 7.x-2.x.
- Open in Jenkins β Open on Drupal.org βCore: 10.2.x + Environment: PHP 8.1 & MySQL 5.7 updated depslast update
8 months ago Patch Failed to Apply - Open in Jenkins β Open on Drupal.org βCore: 10.2.x + Environment: PHP 8.1 & MySQL 5.7 updated depslast update
8 months ago 1 pass - π³π±Netherlands uberengineer
Re-upload for empty file. Rerolled for 1.7
- π©πͺGermany Anybody Porta Westfalica
@aaronpinero please instead incorporate your changes from #10 into the MR.
Patches should not be used anymore.
- First commit to issue fork.