Embark on a journey of knowledge! Take the quiz and earn valuable credits.
Take A QuizChallenge yourself and boost your learning! Start the quiz now to earn credits.
Take A QuizUnlock your potential! Begin the quiz, answer questions, and accumulate credits along the way.
Take A QuizKindly log in to use this feature. We’ll take you to the login page automatically.
LoginGeneral Tech Technology & Software 3 years ago
User submissions are the sole responsibility of contributors, with TuteeHUB disclaiming liability for accuracy, copyrights, or consequences of use; content is for informational purposes only and not professional advice.
No matter what stage you're at in your education or career, TuteeHUB will help you reach the next level that you're aiming for. Simply,Choose a subject/topic and get started in self-paced practice sessions to improve your knowledge and scores.
Kindly log in to use this feature. We’ll take you to the login page automatically.
Login
Ready to take your education and career to the next level? Register today and join our growing community of learners and professionals.
Your experience on this site will be improved by allowing cookies. Read Cookie Policy
Your experience on this site will be improved by allowing cookies. Read Cookie Policy
manpreet
Best Answer
3 years ago
I have searched online for advice on how to markup text of a technical nature so that it can work well for those using assistive technology. If I use voice search then that counts me in as using 'assistive technology'.
I am looking for answers concerning voice search as well as accessibility.
There is a lot of advice on using schema markup, e.g. JSON+LD and RDFa to get results in voice search, however, if I have text that has codes that need to be spelt out or even actual code, or even quotes and citations, I can't squeeze that into some microdata to get pronunciation cues over to some machine.
Before I get too far into my writing I would like to know if any text level elements get noticed, if they do then I can structure my content that bit better at the text level, e.g. using 'code', 'q', 'em', dfn', 'abbr'.