jcsteh / axsgrease Goto Github PK

Greasemonkey scripts to improve the accessibility of various websites (e.g. Pandora) and to solve common web accessibility problems (e.g. windowless Flash).

JavaScript 100.00%

axsgrease's Introduction

AxSGrease

Author: James Teh <[email protected]> & other contributors
Copyright: 2011-2022 NV Access Limited, James Teh

AxSGrease is a set of user scripts (also known as GreaseMonkey scripts) to improve the accessibility of various websites.

Installation

Before you can install any of these scripts, you must first install a user script manager for your browser. For Firefox, you can install GreaseMonkey. For Chrome, you can install Tampermonkey. There are also user script managers for other browsers. See Greasy Fork's page on How to install user scripts for more details.

Once you have a user script manager installed, simply activate the download link for the relevant script below to download and install it.

Scripts

Note: This documentation is out of date. Some newer scripts are missing, some older scripts should be removed, etc.

Following is information about each script.

Asus Router Accessibility fixes

Download Asus Router Accessibility Fixes This script improves the accessibility of the asus router firmware. (this has only been tested on RT-AX56U router). it does the following:

makes tutor help messages automatically read.
Creates a primary and secondary navigation region, and removes layout tables for navigation.
Adds section headers to the nav menu, at heading level 2.
Makes pages that have a title have an h1.
Labels some unlabeled images.

Bugzilla Accessibility Fixes

Download Bugzilla Accessibility Fixes

This script improves the accessibility of bug pages in the Bugzilla bug tracker used by many projects. It does the following:

Makes the bug title, attachments heading and comment number headings accessible as headings.
Sets alternate text for user images so that screen readers don't derive an unfriendly name from the URL.

GitHub Accessibility Fixes

Download GitHub Accessibility Fixes

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.

Monorail Accessibility Fixes

Download Monorail Accessibility Fixes

This script improves the accessiblity of the Monorail issue tracker used by Google for Chromium-related projects. It does the following:

Makes issue titles and comment headings accessible as headings.
Makes the star control and status accessible.

Telegram accessibility fixes

Download Telegram Accessibility Fixes

This script improves the accessibility of the Telegram instant messaging web interface.

It so far does the following:

Marks the chat history as a live region so new messages are announced automatically.

Trello Accessibility Fixes

Download Trello Accessibility Fixes

This script improves the accessibility of Trello. It does the following:

Makes lists and cards accessible as lists and list items, respectively.
Focuses the active card when moving between lists and cards with the arrow keys. If you are using a screen reader, you will need to ensure that the arrow keys are passed to the application to make use of this. For NVDA, you can achieve this by switching to focus mode to move through cards.
Labels badges in cards.
Makes list headers and activity item headers accessible as headings.
Prevents loss of position for screen reader users when pressing the control key.
Adds a shift+m keyboard shortcut to quickly move a card.
Makes checklists accessible.
Makes the checkbox for due date completion accessible.

axsgrease's People

Contributors

Stargazers

Watchers

Forkers

ming-hai nvdaes jwyung yplassiard audreymaniez jessebeach tuukkao dalavancloud gsputnik marcozehe michaeldcurran 43-stuti sanchit002sanchit002 techromantica derekriemer jscholes

axsgrease's Issues

Use document.location.path instead of document.location.href

The regexp would be cleaner if we did
var res = document.location.pathName.match(//[^\/]+/[^\/]+(?:/([^\/?]+))?(?:/([^\/?]+))?(?:/([^\/?]+))?(?:/([^\/?]+))?/);
pathNamed only gives us the thing after the url.
Also why couldn't we use
var res = document.location.pathName.match(/(?:/[^\/]+){2}(?:/([^\/?]+))?(?:/([^\/?]+))?(?:/([^\/?]+))?(?:/([^\/?]+))?/);
I'm happy to give a PR if you want.

Possible erronious code

I was looking to fix the unspoken bug where "level n" is spoken afterward if the role is nuked.
On 1012 of speech.py, role is retreived, although I think this is incorrect since "_role" or "role" both may have our info, and it should already be in role. Above, role is set to either "_role" or "role", depending on which is available. If so, should this line be removed?

New Script for Quip

Put a main region around the document.
Add a button to the beginning of main that removes/restores contenteditable from elements in the main content. There is an outstanding question as to what it will take to force browsers to update their accessibility tree after doing that. Just removing the attribute is not good enough based on Jesse’s bookmarklet. We could leave the restore function off it refreshing the page restored it.
Wrap comments in role=article.
Put button role on the elements that expand comments or expand the comments.
Put a label on each comment article that says who did what when, e.g., Jesse commented 1 day ago.
It would also be really helpful if there were some way we could make the script help with the export process. Resolving that may be quite a bit more tricky. The menu elements have the right roles, but they don’t reliably respond to screen reader click events and never get DOM focus.

Comment age is broken.

Hi:

Visit nvaccess/nvda#5960 or similar
Go by heading with the script installed, you hear things like derekriemer commented Link to this comment
it is the case that they are stupidly putting
derekriemer commented Link to this comment
and Link to this comment is an aria-label. Could the script be updated to nuke this?
Hint:
on Jun 29

Headings for lists on Trello override editfield contents

It seems when navigating by heading to jump between various lists on a Trello board, the name of the list is not spoken. One needs to hit focus mode on one of the headings to get this information.

Make scripts support Chrome.

Hi:
User scripts supported are in chrome. However, https://www.chromium.org/developers/design-documents/user-scripts seems to claim we need //@match in the //userScript part.

Submit BugZilla changes to upstream?

What about submitting the Bugzilla changes to Mozilla? As Bugzilla is open-source I think more people can profit from this "patch".

monorail fixes don't work on the project 0 page

visit https://bugs.chromium.org/p/project-zero/issues/detail?id=1139
Note that monorail fixes don't apply, but this is monorail.

Still maintained?

It seems that jcsteh/axSGrease contains newer and more scripts. Should this repo be updated to point to that one?

Github Scripts: consider removing display:block from tables in github wikis

In github wikis, if you create a table in markdown, for instance in a mediawiki page, github renders it with display:block. As a result, the table is not recognized as a table in Firefox or Chrome.

For an example of this, see the release plans page in the aria-practices wiki. There is a table under the heading "Plans by Version and Release". However, it is not readable as a table when using Firefox or Chrome.

I also reported this to github because I do not think it is appropriate to apply display:block to all wiki tables by default. Further, it is debatable whether or browsers should hide the table semantics based on the display:block styling. For instance, see Firefox bug 1005271.

Until there is some change in Github or in Firefox or Chrome, the only way to read tables in the github wikis is to use IE, which is not really a practical option. So removing or overriding the display:block from the tables would be super helpful!

GitHub Pull Requests - headings on file page no longer getting fixed

IN pull requests, on the files tab, The file names are no longer getting rendered as headings for me.

Reordering issues functionality overridden

Github has recently introduced the ability to reorder issues under milestones using buttons. When the Greasemonkey/Tampermonkey scripts are enabled, these buttons are not recognised.
In Chrome and Firefox with NVDA, there doesn't seem to be any indication that the buttons are present at all. In Firefox with Jaws it's the same, but in chrome the buttons are reported as graphics (with "move up" or "move down" also announced).