From the course: Using Stark for Accessible Design Projects
Unlock the full course today
Join today to access over 23,200 courses taught by industry experts.
Checking touch targets - Stark Tutorial
From the course: Using Stark for Accessible Design Projects
Checking touch targets
- [Instructor] Nothing irritates me more than tapping on a button or link on my phone and nothing happens. This inevitably requires me to zoom in on the offending element and then tap it to get where I want to go. The Touch Targets tool in Stark quickly identifies the offenders and asks you to make adjustments. Why are touch targets important? There are a number of reasons and all are based around the user. They're helpful for users with mobility, dexterity, and fine motor disabilities. Other users to keep in mind are users with one hand or maybe even use a part of their finger or fingers. This tool is also useful for those with low vision who have difficulty seeing the interactive element. So, if I go through the touch targets here (keyboard clicking) and I'm just going to move it over, you can see that there are a number of issues on this site. And a prime offender is right here. These icons. The standard size should be at least 48 by 48 pixels, not 40 by 40, with at least eight to…
Contents
-
-
-
-
(Locked)
Conducting a WCAG audit4m 30s
-
(Locked)
Using the contrast checker3m 59s
-
(Locked)
Using the type checker3m 38s
-
(Locked)
Using the ALT text tool2m 6s
-
(Locked)
Checking touch targets2m 19s
-
(Locked)
Setting and correcting focus order1m 24s
-
(Locked)
Stark Landmarks2m 42s
-
(Locked)
Using the Vision Simulator2m 51s
-
(Locked)
Using the Headings tool1m 46s
-
(Locked)
Using Sidekick5m 46s
-
(Locked)
Automatic monitoring1m 2s
-
(Locked)
-
-