You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Yes, that should have been handled by AMP_Accessibility_Sanitizer
in that case, the AMP_Accessibility_Sanitizer must be added at the very end of the sanitizers ie. post theme support sanitizers
if ( ! empty( $theme_support_args['nav_menu_toggle'] ) ) {
$sanitizers[ AMP_Nav_Menu_Toggle_Sanitizer::class ] = $theme_support_args['nav_menu_toggle'];
}
if ( ! empty( $theme_support_args['nav_menu_dropdown'] ) ) {
$sanitizers[ AMP_Nav_Menu_Dropdown_Sanitizer::class ] = $theme_support_args['nav_menu_dropdown'];
}
// Note: This validating sanitizer must come at the end to clean up any remaining issues the other sanitizers didn't catch.$sanitizers['AMP_Accessibility_Sanitizer'] = [];
@milindmore22 with #6546 being released, please could you verify if this issue is still valid? Will accordingly have it either closed or added to the next release milestone.
Bug Description
We are adding theme support for the navigation menu, but there is a wide range of elements are being used for toggle button elements eg:
div
,a
,span
After adding theme support to them creates an AMP validation error of missing
tabindex
androle
which can be avoided by adding those attributes in case the element is not a button in
AMP_Nav_Menu_Toggle_Sanitizer
The theme I was trying to add support: Lightning
Expected Behaviour
Should not report AMP validation error
Screenshots
PHP Version
7.4
Plugin Version
2.1.4
AMP plugin template mode
Transitional
WordPress Version
5.8
Site Health
No response
Gutenberg Version
No response
OS(s) Affected
No response
Browser(s) Affected
No response
Device(s) Affected
No response
Acceptance Criteria
No response
Implementation Brief
No response
QA Testing Instructions
No response
Demo
No response
Changelog Entry
No response
The text was updated successfully, but these errors were encountered: