Quote:
Originally Posted by roland1
Accessibility says use html not images. So I'll do that. I only have two columns for most. It's the row count that's knocking me off the page.
|
It always is. Our in-house rule is 10 rows and 3 columns--anything larger than that will tend to cause issues.
I'm not saying you can't do HTML, don't get me wrong; but if you want to force your table to remain on a single screen, you can use the page-break before method, of course, but that only works intermittently--your reader decides and chooses,
not you, around font sizes, etc., and how they orient the reader (for example, what can you do around someone who rotates their device to landscape? Not much!).
The other reality is, most people are smart enough to know how to zoom and read a table. Are you absolutely SURE that the table has to be seen on a single "page" (screen)? Or are you imposing your print view onto an Reading device user?
And yes--for accessibility, HTML is better.
Hitch