When it comes to your hotel website accessibility the new laws require that anyone who is blind, deaf, prone to seizures and any disability have the right to use your website and get to the same outcome as an able bodied person.
There are two types of requirements and some properties have already gone through changes to accommodate handicapped guests with the addition of handicapped showers, ramps to room and wheel chair accessible rooms. Other properties, because of a number of reasons maybe exempt. It is up to each owner/general manager to understand if their property is required to have accessible rooms. Depending on the property will depend on how many of these rooms should be available.
The website at WheelchairTravel.org has a good chart on the number of rooms required in relation to the number of total rooms at a property. The chart above by Wheelchair Travel was assembled based on section 224 (specifically 224.2 and 224.4) of the 2010 ADA Standards.
The Web Content Accessibility Guidelines (WCAG 2.0)
– published on December 11, 2008.
The DOJ (Department of Justice) does not require a private business to be compliant. However at the State level you may find that there are different restrictions. This doesn’t stop you from being sued as when it comes to your website anyone searching from anywhere can come and stay and the website has to have certain requirements to be compliant.
Consists of 12 guidelines based on 4 principles: perceivable, operable, understandable and robust. WCAG compliance ensures that your website is accessible by everyone, irrespective of disabilities and age.
On June 5th 2018 the final version of WCAG 2.1 was released. https://www.w3.org/TR/WCAG21
This version added 17 new criteria that addresses a number of accessibility issues a many in regards to barriers on mobile devices. It still uses the A, AA and AAA conformance; it addresses mobile technology, low vision and people with connective disabilities.
A, AA, AAA, are levels of compliance and most private businesses are attempting to meet AA requirements.
– note that the guidelines can be interpreted differently but here are the most recent updates.
- Orientation – landscape or Portrait? – content must not restrict view and operation to a single display orientation. Some users have fixed orientation views such as attached to a wheelchair. Therefore content must be available in both landscape and portrait mode.
- Identify Input Purposes – add information that identifies what the input field is for, for example email sign up, booking form fields. Helps people with cognitive disabilities understand and use form inputs.
- Reflow – avoid horizontal scrolling. A large number of people with low vision need to increase their screen size often more than 200%. Scrolling increases the effort to read by 40 to 100 times. Keep vertical scrolling content at a width equivalent to 320 CSS pixels, horizontal scrolling content at a height equivalent to 256 pixels.
- Non-Text Contrast – visual presentations should have a contrast ratio of at least 3:1, meaning that the contrast for text or graphics need to have enough contract for a low vision person to see them on the screen.
- Text Spacing – text needs to have adequate space between lines and letters. Low vision users need to be able to override paragraph spacing, letter spacing, word spacing and line height.
- Content on Hover or Focus – content that only appears on mouse overs or on focus can present challenges for users with low vision where their mouse accuracy might not be great.
- Character Key Shortcuts – Applies to mobile. Helps users who rely on speech-to-text technologies to interact with content without inadvertently triggering some functionality based on a a shortcut. Like a keyboard shortcut.
- Pointer Gestures – requires that all functionality that uses multipoint or path-based gestures for operation can be used with a single pointer. Applies to mobile, to help users who cannot accurately perform complex pointer gestures such as touchscreen swipes, or two finger pinch/zoom.
- Pointer Cancellation – functionality that can be operated using a single pointer to help people inadvertently initiate touch or mouse events with unwanted results. Helps reduce the chance that a control will be activated accidentally.
- Label in Name –mobile, helps users who rely on speech to text technologies to interact with content and submit things like forms.
- Motion Actuation – mobile, having to tilt or shake for an action to take place. The device maybe mounted and not possible to move.
- Status Messages – making sure that error or success messages can be easily seen. Users who are bling or have low vision may not be able to see success messages.
- Identify Purpose – add the context, to meaning of symbols, regions, buttons, links and fields so that the user agent knows what to do with them.
- Animations from Interactions – motion animation should be able to be disabled unless the animation is essential to the functionality. Some people find animation on a page will give them nausea, headaches and dizziness so it need to be able to be disabled.
- Warning of timeouts – users are warned of the duration of any user inactivity that could cause data loss, unless the data is preserved for more than 20 hours when the user does not take any actions.
- Target Size – ensure that the target for pointer inputs is at least 44 by 44 pixels in most cases.
- Concurrent Input Mechanisms – make sure people can switch from different modes of input when interacting with the web content.
Consequences of not being compliant
There are a variety of cases and top hit states include FL, NY and CA. You can find open cases in https://dockets.justia.com this site gives you a list of people who have ADA lawsuits in any state.
On June 22nd, 2018
A group of 103 members of the House of Representatives asked the DOJ to curb website accessibility lawsuits until formal regulations are adopted.
Many of the cases are being made by the same group of people.
Limit your liability because you cannot be 100% compliant as the target is constantly moving and changing. Private businesses are being sued even though the DOJ said they don’t have to be compliant. When you have a case against you then you have to hire a lawyer to fight for your right and it can still costs a lot of money.
The goal is to try avoiding being sued so that you are not a target. You need to contact your webmaster to make sure they are taking care of this as you are the one who is responsible not the webmaster.
Listed below are some of the basics that need to be covered.
- Keyboard navigation instead of mouse
- Alt tags that describe the images in posts and webpages, including logos, rooms etc.
- Text spacing in paragraphs
- Contrast of colors on the website for text
- Text transcripts of videos
- Buttons and icons have text describing them
- No scrolling side to side
- Text that can be zoomed
- pdfs – able to be read by a screen reader
On your rooms pages you should identify the rooms that are available and the amenities in those rooms for disabled guests. If you don’t have to comply then you should also mention that on the page.
Your booking engine has to identify your ADA rooms and make them available to ADA guests. At any point your last room to be booked should be the ADA room so it is available should an ADA guest want to book.
Tools & Resources
- https://achecker.ca/checker/index.php – a web based checker to look at pages of your site and give you feedback.
- Google Chrome Accessibility Audit tool
- Koa11y – an open source desktop application
- https://helpx.adobe.com/acrobat/using/create-verify-pdf-accessibility.html – pdf accessibility.
Be aware that no webmaster can guarantee your site is 100% compliant but you do need to make changes to bring your website in line as much as possible.