Open Bug 704449 Opened 13 years ago Updated 2 years ago

expose @cite attribute on blockquote/q elements to AT

Categories

(Core :: Disability Access APIs, defect)

defect

Tracking

()

People

(Reporter: surkov, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: access)

there's no visual representation of cite attribute, it's exposed via DOM HTMLQuoteElement interface only. It sounds it's reasonable to expose HyperLink interface on it and provide an action to open hyperlink similarly like we do longdesc attribute on img element. Thoughts?
This sounds reasonable to me, but you might also want to get Jamie's oppinion on how useful this is to AT vendor implementation relying on IA2 rather than iSimpleDOM.
alex wrote: "It sounds it's reasonable to expose HyperLink interface on it and provide an action to open hyperlink similarly like we do longdesc attribute on img element." what action is currently provided for longdesc? It would be a major improvement for all to provide a method for users to be made aware of the cite link and open it via the browser (same goes for longdesc)
Extra action is exposed on img accessible that has longdesc attribute, if AT invokes that action then we open a window with URI pointed by longdesc. I thought something like this we could implement for cite attribute on quote elements. Mozilla had bugs asking to implement visual presentation of @cite attribute but they were closed because HTML spec says nothing about that. I think we could file new bug for that, come with ideas and describe what that's important (that wasn't implemented for ages by no one browsers if I get right).
Will this method, in general, allow user to discern between @longdesc and @cite? What about cases such as <q cite=link1 ><img longdesc=link2 ></q> - would they be able to access both the @longdesc and the @cite?
(In reply to Leif Halvard Silli from comment #4) > Will this method, in general, allow user to discern between @longdesc and > @cite? @longdesc attribute is not applied to to q or blockquote elements, so no collision. > What about cases such as <q cite=link1 ><img longdesc=link2 ></q> - would > they be able to access both the @longdesc and the @cite? in this case we have two accessible objects, q element accessible and img element accessible, each of them is supposed to expose an action.
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.