W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > April to June 2017

Using Markdown for Github accessibility

From: Wayne Dick <wayneedick@gmail.com>
Date: Tue, 25 Apr 2017 11:31:37 -0700
Message-ID: <CAJeQ8SBBjaooCAFnyobBtNNy5M9epuus4sDU0qF6g5ffXEozSg@mail.gmail.com>
To: public-low-vision-a11y-tf <public-low-vision-a11y-tf@w3.org>, GLWAI Guidelines WG org <w3c-wai-gl@w3.org>
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


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.

Received on Tuesday, 25 April 2017 18:32:51 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 21:08:12 UTC