We’ve made the ViewMedica website to be accessible to the widest possible audience by conforming to the Worldwide Web Consortium (W3C) Web Content Accessibility Guidelines. It’s our goal to comply with Level AA and Level AAA compliance, as practicable.
The website works with screen reading software.
Programming used on this site complies with W3C standards for HTML and CSS. That makes sure our site displays correctly in current and future browsers. We use complete start and end tags, nest elements according to specifications, and use unique attributes and IDs. This helps assistive technologies understand page content.
All non-text content, images, have text alternatives that conveys the same information. This helps screen readers transmit information to the user in place of the image.
We use ARIA landmarks to identify regions of the page. This helps screen readers jump to different sections of the page.
Our pages have a skip to main content link. This lets users jump directly to the page’s main content.
Forms connect labels with form controls helping screen readers properly convey the form elements to the user.
We use the proper markup for headings and lists which helps screen readers understand the design structure of the webpage. CSS controls formatting of text, opening up control of the text display to assertive technologies.
We avoid the use of text in images so user agents can read aloud all text and assistive technologies can apply custom style sheets.
People unable to use a mouse can still navigate our site. Keyboard controls and other assistive devices work well.
We do not allow anything on the site to flash more than three times in any one second period (this includes red flashes). Flashing images are known to cause seizures.
Our pages have titles describing their topic or purpose. The title identifies the Web page without having to read what’s on the page. When descriptive titles are used with link text, users can find the content they are interested in.
Most of our site components allow for highlighting by the user agent when they receive focus.
The default human language of each page is set. Speech synthesizers supporting multiple languages can adapt to the pronunciation and syntax to the language used.
When a page component receives focus, it does not initiate a change of context, i.e. forms aren’t submitted automatically and new windows do not launch when a component receives focus.
Navigation is placed consistently and predictably throughout our website.
In forms, if an error is made, the problem is identified and described to the user in text.
Adhering to accessible guidelines is our priority. However, there may be parts of our site that do not meet certain standards.
We are working to achieve Level AA and Level AAA conformance to the Web Content Accessibility Guidelines (WCAG) 2.1, as practicable.
If you’re unable to access parts of our website, please contact us.