Issue 72160 - [A11y] Writer Format->Bullets & Numbering has many unaccessible components.
Summary: [A11y] Writer Format->Bullets & Numbering has many unaccessible components.
Status: CLOSED FIXED
Alias: None
Product: Writer
Classification: Application
Component: ui (show other issues)
Version: OOo 2.0.4
Hardware: All All
: P2 Trivial (vote)
Target Milestone: ---
Assignee: eric.savary
QA Contact: issues@sw
URL:
Keywords: accessibility
Depends on:
Blocks:
 
Reported: 2006-11-30 21:39 UTC by williewalker
Modified: 2013-08-07 14:42 UTC (History)
4 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description williewalker 2006-11-30 21:39:18 UTC
This was logged in the SOffice bug database as:

https://so-web.germany.sun.com/iBIS/servlet/edit.TaskFormServlet?tid=136221

We're finding that database difficult to use, so we're 'moving' the bug here. 
The main problem is that all the selections in the tabs in "Format->Bullets and
Numbering..." don't have any accessible name or description, so the blind user
cannot tell what they are choosing.
Comment 1 eric.savary 2006-12-01 11:22:04 UTC
Description from bugtracker:

Start swriter. Format->Bullets and Numbering. For the Bullet,
Numbering Type, Outline and Graphics tabs, there are several
images of different styles present. There is no meaningful
accessible information associated with them.

For the Bullets pane, the following accessible names are suggested:

- "solid black small circular bullets"
- "solid black large circular bullets"
- "solid black diamond bullets"
- "solid black large square bullets"
- "black right pointing arrow bullets"
- "black and white right pointing arrow bullets"
- "black check mark bullets"
- "black tick mark bullets"


For the Numbering type pane, the following accessible names are suggested:

- Number 1) 2) 3)
- "Number 1. 2. 3."
- "Number (1) (2) (3)"
- "Uppercase Roman number I. II. III."
- "Uppercase letter A) B) C)"
- "Lowercase letter a) b) c)"
- "Lowercase letter (a) (b) (c)"
- "Lowercase Roman number i. ii. iii."


For the Outline pane, providing accessible names is going to be tricky.
This pane displays the different styles that you can apply to a
hierarchical list. It uses various combinations from the
"Bullets" and "Numbering Type" options above, plus some that
are new. There are between 2-5 types given for each graphical
list item.

1/ Number type 2, Number type 2, Number type 6.
2/ Number type 2, Number type 6.
3/ Number type 3, Number type 7, Number type 8.
4/ Number type 2, number type 2, number type 2, number type 2, number type 2.
5/ Number type 2, "A.", number type 8, number type 6.
6/ "A.", number type 4, "a.", number type 8.
7/ "1", "1.1", "1.1.1", "1.1.1.1", "1.1.1.1.1".
8/ Bullet type 6, bullet type 5, "small black diamond followed by right paren".

Again, we'll try to suggest appropriate accessible names.

For the Graphics pane, there are 62 different glyphs that can be used as bullets.
These actually are fairly accessible. They each have a tooltip that
is the path to where the image file is for each glyph. This is spoken
and brailled. What would be an improvement would be to just speak/braille
the basename rather than the whole pathname.

ES->OBR: (tested with at-poke). The deepest info available is "Selection", which
means, in this case, the entire group of pic buttons. Each button should have
its own Ayy1 info.

OBR->OS: from a first glance, this doesn't look like an issue in the bridge .

OS->FL: Are the suggested names o.k. for you?
FL: Strings are O.K.

OS: Sorry, I forgot to ask for the German strings.
Comment 2 Oliver Specht 2006-12-01 11:57:22 UTC
->es: You forgot to assign correctly - and you forgot to close #136221#
Reassigned to fl to get German strings
Comment 3 frank.loehmann 2007-01-02 16:19:19 UTC
FL->OS: I have added the German strings:

- "solid black small circular bullets"
DE: "kleine schwarze ausgefüllte kreisförmige Gliederungspunkte"

- "solid black large circular bullets"
DE: "große schwarze ausgefüllte kreisförmige Gliederungspunkte"

- "solid black diamond bullets"
DE: "ausgefüllte schwarze diamantförmige Gliederungspunkte"

- "solid black large square bullets"
DE: "große schwarze ausgefüllte quadratische Gliederungspunkte"

- "black right pointing arrow bullets"
DE: "ausgefüllte schwarze nach rechts zeigende Pfeile als Gliederungspunkte"

- "black and white right pointing arrow bullets"
DE: "schwarzweiße nach rechts zeigende Pfeile als Gliederungspunkte"

- "black check mark bullets"
DE: "schwarze Kreuzmarken als Gliederungspunkte"

- "black tick mark bullets"
DE: "schwarze Haken als Gliederungspunkte"


For the Numbering type pane:

- Number 1) 2) 3)
DE:"Nummer 1) 2) 3)"

- "Number 1. 2. 3."
DE:"Nummer 1. 2. 3."

- "Number (1) (2) (3)"
DE:"Nummer (1) (2) (3)"

- "Uppercase Roman number I. II. III."
DE:"Große römische Zahlen I. II. III."

- "Uppercase letter A) B) C)"
DE:"Großbuchstaben A) B) C)"

- "Lowercase letter a) b) c)"
DE:"Kleinbuchstaben a) b) c)"

- "Lowercase letter (a) (b) (c)"
DE:"Kleinbuchstaben (a) (b) (c)"

- "Lowercase Roman number i. ii. iii."
DE:"Kleine römische Zahlben i. ii. iii."


For the Outline pane, providing accessible names is going to be tricky.
This pane displays the different styles that you can apply to a
hierarchical list. It uses various combinations from the
"Bullets" and "Numbering Type" options above, plus some that
are new. There are between 2-5 types given for each graphical
list item.

1/ Number type 2, Number type 2, Number type 6.
2/ Number type 2, Number type 6.
3/ Number type 3, Number type 7, Number type 8.
4/ Number type 2, number type 2, number type 2, number type 2, number type 2.
5/ Number type 2, "A.", number type 8, number type 6.
6/ "A.", number type 4, "a.", number type 8.
7/ "1", "1.1", "1.1.1", "1.1.1.1", "1.1.1.1.1".

8/ Bullet type 6, bullet type 5, "small black diamond followed by right paren".
DE:Bullet type 6, bullet type 5, "kleiner schwarzer Diamant gefolgt von einer
rechten Klammer".
Comment 4 Oliver Specht 2007-01-11 12:27:23 UTC
The outline labels should be changed. It doesn't help to find some "Number type 5"

I'd prefer:
1 - Numeric, numeric, lower case letters
2 - Numeric, lower case letters
3 - Numeric, lower case letters, lower case Roman, upper case letters
4 - Numeric
5 - Upper case Roman, upper case letters, lower case Roman, lower case letters
6 - Upper case letters, upper case Roman, lower case letters, lower case Roman
7 - Numeric with all sublevels
8 - B/W right pointing bullet, black right pointing arrow bullet, solid black
diamond bullet, solid black small circular bullets

I'd leave out the parenthesis. 
Comment 5 Oliver Specht 2007-01-12 10:02:49 UTC
After discussion with FL the 'black' parts have been removed because the bullets
will get the text color.

Fixed in 
svx/inc/dialogs.hrc
svx/source/dialog/numpages.src
svx/source/dialog/svxbmpnumvalueset.cxx
Comment 6 Oliver Specht 2007-01-15 07:15:19 UTC
Reassigned for verification
Comment 7 timar74 2007-01-15 21:15:09 UTC
The following two English descriptions are identical in version 1.58.164.2 of
numpages.src

String RID_SVXSTR_BULLET_DESCRIPTION_4
{
    Text [ de ] = "Ausgefüllte nach rechts zeigende Pfeile als Gliederungspunkte";
    Text [en-US] = "Right pointing arrow bullets";
};
String RID_SVXSTR_BULLET_DESCRIPTION_5
{
    Text [ de ] = "Nach rechts zeigende Pfeile als Gliederungspunkte";
    Text [en-US] = "Right pointing arrow bullets";
};
Comment 8 eric.savary 2007-01-16 15:32:51 UTC
Well done, timar! Thank you!
Comment 9 eric.savary 2007-01-16 15:33:30 UTC
->OS: Please correct the strings as following (proposal from MD):

String RID_SVXSTR_BULLET_DESCRIPTION_4
{
  Text [ de ] = "Ausgefüllte nach rechts zeigende Pfeile als Gliederungspunkte";
  Text [en-US] = "Right pointing arrow bullets filled out";
};
String RID_SVXSTR_BULLET_DESCRIPTION_5
{
  Text [ de ] = "Nach rechts zeigende Pfeile als Gliederungspunkte";
  Text [en-US] = "Right pointing arrow bullets";
};" 
Comment 10 Oliver Specht 2007-01-17 07:49:05 UTC
.
Comment 11 eric.savary 2007-01-17 10:59:39 UTC
fixed
Comment 12 eric.savary 2007-01-17 11:00:27 UTC
Verified in CWS os91.
Comment 13 eric.savary 2007-02-02 11:35:29 UTC
Ok in OOF_m5