Many web designers seem to be abandoning tables and using Cascading Style Sheets (CSS) to layout information in a visually identical way. But tables increase the accessibility of tabular information for blind people* using screen readers because they can more easily scroll, page, tab, and move around in the data.
Web pages are created using HTML, the web’s markup language. Like any markup language, it contains hidden tags about unhidden information. Webpages with well-tagged information are advantageous for blind people using screen readers.** Tables are no exception. The TABLE element of HTML has several tags and attributes used to describe a table, its layout, and the data it contains. Tables are a standard way in HTML to describe tabular data. There is no standard way in CSS to display or describe tabular data; crafty web designers can use CSS to simulate tables, but only visually.
- The first tag is <table> which creates the table. But in this tag, designers should add attributes that describe the number of rows and columns (“rows,” “cols”). How this is helpful: A blind person may be looking for a table that contains information on all 50 states, but if the table has less than 50 rows, then they can avoid spending time reading this table and move on to find another. In the JAWS screen reading software, there is a function that allows the user to jump from table to table.
- The second tag to use is <th> to create a cell in a row. The <th> tag is different from the <td> cell-creating tag in that it describes a header. Writers and publishers (web designers included) often make headers larger or bolder than the subordinate text to indicate the header texts’ significance. But only sighted people can notice these cues. Screen readers will notice the <th> tag as a column heading and the user can pan the columns until they find the column they want – this is especially helpful when the web designer has tables in pages without heading text (probably not a good idea) or uses tables to organize the layout of a page (which designers should avoid).

This screenshot “shows” (many are hidden) several elements of accessibility in a webpage I designed for work. For example, the map is a graphic element that blind users can’t see and screen readers can’t describe. A table below the map describes the information seen on the map and takes the user to the same webpage (with detailed information) as the map markers. The table’s first row uses the <th> tag to indicate the row contains important column headings. Also, the table shows tabular data and the webpage does not use tables to organize the layout of the webpage.
In all HTML layout tags, designers can add a “title” attribute that screen reading software will notice and read to the user. Titles should describe well the information in the tagged text or the text immediately following the tag. Use the “title” attribute on these tags: <table>, <div>, and <a> (to describe links). Multimedia should ALWAYS have the “alt” attribute that describes the graphic (essentially a hidden caption). This is also helpful for people who browse with images turned off, or when your server fails to display the image.
*What is good for blind people is usually good for sighted people.
**A screen reader is software that reads text and commands sighted people would see on a computer monitor, but also reads text and commands that are hidden. With HTML and CSS, web designers can give information and commands in hidden code that speak to blind users. An example of this is a link that enables the user and their screen reader to jump over information to a predefined point, like a navigation area, skipping the introduction text.
Wrapping PDF inside Flash, the ultimate in inaccessibility
Published February 5, 2010 Commentary , Webdesign 3 CommentsTags: accessibility, blind, Flash, PDF, visually impaired
Portable Document Format (PDF) files are often inaccessible. The text you see when the file is displayed is stored as a raster image instead of as machine-readable text. You can’t copy and paste the text, a screen reader can’t audibly speak the text, and you can’t search the text. While a PDF is probably a good way to share a text document when you want to ensure formatting and images remain unmodified by file conversion or different versions of software (I’m thinking about Microsoft Word documents), at least the text document is inherently accessible and will always remain so.
Now there’s a trend online to share PDF files within Adobe Flash viewers. They’re websites like DocStoc, SlideShare and Scribd. Flash is inaccessible – blind and visually impaired people can’t interact with it. It’s really that simple. If you want to share textual information, don’t use Flash, and don’t wrap a PDF in Flash – let people download it and use their preferred viewer, whether it be Apple’s Preview, Adobe Acrobat, or Nitro, Cute or Foxit. Try avoiding PDF altogether; if you can’t read my tips below.
Look at this screenshot of a PDF document inside a DocStoc Flash viewer. The screenshot shows the entire web page – imagine your screen is this tall. Notice how much of the screen space is dedicated to viewing the PDF. Then pay attention to how much space the many ads occupy. Not only is the text inaccessible, you have a poor document viewing experience.

If you’re going to stick with PDF, make sure you use Adobe Acrobat Professional so that you can run an Accessibility Check and make changes to the document. Professional also comes with an Optical Character Recognition (OCR) function that reads images and converts them to text. When people scan documents, they don’t run the OCR function and the scan is only useful for well-sighted people.