# Touch target 48dp **URL:** \ **Category:** Questions about Thunkable X\ **Created:** [January 3, 2024, 9:52am UTC](https://community.thunkable.com/t/touch-target-48dp/2766768 "2024-01-03T09:52:49Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![peterjamesleniq](https://avatars.discourse-cdn.com/v4/letter/p/9fc348/32.png) [@peterjamesleniq](https://community.thunkable.com/u/peterjamesleniq)\ **Post date:** [January 3, 2024, 9:52am UTC](https://community.thunkable.com/t/touch-target-48dp/2766768/1 "2024-01-03T09:52:49Z")
I have this Recommendation message for my new app from Android Play Store. I’m wonder how I change the dp from 26 to 48. The issue is minor I guess. Also, what is the difference between 26 and 48 dp? Does it really matter. Thanks ![Untitled](https://us1.discourse-cdn.com/flex015/uploads/thunkable/original/3X/a/f/af8a6b6f1a0dd4e8433c63e5b50551d4c8ebfda4.png) ---
**Author:** ![emlee703](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/emlee703/32/165400_2.png) [@emlee703](https://community.thunkable.com/u/emlee703)\ **Post date:** [January 3, 2024, 12:51pm UTC](https://community.thunkable.com/t/touch-target-48dp/2766768/2 "2024-01-03T12:51:29Z")
Mystery… Did you click the “Learn more” button in the recommendation? Also try this link: [android - What package to download for material design icons? - Stack Overflow](https://stackoverflow.com/questions/35506714/what-package-to-download-for-material-design-icons) ---
**Author:** ![peterjamesleniq](https://avatars.discourse-cdn.com/v4/letter/p/9fc348/32.png) [@peterjamesleniq](https://community.thunkable.com/u/peterjamesleniq)\ **Post date:** [January 3, 2024, 1:41pm UTC](https://community.thunkable.com/t/touch-target-48dp/2766768/3 "2024-01-03T13:41:33Z")
Yep, I read a few things on it. But I still don’t really understand it. Are they saying they just want a border around the Web Viewer? > **[Material Design](https://m2.material.io/design/usability/accessibility.html#layout-and-typography:~:text=resource%20page.-,Pointer%20targets,-Pointer%20targets%20are)** > > Build beautiful, usable products faster. Material Design is an adaptable system—backed by open-source code—that helps teams build high quality digital experiences. > **[Touch target size - Android Accessibility Help](https://support.google.com/accessibility/android/answer/7101858?hl=en)** > > Any on-screen element that someone can click, touch, or otherwise interact with should be large enough for reliable interaction. Consider making sure these elements have a width and height of at least ---
**Author:** ![emlee703](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/emlee703/32/165400_2.png) [@emlee703](https://community.thunkable.com/u/emlee703)\ **Post date:** [January 3, 2024, 1:51pm UTC](https://community.thunkable.com/t/touch-target-48dp/2766768/4 "2024-01-03T13:51:15Z")
Still a mystery… Still don’t know, but it’s not a huge issue I guess… If you want to figure out how to do this, maybe you can ask Thunkable Staff… ---
**Author:** ![matt\_conroy](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/matt_conroy/32/150843_2.png) [@matt\_conroy](https://community.thunkable.com/u/matt_conroy)\ **Post date:** [January 3, 2024, 3:15pm UTC](https://community.thunkable.com/t/touch-target-48dp/2766768/5 "2024-01-03T15:15:45Z")
> [@peterjamesleniq](#): > > Are they saying they just want a border around the Web Viewer? Material Design (and Apple’s [Human Interface Guidelines](https://developer.apple.com/design/human-interface-guidelines)) are near and dear to my heart. Happy to discuss this more. First thing to point out, this is just a recommendation from Google. You can still publish your app as is. Adhering to Material Design Guidelines or HIG is all about accessibility and inclusivity in your app. With touch target size, they are suggesting that the “clickable” area around any clickable element be at least 48dp (pixels per inch), even if the element is smaller than that. With a button, for example, if it is smaller than 48x48 dp, Material Design recommends creating a clickable area around that button. Your web viewer component is larger (much larger) so my guess is that they are referring to some content being viewed within the web viewer itself. Can you share a screenshot of what is in there on your built app? ---
**Author:** ![peterjamesleniq](https://avatars.discourse-cdn.com/v4/letter/p/9fc348/32.png) [@peterjamesleniq](https://community.thunkable.com/u/peterjamesleniq)\ **Post date:** [January 3, 2024, 4:58pm UTC](https://community.thunkable.com/t/touch-target-48dp/2766768/6 "2024-01-03T16:58:26Z")
Hi Matt, thanks. So all those little red boxes, in each of the 4 examples, are the reason for this. Previously the explanatory video would launch automatically, but now the user will have to click a button to watch a video, hoping that that would solve the issue. But it now seems the issue is with youtube. Is that right? Or is there something I can do? ![Untitled](https://us1.discourse-cdn.com/flex015/uploads/thunkable/original/3X/7/6/76edf1251f71f4949f578eca0dc13e8f2d11210b.png) ---
**Author:** ![matt\_conroy](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/matt_conroy/32/150843_2.png) [@matt\_conroy](https://community.thunkable.com/u/matt_conroy)\ **Post date:** [January 3, 2024, 5:03pm UTC](https://community.thunkable.com/t/touch-target-48dp/2766768/7 "2024-01-03T17:03:11Z")
Correct, the issue is how the elements the video itself are displaying. Not much we can do about that. ---
**Author:** ![system](https://us1.discourse-cdn.com/flex015/uploads/thunkable/original/3X/0/f/0f59f292712368bce16ff80133ae10de8a6f27e8.png) [@system](https://community.thunkable.com/u/system)\ **Post date:** [April 2, 2024, 5:05pm UTC](https://community.thunkable.com/t/touch-target-48dp/2766768/9 "2024-04-02T17:05:24Z")
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.