Forum Replies Created

Viewing 1 replies (of 1 total)
  • kyletimm

    (@kyletimm)

    Hello,

    I ran into the same issue with ADA compliance using this plugin. Overall I really like the plugin, as it does some things that other calendar plugins won’t do, or won’t do as easily. From doing some digging around in the codee, I was able to find a solution that worked for me, though it is only temporary. Below is what I found.

    This problem only exists when you are using a non-static calendar. If the navigation buttons aren’t there, there is no problem.

    I’ve been able to fix the problem by changing the default-calendar-grid.php file to change the contents of the buttons that they noted above. I ended up replacing the chevron icons in the file with stylized “<” and “>” characters, respectively. This allows a screen reader to see that there is actually content within the button, and furthermore within the table header, and as a result fixes the errors it has with the calendar.
    I suspect, though haven’t tested yet, that this would work the same by altering a similar line of code in default-calendar-list.php.

    Here is the line of code that i’ve put in in place of the existing code on the php file in question:
    <button class=”simcal-nav-button simcal-month-nav simcal-prev” title=”<?php _e( ‘Previous Month’, ‘google-calendar-events’ ); ?>”><span style=”font-size:2em;font-weight:bold;”><</span></button>
    Note I’ve removed the <i> tag inside the button and simply put in a styled <span> tag along with a “<” character. I did the same for the other button, just replacing the “<” with a “>”.

    Below is an example of one of the sites I made this change on, run through the compliance checking tool I use. As you can see at this point, there are no errors on the page.
    http://wave.webaim.org/report#/http://www.wmschools.org/calendar/

    My request at this point is if the developers of the plugin could please implement a solution like this so that the plugin can be compliant natively, without me having to jump in and edit the code every time the plugin is updated. It doesn’t need to be this solution exactly, as this is admittedly a bit of a rough fix, but if the buttons could be modified with ADA compliance in mind, it would make things a lot easier for sites that use this and have these requirements to meet.

Viewing 1 replies (of 1 total)