Showing results for 
Search instead for 
Did you mean: 
Helper V
Helper V

Standards for coining Accessible Labels

Hello All,


I had never had to really deal with this ever in the past. But now, we do have visually impaired users who would be using the app I am building. Since I have about 271 warnings right now about it, I just want to get it right starting from label1.  This may sound trivial but it suddenly is a huge thing for us to get it right. 


For example: How long can the Accessible Label description be? If I have say, a First Name and Last name Text Boxes/Labels on the screen, do we label it as  "Enter First Name" or would just 'First Name' be fine? Would the width of the label now somehow suddenly  be dependent on the length of the Accessible Label.text. Meaning, If I have First Name as my label text on the screen  BUT If I have 'Enter First Name' as my accessible label', how do I know its not looking awry for the visually impaired audience? So, should I always set my Label width in accordance with the length of the Accessible Label text then?


Please let me know what's a good etiquette to coin these Accessible Label properties? Also, do we normally account for label widths on the form, based off of the lengths of these AC descriptions?




Helpful resources

PA User Group

Welcome to the User Group Public Preview

Check out new user group experience and if you are a leader please create your group


Demo Extravaganza is Back!

We are excited to announce that Demo Extravaganza for 2021 has started!

MBAS on Demand

Microsoft Business Applications Summit sessions

On-demand access to all the great content presented by the product teams and community members! #MSBizAppsSummit #CommunityRocks

Power Apps June 2021

June Power Apps Community Call

Don't miss the call this month on June 16th - 8a PDT

Top Solution Authors
Top Kudoed Authors
Users online (47,893)