Hi Pete,
We'll try to indicate related specs, improve the display definition,
replace XXX. For background on why we still expose group info via
attributes: https://bugzilla.mozilla.org/show_bug.cgi?id=371594
Yeah haspopup filled a gap in atk states.
I think it would be great to add a checkable state. It would be exposed for:
check boxes
toggle buttons (e.g. <div role="button" aria-pressed="true">)
radio buttons
check box menu items
radio menu items
xul check box cells
etc.
Cheers,
David
On 29/11/10 4:11 PM, Pete Brunet wrote:
To those on the list,
- I'd like to indicate when an attribute (like layout-guess) is likely
to only be used in a browser so any notes you have on those would be
helpful.
- Are there any that are not really needed by AT?
David,
- Can your document be enhanced to indicate related specs, e.g. css2?
- display: I'd like to be more precise than "similar to".
- Please replace the XXXs with whatever those are placeholders for.
- Why do you have the group attributes when there are already methods
in IA2 for this information?
- According to your document it appears we don't need haspopup (since
this only for ATK/AT-SPI).
- Why not add a checkable state rather than an attribute? Is this
only for check boxes or radio buttons as well?
David Bolter wrote:
Hi Pete,
Our gecko object attributes document is here:
https://developer.mozilla.org/en/Accessibility/AT-APIs/Gecko/Attrs
It is not 100% polished, but should be helpful already. Feedback
always welcome!
Cheers,
David
On 29/11/10 11:12 AM, Pete Brunet wrote:
The draft IA2 object attributes spec is at
http://www.linuxfoundation.org/collaborate/workgroups/accessibility/iaccessible2/objectattributes
It's been about two years since it was worked on so needs some
reviewing and rework.
Rich, Has Symphony added or changed anything? Also is there a new
accessibility lead that should be on this list in place of Xing?
David, What do we need to add for FF?
Andres, Is there anything we need to add for Adobe?
For any additions please provide the information that would be
needed for the spec, i.e. Name, Values, Comments, Reference (to an
existing standard)
Don't forget there is also a text attribute spec at
http://www.linuxfoundation.org/en/Accessibility/IAccessible2/TextAttributes
which I think is up to date. Please review it also. If there are
no changes I'd like to indicate that the text attribute spec is no
longer a draft.
--
*Pete Brunet*
a11ysoft - Accessibility Architecture and Development
(512) 238-6967 (work), (512) 689-4155 (cell)
Skype: pete.brunet
IM: ptbrunet (AOL, Google), [email protected] (MSN)
http://www.a11ysoft.com/about/
Ionosphere: WS4G
_______________________________________________
Accessibility-ia2 mailing list
[email protected]
https://lists.linux-foundation.org/mailman/listinfo/accessibility-ia2
--
*Pete Brunet*
a11ysoft - Accessibility Architecture and Development
(512) 238-6967 (work), (512) 689-4155 (cell)
Skype: pete.brunet
IM: ptbrunet (AOL, Google), [email protected] (MSN)
http://www.a11ysoft.com/about/
Ionosphere: WS4G
_______________________________________________
Accessibility-ia2 mailing list
[email protected]
https://lists.linux-foundation.org/mailman/listinfo/accessibility-ia2
_______________________________________________
Accessibility-ia2 mailing list
[email protected]
https://lists.linux-foundation.org/mailman/listinfo/accessibility-ia2
