typo3 at t3node.com
Wed Feb 4 00:53:44 CET 2009
On 04.02.2009 00:22 Peter Russ wrote:
>> On 03.02.2009 23:28 Steffen Müller wrote:
>> btw. you could alternatively use pagebrowse extension, which produces
>> accessible HTML (without tables) and is much more configurable.
> 1) Where is that information from: table = not accessible?
Semantically the page browser is kind of a menu or list. So why use
tables? In terms of tables, page browser would be number of result pages
with ONE single row. The data in the columns all serve the same
purpose/meaning. That's totally nonsense an therefore not accessible,
because the form does not reflect the content.
> 2) It's just a question of TS ;-) IMHO extension it not required!
Well, the question was to find a documentation. The extension ships a
good documentation. So why not use it as it could be the economic way of
solving the issue?
More information about the TYPO3-english