Hi Mario,
On Wed, 8 Feb 2012 04:32:24 -0800 (PST)
PMario <[email protected]> wrote:
On Feb 8, 12:59 pm, Bauwe Bijl <[email protected]> wrote:
Implemented Heading-levels:
SiteTitle <h1>
Search, MainMenu, SideBar, Footer and Toolbar <h2>
TiddlerTitle('s) <h3>
Inner tiddler heading <h4> (no other headings bigger then !!!!
should
be used in this case)
Hi Bauwe, Simon,
Since you need fixed headings for h1-h3 for the reader, it would be
possible, to create a formatter, that changes the renderer a little
bit, to make the content compatible with "vanilla" TW.
for that i will write something more later when i am at home and i
have talked to more people which will be this evening.
But in my opinion we also just could do a h6 for the navigation
elements and use h1 through h6 in the normal wiki content as it is in
the normal tw markup.
Screenreaders support navigating levelwhise but its not needed cause
you also can navigate with the h key through the site just heading by
heading and with the numbers 1 through 6 to the headings with that
level. you can also go backwards by using shift and the coresponding
key.
screenreaders use a buffer in which they present the data they have
collected and they are redoing things with the content so its useable.
There are various screenreaders for free around too:
For Windows there is NVDA which can be downloaded here:
www.nvda-project.org. You might use the portable version which doesn't
install anything.
For Linux under Gnome is orca which installed by default with gnome.
you just need to run orca in the run dialog and it should start
talking.
For mac os x there is voiceover which is also integrated in mac os x
and comes by default. don't know how to start but there is information
around.
NVDA and Orca are best used with Firefox, voiceover i guess is best
used with safari.
There is some special handling for "+", "-" prefixes in toolbar
commands. This could be extended. But <fn><key> handling vary with
different browsers. So some more digging will be needed.
What would be the preferred bahaviour?
I would just use the accesskey method used by normal links. i don't
know if we can use that in tw cause when i look at the page also the
toolbar buttons are links when the screenreader sees it.
Wonder if we can just do the same like the new tiddler, new journal,
save wiki buttons.
Screenreaders are capable of reading the shortcut to the user as
she/he has to press it when the accesskey method is used.
Greetings,
Simon
--
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/tiddlywiki?hl=en.
