Issue 71385 - [a11y] Numerous text attributes not provided.
Summary: [a11y] Numerous text attributes not provided.
Status: CLOSED FIXED
Alias: None
Product: Writer
Classification: Application
Component: ui (show other issues)
Version: OOo 2.0.4
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: eric.savary
QA Contact: issues@sw
URL:
Keywords: accessibility
Depends on:
Blocks:
 
Reported: 2006-11-09 16:42 UTC by richburridge
Modified: 2013-08-07 14:42 UTC (History)
4 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description richburridge 2006-11-09 16:42:33 UTC
See also Orca bug #372965 which is blocked because of this bug.
http://bugzilla.gnome.org/show_bug.cgi?id=372965

There are many text attributes that a sighted user can obtain by 
glancing at the screen.  Orca currently does not provide access 
to these attributes. It can't provide them, because they aren't currently
provided by OOo.

Attributes which would be helpful to have access to via Orca include:

* The bulk of the items in the Character dialog (Format menu... Character):
  * Color (foreground and background)
  * Highlighting
  * Position (superscript, subscript, normal)
  * Scale width
  * Spacing (expanded, collapsed, normal)
  * Relief
  * Rotation
  * Outline, Shadow, Blinking

Note that the "style" attribute is covered by OOo issue #71383.
Comment 1 michael.ruess 2006-11-09 21:26:31 UTC
Reassigned to ES.
Comment 2 eric.savary 2006-11-10 10:12:02 UTC
Reassigned to OBR
Comment 3 nospam4obr 2006-12-05 13:28:34 UTC
Note that the color attribute should be there if a specific color has been
chosen. Only the (theme dependant) default colors are not exposed.
Comment 4 nospam4obr 2006-12-22 11:58:19 UTC
As previously stated, the color attributes (foreground/background) are currently
not exposed if they match the default values of the theme. Do you really think
it make sense to provide the RGB values for those ?
Comment 5 joaniediggs 2006-12-22 16:01:59 UTC
When I filed the original Orca bug, my list was based on everything we weren't
getting from Orca -- color being one of them.

I just did a comparison between getDefaultAttributes and getAttributes.  Color
attributes (as you indicated) are attainable via getAttributes when they are NOT
a property of the entire paragraph.  They are attainable via
getDefaultAttributes when they ARE a property of the entire paragraph.  This
seems to be consistent with how other attributes are exposed (right??).  If so,
then perhaps it is not necessary to expose them further.  But I'll let Rich and
others chime in.

As far as I'm concerned, the bottom line is that we need a quick and efficient
(and predictable/reliable) way to obtain ALL of the text attributes.
Comment 6 joaniediggs 2006-12-22 16:52:24 UTC
To follow-up on my previous comment:

If the color is not exposed, can we safely assume that it is definitely black
text on a white background, or is there a possibility that it is something else?
Comment 7 nospam4obr 2006-12-25 07:30:59 UTC
The colors depends on the theme you are using: in most themes the text color is "black on white", while 
on inverse themes it most likely is "white on black". So currently a missing color attribute means somthing 
like: "default".
Comment 8 richburridge 2006-12-28 18:50:21 UTC
Here's what gedit currently supplies as default attributes:

left-margin:2; 
right-margin:2; 
indent:0; 
invisible:false; 
editable:true; 
pixels-above-lines:0; 
pixels-below-lines:0; 
pixels-inside-wrap:0; 
bg-full-height:false; 
rise:0; 
underline:none; 
strikethrough:false; 
size:8; 
scale:1; 
weight:400; 
language:en-us; 
family-name:Monospace; 
bg-color:65535,65535,65535; 
fg-color:0,0,0; 
bg-stipple:false; 
fg-stipple:false; 
wrap-mode:word; 
direction:ltr; 
justification:left; 
stretch:normal; 
variant:normal; 
style:normal

So yes, I think it would be a good idea to specify the foreground and 
background colors as rgb values.

Thanks.
Comment 9 Oliver-Rainer Wittmann 2007-01-17 09:21:19 UTC
implement method <getBackground()> at class <SwAccessibleParagraph> - Writer
implementation of <XAccessibleEditableText> - changed files:
/sw/source/core/access/accpara.hxx, 1.36.174.1
/sw/source/core/access/accpara.cxx, 1.67.96.3
Comment 10 nospam4obr 2007-01-18 12:36:26 UTC
atktext.cxx: revision: 1.5.70.1
atktextattributes.cxx: revision: 1.4.136.2
atktextattributes.hxx: revision: 1.3.176.1

add support for "language" and "scale".
Comment 11 nospam4obr 2007-01-18 15:13:18 UTC
 /vcl/unx/gtk/a11y/atktextattributes.cxx 1.4.136.4 adds support for
"font-effect" attribute as described in
http://www.w3.org/TR/2002/WD-css3-fonts-20020802/#font-effect-prop.
Comment 12 nospam4obr 2007-01-19 13:07:47 UTC
vcl/unx/gtk/a11y/atktextattributes.cxx 1.4.136.5 adds support for "text-decoration" (underline, line-
through, blink) as described in http://www.w3.org/TR/REC-CSS2/text.html#lining-striking-props .
Comment 13 nospam4obr 2007-01-21 00:54:19 UTC
vcl/unx/gtk/a11y/atktextattributes.cxx 1.4.136.6

adds support for 

"text-rotation" in degrees and 
"text-shadow" as in http://www.w3.org/TR/REC-CSS2/text.html#propdef-text-shadow

revision 1.4.136.7 for
"direction" (see ATK docu) and
"writing-mode" as in http://www.w3.org/TR/2001/WD-css3-text-20010517/
#PrimaryTextAdvanceDirection

revision 1.4.136.8 for
"stretch" (see ATK docu) and
"vertical-align" as in http://www.w3.org/TR/REC-CSS2/visudet.html#propdef-vertical-align ("sub", 
"super" and "<percent>%")
Note: ignore ATK attribute "rise" as no mapping seems to be possible in the bridge
"line-height" as in http://www.w3.org/TR/REC-CSS2/visudet.html#propdef-line-height (<percent>% 
and <height>pt)
Note: ignore ATK attribute "pixels-inside-wrap" as a mapping would only be possible for "fixed" line 
height
Comment 14 nospam4obr 2007-01-22 09:51:41 UTC
please verify.
Comment 15 eric.savary 2007-01-24 14:04:19 UTC
Verified in atkbridge5
Comment 16 eric.savary 2007-02-02 11:37:34 UTC
Ok in OOF_m5