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

Re: Action-1715: figure role

From: Richard Schwerdtfeger <schwer@us.ibm.com>
Date: Mon, 31 Aug 2015 10:30:59 -0500
To: Steve Faulkner <faulkner.steve@gmail.com>
Cc: HTML A11Y TF Public <public-html-a11y@w3.org>, "WAI Protocols & Formats" <public-pfwg@w3.org>, "public-svg-a11y@w3.org" <public-svg-a11y@w3.org>
Message-ID: <OF69190620.B3F82278-ON86257EB2.0055177F-86257EB2.00553C22@us.ibm.com>

OK,

Why would we need a separate role for caption and why would aria-labelledby
not work in the mappings?

Rich

Rich Schwerdtfeger



From:	Steve Faulkner <faulkner.steve@gmail.com>
To:	Richard Schwerdtfeger/Austin/IBM@IBMUS
Cc:	"public-svg-a11y@w3.org" <public-svg-a11y@w3.org>, "WAI
            Protocols & Formats" <public-pfwg@w3.org>, HTML A11Y TF Public
            <public-html-a11y@w3.org>
Date:	08/31/2015 09:20 AM
Subject:	Re: Action-1715: figure role



Hi Rich will follow up on this next week when I am back from vacation.

There has been some discussion of late around the current mapping for
figure/figcaption and how appropriate it is for the figcaption to be the
label for the figure. This has brought me back to considering the need for
a caption role for figcaption.

On Monday, 31 August 2015, Richard Schwerdtfeger <schwer@us.ibm.com> wrote:
  Hi Steve,

  I have an action to get with you to get agreement on on a new ARIA Figure
  role. We need this for SVG Accessibility as we need a mechanism to
  isolate figures that could be pulled into a list of figures by assistive
  technologies. Since we are doing this for ARIA and SVG  we would also
  like to reuse it for HTML. Please look at the following text and let me
  know if this definition would be sufficient so that HTML could use this
  role as the default native host language semantics for the figure role.


  figure


        A perceivable section of content which supports the main document,
        and should be easily locatable regardless of its position in the
        layout. A figure may contain a graphical document, an image, or
        other content such as code snippets or example text. A figure
        should be referenced from the main text but does not need to be
        displayed directly where it is referenced.

        A figure MAY have an associate label or caption, or an associated
        description.

        Assistive technologies SHOULD enable users to quickly navigate to
        figures. Mainstream user agents MAY enable users to quickly
        navigate to figures.

  The figure role would be a subclass of role section.

  Name From: Author
  Accessible Name Required: False

  Cheers,
  Rich

        Rich Schwerdtfeger




--
--

Regards

SteveF
Current Standards Work @W3C






graycol.gif
(image/gif attachment: graycol.gif)

Received on Monday, 31 August 2015 15:31:47 UTC

This archive was generated by hypermail 2.3.1 : Monday, 31 August 2015 15:31:48 UTC