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)
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!