Here we are in N – “what’s in a Name?”, part of the A to Z of Accessibility: Power Platform Edition. In this post we’ll be looking at the importance of Naming in what we develop and build. We’ll consider why naming is vital for accessibility and why it is just good dev practice.
This episode of A to Z of Accessibility is for The Evolution Experience.
This section could be easily have been dubbed “Progress Over Perfection” but I wanted to get this in early on so I could encourage and exhort you all to embark upon the expedition that is Accessibility.
This article is not tech specific so applies to everything.
Welcome, reader. I’m looking forward to continuing your training. This is the A to Z Accessibility: The Dark Side comes post!
Question: Are you a Dark Mode-r or a firm adherent to the Light Mode? Well, here at the Letter D I’m here to explore both – and neither.
So here we are at C in the A to Z of Accessibility – Power Platform Edition. In this first “C” post I want to look at the use of Colours, colours everywhere!
This applies to all areas of the Power Platform, yup even Dataverse. It also applies to anywhere that colour is used, so definitely one to pay attention to!
Introduction – What lies ahead I have been talking about Accessibility for a while now, and often link this to DELIVERY rather than BUILD. In this post, “Power Apps, Accessibility, and WCAG”, I’m going to bring all this together. I’m also going to tie it in to the Web Content Accessibility Guidelines (WCAG) around colour contrast. This post itself is going to be a fairly high-level overview of a Power Platform Solution I’ve written. The