WebAIM - Web Accessibility In Mind

E-mail List Archives

Thread: Accessible Excel spreadsheet

for

Number of posts in this thread: 3 (In chronological order)

From: Allayne Woodford
Date: Mon, Jan 26 2015 5:38PM
Subject: Accessible Excel spreadsheet
No previous message | Next message →

Hello Kim,

I have only used the Title Region function a few times in the past with JAWS 15 but have recently upgraded to JAWS 16. I just did a test on a few spreadsheets and found that it will read out either a heading row or column but not both. Whether row or column is selected first while holding down the control key seems to determine which of the two heading information is read out when a TitleRegion name is created.

It doesn't solve your problem but this is my experience with Title Region and JAWS 16.

Kind regards,

Ally Woodford
Project Manager | Media Access Australia
Level 3, 616 - 620 Harris St, Ultimo NSW 2007
Tel: 02 9212 6242 Fax: 02 9212 6289 Mobile: 0419 460 797 Web: www.mediaaccess.org.au
                                               
Media Access Australia - inclusion through technology, Access iQ® - creating a web without limits and cap that! - improving literacy with captions.

Follow us on Twitter @mediaaccessaus @AccessiQ @cap_that



-----Original Message-----
From: = EMAIL ADDRESS REMOVED = [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Wee, Kim (MNIT)
Sent: Tuesday, 27 January 2015 9:56 AM
To: = EMAIL ADDRESS REMOVED =
Subject: [WebAIM] Fwd: Accessible Excel spreadsheet


Over a year ago, I created some instructions on how to create an accessible Excel spreadsheet.

One of the advanced steps is to Define the Title Region. This step worked most of the time, with JAWS 13, in having the screen reader announce the row and/or column header. However, with JAWS 16, this doesn't seem to work anymore and I can't find any information on the web when searching for the issue.

Would anyone have any instructions or advice to share on this issue? I want to make sure we are creating the most useable Excel documents we possibly can.

Thank you.

Kim Wee | Webmaster and accessibility coordinator MN.IT Services @ Education
651-582-8548 (w) | = EMAIL ADDRESS REMOVED = <mailto: = EMAIL ADDRESS REMOVED = >

[cid: = EMAIL ADDRESS REMOVED = 30FB60]<http://www.mn.gov/oet>;

Information Technology for Minnesota Government | mn.gov/mnit<http://www.mn.gov/oet>;

From: Birkir R. Gunnarsson
Date: Mon, Jan 26 2015 6:34PM
Subject: Re: Accessible Excel spreadsheet
← Previous message | Next message →

I had issues with this, and with some help discovered that the culprit
was a Jaws verbosity setting for Excel.
If you go into Jaws verbosity settings for Excel (e.g. by pressing
JawsKey-V from an Excel window), type "name" into the search box.
Make sure the override name setting that shows up (the only search
result) is set to "off", not "on".
This totally fixed it for me.
I am checking with FS to see why this setting was set to "off" by
default, because it very much messes with their own help topic on the
subject where they describe how named regions work.
hth
-B


On 1/26/15, Allayne Woodford < = EMAIL ADDRESS REMOVED = > wrote:
> Hello Kim,
>
> I have only used the Title Region function a few times in the past with JAWS
> 15 but have recently upgraded to JAWS 16. I just did a test on a few
> spreadsheets and found that it will read out either a heading row or column
> but not both. Whether row or column is selected first while holding down the
> control key seems to determine which of the two heading information is read
> out when a TitleRegion name is created.
>
> It doesn't solve your problem but this is my experience with Title Region
> and JAWS 16.
>
> Kind regards,
>
> Ally Woodford
> Project Manager | Media Access Australia
> Level 3, 616 - 620 Harris St, Ultimo NSW 2007
> Tel: 02 9212 6242 Fax: 02 9212 6289 Mobile: 0419 460 797 Web:
> www.mediaaccess.org.au
>
> Media Access Australia - inclusion through technology, Access iQ® - creating
> a web without limits and cap that! - improving literacy with captions.
>
> Follow us on Twitter @mediaaccessaus @AccessiQ @cap_that
>
>
>
> -----Original Message-----
> From: = EMAIL ADDRESS REMOVED =
> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Wee, Kim (MNIT)
> Sent: Tuesday, 27 January 2015 9:56 AM
> To: = EMAIL ADDRESS REMOVED =
> Subject: [WebAIM] Fwd: Accessible Excel spreadsheet
>
>
> Over a year ago, I created some instructions on how to create an accessible
> Excel spreadsheet.
>
> One of the advanced steps is to Define the Title Region. This step worked
> most of the time, with JAWS 13, in having the screen reader announce the row
> and/or column header. However, with JAWS 16, this doesn't seem to work
> anymore and I can't find any information on the web when searching for the
> issue.
>
> Would anyone have any instructions or advice to share on this issue? I want
> to make sure we are creating the most useable Excel documents we possibly
> can.
>
> Thank you.
>
> Kim Wee | Webmaster and accessibility coordinator MN.IT Services @
> Education
> 651-582-8548 (w) | = EMAIL ADDRESS REMOVED = <mailto: = EMAIL ADDRESS REMOVED = >
>
> [cid: = EMAIL ADDRESS REMOVED = 30FB60]<http://www.mn.gov/oet>;
>
> Information Technology for Minnesota Government |
> mn.gov/mnit<http://www.mn.gov/oet>;
>
>
>
>
>
>
>
> > > >


--
Work hard. Have fun. Make history.

From: Wee, Kim (MNIT)
Date: Tue, Jan 27 2015 7:23AM
Subject: Re: Accessible Excel spreadsheet
← Previous message | No next message

Thank you - setting the verbosity settings in Excel corrected the issue.

KIM WEE |  WEBMASTER AND ACCESSIBILITY COORDINATOR
MN.IT SERVICES @ EDUCATION
651-582-8548 (w) | = EMAIL ADDRESS REMOVED =

Information Technology for Minnesota Government | mn.gov/mnit




-----Original Message-----
From: = EMAIL ADDRESS REMOVED = [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Birkir R. Gunnarsson
Sent: Monday, January 26, 2015 7:34 PM
To: WebAIM Discussion List
Subject: Re: [WebAIM] Accessible Excel spreadsheet

I had issues with this, and with some help discovered that the culprit was a Jaws verbosity setting for Excel.
If you go into Jaws verbosity settings for Excel (e.g. by pressing JawsKey-V from an Excel window), type "name" into the search box.
Make sure the override name setting that shows up (the only search
result) is set to "off", not "on".
This totally fixed it for me.
I am checking with FS to see why this setting was set to "off" by default, because it very much messes with their own help topic on the subject where they describe how named regions work.
hth
-B


On 1/26/15, Allayne Woodford < = EMAIL ADDRESS REMOVED = > wrote:
> Hello Kim,
>
> I have only used the Title Region function a few times in the past
> with JAWS
> 15 but have recently upgraded to JAWS 16. I just did a test on a few
> spreadsheets and found that it will read out either a heading row or
> column but not both. Whether row or column is selected first while
> holding down the control key seems to determine which of the two
> heading information is read out when a TitleRegion name is created.
>
> It doesn't solve your problem but this is my experience with Title
> Region and JAWS 16.
>
> Kind regards,
>
> Ally Woodford
> Project Manager | Media Access Australia Level 3, 616 - 620 Harris St,
> Ultimo NSW 2007
> Tel: 02 9212 6242 Fax: 02 9212 6289 Mobile: 0419 460 797 Web:
> www.mediaaccess.org.au
>
> Media Access Australia - inclusion through technology, Access iQ® -
> creating a web without limits and cap that! - improving literacy with captions.
>
> Follow us on Twitter @mediaaccessaus @AccessiQ @cap_that
>
>
>
> -----Original Message-----
> From: = EMAIL ADDRESS REMOVED =
> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Wee, Kim
> (MNIT)
> Sent: Tuesday, 27 January 2015 9:56 AM
> To: = EMAIL ADDRESS REMOVED =
> Subject: [WebAIM] Fwd: Accessible Excel spreadsheet
>
>
> Over a year ago, I created some instructions on how to create an
> accessible Excel spreadsheet.
>
> One of the advanced steps is to Define the Title Region. This step
> worked most of the time, with JAWS 13, in having the screen reader
> announce the row and/or column header. However, with JAWS 16, this
> doesn't seem to work anymore and I can't find any information on the
> web when searching for the issue.
>
> Would anyone have any instructions or advice to share on this issue? I
> want to make sure we are creating the most useable Excel documents we
> possibly can.
>
> Thank you.
>
> Kim Wee | Webmaster and accessibility coordinator MN.IT Services @
> Education
> 651-582-8548 (w) | = EMAIL ADDRESS REMOVED = <mailto: = EMAIL ADDRESS REMOVED = >
>
> [cid: = EMAIL ADDRESS REMOVED = 30FB60]<http://www.mn.gov/oet>;
>
> Information Technology for Minnesota Government |
> mn.gov/mnit<http://www.mn.gov/oet>;
>
>
>
>
>
>
>
> > > list messages to = EMAIL ADDRESS REMOVED =
>


--
Work hard. Have fun. Make history.