This looks cool. I have to admit that to this point, I've not been required to make sure that things are accessible by screen readers and the like. It looks like if I'm ever required to do so, that this plug-in will make things *much* easier! Nice work. :o)
Chris On Dec 3, 2007 1:03 PM, Chris <[EMAIL PROTECTED]> wrote: > > On Dec 3, 5:31 am, "Richard D. Worth" <[EMAIL PROTECTED]> wrote: > > > This looks really good. Especially, thanks for gathering a bunch of > summary > > information in your well-written docs. > > Thank you, and you're welcome. > > > 1. I prefer acronyms exceeding 3 chars to be not all caps. AriaRole, > > AriaState, is a lot easier to read and type. > > As in "XMLHttpRequest"? I agree, and changed the method names. To keep > with the convention of methods starting with lowercase letters, I've > changed them to "ariaState()" and "ariaRole()", etc. > > > 2. When I first saw hasARIARole and hasARIAState, I assumed it would > return > > a boolean (has- and is- suggest boolean to me). Since it's returning a > set > > of elements, perhaps something like AriaRoleFilter, AriaStateFilter > would be > > more jQuery-like. > > They are now ariaRoleFilter() and ariaStateFilter(), respectively. > > I've also added a custom "ariaready" event that gets fired when the > ARIA information in the document has been parsed. > > Thanks again for the feedback. > > Regards, > > Chris > > email: mistermuckle *at* gmail *dot* com > -- http://cjordan.us
