Professional Documents
Culture Documents
The Web Content Accessibility Guidelines (WCAG) is a set a guidelines for how to make websites
accessible. The second version was published in 2008, before websites were available on mobile devices
in any meaningful way.
A few months ago, the WCAG was updated to version 2.1, which includes a whole new section on
guidelines for mobile accessibility. There are several new mobile-specific rules, such as rule 1.3.4, that
“content should not restrict its view and operation to a single display orientation, such as portrait or
landscape, unless a specific display orientation is essential.”
In this article, I will cover some of the new guidelines that relate to interactive elements on a web page.
Due to this dynamic handling of mobile devices, this guideline suggests to create interfaces that are
flexible. For example, it may be easy to think that placing a call-to-action in the bottom right corner is
best because most users may use their device with their right hand. However, this would be the most
inconvenient place to put it for left-handed users. A better placement for a critical call-to-action could be
spanning the entire width of the viewport.
https://bitsofco.de/tips-for-making-interactive-elements-accessible-on-mobile-devices/?fbclid=IwAR1CxNdc0iDC2w_Q1Dx60iv7zeSTu_Zl-zdd7PrmkxB… 1/8
3/17/2019 Tips for making interactive elements accessible on mobile devices
The best way to convey that an element is actionable is by relying on convention and what actionable
elements are expected to look like. For example, links are typically underlined and/or have a distinct
colour from the body text and buttons are usually a rectangular shape with rounded corners.
We can also use the position of an element to convey it’s use. The navigation, for example, is typically at
the top of the page for conventional websites. For mobile devices, a navigation fixed to the bottom of the
viewport is also common.
https://bitsofco.de/tips-for-making-interactive-elements-accessible-on-mobile-devices/?fbclid=IwAR1CxNdc0iDC2w_Q1Dx60iv7zeSTu_Zl-zdd7PrmkxB… 2/8
3/17/2019 Tips for making interactive elements accessible on mobile devices
On Instagram desktop, the navigation is at the top of the page, whereas on mobile, it is in a bar at the bottom of the viewport
A good example of this is the pull to refresh gesture. Unless there is some indication that this gesture is
possible, users will never interact with it. On mobile twitter, they have an icon that pops up when the user
scrolls to the top of the page, showing that there is an interaction available if they pull up more.
https://bitsofco.de/tips-for-making-interactive-elements-accessible-on-mobile-devices/?fbclid=IwAR1CxNdc0iDC2w_Q1Dx60iv7zeSTu_Zl-zdd7PrmkxB… 3/8
3/17/2019 Tips for making interactive elements accessible on mobile devices
Scrolling up on a profile page on Twitter mobile will reveal an icon to pull to refresh
According to guideline 2.5.5, actionable elements should generally have a size of at least 44px by 44px,
unless the target element is inline within a block of text.
https://bitsofco.de/tips-for-making-interactive-elements-accessible-on-mobile-devices/?fbclid=IwAR1CxNdc0iDC2w_Q1Dx60iv7zeSTu_Zl-zdd7PrmkxB… 4/8
3/17/2019 Tips for making interactive elements accessible on mobile devices
<a href="/"><img src="/home/png" alt="Home icon"></a>
<a href="/">Home</a>
Not advisable
1. It reduces the touch target space, since the space between the two links will not be clickable
2. It increases the number of elements that would need to be traversed through for a keyboard user. If
navigating the page by tabbing on the keyboard, this duplication could become tedious if repeated
numerous times
A better alternative would be to group both elements under the same interactive link.
<a href="/">
<img src="/home/png" alt="Home icon">
Home
</a>
Better!
This not only increases the touch target size for the link, it reduces the number of links that will need to be
navigated through on the page.
For example, if a numeric input is required, we can use a number-only keyboard layout by specifying the
type on the <input> element.
<label>
How old are you?
<input type="number">
</label>
https://bitsofco.de/tips-for-making-interactive-elements-accessible-on-mobile-devices/?fbclid=IwAR1CxNdc0iDC2w_Q1Dx60iv7zeSTu_Zl-zdd7PrmkxB… 5/8
3/17/2019 Tips for making interactive elements accessible on mobile devices
In some cases, we need the type of the <input> element to be one thing, e.g. text, but we still want to
restrict the keyboard layout to a numeric one. This can be achieved using the inputmode attribute, which
allows us to specify what particular keyboard layout we want for the input, regardless of the input type.
<label>
How old are you?
<input type="text" inputmode="numeric">
</label>
At the time of writing, the inputmode attribute is not very well supported.
In places that need text entry, we can try to automatically fill out information. For example, by pulling
location data to fill out addresses.
Email Address*
← →
Revisiting the abbr element Removing duplicate objects from an Array
accessibility (is hard)
javascript
bitsofcode. Articles on Frontend Development. All articles are written by Ire Aderinokun, Frontend Developer
and User Interface Designer.
Follow @ireaderinokun
https://bitsofco.de/tips-for-making-interactive-elements-accessible-on-mobile-devices/?fbclid=IwAR1CxNdc0iDC2w_Q1Dx60iv7zeSTu_Zl-zdd7PrmkxB… 7/8
3/17/2019 Tips for making interactive elements accessible on mobile devices
https://bitsofco.de/tips-for-making-interactive-elements-accessible-on-mobile-devices/?fbclid=IwAR1CxNdc0iDC2w_Q1Dx60iv7zeSTu_Zl-zdd7PrmkxB… 8/8