The 'chrome' of the office applications are accessible to the extent
that the menu and buttons are built from standard controls so they
inherit accessibility for free. Of course anything custom fails so the
font and size menus can't be actioned, although I can interact with them
and manually type in a size, but this doesn't work so well for picking a
font. Beyond that, I can't interact or so anything with the document,
pretty much eviscerating all the utility of the application.
As an aside, Microsoft claiming ignorance on this is is laughable. They
even say so on their Office Mac site:
http://mac2.microsoft.com/help/office/14/en-us/word/item/a1a31d9e-86f6-4bbb-b55e-6a25147e57e5
"VoiceOver does not work with the contents of the main document window
or the ribbon. For example, VoiceOver does not read your text in a
document."
What I find unusual is their description of VO support in the VPAT:
http://www.microsoft.com/government/en-us/products/section508/Pages/default.aspx
" VoiceOver functionality is operational for many menus, dialog boxes,
and other application elements. Text to Speech content is available, for
example, for text content within the document area."
This seems a bit disingenuous or at least has errors of omission such as
not being able to actually edit the text, the main point of a word
processor.
CB
On 1/31/13 10:29 AM, Eugenia Firth wrote:
Hi there again
I am glad this lady is reading these posts because I want to point out that a
lot of times when blind people go to the Apple Store to get there Max, people
who don't know it's inaccessible, encourage the person to get Office for the
Mac. Then, the blind person gets home, only to find out the can't use it. This
happened to a blind friend of mine, and it almost happened to another blind
friend of mine. Luckily, I was with her when she went to the Apple store. Also,
the Apple employee almost added it to her software when she got her Mac
computer, and I stopped her before she did it.
Regards,
GG
Sent from my iPhone
On Jan 31, 2013, at 1:34 AM, "J.P." <jshandr...@gmail.com> wrote:
Hey guys,
We are always saying how inaccessible Office for Mac is. The head of
Microsoft's Mac accessibility team is reading this post. Those of you who have
used the software, please give examples where we know it's inaccessible. Sara,
who head's their team is giving us an opportunity that a lot of developers
don't. I know for myself, I would rather load one piece of software. Rather
then having to use a virtual machine.
Thanks, J. p.
--
You received this message because you are subscribed to the Google Groups
"MacVisionaries" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to macvisionaries+unsubscr...@googlegroups.com.
To post to this group, send email to macvisionaries@googlegroups.com.
Visit this group at http://groups.google.com/group/macvisionaries?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
--
Ż\_(?)_/Ż
--
You received this message because you are subscribed to the Google Groups
"MacVisionaries" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to macvisionaries+unsubscr...@googlegroups.com.
To post to this group, send email to macvisionaries@googlegroups.com.
Visit this group at http://groups.google.com/group/macvisionaries?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
