W3C home > Mailing lists > Public > public-html@w3.org > August 2011

Re: how HTML5 figure and figcaption should/could work

From: Steve Faulkner <faulkner.steve@gmail.com>
Date: Wed, 24 Aug 2011 13:52:05 +0100
Message-ID: <CA+ri+VkY6piyeyaLx0RzV8-js2MzuTp2zx2SXbSSfRMj8-3wqQ@mail.gmail.com>
To: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
Cc: HTMLWG WG <public-html@w3.org>, HTML Accessibility Task Force <public-html-a11y@w3.org>
Hi leif,
in initial feedback from users it seems as if the additon of a caption role
for ficaption may not be needed as the figcaption content would be mapped as
the accessible name for the figure.

Note that in some accessibility APis there is already a caption role defined
[1], the addition of one in ARIA would be for APIs that do not have a
caption role defined.

In regards to figcaption being able to accept flow content, i don't think
this is an issue, the caption element has the same content model (with the
exception it cannot include a table) [2] and that does not cause a problem
for its use as the accessble name for a table.


regards
stevef

[1]
http://accessibility.linuxfoundation.org/a11yspecs/ia2/docs/html/_accessible_role_8idl.html#e37ff81431ee3762a5d41a2cb909108d11ca544bc937d13147ed52437e212e20

[2] http://dev.w3.org/html5/spec/tabular-data.html#the-caption-element

On 24 August 2011 12:51, Leif Halvard Silli <
xn--mlform-iua@xn--mlform-iua.no> wrote:

> Steve Faulkner, Wed, 24 Aug 2011 12:37:37 +0100:
> > I have written some stuff down about how figure and figcaption could
> > work for screen reader users, as currently it is not accessibility
> > supported in browsers or AT.
> > I think there may be the need to create a new role to represent
> > figure, probably an ARIA landmark role.
> >
>
> http://www.paciellogroup.com/blog/2011/08/html5-accessibility-chops-the-figure-and-figcaption-elements/
> >
> > I am asking for feedback from users and implementors.
> >
> > any feedback would be appreciated
>
> +1 I defintely think that a new, default role for figure is needed.
>
> As for caption role, which you also propose, would <caption> also get
> the same role? And what about the problem that Rich takes up in that
> regard - that figcaption -- and caption has the same issue - can take
> flow content. [1] Perhaps the default role should not be used if it
> contains flow content?
>
> [1]
>
> http://www.paciellogroup.com/blog/2011/08/html5-accessibility-chops-the-figure-and-figcaption-elements/comment-page-1/#li-comment-14964
> --
> Leif Halvard Silli
>



-- 
with regards

Steve Faulkner
Technical Director - TPG

www.paciellogroup.com | www.HTML5accessibility.com |
www.twitter.com/stevefaulkner
HTML5: Techniques for providing useful text alternatives -
dev.w3.org/html5/alt-techniques/
Web Accessibility Toolbar - www.paciellogroup.com/resources/wat-ie-about.html
Received on Wednesday, 24 August 2011 12:53:14 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:39:27 UTC