jcsteh / axsgrease Goto Github PK

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.

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.

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?

Hi:

1. Visit nvaccess/nvda#5960 or similar
2. 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

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

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.

1. Put a main region around the document.
2. 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.
3. Wrap comments in role=article.
4. Put button role on the elements that expand comments or expand the comments.
5. Put a label on each comment article that says who did what when, e.g., Jesse commented 1 day ago.
6. 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.

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

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).

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!

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

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