I plan for the website to be fully accessible by Aug. 1, 2020, if not sooner.
Commitment to Accessibility
As someone who provides training to web designers and developers on website accessibility and provides accessibility services through my client-based business, I need to practice what I preach. I am committed to making this website accessible and in compliance with Web Content Accessibility Guidelines (WCAG) and good usability practices.
Steps Being Taken
- I am in the process of creating a custom theme myself that is more accessible than the one in use on the site now. I’ve notified the developers of the current theme about some of the issues I’ve found.
- I am also checking the site for accessibility issues and correcting them as I find them. I then plan to have the site tested by another accessibility professional.
- I periodically check the site with a screen reader and will continue to do so when any new functionality is added.
- I have added explanatory text to hyperlinks specifically for screen readers, so that those users can easily distinguish hyperlinks with the same link text from one another and understand the purpose of hyperlinks.
If you need help accessing content on the site, would like to report issues or have a question, please get in touch.
These are known issues of what I’ve checked so far. I will update this list as I find issues that I do not immediately fix.
- On the Podcast page, the episode images and “Read more” links are adjacent links. The new custom theme I am building will eliminate this issue.
- Some signup forms do not have labels associated with fields. These are MailerLite forms, and I must manually modify them. I have also alerted MailerLite about this issue and asked that they add labels to fields on all of the forms they create for use on customers’ websites.
- I am checking that essential images have appropriate Alt-text and that decorative ones have null Alt-text.
- There are some lingering contrast issues.
- I will be checking that hyperlinks that open in a new window warn all users first or I will prevent them from doing so at all.