Skip to content

Check Web Accessibility #6

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
ghutchis opened this issue May 8, 2015 · 8 comments
Open

Check Web Accessibility #6

ghutchis opened this issue May 8, 2015 · 8 comments

Comments

@ghutchis
Copy link
Contributor

ghutchis commented May 8, 2015

We need to check for web accessibility:

http://wave.webaim.org
http://achecker.ca/checker/
http://www.cynthiasays.com
http://fae20.cita.illinois.edu

Anecdotally, a visually impaired staff member said the font size was "small" but was able to increase it easily.

@RitwikGupta
Copy link
Member

I'll have to look up the accessibility guidelines. Let's do this check once Dr. Lambrecht's dev server is up and running.

@JoshuaRogan
Copy link
Contributor

I agree this isn't a primary concern right now. I also already increased the font from 14-16px.

@ghutchis ghutchis added this to the 1.0-launch milestone May 12, 2015
@ghutchis
Copy link
Contributor Author

ghutchis commented Jun 8, 2015

We need to revisit this. Please take a look particularly at the first two links, which indicate some issues, most should be fixable.

@ghutchis
Copy link
Contributor Author

ghutchis commented Jun 8, 2015

@JoshuaRogan JoshuaRogan modified the milestone: 1.0-launch Jun 18, 2015
@RitwikGupta
Copy link
Member

99% of the accessibility "errors" presented by these analyzers is just how Bootstrap uses tags in a broad manner. a tags may necessarily not be links, etc. I'm not sure how to go about this without making the site look ugly.

@JoshuaRogan
Copy link
Contributor

I can make some changes to cut down on them. But you are right I don't
think we will be able to remove all of them.

On Sun, Jul 12, 2015 at 3:27 AM Ritwik Gupta notifications@github.com
wrote:

99% of the accessibility "errors" presented by these analyzers is just how
Bootstrap uses tags in a broad manner. a tags may necessarily not be
links, etc. I'm not sure how to go about this without making the site look
ugly.


Reply to this email directly or view it on GitHub
#6 (comment)
.

Josh Rogan
JoshuaRogan.com

@JoshuaRogan
Copy link
Contributor

All of the empty links that are being flagged for not having text do have title text. From what I have been looking up this is acceptable for accessibility.

@blueocto
Copy link

Hi @JoshuaRogan the title attribute (as far as I've tested) isn't read aloud on screenreaders and is meant to be an accompaniment to actual text inside the tags, not instead of.

The W3C mention "For each anchor element that has a title attribute, check that the title attribute together with the link text describes the purpose of the link."

Scott O'Hara wrote an amazingly thorough article on the complexities of the title attribute here: https://www.24a11y.com/2017/the-trials-and-tribulations-of-the-title-attribute/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants