fix wcag 2.1 accessibility errors on pods

  • Resolved 00lessio

    (@00lessio)


    1 year, 5 months ago

    I’m having accessibility errors using Pods blocks.
    These are the errors I’m getting:

    1. Criterion: 1.1.1 1.3.1 4.1.2 Tech: H65
      Using the title attribute to identify form controls when the label element cannot be used
    2. Criterion: 1.3.1 4.1.2 Tech: ARIA16
      Using aria-labelledby to provide a name for user interface controls
    3. Criterion: 1.3.5 Tech: H98
      Identify the purpose of inputs using the autocomplete value

    I entered the error code and the link to its explanation.

    The errors all concern the search form between the pods and perhaps also the pagination buttons. From what I understand it is enough to add the aria and role attributes to make it accessible. could you help me to solve them, is it possible to add them somehow in the plugin, in the pods search bar template?

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Contributor Scott Kingsley Clark

    (@sc0ttkclark)

    I’m very eager to address these issues. It will take me some time to review the exact changes needed here but your options are:

    1. Provide the accessibility changes to the markup and we’ll incorporate them in a release within days

    2. Provide your search / filter / pagination configuration you were using at the time in the block or PHP or however you were calling it and I can prioritize that in our next release first

    Thread Starter 00lessio

    (@00lessio)

    hello, all right thanks, today I will try to solve them, could you help me understand in some file go to modify to do some tests? I need to know in which file the search bar that activates from the block is generated, thanks

    Plugin Contributor Scott Kingsley Clark

    (@sc0ttkclark)

    This is the folder that we use for frontend based markup, you can see the files here: https://github.com/pods-framework/pods/tree/main/ui/front

    You want to edit the filters.php file and pagination/*.php files there.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘fix wcag 2.1 accessibility errors on pods’ is closed to new replies.