Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Tota11y

khan.github.io

Post reply on HN
Print view View original

71–80 of 93 posts

Re: Tota11y

#71

Post by tracker1 »

Someone1234 wrote: post #60
metaobject wrote: post #21

I'll post this here since people interested in accessibility will be reading this thread. I have terrible vision. One of my pet peeves is when I go to a website on my phone through safari that doesn't allow me to zoom the text. For those occasions, I came across a JavaScript bookmark that I created on my phone that runs to undo whatever is preventing me from zooming in. I'm not a web developer (I do desktop/server so…

This is a little off topic, but if you use Chrome on Android you can disable site's ability to disable zoom. - Open Chrome (or Chrome Beta) on Android. - Settings -> Accessibility - Force enable zoom (check). Sites may need to be reloaded after applying this setting.

For that matter, you can also set a default text-scaling level as well (mine is at 130%), which I tend to do in addition to force enable zoom. Many sites have fonts that are too small on a phone imho... they really should be at least 12pt for most text assuming that proper scaling meta is set... Too many sites use 9-10pt fonts which are just really hard to read.

I'm far sighted, so my phone is literally the hardest thing for me to use much of the time. One of the worst offenders was the Facebook app, which didn't seem to even follow Android's setting for using larger fonts. I've since stopped using the FB app (way too much battery usage), and just use the mobile site, which isn't much better in terms of usability.

Re: Tota11y

#72

Post by dsugarman »

prezjordan wrote: post #48

Hey HN! 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 to…

Great job, love it! It would be really cool if you had a toggle for implementing the suggestions, so you could instantly see if a suggested change looks better.

Re: Tota11y

#73

Post by prezjordan »

dsugarman wrote: post #72
prezjordan wrote: post #48

Hey HN! 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 to…

Great job, love it! It would be really cool if you had a toggle for implementing the suggestions, so you could instantly see if a suggested change looks better.

Thanks :) We've got an issue open for this - https://github.com/Khan/tota11y/issues/21, so hopefully coming soon.

Re: Tota11y

#74

Post by breckenedge »

aikah wrote: post #53
prezjordan wrote: post #48

Hey HN! 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 to…

Nice, what would be cool is to have something like this online (as a service), that could fetch a page and make a report. The report could then be shared with web designers who use an insufficient contrast ratio between their background and their text for instance, no need to be visually impaired to be bothered by sites who do that kind of stuff, and they are way too many.

WAVE[1] at WebAIM will do this for you. It was built by a non-profit dedicated to online accessibility. Just type in an address and go. They also have a Chrome plugin [2] that runs the same accessibility checks in your browser and produces a report. I found it very helpful on a recent accessibility project. Nice to see more developers caring about this.

[1] http://wave.webaim.org/

[2] https://chrome.google.com/webstore/detail/wave-evaluation-to...

Re: Tota11y

#75

Post by nmesse »

prezjordan wrote: post #54
sparaker wrote: post #14

Earlier quoted context omitted.

under an has nothing to do with accessibility. Its just some people think it makes sense to have smaller headings after bigger ones and not the way around. I for one think that it sometimes is important to use an h2 after an h4. This has nothing to do with semantics btw.

Please try and avoid using heading tags for size alone :) If it's for design purposes, just resize some 's, and let headings (even ones hidden off the side of the screen) define the structure of the document (as we explain in the error description). 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. Keepin…

Da basics.... You know, separate content from presentation. Content being the HTML page, and presentation being the styling. Semantically right HTML should be the primary goal when writing HTML. You can than style it 40 different ways using CSS.

Re: Tota11y

#77

Post by magicmu »

prezjordan wrote: post #48

Hey HN! 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 to…

Awesome tool, thank you for making this available to the community! I'm going to take a crack at integrating this into our ember application and (hopefully) cut back on some of the support. Is there any formal ember-cli support in the works?

Re: Tota11y

#78

Post by prezjordan »

magicmu wrote: post #77
prezjordan wrote: post #48

Hey HN! 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 to…

Awesome tool, thank you for making this available to the community! I'm going to take a crack at integrating this into our ember application and (hopefully) cut back on some of the support. Is there any formal ember-cli support in the works?

Nope no formal support. I'm not terribly familiar with ember-cli, but I'd love to hear how we can make it easier to use tota11y with any codebase.
Post reply on HN