Thanks for those links. All of the items labelled draft are a real pain. The IDPF can't seem to get out of there own way.
My thoughts for epub3-itizer are:
1. default to including the accessibility features but controllable with pref setting
2. disable their inclusion if more than one dc:language field is provided in the opf to prevent incorrect xml:lang and lang tags from being created.
3. disable their inclusion if an audio or video resource is present in the opf since that would invalidate the extra metadata. Or is there special metadata entries for these cases?
4. disable their inclusion if mathml tags are found (is this needed? Can text readers grok mathml?)
5. if enabled, use first ncx/nav entry for each xhtml file that links to top of page (no #id used in link) to fill in title tag for head in each page. Leave blank if no top of page link exists in the ncx/nav
6. if enabled, add in the needed metadata as provided above.
That way, the accessibility features will only be added under basic operation forcing them to be hand added if something special is needed to prevent incorrect code from being added.
What do you think?
KevinH
|