Re: aria-describedat?

> If so, what would be the best way to go about actually implementing
> it? Presumably there are gatekeepers (e.g. Asa Dotzler) who have an
> influence on what does or does not go into Firefox's chrome. What's
> the procedure for getting such gatekeepers on side? What's the
> procedure for getting their feedback on the design?

I think file a bug, cc gatekeepers and ask them for feedback.
Alex.

On Wed, Mar 14, 2012 at 4:37 PM, Benjamin Hawkes-Lewis
<[email protected]> wrote:
> On Tue, Mar 13, 2012 at 4:17 PM, Benjamin Hawkes-Lewis
> <[email protected]> wrote:
>> With that in mind, would there be any interest in tackling:
>>
>>    https://bugzilla.mozilla.org/show_bug.cgi?id=longdesc
>>
>> Perhaps along the lines of:
>>
>>    http://my.opera.com/chaals/blog/tell-me-more
>>
>> Or even a more basic implementation as in iCab and Opera?
>>
>> I don't see why a name change should make a difference here, but if
>> there's no interest in implementing browser UI for @longdesc, would
>> there be any interest in implementing such UI for @aria-describedat?
>
> OK, so disappointing radio silence so far; allow me to push the
> conversation in a slightly different direction.
>
> Let's say that to get a universally accessible hidden long description
> link we came up with a design including an accessibility API mapping,
> a context menu action, a hover effect, and a button somewhere in the
> browser chrome that appears when long descriptions are present in the
> page and provides access to long descriptions to keyboard/switch users
> who can't hover over images.
>
> Is it socio-politically feasible for someone (let's say me - for the
> sake of argument) to implement this in Firefox so that all Firefox
> users will have access to long descriptions?
>
> If so, what would be the best way to go about actually implementing
> it? Presumably there are gatekeepers (e.g. Asa Dotzler) who have an
> influence on what does or does not go into Firefox's chrome. What's
> the procedure for getting such gatekeepers on side? What's the
> procedure for getting their feedback on the design?
>
> Would a name change to the attribute make the slightest bit of
> difference to the feasibility of actually doing this?
>
> If there's no chance that Mozilla would even consider adding ambient
> features to Firefox's user interface to support long descriptions for
> all, then we're wasting our time discussing this.
>
> --
> Benjamin Hawkes-Lewis