Have ideas about it?
Go to http://wiki.codetalks.org/wiki/index.php/Firebug_Roadmap
Or reply here.
- Aaron
There's one major difference. WAVE toolbar is probably downloaded by
1000s of people. The Firebug app is something that was downloaded over
13.5 million times since release 1.2.1.
I want accessibility testing to no longer be relegated to those folks
who knows what it means and are going to go look for a toolbar. It needs
to be integrated into mainstream tools to really bring awareness about.
Didn't you say lack of awareness was a major issue? :)
Also, why should I use 2 toolbars to debug when I can just have 1? And
why would I want separate ARIA testing from my other accessibility
testing? There's too much overlap to have a perfect separation anyway.
Through code reuse we plan to take the best stuff from the various
accessibility toolbars (WAT, WAVE, UIUC, WebAim) etc. and bring that
stuff together in one place. It just depends on whether the community is
finally ready to work together on these tools rather than all building
separate ones.
- Aaron
I love the idea and imagine being able to debug the state of your widget against a set of compliance guidelines at any particular instant during the execution of a script. Also, the more we can unify the tooling, the better. I still owe this group a write-up on the Eclipse Accessibility Tools Framework (ACTF), the primary goal of which is to unify many types of accessibility-related tooling in the Eclipse environment.
--> Mike Squillace
IBM Human Ability and Accessibility Center
Accessibility Tools Framework (ACTF) co-technical lead
http://www.eclipse.org/actf
W:512.823.7423
M:512.970.0066
External: http://www.ibm.com/able
Internal: http://w3.ibm.com/able
Aaron Leventhal <aa...@moonset.net>
Sent by: free...@googlegroups.com 09/24/2008 10:56 AM
|
|
As a blind web aplication/accessibility tool developer, I'm wondering if this tool is anymore accessible than Firebug? We need accessible accessibility tools. From its description, it seems not.
--> Mike Squillace
IBM Human Ability and Accessibility Center
Accessibility Tools Framework (ACTF) co-technical lead
http://www.eclipse.org/actf
W:512.823.7423
M:512.970.0066
External: http://www.ibm.com/able
Internal: http://w3.ibm.com/able
"S Lauriat" <slau...@gmail.com>
Sent by: free...@googlegroups.com 09/24/2008 06:16 PM
|
|
|
|
But if we *ever* want to make a dent on the zillions of inaccessible
websites constantly being developed, we need to have at least some a11y
stuff built right into the mainstream tools.
I'm tired of finding out that developers have no clue what accessibility
even is. A lot of Mozilla accessibility bugs are filed when people
couldn't access a network :)
Shawn, about the bloat -- are talking about codesize bloat or
UI/complexity bloat? Because the former can be dealt with via
intelligent code reuse, and the latter can at least be handled by
seamlessly integrating into existing features and rethinking some parts
of Firebug itself.
- Aaron
On 9/25/2008 1:16 AM, S Lauriat wrote:
> Aaron,
>
> Starting somewhere around version 1.1, Firebug has become more and
> more bloated, and I've since switched to using WebKit's (refreshed)
> Inspector
> <http://trac.webkit.org/wiki/ProposedWebInspectorUIRefresh> for my
> primary dev tool. I've spoken with numerous developers who have lost
> faith in Firebug since the 1.0 release for the same reason. I very
> much agree with Michael's view, though I suppose making a Firebug
> extension that handles this might make a good compromise.
>
> -Shawn
>
> On Wed, Sep 24, 2008 at 2:45 PM, Aaron Leventhal <aa...@moonset.net
> <mailto:aa...@moonset.net>> wrote:
>
>
> Michael,
>
> There's one major difference. WAVE toolbar is probably downloaded by
> 1000s of people. The Firebug app is something that was downloaded over
> 13.5 million times since release 1.2.1. <http://1.2.1.>
- Aaron
On 9/25/2008 5:37 PM, S Lauriat wrote:
> Aaron,
>
> With the bloat, it seemed like a bit of both. It started getting
> sluggish and buggy, and kept having so many things added into it that
> it now defaults to having nothing available to you.
>
> I /completely/ agree with the frustration of talking to developers and