Thank you for the reply! The video is definitely helpful, but I guess I'm wondering if there's any info out there written by folks with visual disabilities, about how to name UI elements etc, so that an app or webpage is easy to use for them?
I feel like i'm missing the non-technical part of the discussion—which naming conventions, etc, I should use for my UI elements. ie, do I describe what a button does, or just call it a "completion button." The nitty-gritty stuff of actual implementation I guess.
I'm a self-taught Front End & JS Dev and professional learner with accessibility expertise. I'm passionate about breaking down concepts into relatable concepts, making it more approachable.
To be honest, I am not an iOS developer, so I hope this doesn't get lost in translation. But I would say try your best to not overanalyze how elements render. Ultimately, whatever you do the best thing you can do for a11y is to render things that are semantic. For example, <button> and <main> are semantic and <div> is not. If you use the most semantic rendering, screen readers tend to take away a lot of the heavy lifting for you.
There is some nuance with more custom components and this is where manual testing and learning common screen reader commands come in handy. (Stay tuned for this, this will be my next post)
Thank you for the reply! The video is definitely helpful, but I guess I'm wondering if there's any info out there written by folks with visual disabilities, about how to name UI elements etc, so that an app or webpage is easy to use for them?
I feel like i'm missing the non-technical part of the discussion—which naming conventions, etc, I should use for my UI elements. ie, do I describe what a button does, or just call it a "completion button." The nitty-gritty stuff of actual implementation I guess.
To be honest, I am not an iOS developer, so I hope this doesn't get lost in translation. But I would say try your best to not overanalyze how elements render. Ultimately, whatever you do the best thing you can do for a11y is to render things that are semantic. For example,
<button>and<main>are semantic and<div>is not. If you use the most semantic rendering, screen readers tend to take away a lot of the heavy lifting for you.There is some nuance with more custom components and this is where manual testing and learning common screen reader commands come in handy. (Stay tuned for this, this will be my next post)
Thank you! I look forward to your next post!