Hi Folks

I am writing a Taxonomy of Roles for Accessible Adaptable Applications
See http://www.ubaccess.com/lisa/GUIRoleTaxonomy.html

A bit of background: Roles add semantics to content to improve the accessibility and interoperability of Web Content and Applications. It initially was  the result of the gap analysis of the DHTML accessibility roadmap to add semantics to enable accessible dynamic content and scripts (used with States and Adaptable Properties Module )  but now has  more diverse use cases such as a, accessible custom widgets using scripts, (it can also be used for  a less common base documents  type such as SVG ) or b, restructuring a page to make it easer for slow readers. 

Anyway...

Can  people take a look at it? I have a few specific questions - but would like any (not to abusive)  feedback

Specific questions:

• We had want to make it clear - programaticly how this specification relates to other specification. EG We want to be able to say that our concept of an check box is similar to html or xform or their concept. Not inheritance but just to clarify that they are related ideas - conceptually close. We were going to use SKOS , Let me know if anyone thinks this is usefully and appropriate. (Danbri and Jang seemed to think it was overloading and unnecessary)
• HTML  (I think) have suggested that we extend them so they can point to it for their roles - is this overwriting other people works
• Are there other concepts or taxonomies we should be looking at

And any other comments

All the best
Lisa