Home Forums Event Espresso Premium WCAG and AODA compliance issues

WCAG and AODA compliance issues

Posted: April 13, 2018 at 10:29 am


April 13, 2018 at 10:29 am

This plugin is being flagged for not having some labels, ids and headers… is there a fix for this? I tried adding these manually but not working.


April 13, 2018 at 10:30 am

These are the errors:

Problem: Data table with more than one row/column of headers does not use id and headers attributes to identify cells.
id and headers attributes allow screen readers to speak the headers associated with each data cell when the relationships are too complex to be identified using the th element alone or the th element with the scope attribute.

<table id=”tkt-slctr-tbl-987″ class=”tkt-slctr-tbl”>
<th scope=”col” class=”ee-ticket-selector-ticket-details-th”>
<th scope=”col” clas …

Problem: select element missing an associated label.
select element must have an associated label element. A label element is associated with the select element if the for attribute value of the label is the same as the id attribute of the select element.

<select name=”tkt-slctr-qty-987[]” id=”ticket-selector-tbl-qty-slct-987-2″ class=”ticket-selector-tbl-qty-slct”><option value=”0″> 0 </option><option value=”1″> 1&nb …


  • Support Staff

April 13, 2018 at 10:56 am

Hi there,

We actually have an open ticket that’s assigned to one of our developers to resolve the WCAG issues you’ve reported here. I’ll keep this topic updated when there’s been some progress on this.


April 13, 2018 at 11:01 am

ok thanks – though this plugin also seems to cause issues saving editor files (like home.php) and needs to be disabled in order to save those… a bit glitchy it seems.


  • Support Staff

April 13, 2018 at 11:05 am

I can edit the same file with Event Espresso 4 activated, but you don’t use FTP to edit files?


April 13, 2018 at 11:10 am

Sure if I use FTP it’s fine, but not if I use the WordPress editor to do so – and this is for a client, so the general CMS framework should still behave normally no? CSS files save as usual, it’s the php ones that cannot.


  • Support Staff

April 13, 2018 at 11:21 am

Have you confirmed the same happens with only Event Espresso activated?

I can edit php files fine with EE activated.

Example of functions.php –

header.php –

It could be a plugin conflict or a conflict with the theme. Even though it works when EE is disabled that may just be another symptom of the cause rather than the cause.

If you enable WPDebug using this snippet:

Then try editing the file again and check /wp-content/debug.log, do you see any errors there?


April 17, 2018 at 7:29 am

Hello, is there any news on the three code changes – headers, id, label code just to get this WCAG/AODA compliant? Is there no quick way to just add that myself? This is the only thing holding up a big project.

Seth Shoultes

  • Support Staff

April 17, 2018 at 8:26 am

Hi there,

We are still discussing this internally, in regards to the specific request to add labels. The developers are concerned adding labels in this space will have negative impacts on the table styling, especially in situations where the ticket selector may have been customized.

We also discussed what changes could be made for you to customize this on your end but the developers cautioned against doing so because of how dynamic the code is within the ticket selector. Whomever makes this change will have to scan through a lot of code to make sure nothing is missed or broken.


April 17, 2018 at 9:08 am

ok but the ids/headers can be anything, as long as they are in place. Same with the labels, they don’t need to be added in a visible manner. I have edited core search modules and menu modules in Joomla by doing this, there’s no appreciable difference from a user perspective, but it will then pass a WCAG/AODA scan.


  • Support Staff

April 18, 2018 at 4:07 pm

There’s a branch that adds some accessible markup to the ticket selector, that addresses the two items you listed. Here’s a link to that branch where it’s hosted on Github:

You’re welcome to test that branch if you’d like.

Seth Shoultes

  • Support Staff

April 19, 2018 at 9:38 am

Thanks, Josh!

The changes have been approved and awaiting testing, then merged into core if approved.


April 19, 2018 at 9:46 am

We just deleted the plugin and our events and had to choose another option, unfortunately.

But we may use espresso in the future if you get this stuff worked. Good luck, hopefully it is re-built to pass the highest level of compliance.

Seth Shoultes

  • Support Staff

April 19, 2018 at 11:33 am

Going forward, the ticket selector will meet WCAG 2.0 (Level AA) Guidelines.

Here’s a screenshot of the latest test:


April 23, 2018 at 1:56 pm

ok, so it is compliant now? I just activated the plugin again and it is still failing. or is there a new version to download? This is great news if we can use it!
This one failed both achecker and aodaonline:


  • Support Staff

April 23, 2018 at 4:16 pm

The new version with the work that Seth mentioned isn’t available to download yet.

The release candidate is available to download on Github:

We’ll update this topic when Event Espresso 4.9.62.p is officially released.

The support post ‘WCAG and AODA compliance issues’ is closed to new replies.

Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.

Support forum for Event Espresso 3 and Event Espresso 4.
Documentation for EE3 and EE4
Documentation for Event Espresso 3

Documentation for Event Espresso 4

Status: closed

Updated by  Josh 8 months, 4 weeks ago ago

Topic Tags

Tagged: ,


This topic is: not resolved
Do NOT follow this link or you will be banned from the site!