We Are Committed to Accessibility
What We Strive For and How We Do It
We want to make our web content open and accessible for everyone! Our website is built on WordPress, a popular content management system, using the Icelander theme from Webman Design. After thorough testing, we have determined that this affords us the best combination of robust features, polished layouts and accessibility. We endeavor to make all of our web content conform to the Web Content Accessibility Guidelines (WCAG) 2.1 Levels A/AA.
Known Issues
While we have selected a theme for our website that is "accessibility-ready" there are still a few issues we have identified and are in the process of addressing. These issues may affect particular users with specific hardware and software combinations. Following is a list of the known issues, the impact, and our plan to resolving them as quickly as possible
Issue: Duplicate H1 Headers
Duplicate H1 headers are present on the landing page of our website.
What is the user impact?
This issue may impact screen reader users. The user will encounter two H1 tags, one before the top-level primary menu and then again right after the start of the main content on the page. While the first H1 tag should be H2, the impact for the user will be minimal as it does not block their ability to access or understand the page content and layout nor does it prevent the user from making use of a screen reader's built-in feature to use headers for page navigation.
What pages are affected?
This issue is found on the home page of our website.
What WCAG Criteria applies?
What are we doing about it?
As the theme was developed by a third-party, we have submitted a support ticket with the developer to address this issue in a future theme update. Once the theme is updated to address this issue, we will apply the update to our site.
Issue: Menu Button
When pages are displayed on a tablet or mobile device the responsive layout will collapse the top-level menu navigation links into an expandable menu button. Some screen readers, such as JAWS, VoiceOver and TalkBack, allow for navigating the page via a 'virtual cursor'. This means the screen reader cycles through the page content while the keyboard input focus does not change. For example, when using JAWS this would occur when using the arrow keys to navigate page content. When navigating the page using the virtual cursor, the focus does not remain within the expanded menu and moves to the page content which is hidden behind the visually displayed menu. If using the tab key on the keyboard, the focus cycles through the elements in the expanded menu and stays there until the user decides to collapse the menu or select a navigation link.
What is the user impact?
This may impact some screen reader users (specifically JAWS, VoiceOver and TalkBack users) as the focus may move outside of the open menu and into the page content. This can confuse some users if they are unaware they have navigated outside the current menu. This can be avoided by using the tab key to navigate the menu on a desktop computer while using JAWS. For mobile devices using VoiceOver or TalkBack, this issue will occur if the user 'swipes' past the open menu without selecting a menu link or choosing to close the menu.
What pages are affected?
This issue appears on all pages when the tablet and mobile responsive layouts are active.
What WCAG Criteria applies?
What are we doing about it?
As the theme was developed by a third-party, we have submitted a support ticket with the developer to address this issue in a future theme update. Once the theme is updated to address this issue we will apply the update to our site.
Issue: Video Player Controls
Some pages use an embedded media player that has a control bar that appears at the bottom for the player. Once the video is started the control bar may visually disappear. When using the Tab key to navigate back to the control bar, the control bar may stay hidden and prevent the user from identifying the current input focus within the control bar.
What is the user impact?
This may impact keyboard only users if they try to tab back into the media player control bar after a video has started.
What pages are affected?
This issue is present on all pages that use the embedded media player.
What WCAG Criteria applies?
What are we doing about it?
The embedded video player is provided by a third-party. We have submitted a support ticket with the developer to address this issue. Once this issue is addressed by the third-party the update will be automatically applied to our site.
How to Reach Us
If you encounter any issues accessing our website, please contact us at info@convergeaccessibility.com and we will be sure to reply within one business day. We look forward to any feedback for improving the accessibility of our content.