Kevin

Forum Replies Created

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • in reply to: Section 508/WCAG 2.0 Accessibility #43742
    Kevin
    Participant

    I noticed, thanks! I changed the base unit on the HTML element to % and still needed to override the page title H1/H2’s. One other thing you might want to think about for the theme setting plugin is to add the ability to use font units other than pixels. Other wise I think the changes you’ve made have been a great help!

    in reply to: Section 508/WCAG 2.0 Accessibility #43451
    Kevin
    Participant

    I guess I spoke too soon. The Cryout/Parabola theme setting plugin looks to be inserting its’s styles in the head of each page which still use px font units. I’m guessing I’ll still need to override these in the child css with !important statements until such a time as the plugin is updated.

    in reply to: Section 508/WCAG 2.0 Accessibility #43439
    Kevin
    Participant

    Hello,

    I’m am having an issue overriding the default font sizes in my child css. I’ve tried setting a high priority level when enqueuing the child css and it still seems to be overridden by the parent styles. I’d like to avoid adding !important to all the child font unit declarations.

    **I just saw the latest theme update has converted pixel font units to ems! Please disregard the above paragraph! **

    in reply to: Section 508/WCAG 2.0 Accessibility #39273
    Kevin
    Participant

    In addition to this code you gave me, I needed to add id=”s” to the search input field. Here is my final searchform.php code:

    <label for="s" class="screen-reader-text"><?php _e('Search for', 'parabola'); ?> </label>
    <form role="search" method="get" class="searchform" action="<?php echo esc_url( home_url( '/' ) ); ?>">
    	<input id="s" type="search" placeholder="<?php _e( 'SEARCH', 'parabola' ); ?>" name="s" class="s" value="<?php echo get_search_query(); ?>" />
    	<input type="submit" class="searchsubmit" value="" />
    </form>

    This was able to clear the WCAG/508 error for the form.

    in reply to: Section 508/WCAG 2.0 Accessibility #39270
    Kevin
    Participant

    I thought I had replied to this a couple days ago, but I guess it never went through.

    Thanks for the reply and the news that it will make it into the next update. When can I look for 2.0.3 to be released?

    I’m well versed in CSS so adding the underlines was trivial. I’m going to give the PostCSS plugin pxtorem a test to see if it can automate converting the fonts to relative units.

Viewing 5 posts - 1 through 5 (of 5 total)