Couple suggestions to fix accessibility
-
Hi there; I’ve been trying to get my child theme to validate using an accessibility checker, and I’ve had to make a few tweaks to the code. Thought I’d list them here in case anyone else is working on this too..
In /framework/agama-functions.php I’ve had to change the H3 here to an H2 to solve a header nesting problem (using the grid layout for the blog)
<h2 class="assistive-text"><?php _e( 'Post navigation', 'agama' ); ?></h2>
In /framework/class-agama-frontpage-boxes.php I’ve had to change
echo '<em class="fa '. $box[1]['icon'] .'"></em>';
to add em instead of an i element, and adjust the style sheet to use the em instead of i element.In /framework/agama-functions.php I’ve had to adjust all the <i> tags in the agama_render_blog_post_meta() function to use instead.
In footer.php I had to do the same:
<?php echo sprintf( '<a id="%s"><em class="%s"></em></a>', 'toTop', 'fa fa-angle-up' ); ?>
replacing i with em and adjusting the style sheet.Finally, as an aside, the post meta colours are too light to meet the contrast guidelines:
.entry-header .single-line-meta, .entry-header .single-line-meta a { font-family: Crete Round; font-size: 13px; padding: 5px 15px; color: #aaa; }
Fixing all these allows the theme to meet AA level standards, but such heavy modifications to my child theme make me nervous that future parent-theme updates may cause issues. Can I suggest that you fix the parent theme in a future release so it no longer uses italics tags, and nests that one H3 as an H2 instead? Thanks.
- The topic ‘Couple suggestions to fix accessibility’ is closed to new replies.