Skip to content
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

accessibility ( sr-only versus assistive-text class) #35

Closed
bassjobsen opened this issue Sep 2, 2013 · 1 comment
Closed

accessibility ( sr-only versus assistive-text class) #35

bassjobsen opened this issue Sep 2, 2013 · 1 comment
Labels

Comments

@bassjobsen
Copy link
Owner

The original framework defines the assistive-text class to make content visible for screen reader only. The class have been removed from the main css. Classes should by replaced by the sr-only from Twitter's Bootstrap (see: http://getbootstrap.com/getting-started/#accessibility )

@bassjobsen
Copy link
Owner Author

@67c3a2b32eca2d8013ce481abcc2f925590ca1a1 has the class name change for the post navigation. Note the surrounding heading also changed to h3.

We should pay attention for the logical structure of the header elements (<h1> ... <h6>). Screen readers use this semantic stucture to build a table of contents of your document. See also: Headings and Subheadings.

from: http://bassjobsen.weblogs.fm/twitters-bootstrap-3-rc2-important-changes/

bassjobsen added a commit that referenced this issue Oct 31, 2013
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant