VisitDays Accessibility Statement
VisitDays is committed to creating products that ensure universal access for all users, and are committed to providing a website that is accessible to the widest possible audience, regardless of circumstance and ability.
Our team is continually monitoring and improving accessibility issues as they are identified. Currently, the VisitDays platform and applications overall support Level A accessibility compliance and partial support for Level AA accessibility compliance. Some applications are Level AA compliant.
VisitDays works with industry leaders, such as Tech for All Consulting (TFA), an independent third-party auditor, to evaluate accessibility support and develop an accessibility roadmap to ensure fuller accessibility compliance.
Screen-reader and keyboard navigation
Our website implements the ARIA attributes (Accessible Rich Internet Applications) technique, alongside various different behavioral changes, to ensure users visiting with screen-readers are able to read, comprehend, and enjoy the website’s functions, as well optimizing keyboard navigation for those with limited mobility. Here’s how our website covers some of the most important screen-reader requirements, alongside console screenshots of code examples:
Screen-reader optimization: we utilize multiple background scanners that learns the website’s components from top to bottom to ensure ongoing compliance as the website gets updated. In this process, we provide screen-readers with meaningful data using the ARIA set of attributes. For example, we provide accurate form labels; descriptions for actionable icons (social media icons, search icons, cart icons, etc.) and images; validation guidance for form inputs; element roles such as buttons, menus, modal dialogues (popups), and others.
These adjustments are compatible with all popular screen readers, including JAWS and NVDA.
Additionally, keyboard users will find quick-navigation and content-skip menus, available as the first element of the site while navigating with the keyboard. We also handle triggered popups by moving the keyboard focus towards them as soon as they appear, and not allow the focus to drift outside of it (i.e. focus traps).
The following accessibility features may improve accessibility for users with disabilities:
Browser and Assistive Technology Compatibility
We aim to support the widest array of browsers and assistive technologies as possible, so our users can choose the best fitting tools for them, with as few limitations as possible. Therefore, we have worked very hard to be able to support all major systems that comprise over 95% of the user market share including Google Chrome, Mozilla Firefox, Apple Safari, Opera and Microsoft Edge, JAWS and NVDA (screen readers), both for Windows and for MAC users.
These applications utilize various technologies that are meant to make it as accessible as possible.
We firmly believe that the best way to address these limitations is to improve upon the current applications and consider all new features with respect to accessibility concerns during design, development, and quality assurance. We continually reduce and eliminate use of 3rd party tools and components that are non-compliant, and build new features that immediately conform to WCAG 2.1 specifications without the need for an overlay.
Formal Testing Processes
The VisitDays formal testing processes to determine accessibility compliance includes internal review as well as independent review by expert auditors.
The internal audit is performed by internal VisitDays staff as well as a contracted quality assurance team as part of the systems development lifecycle in accordance with the WCAG 2.1 (Level AA) through code analysis, peer review, automated regression testing and manual functional testing.
The independent audit evaluates the VisitDays Applications to assess its conformance with the WCAG 2.1 (Level AA) Accessibility Guidelines. In the course of this evaluation, the architecture of the web site including the design and development approach and relevant accessibility issues is reviewed.
The objective is to provide accessibility guidance based upon expert testing to identify barriers for people with disabilities and to identify those issues that when addressed can improve usability of the web site for people with disabilities.
The accessibility assessment is conducted according to the following steps:
An accessibility expert conducts an overall technical analysis to identify issues of technical compliance that would affect mobility impaired, deaf/hearing impaired, and low vision users. The evaluator inspects each screen using assistive tools, such as Google Chrome browser’s WAVE and ANDI toolbars. Code analysis is conducted using tools such as the browser Developer Tools.
Keyboard accessibility analysis (for mobility and physically impaired users) is conducted by attempting to thoroughly navigate the web site through the keyboard without using a mouse in Google Chrome.
Speech access analysis (for mobility and physically impaired users) is conducted using Dragon Individual Professional in Google Chrome.
For deaf and hard of hearing users, any audio content is assessed for proper captioning.
The accessibility for low vision users is evaluated three ways: (1) using the screen magnification, palette, and contrast controls provided by the operating systems; (2) using the font resizing capability offered by the browser, (3) using Color Contrast Analyzer version 2.2, and (4) ZoomText low vision software.
An evaluator who is legally blind conducts the screen reader testing. The goal is to identify accessibility barriers that are likely to be experienced by users who are blind. The evaluator works through the web site using tools such as the NVDA screen reader with Google Chrome, JAWS for Windows, and VoiceOver for Mac. Any pages found to have screen reader issues were re-examined in interactive sessions with a sighted evaluator.
Any usability issues for users with disabilities encountered during the accessibility assessments in the above Steps are noted for subsequent mention and sent to the Product Owner for consideration and scheduling within VisitDays’ accessibility roadmap.
Attached to this statement is the VisitDays accessibility roadmap, which includes timelines for resolving existing accessibility barriers.
The following are possible accessibility barriers with interim workarounds:
Possible Accessibility Barriers
VisitDays is committed to transparency with our accessibility compliance to better serve all users. To that end, users may potentially experience the following accessibility barriers within our applications on some pages:
Lack of meaningful semantic organization such as landmark regions, hierarchical heading structure
Lack of programmatic labels for form elements
Color contrast below the 4.5:1 minimum; some content is user-generated, and cannot be guaranteed
Varied visual focus indicators on interactive elements
Form errors can be vague for limited vision users
Page titles not reflecting both the site name as well as specific purpose of the current page
Icons, buttons, and other non-text elements lacking text equivalents, particularly with user-generated content
Some modals allow keyboard navigation outside of the modal window (no keyboard trap) and modals lack an explicit mechanism to close or exit
Notes, Comments, and Feedback
Despite our very best efforts to allow anybody to adjust the website to their needs, there may still be pages or sections that are not fully accessible, are in the process of becoming accessible, or are lacking an adequate technological solution to make them accessible. Still, we are continually improving our accessibility, adding, updating, and improving its options and features, and developing and adopting new technologies.
VisitDays is committed to handle accessibility questions and concerns, including accessibility-related assistance or the need for alternative formats of documentation and any accessibility problems. We have dedicated team members to handle these requests. Please direct any questions or concerns to the main point of contact Michael Moore, Chief Technology Officer, email@example.com.