Re: 'role' should be property

Andrew Fedoniouk wrote:
> About the role: it should be role DOM attribute and role CSS [property]
> that allowed to override value of the DOM attribute.

   Note that this is actually contradictory to the way CSS is handled.
If a specify a |style| attribute on an element, that element will have
that style regardless of what's in the style sheet. What you propose
would be the equivalent of having the style sheet override the |style|

> IAccessible::accRole() [1] is a good example of the case.
> Currently is just impossible for the web author willing to deliver 
> rich content to make it yet accessible. 
> [1]

   Why can't be just standardize a way of using ARIA with HTML[1]?
Perhaps we could roll it into some microformats:

| <html lang="en">
|   <head>
|     <meta name="microformat"
|     content="" title="axs">
|   </head>
|   <body>
|     <span id="slider"
|     class="myslider axs slider valuemin-0 valuemax-50 valuenow-33"
|     tabindex="0" >
|     </span>
|   </body>
| </html>

   In the above, the <meta> tag associates the class name "axs" with an
accessibility microformat. When the class name is declared in a |class|
attribute, the element it's declared on and all it's children will have
their class names checked first against the microformat associated with
"axs". If there's a match, the class names will only be processed for
that specific microformat or supersets thereof. Thus, you can specify
exactly what microformat you want processed and avoid conflicts.

   If the "axs" class name is omitted, the microformat associated with
"axs" will become the first default to check if no other microformat is
specified. If the <meta> is omitted as well, the user agent can still
process the microformat, but the order of processing will be determined
by the user agent.


Received on Friday, 25 May 2007 11:35:30 UTC