How much easier is it for screen readers to handle <div> based websites as opposed to older <table> based websites, and why are they worse?
How much easier is it for screen readers to handle <div> based websites as
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
How much easier is it for screen readers to handle <div> based websites as opposed to older <table> based websites, and why are they worse?
Screen readers assume the content inside a
tableis tabular, and reads it as such. E.g. “row 1, column 1: (contents)”. If you use tables to lay out your site, this won’t necessarily make any sense. You are telling the end-client you have data with tabular significance, when you actually don’t.By contrast,
divhave no meaning other than “section”, so screen readers make no attempt to signify them. You can use divs to make arbitrary visual breaks in your layout without impacting the meaning of the markup.This is what we mean when we say “semantic” markup. Semantic means the markup accurately describes the meaning of the content inside of it – tables wrap tabular data,
ULs wrap unordered lists, etc.