EDIT: The commit message is an imgur link of the original email: https://imgur.com/QC51FZz
3,580 karma · joined March 15, 2012
webmaster @ notion
email me! scalesjordan@gmail.com
EDIT: The commit message is an imgur link of the original email: https://imgur.com/QC51FZz
There's a certain undertone with the word "actual" - as if other depictions of feminism are not valid. It's just strange that it's there at all.
But whatever, words are hard.
> women working a 'typical' male job is actual (not true) feminism when you compare it to bitching on tumblr or bitching about a shirt of a scientist. in my opinion.
[0]: https://www.reddit.com/r/pics/comments/3e1q3j/actual_feminis...
There is currently a post with several thousand points: a picture of two women on the back of a garbage truck with the caption "Actual feminism." I'm not sure what that has to do with feminism, but I guess Reddit thinks women need to work seemingly "dirty" jobs before they're allowed to complain about work conditions.
But you're right, if you customize your subreddits you can avoid a lot of the scum.
Look at the front page right now.
Focusable should be the default, as many folks can't (or don't want to) use a mouse. Use the semantic <button> tag or even just an <a> with role="button" and you'll get accessibility for free.
[0]: http://thatjdanisso.cool/a11y/clicking-with-a-keyboard/
Gulp uses streams, this uses generators. Some folks may like the look and feel of generators more than streams.
This is a known bug (https://github.com/Khan/tota11y/issues/1) that comes from upstream (https://github.com/GoogleChrome/accessibility-developer-tool...) and will hopefully be fixed soon.
As for your notes on screen-reader text: you can "hide" it by not actually hiding it, but placing it off the side of the page. This will be picked up by screen-readers and will not cause any positioning issues.
We use the following snippet all over Khan Academy. Bootstrap 3 uses it as well.
.sr-only {
border: 0;
clip: rect(0,0,0,0);
height: 1px;
margin: -1px;
overflow: hidden;
padding: 0;
position: absolute;
width: 1px;
}
So I'd like to assure you that your image link is good to go (assuming the alt-text is good!). Sorry for the troubles.Perhaps we can detect if a popular userscript manager is installed and provide a one-click link that way. Not sure if this is possible though.
[0]: http://nibbler.silktide.com/
[1]: http://pa11y.org/
The reason for this is because many screen-readers have keyboard shortcuts to jump from heading to heading. Many users will map out the page with this key-binding. Keeping the headings in a good order is very important.
At Khan Academy we use Chrome's Accessibility Developer Tools (https://github.com/GoogleChrome/accessibility-developer-tool...) as part of our testing infrastructure. A few of us also have the browser extension to do some manual testing, which is what tota11y is for.
tota11y uses Accessibility Developer Tools internally.
Love the work Alice & co are doing. We're big users of Accessibility Developer Tools (https://github.com/GoogleChrome/accessibility-developer-tool...) at Khan Academy both as part of our automated testing process and now as part of tota11y.
Really excited to see it to make its way into DevTools proper! Been rocking the extension for a few months now.
Userscript is an awesome idea, thanks for taking the time to build this out. Is this something that will work in all browsers? What's the installation process like? Perhaps we can build one of those into the project page as well.
I built this utility with the help of two colleagues[0][1] after working on accessibility at Khan Academy for a few weeks, and seeing first-hand the process of evangelizing accessibility on a dev team. Our automated tests were far from approachable (and became more annoying than helpful), so we built tota11y to make the manual testing experience more interactive and educational (we like teaching things).
I touch on this in our engineering blog [2]
Anyway, super thrilled to see tota11y near the top of HN this morning, and happy to answer any questions you may have.
[0]: https://twitter.com/himichelletodd
HTML_CodeSniffer is significantly more comprehensive than tota11y, so I encourage everyone reading this to also check out corney91's link.
tota11y takes more of a visualization approach, because in our experience being greeted with several dozen errors which we've never seen before didn't motivate us to keep the site accessible. My aim was to make the experience more interactive while explaining errors (and fixes!) as best I can.
We're still figuring out where tota11y fits in this great big world of a11y testing, but so far folks have responded well to this approach.
I've heard of some ways to visualize this with SVG filters - so this will be coming soon.
Still thinking of creative ways to find and label the errors, rather than just showing the user how the page will look under a certain type of color-blindess.
http://martinfowler.com/articles/collection-pipeline/
I also don't think he invented the term. A quick google search shows it's connected with LINQ.