Personalization Semantics 1.0 proposal - overlap with ARIA

Hi all,

I did some review of proposed properties in

http://www.w3.org/TR/personalization-semantics-1.0/

and  how they overlap with concepts in the ARIA specifications.

In my opinion, the properties below should be better handled by current or future ARIA concepts instead being part of COGA personalization.

Properties not mentioned here fall clearly in the COGA realm. They should be supported also by screen readers, of course, e.g. directly from DOM if there will be no API mapping on platforms.

Personalization options for ARIA properties were no topic yet, so this remains also to be discussed.

Please feel free to correct me in case I missed or confused something.

Best Regards
Stefan

coga-action<http://www.w3.org/TR/personalization-semantics-1.0/>, coga-actiontaken<http://www.w3.org/TR/personalization-semantics-1.0/>, coga-destination<http://www.w3.org/TR/personalization-semantics-1.0/>, coga-explain<http://www.w3.org/TR/personalization-semantics-1.0/>

It makes sense to have an additional "affordance" oriented property "aria-actions" for blind users what will happen (or was has already happened) and where if they focus roles before interaction, although we would have a potential conflict with allowed aria-roledescription content, which may cover this also by longer explanations of control scope.

coga-extrahelp<http://www.w3.org/TR/personalization-semantics-1.0/>, coga-helptype<http://www.w3.org/TR/personalization-semantics-1.0/>

These could be more efficently covered by a future "aria-controlhelp" replacing "default screen reader hints to use controls"  but I see the point for COGA, too.

coga-feedback<http://www.w3.org/TR/personalization-semantics-1.0/>

This is the realm of replacing "default screen reader announcements when interacting with controls" and could therefore be of benefit in a future "aria-feedback" property for AT. What is missing here is a concept for event-dependant feedback.

coga-messageimportance<http://www.w3.org/TR/personalization-semantics-1.0/>, coga-messagefrom<http://www.w3.org/TR/personalization-semantics-1.0/>, coga-messagetime<http://www.w3.org/TR/personalization-semantics-1.0/>

These are also of great interest for blind users and therefore clear candidates for future additions to the ARIA alert role.

coga-status<http://www.w3.org/TR/personalization-semantics-1.0/>, coga-step<http://www.w3.org/TR/personalization-semantics-1.0/>, coga-steplocation<http://www.w3.org/TR/personalization-semantics-1.0/>

Should be semantic extensions of properties of the ARIA list role. Alternatively, of a lst derived ARIA role task with task items

coga-field<http://www.w3.org/TR/personalization-semantics-1.0/>

This property is redundant to what correct labelling of a field should do using one of the already existing labelling techniques and is considered therefore as superfluous and not needed at all