-
Notifications
You must be signed in to change notification settings - Fork 534
Modify advice to use figcaption as table caption #251
Comments
Thank you for looking into it. Rabab |
Is there any practical rationale for saying the Changing should to may seems reasonable, and removing the statement entirely seems reasonable, unless there is some legacy that means one approach is actually better. |
I was actually wondering why we have a |
On 28 April 2016 at 01:33, Travis Leithead notifications@github.com wrote: too tied up in table processing to be portable to this scenario? I believe this is the reason for figcaption, I can find historical Regards SteveF |
Another argument to support removal of < figcaption > statement with data tables:
@stevefaulkner it will be great if you can bring more info. |
https://youtu.be/ZV0a6jSda30
|
Thanks for the demo! So, |
In principle, either approach should work. Recommending It doesn't seem illogical that a In any case, I think we need tests to discover what actually works, and then we should make the spec match. @RubyDo can you post the test case somewhere so we can try it out in other systems? (Otherwise I can make a couple, but I assume you already have the thing written so it's easy). |
@chaals I updated my demo comment with steps |
Have made some change: 1fa9024 in the spec after reviewing the discussion:
|
This makes things much easier to read and understand. Couple of thoughts... I would be inclined to drop the examples that use Also, minor editorial nit, in the last note in section 4.9.1.1: The word "the" should be added between "of" and "method". |
Hmm. This is a problem, because it is also used to provide a caption for sighted users, where the extra information is actually pretty valuable. I presume this dilemma is why the HTML 5 spec hoped that using Perhaps the answer is that the "further information" should be provided in the body of the |
@LJWatson |
@chaals Agree the descriptive info should be visible. The other examples suggest ways to do this and retain a programmatic association with the table, but without cluttering up the |
Migrated from Bugzilla #22074:
https://www.w3.org/Bugs/Public/show_bug.cgi
@stevefaulkner
If the
<figure>
contains only a table, is the assumption here that the<caption>
would provide the accessible name for both the<figure>
and the<table>
?The text was updated successfully, but these errors were encountered: