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

Re: Re[2]: GitHub accessibility improvements

From: David MacDonald <david100@sympatico.ca>
Date: Fri, 19 May 2017 13:45:50 -0400
Message-ID: <CAAdDpDbbaif5610VgQdqmYDkAt1S7BrPC_vuZE_WhVkwFguETA@mail.gmail.com>
To: Eric Eggert <ee@w3.org>
Cc: "Repsher, Stephen J" <stephen.j.repsher@boeing.com>, WCAG <w3c-wai-gl@w3.org>
Will it be German Beer or Dutch Beer?

... <inside joke from CSUN>

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 Fri, May 19, 2017 at 8:59 AM, josh@interaccess.ie <josh@interaccess.ie>
wrote:

> Congrats Steve *awesome.
>
> ------ Original Message ------
> From: "Eric Eggert" <ee@w3.org>
> To: "Repsher, Stephen J" <stephen.j.repsher@boeing.com>
> Cc: "WCAG" <w3c-wai-gl@w3.org>
> Sent: 19/05/2017 12:04:20
> Subject: Re: GitHub accessibility improvements
>
> Thank you, Steve, for taking the initiative on this. I think the AG WG and
> other working groups now owe you a drink of your choice at TPAC or WG
> meetings :-)
>
> Best,
> Eric
>
> On 18 May 2017, at 14:03, Repsher, Stephen J wrote:
>
>
> I followed up with GitHub support regarding easier navigation of comment
> threads. They responded by implementing an <h3> tag around each comment’s
> header containing the name and date/time. This change is live on the site
> now.
>
> To keep the dialogue open with their accessibility team, I also made them
> aware of the list of fixes implemented by the NV Access GreaseMonkey script
> (listed below). I’ll keep the group apprised of any additional changes they
> inform me of.
>
> Steve
>
>
> Begin forwarded message:
>
>
> Hey Steve,
>
> Thanks for sending that over! I'll pass those suggestions over to our
> accessibility team. :)
>
> Cheers,
> Antonio
> GitHub Support
>
> Okay, thanks. For other accessibility issues, you might start by taking a
> look at the list of fixes implemented by the NV Access Grease Monkey script
> (https://github.com/nvaccess/axSGrease). I've copied it here:
>
> This script improves the accessibility of GitHub. It does the following:
> • Makes various headings accessible as headings, including:
> • Comment headers in issues, pull requests and commits
> • Commit group headers in commit listings
> • The commit title for single commits
> • The header for each changed file in pull requests and commits
> • Ensures that various data tables aren't treated as layout tables,
> including:
> • The file content when viewing a single file
> • File listings
> • Diff content
> • Tables in Markdown content
> • When there are lines of code which can be commented on (e.g. a pull
> request or commit), puts the comment buttons after (rather than before) the
> code.
> • Makes the state of checkable menu items accessible; e.g. in the watch and
> labels pop-ups.
> • Marks "Add your reaction" buttons as having a pop-up, focuses the first
> reaction when the add button is pressed and makes the labels of the
> reaction buttons less verbose.
>
>
>
>
>
>
> --
>
> Eric Eggert
> Web Accessibility Specialist
> Web Accessibility Initiative (WAI) at World Wide Web Consortium (W3C)
>
>
>
Received on Friday, 19 May 2017 17:46:26 UTC

This archive was generated by hypermail 2.3.1 : Friday, 19 May 2017 17:46:27 UTC