unknown
1970-01-01 00:00:00 UTC
About the tracking mouse pointer: If you go to system settings (appeara=
nce=20
section) > workspace effects (Arbeitsfl=E4chen-Effekte), you will find =
=20
accessibility option including the animations for mouse clicks and magn=
ifying=20
glass under the mouse cursor (I'm still running 4.13, not sure if those=
=20
options have been implemented in 5.1 now).=20
Cheers,
Heiko.
de some
pher
to see
I like those ideas, in particular when they can get tested easily.
Katepart
(that means the following works in Kate and KWrite etc.) has an ela=
borated
t to
7AJb
ax
Colored
save it
ected)
as you
ne the
lored
her
rd
ntific
that
bcams
-file/
nce=20
section) > workspace effects (Arbeitsfl=E4chen-Effekte), you will find =
=20
accessibility option including the animations for mouse clicks and magn=
ifying=20
glass under the mouse cursor (I'm still running 4.13, not sure if those=
=20
options have been implemented in 5.1 now).=20
Cheers,
Heiko.
Hi,
=20
I am a visually impaired user. Changing the background to black and h=
ave a=20
I am a visually impaired user. Changing the background to black and h=
white font is very helpful for me. But many application do not suppor=
t it.they simply ignore system settings.
I can only see a small area of the screen and therefore the tracking =
mouseI can only see a small area of the screen and therefore the tracking =
pointer and the circles around the mouse pointer when you press contr=
ol arewonderful things, available in Windows OS. These are the things which=
wouldmake life easier.
=20
thanks
Reinhard
=20
nts=20
thanks
Reinhard
=20
Date: Fri, 19 Sep 2014 14:57:32 +0200
Subject: Re: [Kde-accessibility] experimental idea with colour fo=
Subject: Re: [Kde-accessibility] experimental idea with colour fo=
Content-Type: text/plain; charset=3D"us-ascii"
=20
i somehow made a little kate script ... that is now broken. (i ma=
=20
i somehow made a little kate script ... that is now broken. (i ma=
blurred and normal screen shots, to demonstrate that you can deci=
the
letters if you know the colour code used, despite been impossible=
letters if you know the colour code used, despite been impossible=
their shapes)
=20I like those ideas, in particular when they can get tested easily.
Katepart
(that means the following works in Kate and KWrite etc.) has an ela=
highlighting [1], which is easy to modify. (This is my first attemp=
create a syntax highlighting file; for sure there is much room for
improvement.)
=20
1. Download the highlight definitions from http://pastebin.com/GzkH=
improvement.)
=20
1. Download the highlight definitions from http://pastebin.com/GzkH=
2. Place it at ~/.kde4/share/apps/katepart/syntax/ (create the synt=
folder if it doesn't exists) under the name coloredtext.xml
3. (Re)start Kate, go to Extra > Highlighting > Markup and select "=
3. (Re)start Kate, go to Extra > Highlighting > Markup and select "=
Text"
4. Download the color scheme from http://pastebin.com/GsVSw3JY and =
4. Download the color scheme from http://pastebin.com/GsVSw3JY and =
anywhere under the name coloredtext.katehlcolor
5. In Kate/KWrite go to Settings > Fonts & Colors, tab "Styles for
highlighting", find Markup/Colored Text at the dropdown (if not sel=
5. In Kate/KWrite go to Settings > Fonts & Colors, tab "Styles for
highlighting", find Markup/Colored Text at the dropdown (if not sel=
and load the color definition via "Import" from the downloaded file=
=20
Now every letter gets its own color. And you can modify the scheme =
=20
Now every letter gets its own color. And you can modify the scheme =
want
=20
Beside from the technical solution I believe it makes sense to defi=
=20
Beside from the technical solution I believe it makes sense to defi=
highlighting carefully. The proof-of-concept scheme is just multico=
without any concept. What I have in mind is to put syllables or rat=
phonemes into foreground, and to move less important letters backwa=
(vocals for instance).
But perhaps an individual solution would be even better. For a scie=
But perhaps an individual solution would be even better. For a scie=
study I would measure eye fixations and highlight those parts later=
got special attention, that means a high number or long duration of=
fixations. Unfortunately the resolution and framerate of inbuilt we=
fixations. Unfortunately the resolution and framerate of inbuilt we=
is not sufficient, as far as I know. So we cannot provide this as a=
generic accessibility tool.
=20
Cheers,
Heiko.
=20
[1] http://kate-editor.org/2005/03/24/writing-a-syntax-highlighting=
generic accessibility tool.
=20
Cheers,
Heiko.
=20
[1] http://kate-editor.org/2005/03/24/writing-a-syntax-highlighting=
_______________________________________________
kde-accessibility mailing list
https://mail.kde.org/mailman/listinfo/kde-accessibility
kde-accessibility mailing list
https://mail.kde.org/mailman/listinfo/kde-accessibility