Recommended Agency

text controls: text only | A A A

Sorry, our twitter status is currently unavailable, posted 33 minutes ago

RSS feed icon What is RSS?

blog archive.

October 2019


Displaying all 2 articles

Pointer Gestures - Understanding WCAG

Pointer Gestures - Understanding WCAG

A flash of online activity for me can tick off many a to-do: Need to make a payment? Internet banking. Shops closed and want an outfit for tomorrow? Online shopping with next day delivery. Parcel to track? Scan QR code and find it fast.

Picture going to do these things then finding you’ve been locked out while you watch your friends accessing everything with ease. For many of the 13.9 million disabled people in the UK, that’s how browsing the world wide web feels.

That’s where the Web Content Accessibility Guidelines (WCAG) comes in. If you haven’t heard of this it’s the Web Accessibility Initiative of the World Wide Web Consortium. Full of criteria we need to adhere to in order to make websites accessible to everyone with or without disability.

People with visual, auditory, motor, speech and cognitive disabilities rely on various assistive technologies and alternative methods of interaction to use digital documents, web and mobile apps. This is just one thing we must consider when creating a website.

From time to time we are going to select a WCAG2.1 success criterion to simplify in a blog. If you’ve ever browsed the guidelines you’ll understand why, it’s an overwhelming but amazing resource https://www.w3.org/WAI/standards-guidelines/wcag/

Let’s kick things off with pointer gestures. Here’s a snippet from WCAG:

Pointer Gestures (A)

Success Criterion 2.5.1: Pointer Gestures

All functionality that uses multipoint or path-based gestures for operation can be operated with a single pointer without a path-based gesture, unless a multipoint or path-based gesture is essential. (This requirement applies to web content that interprets pointer actions i.e. this does not apply to actions that are required to operate the user agent or assistive technology).

I’m guessing you’ve got questions…

 

What is a single-pointer gesture?

A tap, click, double tap, double click, long press, or click & hold (users needn’t concern themselves with direction/much movement)

 

What is a multi-point gesture?

A two-finger pinch zoom or a split tap where one finger rests on the screen and a second finger taps. These gestures are impossible for some users who may have no choice but to type with a single finger.

 

What is a path-based gesture?

A gesture that involves an interaction where it’s not just the endpoints matter such as swiping a carousel. Think about how you swipe, your thumb starts in one place (generally centrally - call that point 1) and ends in another (say to the left and in line with where it began - call it point 2) if your thumb starts at point 1 but goes all over the screen before landing at point 2, you won’t achieve the same result; it may not swipe or you may have triggered a link that’s taken you off to another page.

 

Why is this important?

Some people can’t perform gestures in a controlled manner so accuracy isn’t possible, or they might use a device like an eye-gaze system, or speech-controlled mouse emulator. These specialised or adapted input devices aren’t necessarily capable of performing multipoint or path-based gestures.

 

So what does this all mean?

The content can respond to multipoint or path-based gestures but an alternative method must be provided i.e. the play / pause controls that accompany a carousel or the plus and minus buttons used to zoom in and out on google maps. 

Worth noting this applies only to the web content so not the operating system or what users may need to do to operate their assistive technologies, that’s not the responsibility of those building the website.

If this has helped make things clearer, there's more ’WCAG made easy’ to come, so watch this space!

Jordana Jeffrey
Jordana

Created on Wednesday October 09 2019 08:02 AM


Tags:


Comments [0]








Surprising Screen Reader User Survey Results

Surprising Screen Reader User Survey Results

WebAIM (Web Accessibility In Mind), international web accessibility experts, conducted a survey over August and September 2019 in an effort to capture preferences of screen reader users. The survey was distributed worldwide and the second highest response, at 27%, came from Europe/UK participants.

Allergy information: If facts and figures trigger headaches and fatigue you may wish to hit the home button and see how else we can help you!

I’ll gently open with these statistics that will give you an idea of the participants involved in the survey:

71.3% exclusively rely on screen reader audio, further emphasising the need to consider these users in web design and development.

Surprisingly 12.4% of screenreader users don’t have a disability. Of the remaining 87.6% the majority are using this due to blindness, closely followed by low vision / visual impairment then deafness / difficulty hearing, after that was cognitive and motor difficulties.

15.8% reported multiple disabilities. 4.7% of respondents reported being both deaf and blind.

62.2% consider themselves advanced in terms of screen reader proficiency. Just 5.4% were beginners.

Most felt confident in using the internet. Compared to previous surveys this suggests screen reader users are becoming more accustomed to internet use.

Almost half of screenreader users were aged between 21 and 40.

 

Money Matters

Accessibility is about everybody with or without disabilities having the right to access the contents of the internet. Which begs the question, are screen reader solutions that charge a fee for use, excluding the less privileged who require assistive technology to benefit from online content?

Interestingly 37% downloaded their primary desktop / laptop screen reader free of charge from the internet while 22.7% bought it themselves. 13% were fortunate enough to have it provided by their employer.

The primary screen reader front runners were NVDA (NonVisual Desktop Access) and JAWS (Job Access With Speech). NVDA is a free, high quality screen reader, accessible to all https://www.nvaccess.org. JAWS provides speech and Braille output for the most popular computer applications on your PC. JAWS isn’t free which could be why for the first time in 10 years it is not the most popular choice.

 

Accessibility First

Many of the results were a very helpful reference for me as a designer especially as accessibility is a priority here at focus. Here are a few findings that may open your eyes to the importance of designing and developing with accessibility in mind.

Top 3 browsers used most often by survey respondents were: Chrome making up for nearly half at 44.4%, Firefox over a quarter at 27.4% and internet explorer 11 at 10.9% (just beating safari at 9.8%). Compared with previous results this shows a sharp increase in chrome usage and a continued decline in the others.

Over 5 times more participants access their screen reader using a windows operating system than than iOS.

Nearly all respondents had JavaScript enabled.

If a text-only or screen reader version of a web site is available the majority of those asked said they would seldom use it.

Mobile and tablet were the most popular choice of device, very closely followed by laptop then desktop. Proving once again that mobile accessibility should not be an afterthought.

Jordana Jeffrey
Jordana

Created on Tuesday October 01 2019 08:00 AM


Tags: accessibility screenreader survey webdesign webdevelopment


Comments [0]