Re: Headings in comments

Hey Sean,
Shouldn't there be a single solution that works for all?

Thanks,
-Vasu

Regards,

Srinivasu Chakravarthula - Twitter: http://twitter.com/CSrinivasu/
Website: http://www.srinivasu.org | http://serveominclusion.com

Let's create an inclusive web!

Lead Accessibility Consultant, Informatica


On Thu, Nov 30, 2017 at 7:20 AM, Sean Murphy (seanmmur) <seanmmur@cisco.com>
wrote:

> Is this for visual layout so people can see where the comments and their
> relationship or for screen reader users? If the latter, I would propose
> regions and call it comments. Using a div with the correct ARIA attribute
> would work.
>
>
>
> [image:
> https://www.cisco.com/c/dam/m/en_us/signaturetool/images/banners/standard/08_standard_graphic.png]
>
> *Sean Murphy*
>
> ENGINEER.CUSTOMER SUPPORT
>
> seanmmur@cisco.com
>
> Tel: *+61 2 8446 7751*
>
>
>
>
>
>
>
>
>
> Cisco Systems, Inc.
>
> The Forum 201 Pacific Highway
> <https://maps.google.com/?q=201+Pacific+Highway%0D+ST+LEONARDS%0D+2065%0D+Australia&entry=gmail&source=g>
>
> ST LEONARDS
> <https://maps.google.com/?q=201+Pacific+Highway%0D+ST+LEONARDS%0D+2065%0D+Australia&entry=gmail&source=g>
>
> 2065
> <https://maps.google.com/?q=201+Pacific+Highway%0D+ST+LEONARDS%0D+2065%0D+Australia&entry=gmail&source=g>
>
> Australia
> <https://maps.google.com/?q=201+Pacific+Highway%0D+ST+LEONARDS%0D+2065%0D+Australia&entry=gmail&source=g>
>
> cisco.com
>
> [image: http://www.cisco.com/assets/swa/img/thinkbeforeyouprint.gif]
>
> Think before you print.
>
> This email may contain confidential and privileged material for the sole
> use of the intended recipient. Any review, use, distribution or disclosure
> by others is strictly prohibited. If you are not the intended recipient (or
> authorized to receive for the recipient), please contact the sender by
> reply email and delete all copies of this message.
>
> Please click here
> <http://www.cisco.com/c/en/us/about/legal/terms-sale-software-license-agreement/company-registration-information.html>
> for Company Registration Information.
>
>
>
>
>
> *From:* Mike Gifford [mailto:mike@openconcept.ca]
> *Sent:* Thursday, 30 November 2017 12:15 PM
> *To:* Tobias Bengfort <tobias.bengfort@posteo.de>
> *Cc:* w3c WAI List <w3c-wai-ig@w3.org>
> *Subject:* Re: Headings in comments
>
>
>
> I think we’ve got this settled in Drupal 8.
>
>
>
> By default headings are enabled in comments (H2-H6).
>
>
>
> We discussed this and would like to see the ability to position the top
> header under whatever header that comment will be positioned in, but at
> this stage there isn’t a sweet universal way to do this. Maybe in HTML 6.
>
>
>
> YouTube & Disqus are not good examples of accessibility.
>
>
>
> If someone is writing a detailed comment, they should be able to break it
> down into sections that allow for greater readability/navigation.
>
>
>
> If you’re restricting the length of the comments to say 250 characters
> then you might as well eliminate the headings. If you don’t restrict the
> length of the comments you should restrict the structure.
>
>
>
> Mike
>
>
>
> On Nov 29, 2017, at 7:40 PM, Tobias Bengfort <tobias.bengfort@posteo.de>
> wrote:
>
>
>
> Hi,
>
> I was wondering about the best practices for headings in comments.
>
> I looked at the comments on youtube and disqus and found that neither
> have headings. It would also be hard to tell which part of a comment
> qualifies as a useful title.
>
> Do you think that each comment should have its own heading to allow easy
> navigation? Or should headings in comments be omitted in order not to
> clutter the document outline?
>
> tobias
>
>
>
> --
>
> Mike Gifford, President, OpenConcept Consulting Inc.
> Drupal 8 Core Accessibility Maintainer - https://drupal.org/user/27930
> Twitter: @mgifford @openconcept_ca
>
>
> Open source web development for social change - http://openconcept.ca
> Drupal Association Member | Acquia Partner | Certified B Corporation
>
>
>