It looks pretty nice, but the "select" element lacks a label, and as you have said in your previous post, the "assertive" value for the "aria-live" attribute is "rude".
A "polite" value looks more appropriate and the role "region" could be completed with an "aria-roledescription" attribute with a value like "notification" for example.
I read about aria-roledescription. I decided to update the role to alert and initially I thought to add value - "Details about cuisine" but then changed it to 'notification' as "Details about cuisine" was looking like repetitive information + was not useful for screenreaders
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
It looks pretty nice, but the "select" element lacks a label, and as you have said in your previous post, the "assertive" value for the "aria-live" attribute is "rude".
A "polite" value looks more appropriate and the role "region" could be completed with an "aria-roledescription" attribute with a value like "notification" for example.
Hey,
Oh!! yes. Thank you for highlighting missing 'label'.
let me explore on this -" role "region" could be completed with an "aria-roledescription" attribute with a value like "notification" for example."
I read about aria-roledescription. I decided to update the role to alert and initially I thought to add value - "Details about cuisine" but then changed it to 'notification' as "Details about cuisine" was looking like repetitive information + was not useful for screenreaders