W3C home > Mailing lists > Public > public-low-vision-a11y-tf@w3.org > April 2017

Re: Using Markdown for Github accessibility

From: David MacDonald <david100@sympatico.ca>
Date: Tue, 25 Apr 2017 15:04:33 -0400
Message-ID: <CAAdDpDa6UX9ZvB5Y6QWYiP+vprQwBSMj9hq1AokU8+NcV_z_iw@mail.gmail.com>
To: Wayne Dick <wayneedick@gmail.com>
Cc: public-low-vision-a11y-tf <public-low-vision-a11y-tf@w3.org>, GLWAI Guidelines WG org <w3c-wai-gl@w3.org>
So would you like every comment to start with a ## level 2 heading going
forward?

Cheers,
David MacDonald



*Can**Adapt* *Solutions Inc.*

Tel:  613.235.4902

LinkedIn
<http://www.linkedin.com/in/davidmacdonald100>

twitter.com/davidmacd

GitHub <https://github.com/DavidMacDonald>

www.Can-Adapt.com <http://www.can-adapt.com/>



*  Adapting the web to all users*
*            Including those with disabilities*

If you are not the intended recipient, please review our privacy policy
<http://www.davidmacd.com/disclaimer.html>

On Tue, Apr 25, 2017 at 2:31 PM, Wayne Dick <wayneedick@gmail.com> wrote:

> There are ways that regular members of the group could help assistive
> technology users with Github.
>
> The easiest way is to enable heading navigation.
>
> H1 = # text
> H2 = ## text
>
> Etc.
>
> Each SC has a main issue, like 78 for adaptive text. Github does not have
> a way to partition these into threads.
>
> We could block these off with headings.
>
> # To start a new item.
> ## to continue an item.
>
> Then follow your message from this heading.
>
> People who are not on AG do not need to do this, but members can.
>
> We don't need to go back and address everything. Just start now.
>
> When you start an new idea thread, give it an H1
>
> # New Thread Name
>
> When you respond to a thread give it an H2
>
> ## Continue Thread Name
>
> Even 50% compliance would give us landmarks to shoot at.
>
> Wayne
>
>
Received on Tuesday, 25 April 2017 19:05:09 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 27 April 2017 14:44:35 UTC