MHonArc v2.5.0b2 -->
office message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: Re: [office] Re: [office-accessibility] Re: [office] Fw: [office-accessibility] Inclusionof tables in the .odp profile for presentations
Hi Lars,
I have to agree with Malte here. Tables should behave as if they were part of the slide. A goal of this groups effort is to raise the bar on the accessibility and usability of presentations. As Malte indicates we introduce usability and accessibility problems on a number of levels. Users would find using an embedded OLE object for table as a step back from what they are accustomed to today.
Cheers,
Rich
Rich Schwerdtfeger
Distinguished Engineer, SWG Accessibility Architect/Strategist
Chair, IBM Accessibility Architecture Review Board
blog: http://www-106.ibm.com/developerworks/blogs/dw_blog.jspa?blog=441
"Two roads diverged in a wood, and I -
I took the one less traveled by, and that has made all the difference.", Frost
Malte.Timmermann@Sun.COM>">Malte Timmermann <Malte.Timmermann@Sun.COM>
Bad thing with embedded object is
- If you read the slide with AT, you can't read the content of OLE objects
- Activation normally doesn't help here, you would have to read the
content from OLE separately
(Special OOo implementation of internal OLE objects could change that,
but...)
- You can't activate OLE in read-only documents
- OLE objects can't grow while editing, which would be really bad for
table editing
Malte.
Lars Oppermann wrote:
> Hi Guys,
>
> Just a quick question here: is it, from an A11Y perspective absolutely
> unacceptable to have embedded tables? If the application is able to
> activate the embedded object in-place and the activated context is
> sufficiently accessible...
>
> Also from a file-format perspective, the structural information would be
> available, if the embedded table object is ODF.
>
> I understand, that this is not very lightweight. I would like to know
> whether it has to be ruled out completely from an A11Y point of view.
>
> All the best,
> /lars
>
> Richard Schwerdtfeger wrote:
>
>> Since not everyone is an accessibility expert - The reason we need a
>> real table construct in presentations is that we need to be able to do
>> structural navigation. We need to have row, column constructs, headers,
>> etc. otherwise we have an inaccessible solution. We will also have to
>> address keyboard navigation of tables once we have a "tables for
>> presentations" specification.
>>
>
>
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. You may a link to this group and all your TCs in OASIS
at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]