Hide Accessibility checker for user roles like editors

  • Resolved handjes

    (@handjes)


    2 weeks, 6 days ago

    How can the Accessibility checker be hidden for user roles like the editor? It’s in the way of their work flow; they don’t need to see it.

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author williampatton

    (@williampatton)

    Hi @handjes,

    What features are you wanting to hide from editors? We have a filter to change who can see the frontend highlighter and another filter to hide the widget from the main dashboard page.

    If you want to hide the metabox in the editor we do not have a filter for that but I can make a card on our board to consider adding one if this is what you are wanting to hide.

    Thread Starter handjes

    (@handjes)

    All features, but especially the metabox in de editor.

    • This reply was modified 2 weeks, 6 days ago by handjes.
    Plugin Author williampatton

    (@williampatton)

    Hey again @handjes,

    I’m afraid I don’t have a solution for you right now in that case but I will make cards on our internal development board to make it easier to enable/disable features for different user roles.

    I did look at the code earlier to see if there was a really quick way that I could figure out getting the metabox hidden but there doesn’t seem to be an easy way without making significant code changes so it will take some developer time to do it.

    For the moment you could tell Editors how to hide the metabox in the editor. You can do that by clicking the 3 dots menu item in the top right corner, clicking on ‘preferences’ and then unchecking the accessibility checker box. This setting should be saved on a per user basis only though – not for all users.

    For the frontend hilighter we do have a filter that is documented here if you wanted to implement that as well: https://equalizedigital.com/accessibility-checker/customize-who-can-see-front-end-highlighter-edac_filter_frontend_highlighter_visibility/

    Plugin Author williampatton

    (@williampatton)

    Hi again @handjes,

    I have taken a look at it is not a simple change for me to make to get it working for you like you are asking. I have created an issue on our github repo to track progress towards offering this for you but I do not yet have a specific date we will work on it or release it.

    You can follow along with progress at the github issue or add any additional information there that you think is relevent.

    Thread Starter handjes

    (@handjes)

    Thanks, but I’ll uninstall the plugin for now on production sites.

Viewing 5 replies - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.