The idea is to identify which issues live within the the_content area and which issues are global and part of the theme. We would then only show issues to users who have the ability to fix those issues or even only issues from posts they are the author of. We would create a custom user capability that gives access to see side-wide issues. This capability would likely only be added to administrators by default.
Create a proof of concept to identify the location/landmark of an issue.
This will likely be a new column in the wp_accessibility_checker database table.
header
nav
main
aside
section
footer
block (maybe store block ID)
One idea is to add flags via WordPress action/filters. For example wp_head, wp_footer, comment_text, etc.
The idea is to identify which issues live within the
the_contentarea and which issues are global and part of the theme. We would then only show issues to users who have the ability to fix those issues or even only issues from posts they are the author of. We would create a custom user capability that gives access to see side-wide issues. This capability would likely only be added toadministratorsby default.wp_accessibility_checkerdatabase table.One idea is to add flags via WordPress action/filters. For example
wp_head,wp_footer,comment_text, etc.Related: https://github.com/equalizedigital/accessibility-checker/issues/58