Forum Discussion
WCAG 2.5.5 Target size - with different screen resolutions
Thank you for the reply Phil. I understand the need for the button to be big enough, but it's just tricky to make sure that the dimensions are going to be correct - even in a lot of the training from Articulate, it mentions the 44 x 44px, but then seems odd to not have an explanation how to achieve this, so we know we are compliant. When designing buttons, I do use common sense, I just wondered if there was something easier to help with that.
The only way you can guarantee this, is to determine the minimum device size that you are supporting. For example, if you had a tablet device, you may see the button at 44x44 in landscape view, but rotate to portrait, and the view scales and the button size would be reduced significantly.
So, if you determine the minimum device size is 1024x768, and landscape view, ensure your button is 44x44 at this minimum view, and then anything else beyond that will be larger.
You just need to make this clear to end users. It's not ideal, but since Storyline is not responsive, it is the only way you can ensure content will be accessible and meet the WCAG guidelines.
